Comment 18 for bug 407862

Yes. I think the reload needs to stay as a hard restart until upstream
refactors the code to separate the privileged and non-privileged code
base slightly more effectively.

How would the third party app know that the syslog server that is
running is rsyslog rather than syslog-ng or sysklogd? Don't they all
use different pidfile, init script names and process identifiers? Is
anything tied that closely to rsyslog?

Anything that does depend upon HUPing rsyslog should depend upon it or
its virtual package shouldn't it? Or at the very least
suggest/recommend it.

2009/8/17 Michael Terry <email address hidden>:
> I meant 'wont fix' in the sense of after we fix bs=1 and we set the init
> script to always use hard restarts.  Then, we just say 'wont fix' to
> users of manual HUPs.  Is there a use case for manual HUPs vs init
> script restarts?  (serious question, are there 3rd party apps that
> depend on being able to HUP rsyslog for example?)
>
> As for disabling lightweight restarts via HUPs, I guess that's the same
> question -- if we just ignore HUPs, will we break anything?
>
> --
> [karmic] Messages not being sent to system logs
> https://bugs.launchpad.net/bugs/407862
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Neil Wilson