Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (nike.apache.org: 76.96.30.17 is neither permitted nor
 denied by domain of jim@jagunet.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: [PATCH] DefaultRuntimeDir, ap_runtime_dir_relative()
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <4F57C617.6040601@kippdata.de>
Date: Thu, 8 Mar 2012 07:07:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B971E03D-950A-4256-AC5C-D1B58BCAB5E1@jaguNET.com>
References: 
 <CAKUrXK4wn4waH7NKFjX=GyHoUCyQaRLOm4+XVQ5XjqRxnHqF1g@mail.gmail.com>
 <4F57C617.6040601@kippdata.de>
To: dev@httpd.apache.org

Not sure how this changes things with the current impl... Certainly
collisions are possible using ServerRoot or the modules which use
DEFAULT_REL_RUNTIMEDIR already, right?

But yeah, I agree that noting this in the declaration
comments makes sense.

On Mar 7, 2012, at 3:33 PM, Rainer Jung wrote:

> Since a user can now easily move all those non-log read/write files to =
a central dir like /var/run/apache etc., do we think we need to keep the =
files themselves separate between instances by choosing unique file =
names (adding parent pid or similar)? Or should we document that you =
should *not* use the same directory for multiple instances?
>=20
> Although adding a pid to the file names seems simple, it often leads =
to accumulating garbage files.
>=20
> Regards,
>=20
> Rainer
>=20