>> system("killall -9 radiusd");
>
>if you do this ? when is the radiusd going to start again ?
Yes, if you're using Merit Radius. Merit runs from inetd.conf, and forks
over radiusd processes when the portmaster requests authentication for a
user. Also, when Merit Radius starts a radiusd process, it reads the users
file into memory (I guess for speedier responses). If you do not kill it
after adding a user, the user will not be valid as the old users file will
still be in memory. After you've killed it off, when the next
authentication request comes, the new users file will be loaded into
memory, and your new user will be authenticated.
If you're using Livingston radius (and I may be wrong, I stopped using it a
while ago), it reads the users file directly off the hard drive, not from
memory. So take this line out of the code. I used to start the old
Livingston radiusd in /etc/rc.local - so yes, if you kill it, it will not
start back up.
Rick