On Wed, Feb 25, 2004 at 01:35:20AM -0300, Henrique de Moraes Holschuh <firstname.lastname@example.org> wrote:
> > You could try running the control program a few times, checking between each
> > invokation to see if the daemon is really dead. After a while, you can then
> > use start-stop-daemon to kill it manually.
> And you can use ssd --start --test to check if the daemon is really dead,
Thanks for both of you for the answers. I think I misunderstood the
purpose of --stop and --retry. I thought it does the looping for me, and
I would reinvent the wheel if I do the looping for myself. Matt, I know
--signal, but SIGTERM is quite OK, I just don't need it immediately
delivered. See the timeframe:
- control program is called with the 'stop' argument,
- loop for for example five seconds, and every second check if the
daemon really exited. If yes, then return.
- if the loop expired, but daemon is still running, _only then_ deliver
Instead I get the signal delivered as soon I invoke ssd, at least it
seems as the daemon does not even reach the first line for printing