[Babel-users] SIGHUP shouldn't kill babeld

[Antoine Beaupré]

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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-properly-reopen-logfiles-on-SIGHUP-instead-of-exitin.patch
Type: text/x-diff
Size: 668 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20130921/b9817530/attachment.patch>
-------------- next part --------------

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.

-- 
Il n'existe aucune limite sacr?e ou non ? l'action de l'homme dans
l'univers. Depuis nos origines nous avons le choix: ?tre aveugl? par
la v?rit? ou coudre nos paupi?res.
                        - [no one is innocent]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/babel-users/attachments/20130921/b9817530/attachment.sig>