In trying to run the test case for this, I didn't get the squid-deb- proxy service started, with 0.3.1 or 0.3.1.1
This is because squid needs the network up to do DNS lookups... it fails with: 2010/11/15 18:10:19| Starting Squid Cache version 2.7.STABLE9 for x86_64-debian-linux-gnu... 2010/11/15 18:10:19| Process ID 1653 2010/11/15 18:10:19| With 1024 file descriptors available 2010/11/15 18:10:19| Using epoll for the IO loop 2010/11/15 18:10:19| Performing DNS Tests... FATAL: ipcache_init: DNS name lookup tests failed. Squid Cache (Version 2.7.STABLE9): Terminated abnormally. CPU Usage: 0.000 seconds = 0.000 user + 0.000 sys Maximum Resident Size: 7216 KB Page faults with physical i/o: 0 If I manually start squid-deb-proxy *after* the wifi associates (no wired connection here) then it works fine. so the job cannot be start on runlevel [2345] It should be (as squid is) start on (local-filesystems and net-device-up IFACE!=lo) Testing with this modification seems to produce the desired result with 0.3.1.1's upstart job. So I'd say this SRU should also include this modification to /etc/init /squid-deb-proxy.conf before moving to -updates should we open a separate report for that -- Avahi service for squid-deb-proxy does not start https://bugs.launchpad.net/bugs/666014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
