Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4A0C9430.2090404@kippdata.de>
Date: Thu, 14 May 2009 23:59:12 +0200
From: Rainer Jung <rainer.jung@kippdata.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de;
 rv:1.9.1b3pre) Gecko/20090223 Lightning/1.0pre Thunderbird/3.0b2
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Working directory, piped logs and relative paths
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

I noticed some differences between Unix and Windows way of handling
piped loggers I wanted to give notice of:

Both platforms use a shell resp. cmd.exe to start the piped logger. In
principle both allow to use a relative path for the log program.

On Unix the working directory of the httpd processes is "/" (like for
any good daemon), so any relative path containing a slash is interpreted
relative to "/" and thus isn't really useful. The only non-absolute
paths that are nice are the ones without slashes, because they are
searched for by the shell in PATH.

On Windows the working directory of the httpd processes is the current
directory when started not as a service and the server root when started
as a service. Especially the latter makes it nice to use relative paths
in piped loggers. Using the current directory for the non-service httpd
is somehow a surprise, because it means that the interpretation of a
relative logger path in the config depends on the current shell
directory at the moment the web server is started. Of course, most
Apaches on Windows run as a service.

Regards,

Rainer