Two issues I noticed while looking at the source for my problem: in threads.c I believe it would be safer to end the fork_mutex critical section after the forkers structure is updated (after line 1069), not before (1051).
Also it seems like if it ran out of slots it will return without unblocking SIG_CHLD (threads.c:1058). Not sure if this is intentional or not.
Neither of these affect my issue, unfortunately, so I'll keep looking.
-- L.C.
Alan DeKok wrote:
"L.C. (Laurentiu C. Badea)" <[EMAIL PROTECTED]> wrote:
With Red Hat 9 and the 2.4.20-8 kernel it does the same thing (same freeradius as before but rebuilt for RH 9 from the src.rpm). So it seems that a wider range of kernels is affected. Tried on a dual cpu machine with both smp and up kernels to make sure.
Do you have any pointers as to what this bug is, or what kernel versions contain the fix ?
Search the list archives. I don't recall much more than that.
I suppose outside of getting a "fixed" kernel, there really isn't another way to overcome this problem ?
Run the server in single-threading mode.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
