HUP handling: a thought
A.Cudbard-Bell at sussex.ac.uk
Sun May 6 20:17:12 CEST 2007
Peter Nixon wrote:
> On Sun 06 May 2007, Nicolas Baradakis wrote:
>> Alan DeKok wrote:
>>> Nicolas Baradakis wrote:
>>>> I like when the things are simple: edit the config files with your
>>>> favorite editor, and run a command to reload the server. (kill -HUP
>>>> or something else)
>>> It's nice, but can result in ~1s hiccups when everything gets
>>> reloaded. [...]
>> Indeed. At some point we need to make a tradeoff between a solution
>> that is simple for the administrator but not very efficient, and
>> a complex configuration mechanism that allow extensive control on
>> a running server. (personally I tend to prefer the former solution)
> I also tend to agree with you here. At the end the whole premise for high
> level languages like java, python, ruby etc is that while its a bit less
> efficient in terms of CPU time, the most valuable resource is infact the
> human one, and its worth wasting some CPU time to make the developer or
> admin's job easier...
Yes, and putting the configuration for freeradius in a SQL database
opens the door for other languages like ruby. You can automate the
configuration process a great deal, when you have a high level language
that can manipulate the SQL data.
So in the end it *will* make the admins job easier, so long as they
invest the time to start with.
Granted configuring freeradius via the SQL CLI, would be slow and
painfull, but you don't have to configure it via the SQL CLI !!
More information about the Freeradius-Devel