Re: SIGHUP signal to RADIUS processes

Brian Moore (bem@cmc.net)
Thu, 20 Mar 1997 21:02:41 -0800 (PST)

Hrrrm... haven't played with 2.0 yet (too damned many other things going
on and 1.16 is stable as a rock, so why mess with it :)), but 1.16 has
that problem if running multi-processed on Solaris.

To fix it, use the -s flag to single 'thread' it. (Not 'real' threads, hence
the quotes :)). If I bothered to look, it's probably the difference between
SysV signals on child death and BSD signals, but it works with -s so why mess
with it. :)

On Fri, 21 Mar 1997, Keith K Chau wrote:

> Hi all,
>
> We have a customer who runs a PM-25 and RADIUS 2.0 (on Solaris).
> Recently, he gets many repeating error messages all over his console
> screen, which resembles the following:
>
> "Mar 20 11:15:39 hn radius [22313]:Sending SIGHUP signal to
> unresponsive child process 22328."
>
> Anyone knows what the possible cause is?
>
> Thank you.
>
> Keith
>