Search squid archive

Re: unlinked squid process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Thanks,
>
> that is very interesting,
> the ownership of swap.state on all servers are squid,
> because it is pipe the echo output so it shouldn't change
> the permission.
>
> however was wondering if clearing swap.state is the way of
> clearing cache !!!!
>
> I was checking the squid that comes with Centos,
> it does not have any flush option, probably flush is a
> bad idea ?

Yes. Its not possible yet without destroying and rebuilding the entire fs.
http://wiki.squid-cache.org/SquidFaq/OperatingSquid#head-997ff43f2b62743af566fb32f62e8ed512f49be2

>
> Quoting Adrian Chadd <adrian@xxxxxxxxxxxxxxx>:
>
>> On Tue, Oct 23, 2007, squid@xxxxxxxxxxxxxx wrote:
>>> Hi
>>>
>>> we are using SQUID 2.6.STABLE13
>>>
>>> we usually restarting squid by flushing it
>>> service squid restart
>>> service squid flush
>>>
>>> flush)
>>>         $0 stop
>>>         sleep 2
>>>         echo -n 'Flushing squid cache: '
>>
>>>         echo "" > /var/spool/squid/cache/swap.state
>>
>> This line isn't flushing the cache and its probably creating a
>> root-owned
>> swap.state file thats causing your problem.
>>

Seeing as how badly that was treating squid.
Please include the rest of the script, so we can check the other operations.

Amos



[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux