Public bug reported:
After performing a dist-upgrade of my lucid installation, I got the
following upstart error in my boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20squid start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20squid
start: Unknown job: S20squid
One can reproduce this bug, by simply issuing "sudo
/etc/rc(2-5).d/S20squid start". Since S20squid is simply a symlink to
/etc/init.d/squid this affects all runlevels. However it seems to be non
critical since squid is started anyway (I have no idea why). The issue
can be fixed by modifying line 8 in /etc/init.d/squid from
JOB="${INITSCRIPT%.sh}"
to
JOB="squid"
So there are two issues here, if I am not mistaken. First the redundancy
since squid is started by two different scripts(?) and secondly the
wrong line in /etc/init.d/squid.
I am running Ubuntu 10.04.3 LTS
My squid version is 2.7.STABLE7
The system is up-to-date (aside from the grub package which is held back)
If you need any more information I am happy to provide it.
Thanks for your efforts
B. Brandt
** Affects: squid (Ubuntu)
Importance: Undecided
Status: New
--
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/908905
Title:
upstart problems with S20squid script
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/908905/+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
