Kristina Pfaff-Harris <[EMAIL PROTECTED]> wrote: > The wierd thing is, checkrad DOES respond -- it just responds with a > timeout, and if that weren't strange enough, checkrad appears to be > exiting normally, that is, it's not hanging or anything.
Yeah, but if it doesn't respond within 10 seconds, the code in session.c gives up, and tries to kill checkrad. If checkrad takes 30 seconds to time out, then that's bad. > Heh. Any ideas on where to start looking to track down a long-term > solution? :-) Find out why the SIGTERM is getting delivered to radiusd, and not to checkrad. I think, though, that the calls to kill() in session.c should probably go away. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
