>From the fingers of Garry Glendown flowed the following:
>
>Matthew J. Probst wrote:
>> I think it could be completely stable if we ran a seperate httpd process
>> all together (with stripped out config files, and only one child process)
>> that is attached to some port of the machine other than 80 and is
>> dedicated to modifying the main server config files and re-huping the
>> daemon. The one httpd would have to run under root and only root though..
>
>Apache supports access to different ports from one server process ...
>so, technically, the same server could do both ...
Technically, yes, but I'd much rather have a separate admin server,
with its own config files and identity. Less likely to shoot your
foot off that way if you commit a change to the config that disables
the admin function.. not to mention the idea of telling the server
to HUP itself seems a bit problematical. Difficult to start that
way, too - not to mention stopping.
#ken :-)}
