RE: [Help-gnu-radius] Cron Job for rebooting the radius.

[Cline Communications, Corp.]

Radctl?  What's that?  Why not the Radiusd?

What normally is the full path to this radctl?

And out of curiosity, do you notice much different load time running your
every 5 minute cron?  We have quite a few crons on this server in specific
that run at midnight, which is originally what I was thinking of doing for
the radius, too, but the 5 minute deal sounds much better.  Doing it every 5
minutes, does that slow down the server at all?

Thanks!




-----Original Message-----
From: Sergey Poznyakoff [mailto:address@hidden
Sent: Wednesday, August 27, 2003 8:16 AM
To: address@hidden
Cc: Christian Schrader; address@hidden Org
Subject: Re: [Help-gnu-radius] Cron Job for rebooting the radius.


Cline Communications, Corp. <address@hidden> wrote:

> It does not necessarily die or hang on the fault of the radius software.
> Perhaps it's a problem on the server end, but for one reason or another
the
> server needs to be rebooted and restarting the radius software after
> rebooting is forgot about.

Well, anyway, let me note that I quite agree with Gerald: restarting it
seems to be a bad idea. If your radiusd coredumps or hangs or something
like that, let me know so I may fix the bug.

> Having a script that detects if it is running or
> not would be great as it would constantly check and if it's not running it
> would start it, right?!

The following command does the trick:

   radctl -s which >/dev/null || radctl restart

For example, adding this to your crontab:

*/5 * * * *   radctl -s which >/dev/null || radctl restart

will each 5 minutes check if the daemon is still running, and if not
will restart it. Notice, that you may need to supply the full path
to radctl.

Regards,
Sergey