Excerpts from Daniel Hahler's message of Tue May 15 08:53:06 UTC 2012: > For what it's worth, this does not happen with the squid-deb-proxy > package (which uses squid with an optimized config) - at least after > several boot processes. > > The init/start script is different, for example, it uses > "start on (local-filesystems and net-device-up IFACE!=lo)"
This is basically wrong. A system may have more than one interface and there is no guarantee that one of them is "the right one". That said, this makes perfect sense, because with NM, this will delay the start until *after* the first interface comes up, whereas with runlevel 2, that event will actually come before the first interface is up, so that starts the window where squid is starting up, polling for DNS entries and failing, and then it gets HUP just as the interface comes up. My patch to ignore HUP early on should solve this issue, but I haven't pushed it back upstream yet. -- 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/978356 Title: squid3 gets killed at startup with dnsmasq and no networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/978356/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
