Check the startup script, and see what squid.conf it uses. Squid looks for
a conf file in a default location specified when it is compiled, but can be
told (with the -f option) to use a different config file. Running squid
-k reconfigure without the -f option will reconfigure squid to use the
config file in the default location, which could explain the problems you
are seeing.
Just a thought.
Chris
-Original Message-
From: Elsen Marc [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 02, 2004 5:45 AM
To: Jafar Aliev; [EMAIL PROTECTED]
Subject: RE: Re[4]: [squid-users] 'Squid -k reconfigure' changes
ownership of the swap.state file
Squid -k parse does not produce any errors or warings.
There are no errors in cache.log file after cold start.
(except strange
chdir: /var/squid/cache: (2) No such file or directory
but I didn't find any occurrence of /var/squid/cache in config file)
...
You should treat that message as an error and resolve it :
make sure that cache dirs defined in squid.conf exist and
are accessible by the user squid runs as.
M.
