On 06.03.2012 15:53, Jeff Trawick wrote:
On Tue, Mar 6, 2012 at 8:38 AM, Plüm, Rüdiger, VF-Group
<ruediger.pl...@vodafone.com> wrote:
Sounds reasonable.
BTW, I started sketching out a RuntimeDir directive and
ap_runtime_dir_relative() API. (i.e., I threw some code together but
I don't have time this a.m. to test it ;) ).
If something like that is considered the basis of an appropriate
resolution to this particular problem, I'll proceed in the short term.
Otherwise, I may wait for a rainy day.
I like the idea even if the current problem will be fixed without. I
think the locations of all created or read file can be influenced by
configuration except for some implicit files in DEFAULT_REL_RUNTIMEDIR,
which is a build time setting. So being able to influence helps in post
build adoption of the layout.
I hope there's no boostapping problem in the sense of runtimedir needed
before config was parsed.
Have a rainy day ;)
Regards,
Rainer
-----Original Message-----
From: Jeff Trawick [mailto:traw...@gmail.com]
Sent: Dienstag, 6. März 2012 14:37
To: dev@httpd.apache.org
Subject: Re: httpd 2.4.1 and mod_slotmem_shm / mod_proxy_balancer
(AH01179)
On Tue, Mar 6, 2012 at 7:56 AM, Jim Jagielski<j...@jagunet.com> wrote:
OK... What I'll do is add a directive which provides a
"default" location for slotmem file...
Uhh, that seems as endless as per-mutex directives.
Is slotmem not using DEFAULT_REL_RUNTIMEDIR already? (not perfect,
but a good start)
Directive to specify runtime directory (API returns serverroot +
DEFAULT_REL_RUNTIMEDIR if not configured).
Directive like Mutex but for shmem?
