RE: hupping freeradius
> From: Simon Allard > Sent: Thursday, 28 August 2003 7:21 AM > > On reflection, that seems a better idea. If (when) you find it works > > better, I'll change the Debian initscript to do that instead. > Hupping the pidfile by using "start-stop-daemon --stop --signal 1 --quiet > --pidfile $pidfile" instead of killall -HUP works alot better. > When my servers were doign killall -HUP's I would get to work and find > them using 200meg of ram and more threads than actually required. > Hupping the pidfile worked the way it should work :D > I have changed all my production servers over to this method and they are > a lot happier. I've committed the change to CVS. It'll be in 0.9.1. Thankyou. :-) When I get the chance, I'll have a look to see _why_ the child threads didn't handle SIGHUP properly, and if it can be fixed. That may _not_ be in 0.9.1 though. -- = 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
RE: hupping freeradius
> 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. Hupping the pidfile by using "start-stop-daemon --stop --signal 1 --quiet --pidfile $pidfile" instead of killall -HUP works alot better. When my servers were doign killall -HUP's I would get to work and find them using 200meg of ram and more threads than actually required. Hupping the pidfile worked the way it should work :D I have changed all my production servers over to this method and they are a lot happier. - Simon Simon Allard (Senior Tool Monkey) IHUG Ph (09) 358-5067 Email: [EMAIL PROTECTED] I'm out of my mind right now, but feel free to leave a message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: hupping freeradius
> You say that I don't need to HUP the server to re-read the userfiles? Care > to go into more detail? > > ATM I am only hupping the server to re-read the usersfile as I was under > the assumption that it loaded it into memory. RTFM Simon :D fastusers is exactly what I am after. Thanks :D. I will still look into that hup thing though for you as I will need to hup the server when the huntgroup file changes, Simon Allard (Senior Tool Monkey) IHUG Ph (09) 358-5067 Email: [EMAIL PROTECTED] I'm out of my mind right now, but feel free to leave a message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: hupping freeradius
> 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 You say that I don't need to HUP the server to re-read the userfiles? Care to go into more detail? ATM I am only hupping the server to re-read the usersfile as I was under the assumption that it loaded it into memory. Simon Allard (Senior Tool Monkey) IHUG Ph (09) 358-5067 Email: [EMAIL PROTECTED] I'm out of my mind right now, but feel free to leave a message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
RE: hupping freeradius
> 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
hupping freeradius
Hi guys. I have just upgraded to 0.9.0. It's running really well. Big thanks goes to all the people involved. 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? 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. Thanks :) Simon Allard (Senior Tool Monkey) IHUG Ph (09) 358-5067 Email: [EMAIL PROTECTED] I'm out of my mind right now, but feel free to leave a message. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
