Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Apache: Dev

Why does CacheLockPath default to a directory in /tmp instead of runtime-dir?

 

 

Apache dev RSS feed   Index | Next | Previous | View Threaded


trawick at gmail

Aug 5, 2012, 6:14 AM

Post #1 of 3 (148 views)
Permalink
Why does CacheLockPath default to a directory in /tmp instead of runtime-dir?



cifali.filipe at gmail

Aug 5, 2012, 6:29 AM

Post #2 of 3 (145 views)
Permalink
Re: Why does CacheLockPath default to a directory in /tmp instead of runtime-dir? [In reply to]

Normally /tmp is mounted at RAM (tmpfs) and it does provide better
performance?

2012/8/5 Jeff Trawick <trawick [at] gmail>

>
>


--
[]'s

Filipe Cifali Stangler


trawick at gmail

Aug 5, 2012, 6:41 AM

Post #3 of 3 (140 views)
Permalink
Re: Why does CacheLockPath default to a directory in /tmp instead of runtime-dir? [In reply to]

On Sun, Aug 5, 2012 at 9:29 AM, Filipe Cifali <cifali.filipe [at] gmail> wrote:
> Normally /tmp is mounted at RAM (tmpfs) and it does provide better
> performance?

Sure. And I guess there's a bit of value with them getting cleaned up
at reboot.

mod_auth_digest is another module that places in /tmp the sort of
artifact that other modules place in the runtimedir (or hard-coded
"logs/").

Hopefully in the future you'll be able to code "DefaultRuntimeDir
/var/run/foo.example.com" and everything gets the same benefit (and
without such a directive everything is created in a predictable
location). It appears that a bunch of modules still need to get
smarter though.

>
> 2012/8/5 Jeff Trawick <trawick [at] gmail>
>>
>>
>
>
>
> --
> []'s
>
> Filipe Cifali Stangler
>



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

Apache dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.