mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2026-05-04 12:58:02 +02:00
b7e77c6b03
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> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| run-test-systemserver.sh | ||
| run-test.sh | ||
| test-activation-forking.py | ||
| test-ids.c | ||
| test-names.c | ||
| test-pending-call-dispatch.c | ||
| test-pending-call-timeout.c | ||
| test-privserver-client.c | ||
| test-privserver.c | ||
| test-shutdown.c | ||
| test-threads-init.c | ||
| test-wait-for-echo.py | ||
| tmp-session-like-system.conf | ||