> The list of changes from 0.2 is long. There are a number of bug
> fixes, feature enhancements, and other corrections. It's been two
> months since 0.2 was released. I think it's time for 0.3
> Are there any critical fixes which MUST go in before 0.3 is
> released? If not, I think I'll tag it, and release it on Monday.
2 minutes ago is found out problem.
I use Exec-Program to process Acct-Start/Acct-Stop packets comming
from RAS to freeradius. IMHO it better and more easy then to parse detail.
On the other hand I have to restart my freeradius to prevent unworking
state with "Error: Dropping conflicting authentication packet from client"
messages.
I just make every hour:
kill `cat /var/run/radiusd.pid`
i.e. send SIGTERM signal
So at moment of executing external script with Exec-Program
it is possible execution "kill `cat /var/run/radiusd.pid`".
in radiusd.c we have
signal(SIGTERM, sig_fatal);
in
static void sig_fatal(int sig)
....
/*
* Kill all of the processes in the current
* process group.
*/
kill(0, SIGKILL);
All children is killing with SIGKILL signal!!!
So my script dies :(. I lost data which were processed in script.
May be better to kill children with same signal as freeradius was
signaled.
It normally not to kill server too often. but killing all children
with not traped signal - not right.
Sincerely,
Michael Chernyakhovsky.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
