> From: Simon Allard
> Sent: Tuesday, 26 August 2003 12:56 PM
> I have noticed that sending the HUP signal works now!. I changed my
> scripts to HUP the server every 20 minutes or so, so it can read the new
> userfiles. (I was loosing a lot of accounting packets when I did a restart
> so HUP works much better).
>
> The init script in the debian dir does a killall -HUP freeradius. When I
> do this 2 more threads appear for no reason and memory sky rockets after a
> while. After 1 day I am using 200meg or so. I onkly use 30meg when
> freeradius first starts.
>
> Firstly, is HUP something I should be using yet? Is anyone else seeing
> this problem?
Funny you asked this, I just asked the same question on the devel list,
and the answer is that HUP should be useable.
However,
"The only reason to HUP the server is to read changed *.conf files. If
you use the 'fastusers' module ( recommended as it is faster as the name
implies ) or sql, you won't need to HUP the server to read changes
in the 'users' file, either." -- Chris Parker
I guess this applies in your case though. :-)
> I am going to have a play around with just hupping the pid that ends up in
> /var/run/freeradius/radiusd.pid and see if that makes a difference.
On reflection, that seems a better idea. If (when) you find it works
better, I'll change the Debian initscript to do that instead.
--
=========================================================
Paul "TBBle" Hampson
Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]
This is a one line proof...if we start
sufficiently far to the left.
-- Cambridge University Math Department
---------------------------------------------------------
Random signature generator 3.0 by Paul "TBBle" Hampson
=========================================================
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
