Public bug reported:
I did a merge for the squid3 package and was also looking at
- https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523 and
- https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/988802
Given that SIGHUP may sometimes have arrived too quickly (as mostly slower
machines ran into this) and the fix that is proposed there (it sounds sensible
to initialize the signal handler sooner) did make the other bug more obvious, I
guess that by making the upstart job respawning it should at least ensure
squid3 is running.
Though it probably makes most sense to do the merge without an other changes
and evaluate the situation after that.
I will attach diffs for the merge as I would do it. Please have a look.
Thanks.
** Affects: squid3 (Ubuntu)
Importance: Wishlist
Assignee: Stefan Bader (stefan-bader-canonical)
Status: In Progress
--
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/1016560
Title:
Please merge squid3 3.1.20-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1016560/+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
