Hello all,

Frequently after an upgrade or simply a reboot I encounter some weird pb
to use my squid cache. I didn't analyse further because those pb was always solved by a stop of squid,
a cleanup of the spool (rm -rf /var/spool/squid/) and a restart of the
daemon ;-)

So the idea would be to put a variable option (by default preset to
false) in /etc/default/squid, which would allow /etc/init.d/squid to do
this cleanup at boot time (may be also at a restart).

Thanks in advance for your attention,
	Joel

Hello Luigi,

Sorry I do have made some mistakes with reportbug: the title was:
"Couldn't it be possible to add a boot option to clean spool (somewhere in /etc/default)?"

Apologies,
	Joel

Debian Bug Tracking System wrote:

retitle 338783 squid: please add a boot option to clean spool
(somewhere in /etc/default)
thanks

Hi,
zapping the cache every time you reboot is not an effective choiche.
Usually corruptions of cache_dir are caused by unclean shutdown. Can
you please provide your /etc/squid/squid.conf and /var/log/squid/
cache.log next time it happens?

Regards,

Hello Luigi,


Luigi Gangitano wrote:
Well, as mentioned in my proposal, I don't want to be a default, just a possibility.
In general, I use my system only the week-end, and restart next week-end, so anyway the cache is not any more relevant.
Not in the most time I encountered the pb, it was during a simple update of the pkg, though.
Of course ;-)

Thanks,
	Joel

Hello Luigi,

Sorry for delay but it was a long time that I met pb with squid since today ;-)



Luigi Gangitano wrote:
I join it and you will noticed that pb doesn't occure because of a bad way of shutdown but simply because the fs became full at one
moment and this broken the cache ;<(

Hth,
	Joel

ps: my install is always an unstable debian ;-)