Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 24865 invoked by uid 6000); 22 Dec 1997 21:09:52 -0000 Received: (qmail 24848 invoked from network); 22 Dec 1997 21:09:38 -0000 Received: from scanner.worldgate.com (198.161.84.3) by taz.hyperreal.org with SMTP; 22 Dec 1997 21:09:38 -0000 Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.7/8.8.7) with UUCP id OAA10274 for new-httpd@apache.org; Mon, 22 Dec 1997 14:09:37 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id OAA05571 for ; Mon, 22 Dec 1997 14:10:57 -0700 (MST) Date: Mon, 22 Dec 1997 14:10:57 -0700 (MST) From: Marc Slemko To: TLOSAP Subject: [PATCH] remove bogus LockFile warning from docs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org None of the issues with placement of the LockFile apply, so the below warning about the LockFile directive is not necessary. The only risk is that someone else could create a file with that name and prevent the server from starting; well, a lot of files unless they can guess the pid. Index: core.html =================================================================== RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v retrieving revision 1.87 diff -u -r1.87 core.html --- core.html 1997/12/14 01:04:56 1.87 +++ core.html 1997/12/22 21:07:52 @@ -1029,9 +1029,6 @@ must be stored on a local disk. The PID of the main server process is automatically appended to the filename.

-The LockFile is subject to the same warnings about log file placement and -security. -


MaxClients directive