Global 'kill' was fixed, thanx. But:
1. When I'm running with -x (process does not fork to background)
and send TERM to main process, modules are cleaned-up, I see
STATS: Total Threads: 3, Active Threads: 0
STATS: Total number of requests handled so far: 0
STATS: Per thread statistics:
STATS: Thread Num: 1, Requests Handled: 0
STATS: Thread Num: 2, Requests Handled: 0
STATS: Thread Num: 3, Requests Handled: 0
start_servers times, main process does not exit and on ps
I see main process with one <defunc> child.
2. When running in background (without any options), after TERM
modules are NOT cleaned-up (but main process and its child are
all terminated).
I'm not very familiar with thread programming...but I thing that
something wrong neither in my thread library (libpthread-0.7) or
in thread usage within freeradius. Or in its termination logic.
> "Paul Hampson" <[EMAIL PROTECTED]> wrote:
>> I seem to be having the opposite problem to everyone else
>> on the list... My radiusd seems to work fine (just setting
>> it up) but when I kill it (either with the debian init.d
>> script supplied or 'kill') it kills every other thread it
>> can get it's hands on. All my gettys, my sshd. Only init
>> and the various kernel threads survive. Actually, bash
>> survives too... I dunno how that works. :-)
> Yeah, sorry.... more dumb typos on my part. I'll fix it today or
> tomorrow.
> Alan DeKok.
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
