Re: daemontools feature request: user signals

"Lester Vecsey" <[email protected]> wrote:
> How about starting with the svstat source and snipping out much of its code
> so that you're left with just the portion that retrieves the current 'pid'
> of the specified service. Then through command line options you can have
> this new utility send a kill signal, either usr1, or usr2.

That would be easier done (and more future-proof) as a shell script
calling svstat and parsing its output.  But either way, you lose the
guarantee you have with signals sent through svc/supervise: the signal
will be sent to the right process, no matter what.  If you don't go
through svc/supervise, the service might die just after you get its
pid, the pid might be reused, and you might send the signal to the
wrong process.  It would be better if svc/supervise supported SIGUSR1
and SIGUSR2 directly.


paul