On Fri, 2005-01-21 at 08:00 +, Neil Craig wrote:
> Could use cron to HUP server every so often
>
> >>> [EMAIL PROTECTED] 21/01/2005 00:05:09 >>>
> Just floating an idea...
>
> Is it worth considering adding a "periodic" section to radiusd.conf
> and
> the radius server? Rather than retrofitti
"Neil Craig" <[EMAIL PROTECTED]> wrote:
> Is it worth considering adding a "periodic" section to radiusd.conf
> and the radius server? Rather than retrofitting reload this, reload
> that, functionality into existing functions that are called during
> the processing of a request, modules could imple
When you're using EAP, it's not always that simple. HUPping a server or
taking it offline is something you'd rather avoid if possible as it
becomes noticible to the end users when you do it. We do indeed have
redundant servers. If one fails, then yes, the other picks up the load,
but it's no
Why doesn't everyone just setup redundant radius servers so you can afford
to HUP a server or even take one offline for a bit? It seems that would
be best practice anyway. Freeradius is very stable from my experiences,
but I can't say the same for some of the hard drives I've had in our
machines.
Could use cron to HUP server every so often
>>> [EMAIL PROTECTED] 21/01/2005 00:05:09 >>>
Just floating an idea...
Is it worth considering adding a "periodic" section to radiusd.conf
and
the radius server? Rather than retrofitting reload this, reload that,
functionality into existing functions th
Just floating an idea...
Is it worth considering adding a "periodic" section to radiusd.conf and
the radius server? Rather than retrofitting reload this, reload that,
functionality into existing functions that are called during the
processing of a request, modules could implement a "periodic funct
Michael Griego <[EMAIL PROTECTED]> wrote:
> That's actually not completely true in our case. In our case, where
> we're actively deploying wireless APs, we can bring up several new NASes
> each day.
Adding new NASes without re-starting the server is a good idea.
I've had it as a low-priority
Kostas Kalevras wrote:
> In any case, client updates are really rare actions. I think a HUP (in
> one form or another) can be enough, especially taking into account the
> extra work required to get any other way working right.
That's actually not completely true in our case. In our case, where
we
On Thu, 20 Jan 2005, Mark Elkins wrote:
On Wed, 2005-01-19 at 23:05 +0200, Kostas Kalevras wrote:
On Wed, 19 Jan 2005, Alan DeKok wrote:
"Neil Craig" <[EMAIL PROTECTED]> wrote:
Is it possible to add a NAS to SQL and have Freeradius recognise and
use it without restarting radius? The only way I can
On Wed, 2005-01-19 at 23:05 +0200, Kostas Kalevras wrote:
> On Wed, 19 Jan 2005, Alan DeKok wrote:
>
> > "Neil Craig" <[EMAIL PROTECTED]> wrote:
> >> Is it possible to add a NAS to SQL and have Freeradius recognise and
> >> use it without restarting radius? The only way I can get this to work is
>
On Wed, 19 Jan 2005, Alan DeKok wrote:
"Neil Craig" <[EMAIL PROTECTED]> wrote:
Is it possible to add a NAS to SQL and have Freeradius recognise and
use it without restarting radius? The only way I can get this to work is
by adding in the entry and restarting, otherwise it thinks it's an
invalid NAS
"Neil Craig" <[EMAIL PROTECTED]> wrote:
> Is it possible to add a NAS to SQL and have Freeradius recognise and
> use it without restarting radius? The only way I can get this to work is
> by adding in the entry and restarting, otherwise it thinks it's an
> invalid NAS
You can HUP the server.
Hi
Is it possible to add a NAS to SQL and have Freeradius recognise and
use it without restarting radius? The only way I can get this to work is
by adding in the entry and restarting, otherwise it thinks it's an
invalid NAS
Thanks in advance
Neil
-
List info/subscribe/unsubscribe? See http://ww
13 matches
Mail list logo
