The start-stop-daemon manpage lists '--retry' as option 'only used for stopping daemons'. It's quite unclear what 'stopping daemons' means in that context but it seems to work well with '--signal' as well. I'd appreciate if we allowed it being used that way as well.
Uhm, I can't follow you..
--retry is only used in combination with the --stop command, it can be either a timeout value or signal/timeout combined (like SIGTERM/5).
--signal is only used for the kill signal.
start-stop-daemon -S, --start daemon [--] [arguments]
start-stop-daemon -K, --stop daemon
start-stop-daemon -s, --signal signal daemon
I think I meant the third syntax.
@idl0r | mgorny: re bug 382345 - please give me an example or so. i still don't get it :P
@mgorny | idl0r: eh, if I did remember what I was doing at that time
@mgorny | but I think it was very hacky
@mgorny | maybe I wanted to send two signals at once, or a single signal with a delay
@mgorny | (something like --signal 0 --retry 30/SIGTER<)
@mgorny | but the bug was just about 'is it legit to use something like --signal HUP --retry 15/TERM?'
I think what you want is something like
The --signal option is not part of stopping a daemon.
Does that give you what yu are looking for?
(In reply to comment #4)
> I think what you want is something like
> --retry 0/HUP,15/TERM
> The --signal option is not part of stopping a daemon.
> Does that give you what yu are looking for?
Were. Right now, I don't use OpenRC anymore and I have no idea what I needed that for :P.
In that case, would you have any issues with us closing this bug as
After speaking with mgorny on irc, this bug appears to just be a
documentation issue. We need todocument that --retry can work with