Thomas, I have confirmed this on natty:
upstart:
Installed: 0.6.7-5
Candidate: 0.6.7-6
Version table:
0.6.7-6 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
*** 0.6.7-5 0
100 /var/lib/dpkg/status
I believe this happens because of the way restart happens in a single event
which changes the job's goal from stop, to start. At no point is a new job
object created, so the newly parsed configuration is not present. This also
probably has a lot to do with bug #703800 which causes restart to not work if
there is a pre-stop. I imagine they will have the same fix, but are not the
same bug.
** Changed in: upstart (Ubuntu)
Status: New => Triaged
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Also affects: upstart
Importance: Undecided
Status: New
** Summary changed:
- service <service> restart does nothing if service running
+ service <service> restart does not use an updated job configuration
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/707479
Title:
service <service> restart does not use an updated job configuration
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
