Default locations for cache/generated files should respect the FHS

[GoogleCodeExporter]

What version of the product are you using (please check X-Mod-Pagespeed
header)?

0.10.19.5-r1253

On what operating system?

Debian squeeze amd64

Which version of Apache?

2.2.16

Which MPM?

prefork

=============

The default locations for ModPagespeedFileCachePath (/var/mod_pagespeedcache/) 
and ModPagespeedGeneratedFilePrefix (/var/mod_pagespeedfiles/) do not comply 
with the Linux Filesystem Hierarchy Standard (http://www.pathname.com/fhs/). 
Ideally, it should place its files in the locations mandated by the above 
standard. I'd suggest:

    ModPagespeedFileCachePath            "/var/cache/mod_pagespeed/"
    ModPagespeedGeneratedFilePrefix      "/var/lib/mod_pagespeed/"

Original issue reported on code.google.com by crispyg...@googlemail.com on 24 Jan 2012 at 12:48

[GoogleCodeExporter]

Slightly confused since the documentation seems to differ fro mthe defaults in 
the config file.

mine currently reads:

    ModPagespeedFileCachePath            "/var/mod_pagespeedcache/"
    ModPagespeedGeneratedFilePrefix      "/var/mod_pagespeedfiles/"

But I have seen a few examples on the web along the lines:

    ModPagespeedFileCachePath            "/var/mod_pagespeed/cache/"
    ModPagespeedGeneratedFilePrefix      "/var/mod_pagespeed/files/"

So besides the point the original poster asked, can someone tell me what the 
paths are supposed to be?

Original comment by ovi...@pacura.ru on 2 Apr 2012 at 12:40

[GoogleCodeExporter]

Your version was caused by a bug in our installation process for one release.
The correct version has the extra '/' per the versions you've found on the web.

But, that said, either works fine, it's just the name of the directory for 
storing files.

If you want to fix the config file, you'll need to:
* stop Apache
* edit pagespeed.conf to add the '/'
* rm -rf /var/mod_pagespeedcache /var/mod_pagespeedfiles
* start Apache.

This will clear your cache so don't do it if you want to keep it for some 
reason,
however clearing it is not serious since it will be recreated automatically.

Original comment by matterb...@google.com on 2 Apr 2012 at 12:54

[GoogleCodeExporter]

Thx. for clarifying.

Original comment by ovi...@pacura.ru on 3 Apr 2012 at 6:55

[GoogleCodeExporter]

Original comment by jmara...@google.com on 10 May 2012 at 7:44

[GoogleCodeExporter]

Original comment by jmara...@google.com on 17 May 2012 at 7:37

• Added labels: Milestone-v23

[GoogleCodeExporter]

Original comment by jmara...@google.com on 24 May 2012 at 7:50

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r1643.

Original comment by jefftk@google.com on 6 Jun 2012 at 3:29

• Changed state: Fixed