Comment 9 for bug 561750

Chuck, you said it "should be fixed for Lucid" back in April. Unfortunately, I'm still observing
exactly the same problem, of squid starting then immediatly stopping on boot.
I have resolvconf, along with a local copy of bind9 for my home network.

My /etc/resolvconf/update-libc.d/squid has the lines:

if status squid | grep "start/running" > /dev/null; then
        restart squid
fi

Syslog reveals:

Aug 16 11:30:34 foo squid[1868]: Squid Parent: child process 1870 started
[...]
Aug 16 11:30:38 foo acpid: 1 client rule loaded
Aug 16 11:30:39 foo kernel: [ 78.143745] nf_conntrack version 0.5.0 (10981 buckets, 43924 max)
[...]
Aug 16 11:30:40 foo named[2367]: starting BIND 9.7.0-P1 -u bind
Aug 16 11:30:40 foo named[2367]: running
[...]
Aug 16 11:30:41 foo init: squid main process (1868) killed by TERM signal
Aug 16 11:30:41 foo init: squid main process (2455) terminated with status 1

The relevant portion of cache.log ends up like:

2010/08/16 11:30:39| 0 Objects expired.
2010/08/16 11:30:39| 0 Objects cancelled.
2010/08/16 11:30:39| 0 Duplicate URLs purged.
2010/08/16 11:30:39| 0 Swapfile clashes avoided.
2010/08/16 11:30:39| Took 4.5 seconds (18266.9 objects/sec).
2010/08/16 11:30:39| Beginning Validation Procedure
2010/08/16 11:30:39| Completed Validation Procedure
2010/08/16 11:30:39| Validated 82655 Entries
2010/08/16 11:30:39| store_swap_size = 2793828k
2010/08/16 11:30:39| storeLateRelease: released 0 objects
2010/08/16 11:30:41| Preparing for shutdown after 0 requests
2010/08/16 11:30:41| Waiting 3 seconds for active connections to finish
2010/08/16 11:30:41| FD 16 Closing HTTP connection
2010/08/16 11:30:41| Shutting down...