Peter Nixon wrote:
The system should do _something_ when it receives -HUP (other than crash). It this turns out to be a full restart, then so be it...
So there's a requirement to handle HUP. I don't see why. How about a requirement to dynamically update the running configuration? That could be done via re-exec on HUP, or by the crazy SQL scheme I talked about. I don't understand the fixation on HUP. I don't like SQL, but if I can use an SQL client to edit *every* configuration parameter in a running server, I don't see why HUP would *ever* be necessary. Recent versions of OpenLDAP support an "dn=config", or something like that. It means any configuration parameter can be dynamically changed, meaning you *never* have to HUP the server. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog