Commit report for v3.1.x branch - logrotate

Arran Cudbard-Bell a.cudbardb at
Fri Sep 18 10:55:03 CEST 2015

> On 18 Sep 2015, at 01:15, Alan DeKok <aland at> wrote:
> On Sep 17, 2015, at 7:44 PM, Matthew Newton <mcn4 at> wrote:
>> You're right. It should use -USR1 to reload the config, and -HUP
>> for reopening the log files ;-P
>  Nginx does:
> -s signal Send a signal to the master process. The signal can be one of: stop, quit, reopen, reload. The following table shows the corresponding system signals.
> 	• stop SIGTERM
> 	• quit SIGQUIT
> 	• reopen SIGUSR1
> 	• reload SIGHUP
>  That makes sense.  And it's a bit more portable than "killall" or "kill".

I'm fine with sacrificing the talloc memory dump stuff associated with SIGUSR1, especially since there's a command now.

Also we need to remove the signal handler on SIGUSR2 as it interferes with valgrind.


Arran Cudbard-Bell <a.cudbardb at>
FreeRADIUS development team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 872 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <>

More information about the Freeradius-Devel mailing list