damk wrote:
> Maybe your /var/run not chown-ed by nobody.


Thank you, but seems not. /var/run is owned by root and should not be
changed due to system defaults. And this worked with the former
squid-release.

But I tried something similar to your idea: I created /var/run/squid/
owned by the user, the squid-cache runs with. This directory I also
placed in squid.conf and in my initscript.

If squid starts, I see the squid.pid generated with owner root in this
directory. But when I do something like "squid -k check" I get the same
error as before (squid: ERROR: No running copy).

Something must have been changed in the way "pid_filename" is used in
squid-2.5.STABLE4

Greetings,
Oliver


> On Thu, 08 Jan 2004 11:19:46 +0100, Oliver Zimmermann
> wrote:
>
>> Hi,
>>
>> I got problems with the Squid PID after updating from
>> squid-2.5.STABLE1 to squid-2.5.STABLE4.
>>
>> The daily "squid -k rotate" didn't work anymore with error
>> "squid: ERROR: No running copy".
>>
>> I read in the FAQ, that possibly the squid.pid is missing - but that's
>> not the case:
>>
>> ps ax|grep squid
>> 25694 ? S 0:00 /usr/local/squid/sbin/squid -D -sYC -f
>> /etc/squid.conf
>> 25697 ? R 0:12 (squid) -D -sYC -f /etc/squid.conf
>>
>> ... and /var/run/squid.pid contents 25697
>>
>> Squid should use that file, because squid.conf has:
>> #Default:
>> # pid_filename /usr/local/squid/var/logs/squid.pid
>> pid_filename /var/run/squid.pid
>>
>> With a softlink I could solve the problem:
>> ln -s /var/run/squid.pid /usr/local/squid/var/logs/squid.pid
>>
>> After this workaround the error disappeared.
>>
>> Is this a known problem in squid-2.5.STABLE4 on Debian/stable ?
>>
>> Greetings,
>> Oliver
>>
>>
>>
>>
>>
>>

>
>
>