Re: checking radiusd with cron
"Thomas S. Crum - AAA Web Solution, Inc." <[EMAIL PROTECTED]> wrote: > I've noticed that when radius dies, it usually kills all of its processes > with it. Yes. That makes sense, the way the server is written. > I wrote a cron that every minute just runs /usr/local/sbin/radiusd, if > radiusd is running it will fail because it cannot bind the port. If not, it > will start radiusd. Why not just use daemontools? See the 'doc' directory. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: checking radiusd with cron
On Tue, Mar 11, 2003 at 09:24:02AM -0500, Thomas S. Crum - AAA Web Solution, Inc. wrote: > This may seem like an oversimplified approach, but can someone please > comment. > > I've noticed that when radius dies, it usually kills all of its processes > with it. Some have written a cron that checks first and then restarts etc. > > I wrote a cron that every minute just runs /usr/local/sbin/radiusd, if > radiusd is running it will fail because it cannot bind the port. If not, it > will start radiusd. Try reading doc/supervise-radiusd.txt . -- Simon - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: checking radiusd with cron
why not use radwatch? rc.radiusd supplied with the server already starts radiusd with radwatch. otherwise, the only problem about your approach is the active waiting. Thomas S. Crum - AAA Web Solution, Inc. wrote: This may seem like an oversimplified approach, but can someone please comment. I've noticed that when radius dies, it usually kills all of its processes with it. Some have written a cron that checks first and then restarts etc. I wrote a cron that every minute just runs /usr/local/sbin/radiusd, if radiusd is running it will fail because it cannot bind the port. If not, it will start radiusd. This server will be used in a production environment to auth approx 1000 users. Does this seem reasonable? -- Artur Hecker Département Informatique et Réseaux, ENST Paris http://www.infres.enst.fr/~hecker - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
checking radiusd with cron
This may seem like an oversimplified approach, but can someone please comment. I've noticed that when radius dies, it usually kills all of its processes with it. Some have written a cron that checks first and then restarts etc. I wrote a cron that every minute just runs /usr/local/sbin/radiusd, if radiusd is running it will fail because it cannot bind the port. If not, it will start radiusd. This server will be used in a production environment to auth approx 1000 users. Does this seem reasonable? Thank you in andvance for any comments. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
