Colin Walters 949a64b127 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>		2009-12-15 13:08:02 -05:00
..
.gitignore	Bring .gitignore files up to date; add *.o, *~ etc. to top-level .gitignore	2007-10-10 17:38:00 +01:00
org.freedesktop.DBus.TestSuite.PrivServer.service.in	Add "PrivServer" test which exercises DBusServer and dbus_shutdown	2008-05-30 17:11:15 -04:00
org.freedesktop.DBus.TestSuiteEchoService.service.in	2007-07-24 Richard Hughes <richard@hughsie.com>	2007-07-24 12:48:45 +00:00
org.freedesktop.DBus.TestSuiteForkingEchoService.service.in	Ignore exit code zero from activated services	2009-12-15 13:08:02 -05:00
org.freedesktop.DBus.TestSuiteSegfaultService.service.in	2007-07-24 Richard Hughes <richard@hughsie.com>	2007-07-24 12:48:45 +00:00
org.freedesktop.DBus.TestSuiteShellEchoServiceFail.service.in	2007-07-24 Richard Hughes <richard@hughsie.com>	2007-07-24 12:48:45 +00:00
org.freedesktop.DBus.TestSuiteShellEchoServiceSuccess.service.in	2007-07-24 Richard Hughes <richard@hughsie.com>	2007-07-24 12:48:45 +00:00