I think you have to create the initial log files yourself.  Apache will
look for the files and if they can't be found then it forgets about it.

On the other hand if it finds the log files specified then it will add to
them.

Chris

On Mon, 24 Aug 1998, Joshua E Hope wrote:

> 
> 
> Josh Hope
> "Yes, I use UNIX. Why are you laughing?!"
> -----------------------------------------
> root                 nefas       melkor
> root@unixgeek.ml.org @SuperChat  @ChatNet
> -----------------------------------------
>                    http://unixgeek.ml.org
> 
> 
> On Mon, 24 Aug 1998, Simon Raahauge DeSantis wrote:
> 
> > On Mon, 24 Aug 1998, Joshua E Hope wrote:
> > > > > On an aside, and unrelated note, Apache still is not functioning (won't
> > > > > work either as a normal daemon or when called via inetd)...no replies to
> > > > > my previous post on this topic :)
> > > > 
> > > > Well, "doesn't work" isn't enough for any of us mere mortals to debug
> > > > remotely...
> > > 
> > > Well, yes I am sorry. There isn't much else to add to this problem,
> > > however. When I run apache from inetd and attempt to access the site via
> > > lynx I get the error "Network read error". Whenever I run apache via the
> > > command line, it just doesn't work. It quits immediately after running it.
> > > It won't show up on a ps listing...for those that will suggest it, yes I
> > > set the type in httpd.conf to standalone when as a standalone, and inetd
> > > when as inetd...
> > > 
> > 
> > I don't suppose you've looked at the Apache error_log? 
> 
> Of course! It doesn't create an error log...or any log, to be percise.
> Yes, all the paths to the places to create log files are correct...it just
> doesn't make any logs at all. It does nothing as far as I can tell...
> 
> > -Simon Raahauge DeSantis
> > 
> > 
>