Steve Langasek writes ("Re: Bug#732124: "initctl reload" behaviour should be
configurable in job file"):
> On Sat, Dec 14, 2013 at 12:49:01PM +0000, Ian Jackson wrote:
> > Package: upstart
> > Version: 1.20-1
> > Severity: wishlist
>
> (Where does this version number come from? Is this just a transposition
> error of 1.10-2, the current version in tetisting/unstable?)
Yes. Oh bum. Shall I fix all of the reports I submitted today ?
> As of version 1.10, upstart does support a 'reload signal' directive to
> specify a signal other than SIGHUP. It seems the initctl(8) manpage has not
> been updated yet to match.
Aha.
> Do you consider fixing the manpage to be a sufficient solution for this bug,
> or do you think that support for arbitrary reload commands is needed? For
> my part I don't think that there's a need for abstract 'reload's when one
> can do a 'restart' instead.
I haven't done a survey but I imagine there are daemons out there
which don't like being randomly HUPped. Of course they could be
fixed, but asking them to handle a signal is rather unfriendly.
So I think the best answer would be to provide a command-based
override. But it's hardly a high priority and if you feel like
closing this bug on the basis that it's a wishlist item you're not
going to get round to, I won't mind.
Thanks,
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
