Thank you for your reply, Mr.DeKok. > Use 1.1.6. It has a NUMBER of bugs fixed over 1.1.0.
ok, I will consider it. but 1.1.6 crash when it recieve SIGHUP ... Hmmm... I think that "stopping responding" in our site is similar following reports. 2007-February/060174.html 2006-March/051900.html Are these problem resolved ? Is not "Port OpenSSL locking fixes from CVS head" (in ChangeLog for 1.1.5) related ? --- Alan DeKok <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > We using freeradius 1.1.0 for PEAP authentication, > > and it is working well almost. > > Use 1.1.6. It has a NUMBER of bugs fixed over 1.1.0. > ... > > (gdb) attach 10127 > > Attaching to program: /usr/dot1x/sbin/radiusd, process 10127 > > Symbols already loaded for /lib/libcrypt.so.1 > > ....(snip)... > > 0x401998cc in pthread_mutex_trylock () from /lib/libpthread.so.0 > > (gdb) whrere > > #0 0x401998cc in pthread_mutex_trylock () from > /lib/libpthread.so.0 > > If the code is blocking in the libc malloc() implementation, there > isn't much that FreeRADIUS can do to fix that. > > Try upgrading to 1.1.6, and see if that fixes it. I don't know... > > Alan DeKok. > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > -------------------------------------- Start Yahoo! Auction now! Check out the cool campaign http://pr.mail.yahoo.co.jp/auction/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html