Example dbusd: use readiness notification; process instead of bgprocess.
authorDavin McCall <davmac@davmac.org>
Sat, 17 Nov 2018 11:10:28 +0000 (11:10 +0000)
committerDavin McCall <davmac@davmac.org>
Sat, 17 Nov 2018 11:10:28 +0000 (11:10 +0000)
doc/linux/services/dbusd

index 00c353e9f4de4484b3d00ab53bc4ae6004ac5616..885d08165ddfd4e813d9a353a3843f7c1a7bc55f 100644 (file)
@@ -1,15 +1,15 @@
 # Dbus daemon.
 
-# Dbusd can use socket activation, which Dinit (sort-of) supports. However, this currently
-# requires building Dbus against SystemD.
+# Dbusd can use socket activation, which Dinit (sort-of) supports. However,
+# this currently requires building Dbus against SystemD. Alternatively, we
+# can use the --print-address option for an effective readiness notification.
 
 # For non-socket-activated:
-#type = bgprocess
-#command = /usr/bin/dbus-daemon --system
-#pid-file = /var/run/dbus/pid
-#restart = false
+#type = process
+#command = /usr/bin/dbus-daemon --system --nofork --nopidfile --print-address=4
 #depends-on = rcboot
 #logfile = /var/log/dbus-daemon.log
+#ready-notification = pipefd:4
 #smooth-recovery = yes
 
 # For socket-activation: