"service start" complains about using the init script and recommends using "service"
Bug #427277 reported by
Martin Pitt
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysvinit (Ubuntu) |
Fix Released
|
Low
|
Dustin Kirkland |
Bug Description
Binary package hint: sysvinit
I'm using Scott's upstartification PPA (http://
$ sudo service hal start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service hal 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 hal
start: Job is already running: hal
So it complains that I should do exactly what I already did. :-)
Related branches
Changed in sysvinit (Ubuntu): | |
importance: | Undecided → Low |
Changed in sysvinit (Ubuntu): | |
status: | New → Confirmed |
tags: | added: ubuntu-boot |
Changed in sysvinit (Ubuntu): | |
assignee: | nobody → Dustin Kirkland (kirkland) |
To post a comment you must log in.
I'm seeing this in Karmic proper now:
atomicity:[~] sudo /etc/init.d/anacron start
[sudo] password for mdz:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service anacron 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 anacron
anacron stop/waiting
atomicity:[~] sudo service anacron start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service anacron 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 anacron
anacron stop/waiting
atomicity:[~] sudo start anacron
anacron stop/waiting