www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan vandenBerg <vinc...@pha.jhu.edu>
Subject config/965: Please include important config updates in conf/*-dist files.
Date Mon, 04 Aug 1997 17:40:01 GMT

>Number:         965
>Category:       config
>Synopsis:       Please include important config updates in conf/*-dist files.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Mon Aug  4 10:40:00 1997
>Originator:     vincent@pha.jhu.edu
>Release:        1.2.1
solaris 2.5.1, SunPro C
uname -a:
SunOS eta 5.5.1 Generic_103640-03 sun4m sparc SUNW,SPARCstation-20
This is just a semi-trivial suggestion. When I tried upgrading from
1.2.0 to 1.2.1, I ran into the already-documented problem with the change
in the default lockfile location (PR#'s 835 and 936). I've already solved
my problem by adding the LockFile directive to my httpd.conf file. Previously,
I didn't even know about the lockfiles since the old default location,
/usr/tmp/htlock, worked fine on my systems.

We've been religiously keeping our apache server current, so I've probably
built six or seven different versions of apache in the last year. My stantard
procedure is to diff the conf/*-dist config files with those of the previous
version to see if there are any new changes that I need to incorporate in
my config files. My suggestion is that you update the *-dist config files
even when you add minor config changes like changing the default lockfile

Thanks a lot.



View raw message