summaryrefslogtreecommitdiff
path: root/docs/reference/node-startup-controller
diff options
context:
space:
mode:
authorFrancisco Redondo Marchena <francisco.marchena@codethink.co.uk>2012-07-31 16:52:06 +0100
committerFrancisco Redondo Marchena <francisco.marchena@codethink.co.uk>2012-07-31 17:16:00 +0100
commit9d71065bfb59eb10fbd8ece605485d3864d08c08 (patch)
tree12d236627b434b75404fb91be7bc857a9dc9b805 /docs/reference/node-startup-controller
parent67227db2d1e6bc4937d33ba94fd753080e8eb31c (diff)
downloadnode-startup-controller-9d71065bfb59eb10fbd8ece605485d3864d08c08.tar.gz
Query the "active-state" property of units in the "job-removed" handler
Our previous attempt to fix the TargetStartupMonitor failed because when a target is stopped, systemd drops the unit from the system bus and the proxies we created in TargetStartupMonitor were no longer associated with these unit objects that previously existed on the bus. When such a target is started again, the proxy will no longer receive property change signals from systemd. This commit tries to implement the TargetStartupMonitor in yet another way, which is to listen to systemd's "job-removed" signal again. In response to receiving "job-removed" signals, we now create a SystemdUnit for the affected unit and query that for its current "active-state" value. Perhaps this will work.
Diffstat (limited to 'docs/reference/node-startup-controller')
0 files changed, 0 insertions, 0 deletions