[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0"

[D J Gardner]

On the available evidence that this bug is caused by resolvconf reload squid "too soon", I attach a work-around patch. 
It delays any resolvconf reload by 30 seconds if it occurs within 200 seconds of boot. 
Those numbers might well need tuning on other systems, but the patch has solved the issue for my computer 
i.e. squid3 now starts properly. 


** Patch added: "Delay resolvconf reload when immediately after boot"
   https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/988802/+attachment/3197159/+files/squid3-reslovconf_delay.patch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/988802

Title:
  squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/squid/+bug/988802/+subscriptions