Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 14FA010DC7 for ; Wed, 21 Aug 2013 13:06:12 +0000 (UTC) Received: (qmail 85842 invoked by uid 500); 21 Aug 2013 13:06:10 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 85528 invoked by uid 500); 21 Aug 2013 13:06:09 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 85157 invoked by uid 99); 21 Aug 2013 13:06:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 13:06:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-la0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 13:06:05 +0000 Received: by mail-la0-f41.google.com with SMTP id ec20so313519lab.28 for ; Wed, 21 Aug 2013 06:05:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=cWIoR4LTbHYiSnf7/hMvoigs9guxxZoh8Qwa+v6w1NA=; b=bv03y8G4y1GiyO23oFxX6PQRES/a5f4rSkkiHQWy/XsuYzqOtULkGJ5eeXELEK5LZ6 ANjd10YWllS5dTvxpEStU6iYxzSMm7QiFzG50htDx7tGRuWAOdE3OEfxtYT/dkpmO2/w dBwAYWjug6mQCfCwFiCT/ZqEw2Ab1+Y/Xu0JHbXkW+sYhtnhbZsM46R4dQsHcK5ETVbG /GpJRwZ7SRMgiN8IR38SJo4nwkvGe7C1u3gPnVEyG/23MugxZGb5E4IdPirHjBVTiCiv IxeNJ+W2tME+YGZvyRuC/JSnqdKe+QFUUaHJQWfUli/wo2R3PVRcBnJ8UVv7v7flpbjy qufg== MIME-Version: 1.0 X-Received: by 10.152.26.72 with SMTP id j8mr6023361lag.19.1377090343847; Wed, 21 Aug 2013 06:05:43 -0700 (PDT) Received: by 10.114.184.99 with HTTP; Wed, 21 Aug 2013 06:05:43 -0700 (PDT) In-Reply-To: <227D2559-476D-4D2C-9C7E-3293B359D269@jaguNET.com> References: <227D2559-476D-4D2C-9C7E-3293B359D269@jaguNET.com> Date: Wed, 21 Aug 2013 09:05:43 -0400 Message-ID: Subject: Re: DefaultRuntimeDir From: Jeff Trawick To: Apache HTTP Server Development List Content-Type: multipart/alternative; boundary=089e0160c36ec4cbf404e474d45b X-Virus-Checked: Checked by ClamAV on apache.org --089e0160c36ec4cbf404e474d45b Content-Type: text/plain; charset=ISO-8859-1 On Wed, Aug 21, 2013 at 8:27 AM, Jim Jagielski wrote: > The 2.4 STATUS file has: > > * opinion on more complete DefaultRuntimeDir use in 2.4.x? > o If a module has a config directive for the run-time file that > treats the configured path as relative to server root, preserve > that behavior but change the location when not configured to > respect DefaultRuntimeDir. With these changes, users with no > per-runtime-file configuration directives can control > everything with DefaultRuntimeDir. > BUT: Existing users of DefaultRuntimeDir might get a short-term > scare > when some unconfigured run-time file starts respecting their > DefaultRuntimeDir directive after an upgrade. > +1: trawick, jim, rjung > rjung: applicable trunk revisions WITHOUT the compatibility tweaks > described above: > scoreboard r1369477 > core/pid file r1369808 > core/mutex r1370288 > mod_socache_XXX r1370225, r1407385 > mod_ldap r1371684 > mod_cache r1407381 > mod_slotmem_plain r1370763 > igalic: We have three votes, what's the status here? > Independently, backport any doc tweaks to 2.4 API migration page. > > To be honest, I also wonder what the status of this is... > I'd like to have the 1st 3 in 2.4, but am unsure what is > required, if anything, to make it acceptable. Is it just > the "preserve" line? > I think that we've already backported everything we can without risking a change in the meaning of someone's configuration. DefaultRuntimeDir can/should be used for new additions to 2.4 when appropriate, but these remaining ones are dangerous without some 2.4-specific mitigation. I'll try to look through this in the next day to see if there is some mitigation we can do to allow the feature without breaking any current 2.4 behavior. I fear that a "safe" implementation would require some explicit opt-in for these remaining features, and a config that did the opt-in could then move all the runtime files just by changing DefaultRuntimeDir. -- Born in Roswell... married an alien... http://emptyhammock.com/ --089e0160c36ec4cbf404e474d45b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Aug 21, 2013 at 8:27 AM, Jim Jagielski <jim@jagun= et.com> wrote:
The 2.4 STATUS file has:

=A0 =A0* opinion on more complete DefaultRuntimeDir use in 2.4.x?
=A0 =A0 =A0o If a module has a config directive for the run-time file that<= br> =A0 =A0 =A0 =A0treats the configured path as relative to server root, prese= rve
=A0 =A0 =A0 =A0that behavior but change the location when not configured to=
=A0 =A0 =A0 =A0respect DefaultRuntimeDir. =A0With these changes, users with= no
=A0 =A0 =A0 =A0per-runtime-file configuration directives can control
=A0 =A0 =A0 =A0everything with DefaultRuntimeDir.
=A0 =A0 =A0 =A0BUT: Existing users of DefaultRuntimeDir might get a short-t= erm scare
=A0 =A0 =A0 =A0when some unconfigured run-time file starts respecting their=
=A0 =A0 =A0 =A0DefaultRuntimeDir directive after an upgrade.
=A0 =A0 =A0 =A0+1: trawick, jim, rjung
=A0 =A0 =A0 =A0rjung: applicable trunk revisions WITHOUT the compatibility = tweaks
=A0 =A0 =A0 =A0 =A0 =A0 =A0 described above:
=A0 =A0 =A0 =A0 =A0 scoreboard =A0 =A0 =A0 =A0 r1369477
=A0 =A0 =A0 =A0 =A0 core/pid file =A0 =A0 =A0r1369808
=A0 =A0 =A0 =A0 =A0 core/mutex =A0 =A0 =A0 =A0 r1370288
=A0 =A0 =A0 =A0 =A0 mod_socache_XXX =A0 =A0r1370225, r1407385
=A0 =A0 =A0 =A0 =A0 mod_ldap =A0 =A0 =A0 =A0 =A0 r1371684
=A0 =A0 =A0 =A0 =A0 mod_cache =A0 =A0 =A0 =A0 =A0r1407381
=A0 =A0 =A0 =A0 =A0 mod_slotmem_plain =A0r1370763
=A0 =A0 =A0 =A0 igalic: We have three votes, what's the status here? =A0 =A0 =A0 =A0Independently, backport any doc tweaks to 2.4 API migration = page.

To be honest, I also wonder what the status of this is...
I'd like to have the 1st 3 in 2.4, but am unsure what is
required, if anything, to make it acceptable. Is it just
the "preserve" line?


I think that we've already backported everything we c= an without risking a change in the meaning of someone's configuration. = =A0DefaultRuntimeDir can/should be used for new additions to 2.4 when appro= priate, but these remaining ones are dangerous without some 2.4-specific mi= tigation.

I'll tr= y to look through this in the next day to see if there is some mitigation w= e can do to allow the feature without breaking any current 2.4 behavior. = =A0I fear that a "safe" implementation would require some explici= t opt-in for these remaining features, and a config that did the opt-in cou= ld then move all the runtime files just by changing DefaultRuntimeDir.

--
Born in Roswell... married= an alien...
http= ://emptyhammock.com/
--089e0160c36ec4cbf404e474d45b--