Re: SIGHUP signal to RADIUS processes

Captain Scarlet (gryphon@server.livingston.com)
Thu, 27 Mar 1997 10:27:47 -0800 (PST)

> Keith K Chau <keithc@unitech.com.hk> wrote:
>
> > 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?
>
> In my opinion this problem is caused by a bug in Radius 2.0

These messages happen when a radiusd child process, spawned off to
handle a service request, doesn't die of its own accord (as it should)
after completing its mission. The parent process goes round every now
and then and reaps any child processes that don't do this. The
messages are most commonly seen on RADIUS servers which are busy
computers - the child processes don't get enough CPU time to die on
their own before the parent gets around to reaping them.

--G.

-- 
'Twas brillig, and the slithy toves  |  Benjamin D. Hutchins, texaport minion
Did gyre and gimble in the wabe:     |  Livingston Enterprises, Inc.
All mimsy were the borogoves,        |  BellNet 800-458-9966 FAX 510-426-8951
And the mome raths outgrabe.   -><-  |  http://www.livingston.com/      S.I.G.