[Babel-users] SIGHUP shouldn't kill babeld

[Charles N Wyble]

+1 for this patch.  

"Antoine Beaupré" <anarcat at orangeseeds.org> wrote:
>Hello!
>
>After noticing a 80MB babeld logfile on my router, I figured I would
>implement log rotation for it. Unfortunately, it turns out that babeld
>exits when it receives SIGHUP, the default signal delivered by log
>rotation software (at least newsyslog in FreeBSD and logrotate in
>Debian).
>
>It is a very old tradition in UNIX daemons to use the SIGHUP signal for
>exactly that reason: reload your config files and reopen your logs!
>
>This seems to be what SIGUSR2 is doing to babel, and while I can adapt
>my configuration to do that, it seems more appropriate for Babel to
>follow usual standards.
>
>here's a patch.
>
>
>
>------------------------------------------------------------------------
>
>
>A.
>
>PS: Ideally, there would also be a routine to reload the configuration,
>but I couldn't find any, so this is not yet implemented.
>
>-- 
>A ballot is like a bullet. You don't throw your ballots until you see
>a target, and if that target is not within your reach, keep your
>ballot in your pocket.
>                         - Malcom X
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Babel-users mailing list
>Babel-users at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20130923/ddd06c10/attachment.html>