summaryrefslogtreecommitdiff
path: root/configure.in
diff options
context:
space:
mode:
authorColin Walters <walters@verbum.org>2009-12-14 18:12:24 -0500
committerColin Walters <walters@verbum.org>2010-01-28 17:01:24 -0500
commitb7e77c6b035f634f372c1749e61c14bde18b5d95 (patch)
tree2e7cc5c81b41e3b287bdd53e3b37dc7cd1d6104b /configure.in
parenta8e620a0ff60eef983a9be95e2b27dbcdcbaf654 (diff)
downloaddbus-b7e77c6b035f634f372c1749e61c14bde18b5d95.tar.gz
Ignore exit code zero from activated services
A variety of system components have migrated from legacy init into DBus service activation. Many of these system components "daemonize", which involves forking. The DBus activation system treated an exit as an activation failure, assuming that the child process which grabbed the DBus name didn't run first. While we're in here, also differentiate in this code path between the servicehelper (system) versus direct activation (session) paths. In the session activation path our error message mentioned a helper process which was confusing, since none was involved. Based on a patch and debugging research from Ray Strode <rstrode@redhat.com>
Diffstat (limited to 'configure.in')
-rw-r--r--configure.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/configure.in b/configure.in
index 2e6422c1..7feb1a93 100644
--- a/configure.in
+++ b/configure.in
@@ -1441,6 +1441,7 @@ test/data/valid-config-files-system/debug-allow-all-pass.conf
test/data/valid-config-files-system/debug-allow-all-fail.conf
test/data/valid-service-files/org.freedesktop.DBus.TestSuite.PrivServer.service
test/data/valid-service-files/org.freedesktop.DBus.TestSuiteEchoService.service
+test/data/valid-service-files/org.freedesktop.DBus.TestSuiteForkingEchoService.service
test/data/valid-service-files/org.freedesktop.DBus.TestSuiteSegfaultService.service
test/data/valid-service-files/org.freedesktop.DBus.TestSuiteShellEchoServiceSuccess.service
test/data/valid-service-files/org.freedesktop.DBus.TestSuiteShellEchoServiceFail.service