Not all upstart jobs correspond to running services. 'networking' is
one that does not. 'stop/waiting' is the expected state for a task that
has run, and finished.
--
Can start, but not restart, a stopped Upstart job
https://bugs.launchpad.net/bugs/430883
You received this bug notification beca
I am using karmic up-to-date (upstart-0.6.3-11 and
debhelper-7.3.15ubuntu3) and still broken. There is no way to stop/start
a service:
r...@quimerix:~# status networking
networking stop/waiting
r...@quimerix:~# start networking
networking stop/waiting
r...@quimerix:~# stop networking
stop: Unknown
debhelper side should be fixed in 7.3.15ubuntu3. Changelog:
debhelper (7.3.15ubuntu3) karmic; urgency=low
* dh_installinit:
- Create the upstart-job symlink even when --upstart-only is called,
since this simplifies implementation of...
- --restart-after-upgrade: we can't use the
This bug was fixed in the package upstart - 0.6.3-6
---
upstart (0.6.3-6) karmic; urgency=low
* Don't use "telinit q" to reconnect to D-Bus, since that breaks
lots of things. Invent another secret way instead.
[ Steve Langasek ]
* upstart-job's restart target must also not
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu
--
Can start, but not restart, a stopped Upstart job
https://bugs.launchpad.net/bugs/430883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Had a closer look at policy, and see that it says:
`restart'
stop and restart the service if it's already running, otherwise
start the service
So upstart-job needs to be changed to implement this behavior still.
I'll have a look at this ASAP.
** Changed in: upstart (Ubun
Steve worked on making upstart-job more policy compliant, I think that
he's done now.
** Changed in: debhelper (Ubuntu)
Assignee: Scott James Remnant (scott) => Steve Langasek (vorlon)
--
Can start, but not restart, a stopped Upstart job
https://bugs.launchpad.net/bugs/430883
You received t
** Changed in: debhelper (Ubuntu)
Milestone: ubuntu-9.10-beta => None
** Changed in: debhelper (Ubuntu)
Assignee: Scott James Remnant (scott) => (unassigned)
** Changed in: debhelper (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Tags removed: ubuntu-boot
--
Ca
** Changed in: upstart (Ubuntu)
Milestone: None => ubuntu-8.04.4
** Changed in: upstart (Ubuntu)
Milestone: ubuntu-8.04.4 => ubuntu-9.10-beta
** Changed in: debhelper (Ubuntu)
Milestone: None => ubuntu-9.10-beta
** Changed in: upstart (Ubuntu)
Milestone: ubuntu-9.10-beta => None
** Changed in: debhelper (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: debhelper (Ubuntu)
Importance: Medium => Low
--
Can start, but not restart, a stopped Upstart job
https://bugs.launchpad.net/bugs/430883
You received this bug notification because you a
tag ubuntu-boot
--
Scott James Remnant
sc...@canonical.com
--
Can start, but not restart, a stopped Upstart job
https://bugs.launchpad.net/bugs/430883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
We should review the debhelper autoscripts to make sure they're
consistent with what packages expect.
** Changed in: debhelper (Ubuntu)
Importance: Undecided => Medium
** Changed in: debhelper (Ubuntu)
Status: New => Confirmed
--
Can start, but not restart, a stopped Upstart job
https
This is by design.
Upstart's "restart" command is intended to *only* atomically restart a
running instance, that's because I consider it a bug that a restarting a
service that is not running can start it in the old system.
This can mean that a sysadmin's desire to have a service not running is
no
13 matches
Mail list logo
