This bug was fixed in the package squid - 2.7.STABLE9-2ubuntu5.2
---
squid (2.7.STABLE9-2ubuntu5.2) maverick-proposed; urgency=low
* d/squid.upstart: start on was not sufficient to restart squid
on transition from runlevel 1 to 2 (LP: #561779). Also stop on
condition was
I was able to reproduce this issue with squid 2.7.STABLE9-2ubuntu5.1,
and have verified that the version in maverick-proposed,
2.7.STABLE9-2ubuntu5.2 appears to fix the issue. After upgrading, squid
continued to function as expected. Marking verification-done.
** Tags removed: verification-needed
** Tags removed: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/750371
Title:
squid causing /var to stay busy during shutdown
To manage notifications about
This bug was fixed in the package squid - 2.7.STABLE7-1ubuntu12.4
---
squid (2.7.STABLE7-1ubuntu12.4) lucid-proposed; urgency=low
* d/squid.upstart: start on was not sufficient to restart squid
on transition from runlevel 1 to 2 (LP: #561779). Also stop on
condition was not
Thank you very much for your time!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/750371
Title:
squid causing /var to stay busy during shutdown
To manage notifications about this
Thank you very much Clint and Chris, and especially Jorge!
I have finally found some time to get rid of my ugly workaround to this
bug (which involved manually stopping squid before filesystem
unmounting) and installed squid 2.7.STABLE7-1ubuntu12.4 from lucid-
proposed.
Besides a dirty
Thanks ryokenau, marking verification-done-lucid.
We still need somebody to verify this on maverick. Thanks!
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
Hello ryokenau, or anyone else affected,
Accepted squid into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
Hello ryokenau, or anyone else affected,
Accepted squid into maverick-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/lucid-proposed/squid
** Branch linked: lp:ubuntu/maverick-proposed/squid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/750371
Title:
squid causing /var
Good eyes there Jorge. I missed that entirely.
It seems I inadvertently fixed this in natty at 2.7.STABLE9-2.1ubuntu6
when fixing bug #561779. But it needs to be fixed in maverick and Lucid
as well. I would agree with you that this is a High Priority, as squid
needs to be stopped!
** This bug is
I've uploaded fixed squids to lucid-proposed and maverick-proposed.
Thanks again Jorge!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/750371
Title:
squid causing /var to stay busy
*** This bug is a duplicate of bug 688541 ***
https://bugs.launchpad.net/bugs/688541
Also on the 2nd line for 'stop on' there is no space after runlevel.
Correct syntax should be:
start on runlevel [2345] or net-device-up IFACE!=lo
stop on runlevel [!2345]
I also applied codewarrior's
*** This bug is a duplicate of bug 688541 ***
https://bugs.launchpad.net/bugs/688541
On ubuntu 10.04.3 LTS the problem is on the start on line in
/etc/init/squid.conf file. It is different from the one in ubuntu 11.04.
You should have something like:
start on runlevel [2345] or
*** This bug is a duplicate of bug 688541 ***
https://bugs.launchpad.net/bugs/688541
/etc/init/squid.conf actually does have the appropriate 'stop on':
stop on runlevel [!2345]
However, umountfs/sendsigs don't wait for these things to actually die
before completing the shutdown.
That is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I was able to confirm this issue in the latest development release as
well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
** Description changed:
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid
- 2.7.STABLE7-1ubuntu12.2. When I
+ 2.7.STABLE7-1ubuntu12.2. When I shutdown or reboot the system, I get the
+ following error:
- shutdown or reboot the system, I get the
17 matches
Mail list logo
