On Fri, 21 Feb 2003, Adam Fladwood wrote: > When using checkrad w/ a PM3 if the public snmp string is not set to > 'public' in the portmaster checkrad will timeout, not that big of an > issue - however, it causes the entire radius daemon to crash, saying it > couldn't process signal 15, and shutdowns all the child processes as well > as the master.
For what it's worth, I've also noticed that the entire radiusd also seems to die if you set the nastype incorrectly as "livingston" when it's actually a "cisco." Haven't really looked into it, since setting the appropriate nastype value works around this. It seemed odd that checkrad would crash the whole server... Also, I did have to go into checkrad and manually change my community string from public to what we're using. I ended up setting it as $community_string or something towards the top of the script, and then replacing "public" with $community_string. I'd submit a patch, but I wasn't sure how to prompt for the community string in the configure stuff. (Maybe --with-community-string='blahblah'? as a configure option?) K. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
