On 9/15/06, David Salisbury <salisbury@xxxxxxxxx> wrote:
Hi Guys, Wondering if anyone knows of a fix here, though it's not critical but it is kind of annoying. Though I make no reference to a "ServerRoot"/logs directory in the configuration file, apparently Apache needs one to exist in order to run. ErrorLog, TransferLog, PidFile, etc.. all those I give complete path names to a directory outside of ServerRoot, yet for some reason, Apache will not start unless there's a /logs directory underneath the ServerRoot, even though nothing seems to be written there. If I remove the ServerRoot/logs directory, upon startup the ErrorLog ( written where I've told it to be ) records: "[emerg] (2)No such file or directory: Couldn't create accept lock (/usr/local/webapp/logs/accept.lock.28901)" If I take my ErrorLog directives and put them just into the VirtualHost blocks, then I get a different error sent to stdout, saying the serverroot/logs directory can not be found. This is reminiscent of a below bug report.. but that was for 1.3 and I'm running 2.2.2. http://issues.apache.org/bugzilla/show_bug.cgi?id=31086 I can leave the empty /log directory laying around I suppose.. put it's just not right. ;) Thanks for any information,
You missed LockFile: http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|