Have the same behaviour on a x86_64 server freshly-upgraded from Oneiric to Precise. On system reboot, squid3 does not start properly - gets killed by HUP signal as recorded in syslog. Logging into the system by ssh and manual starting service squid3 helps to resolve the problem. But having squid3 starting normally on bootup would be very beneficial.
I strongly suspect this misbehaviour happens due to incomplete integration of upstart, ifupdown and resolvconf packages functionality. I use system without NetworkManager (it's a server after all), my interfaces are controlled by ifupdown and by ppp scripts. Probably upstart starts ifupdown too early, again as it usually happens when you have resolvsconf in universe instead of main. -- 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
