On Thu, Nov 11, 2010 at 02:16:57PM +0100, Alan T DeKok wrote:
> Josip Rodin wrote:
> > OK, so I tried it, and it actually doesn't work for me. I HUP'ed my FR
> > server process running since Oct 16, that logrotate had previously rotated
> > out and cleared out. After the HUP, the /var/log/freeradius/radius.log file
> > is still zero-sized, while the files used by linelog continue to fill up
> > normally.
> >
> > Are we sure we are all still talking about the same problem here? :)
>
> $ ./src/main/radiusd -sfd ./raddb/ -l ./foo
>
> In another window:
>
> $ more foo
> ...
> Thu Nov 11 14:14:01 2010 : Info: Ready to process requests.
>
> $ rm foo
> $ killall -HUP radiusd
> $ more foo
> Thu Nov 11 14:14:33 2010 : Info: HUP - loading modules
> ...
>
>
> It works for me. Are you sure that the logs are going to
> "radius.log", and not somewhere else? See also "lsof", to find out
> which files the server has open. It *should* have a long-lived handle
> to the log file.
Ah, no, here we go. I had stopped and started it again, and then it was able
to tell me:
Thu Nov 11 15:10:24 2010 : Info: Received HUP signal.
Thu Nov 11 15:10:24 2010 : Info: HUP - Re-reading configuration files
Thu Nov 11 15:10:24 2010 : Error: Unable to open file
"/etc/freeradius/radiusd.conf": Permission denied
Thu Nov 11 15:10:24 2010 : Error: Failed to re-read /etc/freeradius/radiusd.conf
How's that?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
