On Thu, Apr 12, 2012 at 04:45:56PM +0200, Jan Weiher wrote: > Am 12.04.2012 16:32, schrieb Matthew Newton: > > I'll dig a bit more, but the easy solution is to change the > > logrotate script to restart, rather than reload/HUP. > > > > Yes, that would be a solution for me as well, because when logrotate > runs, the freeradius server is basically idle, but I dont think this is > a solution for somebody who needs the server 24/7.
Although a reload takes 0.02 seconds, a restart still only takes 0.3 seconds, which is so quick our NASes wouldn't even notice. I wouldn't worry about it. I've found out why only one of our servers is affected - the other two have an old init script that don't implement reload, which means logrotate hasn't actually been restarting the daemon... :) So that seems to indicate it's the HUP that causes the problem. Matthew -- Matthew Newton, Ph.D. <m...@le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ith...@le.ac.uk> - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html