Re: [PATCH] Core Update 165: Restart Squid during the update

["Peter Müller" <peter.mueller@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hello Michael,

thanks for your reply.

This is necessary because (a) we ship a new version of Squid with Core Update 165
and (b) not restarting Squid afterwards caused the web proxy to stall on my testing
machine.

Thanks, and best regards,
Peter Müller


> Why is this necessary?
> 
>> On 20 Mar 2022, at 10:20, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Fixes: #12810
>>
>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>> ---
>> config/rootfiles/core/165/update.sh | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/config/rootfiles/core/165/update.sh b/config/rootfiles/core/165/update.sh
>> index ffb552c80..2c2e6a10c 100644
>> --- a/config/rootfiles/core/165/update.sh
>> +++ b/config/rootfiles/core/165/update.sh
>> @@ -128,6 +128,7 @@ ldconfig
>> # Start services
>> telinit u
>> /etc/rc.d/init.d/firewall restart
>> +/etc/rc.d/init.d/squid restart
>>
>> # Fix ownership of classification file.
>> chown nobody:nobody /usr/share/suricata/classification.config
>> -- 
>> 2.34.1
>