Date: Sat, 12 Jul 1997 16:14:31 -0600 (MDT) From: Marc Slemko <marcs@znep.com> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: ivaudrey@test.nemko.ltd.uk, markm@FreeBSD.ORG, FreeBSD-Ports@FreeBSD.ORG Subject: Re: Apache 1.2.1 port will not start up Message-ID: <Pine.BSF.3.95.970712160833.17160C-100000@alive.znep.com> In-Reply-To: <199707122133.OAA09690@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
As of 1.2.1, Apache defaults to useing flock() locking to serialize
accept() calls in multiple children on FreeBSD. The lockfile defaults to
being named logs/accept.lock.
The FreeBSD port uses a different directory structure that doesn't have a
logs subdirectory under server_root. Apache should print the name of the
file it can't open; it does so for fcntl() locking, but it was accidently
ommitted for flock() locking. That is fixed in the CVS repository.
Printing the filename makes the problem and the fix more obvious. We are
thinking about a better location, based on feedback from situations like
this. Unfortunately, there is no "logs" directory we can use. Speaking
generically for all platforms, /var/run is no good, /var/tmp is no good,
/usr/tmp is no good, /tmp may be ok, server_root may be ok.
The FreeBSD port should probably define DEFAULT_LOCKFILE in the FreeBSD
section of conf.h; since it uses a different directory structure, it
should completely use that. Using the LockFile directive is a workaround,
but on any given platform with any given install it shouldn't be necessary
unless you change the directory structure.
--
Marc Slemko | Apache team member
marcs@znep.com | marc@apache.org
On Sat, 12 Jul 1997, Satoshi Asami wrote:
> * open: No such file or directory
> * Cannot open lock file
> *
> * I've been following the Apache ports since the early 1.2 betas, and this
> * is the first time I've had a problem. Is it the port or (much more
> * likely) me that is broken?
>
> I saw the same problem. After some looking around in the source, I
> created a directory "/usr/local/etc/apache/logs" and apache now starts
> fine.
>
> The name of this directory (nor any of the strings "logs" "lock",
> upper-case or not) doesn't appear in any of the config files in
> /usr/local/etc/apache, I'm not sure what to make of it.
>
> Satoshi
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970712160833.17160C-100000>