Antwort: [RFC] Missing signal handling in ndo2db

[Hendrik Baecker]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sascha.Runschke at gfkl.com schrieb:
> In my opinion ndo is totally missing a proper handling of itself and
> its children. What you describe is just a designflaw in my eyes.
> 
What I've described was a missing signalling to the childs, can't
imagine how some system paths and files in there should help a program
to communicate with his childs...

> What ndo2db should have:
> 
> - a pidfile handling via /var/run
> - a subsys handling via /var/lock/subsys
> 
> So it makes it easier to identify ndo2db processes and handle them
> properly.
If I am right, this just helps out the init scripts to handle the
process state, even not the program itself.

- From a Redhat Site
(http://www.redhat.com/magazine/008jun05/departments/tips_tricks/):
"This file represents that a service's subsystem is locked, which means
the service should be running. Since a service may consist of multiple
executables with different names, finding the process ID (PID) of a
single executable may not be sufficient to determine the status of the
entire service itself."

> 
> If ndo is getting pushed again now, I'm more then happy to contribute
> my init script, which is much more sophisticated then the usual
> one. Put it to good use :) I'll attach it as file, so the indenting
> doesn't get broken.
> 
Thanks for this. I'll have a look at it.
> But - I wrote it for RedHat Enterprise Linux 5 and I am not sure
> how well it works on other distributions. I always wanted to take
> a look into that, but I'm currently under too much pressure at work
> here.
> 
I'm able to test on Debian and SuSE, guess we should get it to work.

Regards,
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkpLa6UACgkQlI0PwfxLQjmjTgCfdRbTxdVJKV+e4bcRW0hwlhrm
muUAn2xE/1e9kIsVVEmPwrE9vlHkuN6b
=zqQL
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------