I updated all the server to freebsd 4.10 with the latest patch release,
rebuilt world and kernel and I am still having the same issue when I
attempt to restart or HUP the radiusd process.  It seems to be looping as
Alan said.  I did do the gdb and when it I issue the radiusd.sh restart
command, it prints this to the screen and stops.

Program received signal SIGTERM, Terminated.
0x10250654 in __sys_poll () from /usr/lib/libc_r.so.4

I'm not sure how helpful that will be to anyone but it's all the
information it showed.

Let me know if this rings any bells.

Joe H.



On Wed, 19 Jan 2005, Alan DeKok wrote:

> Joe H <[EMAIL PROTECTED]> wrote:
> > With my situation, doing the restart of the process causes radius to stop
> > working and the radius process climbs to about 90% CPU usage.
>
>   It sounds like it's in a busy loop.
>
>   My suggestion is to use gdb to attach to the running process, and
> see where in the source it's busy-looping.
>
>   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

Reply via email to