On Sun, 13 Mar 2011 16:33:49 +0300, Hasanen AL-Bana wrote:
I had this issue before , doing squid -k reconfigure or reload
doesn't
release cache disk. You need to do squid stop/start.
"-k reconfigure" should work. But recently there seems to be something
preventing it from identifying some changes like this removal :(
"-k restart" does the full stop/start cycle to pick up all changes when
reconfigure is broken.
Amos
2011/3/13 VÃctor Josà HernÃndez GÃmez <vjhergom@xxxxxxxxxx>:
Hi all,
I had planned some work on the ext3 partition used for cache data in
our
squid 3.1.11 instalation, which should be unomunted and mounted
after some
filesystem parameters modifications.
So I thought it could work the following
Â1. comment cache_dir line on squid.conf
Â2. add cache deny all
Â3. (reconfigure) squid -k reconfigure
(so users could navigate and ...) ÂIf squid is not using cache data
at all,
then I could modify ext3 params on the partition...
Â4. work on partition
Â5. umount partition
Â6. mount
Â7. undo changes on squid.conf and reconfigure
This was not the case, as before I tried to unmount the partition
Âsquid
still was using swap.state file ... (lsof /partition warned me), so
I had to
undo the work on partition and undo changes on squid.conf...
What asumption was wrong? Should squid free the filedescriptor
related to
swapstate file? Any other approach to get what we need?
Thank you in advanced for your help,
--
VÃctor J. HernÃndez GÃmez
