On Sun, 30 Jan 2005 22:35:47 -0500
Stephen Gran [EMAIL PROTECTED] wrote:
The debian init script has been sending the kill signal to the whole
process group for some time, and now it checks if the pid is negative
first. If htere is a problem with the package supplied init script, let
me know,
On Mon, 31 Jan 2005 at 22:50:29 +0800, imacat wrote:
Than you for your hint, though I cannot access
http://people.debian.org/~sgran/debian now. (people.debian.org and
packages.debian.org are down?)
Yes.
http://lists.debian.org/debian-devel-announce/2005/01/msg00013.html
Though the
On Mon, Jan 31, 2005 at 10:50:29PM +0800, imacat said:
On Sun, 30 Jan 2005 22:35:47 -0500 Stephen Gran [EMAIL PROTECTED]
wrote:
The debian init script has been sending the kill signal to the whole
process group for some time, and now it checks if the pid is
negative first. If htere is a
On Mon, 31 Jan 2005 17:41:43 -0500
Stephen Gran [EMAIL PROTECTED] wrote:
The problem is that when you kill `cat $pidfile`, you don't end up
signalling the thread that is listening for signal events, and it has to
be communicated over to that thread by the thread that wrote the pid
file. This
On Sun, 30 Jan 2005 16:01:32 -0600
Ren?Berber [EMAIL PROTECTED] wrote:
imacat wrote:
It's an option (*not* available in all Unixes or Unix like environments)
to send the signal to all threads in the process group.
Thank you. I somehow got it now. The manpage on my Debian machine
does
On Mon, Jan 31, 2005 at 10:14:29AM +0800, imacat said:
This negative PID won't work for
kvm_getprocs().
What is suggested here? Stop using the PID file now? Stop using
start-stop-daemon? Modify the source, recompile and make my own copy of
start-stop-daemon so that it send a positive
