Bug 674333 - squid -z does not create swap directories.
Summary: squid -z does not create swap directories.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 14:23 UTC by Eddie Lania
Modified: 2014-11-09 22:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-01 15:52:49 UTC
Type: ---


Attachments (Terms of Use)

Description Eddie Lania 2011-02-01 14:23:16 UTC
Description of problem: 
I cleared the /var/spool/squid directory and used "squid -z" to recreate the squid cache directories but it doesnt work.

Permissions for /var/spool/squid are okay.


Version-Release number of selected component (if applicable):
squid-3.1.10-1.fc13.i686


How reproducible: Always


Steps to Reproduce:
1. stop service squid
2. remove all contents in /var/spool/squid
3. do a "squid -z"
  
Actual results: /var/spool/squid stays empty


Expected results: /var/spool/squid to be filled with swap directories


Additional info:

Comment 1 Jiri Skala 2011-03-01 13:26:26 UTC
Hi,
it depends on setting option 'cache_dir' that is commented by default in squid-3.1. If you have no cache_dir defined in squid.conf there will not be created swap dirs:

http://www.squid-cache.org/Versions/v3/3.1/squid-3.1.7-RELEASENOTES.html#ss3.2

"...
cache_dir
Default changed to 256MB in-memory cache. see cache_mem and maximum_object_size_in_memory for size parameters.
'null' storage type dropped. In-memory cache is always present. Remove all cache_dir options to prevent on-disk caching.
..."

What about your configuration?

Comment 2 Eddie Lania 2011-03-01 15:52:35 UTC
Thank you.

That, indeed, was my problem.

It's solved now by uncommenting the line.

Best regards,

Eddie.


Note You need to log in before you can comment on or make changes to this bug.