That must be exactly what happens, as the new log file started at almost
exactly the same time. I'm going to have to look to see what I can do to
avoid the situation. Ideally, we'd be able to tell Apache to just not *load*
the VirtualHost zone if it can't be resolved, instead of dying completely.
There's probably such a setting somewhere, I'm going to go dig for it.
Thanks a lot,
> > I've got a couple of Apache servers set up with JServ hosting servlet
> > On Friday I had to pull a couple of the hosted sites, but I didn't have
> > to edit the conf file, so I just pulled them from DNS to remove access
> > the sites.
> > At some point this morning, the systems went down because Apache
> > the httpd.conf file and refused to run because it couldn't resolve a
> > of the VirtualHosts directives.
> > Is Apache supposed to reload the file periodically? If so, is there some
> > control over it? I'd like to turn it off, if possible, or at least know
> > the interval is that it waits to reload....
> > thanks,
> > fnord
> On my system, to support log-rotation, a process called "newsyslog" is run
> periodically which checks the size of the log files. When certain
> conditions are met, it rotates the logs, and issues a HUP signal to the
> apache process. (This makes Apache close the current filehandles and
> start a new one) A side effect of this could be that upon the HUP, it
> re-loads the config file.