© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
If I create a job that looks like this:
manual
script
sleep 5
end script
post-start script
sleep 10
end script
Then what I see is these state transitions:
$ dbus-monitor member=StateChanged
signal sender=
string ":1.307"
signal sender=:1.0 -> dest=(null destination) serial=712 path=/com/
string "starting"
signal sender=:1.0 -> dest=(null destination) serial=713 path=/com/
string "security"
signal sender=:1.0 -> dest=(null destination) serial=714 path=/com/
string "pre-start"
signal sender=:1.0 -> dest=(null destination) serial=715 path=/com/
string "spawned"
signal sender=:1.0 -> dest=(null destination) serial=716 path=/com/
string "post-start"
signal sender=:1.0 -> dest=(null destination) serial=719 path=/com/
string "stopping"
signal sender=:1.0 -> dest=(null destination) serial=720 path=/com/
string "killed"
signal sender=:1.0 -> dest=(null destination) serial=721 path=/com/
string "post-stop"
signal sender=:1.0 -> dest=(null destination) serial=722 path=/com/
string "waiting"
The result of not ever going into the running state is that we don't get the "started" signal emitted onto DBus. It seems to me that it was started, and it ran, so the started signal should be emitted.