Hi,
>In the meantime, I managed to make a new mess. I accidentally ran >radiusd without the -X option and couldn't figure out how to >"properly" stop it so I just killed the process. Now when I run >radiusd -X, it claims to be listening on 1812 and 1813, but nmap says >it isn't and I can't get a telnet connection off either port. My >firewall config hasn't changed, but just for good measure I turned >iptables off completely and still get the same results... Anyone seen >this particular mistake before? Nmap? Why scan ports when you can simply eg 'netstat -an | grep 1812' Anyway, 'killall radiusd' should do the trick nicely (well, nastily actually) - or any other variants of process management - people may prefer The pidof method etc. Than you can restart the daemon Alan No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.707 / Virus Database: 270.14.73/2513 - Release Date: 11/19/09 07:51:00 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
