The log of dbus-daemon always printed twice through systemd because an logical error. In systemd environment, regardless whether dbus-daemon is forked or not, it shouldn't print error to stderr but only syslog, because systemd implemented syslog. Otherwise, the log of dbus printed to stderr and syslog will both catched by systemd journal. And then duplicated like below. ... Aug 23 11:11:52 localhost.bj.intel.com dbus[282]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Aug 23 11:11:52 localhost.bj.intel.com dbus-daemon[282]: dbus[282]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Aug 23 11:11:52 localhost.bj.intel.com dbus-daemon[282]: dbus[282]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Aug 23 11:11:52 localhost.bj.intel.com dbus[282]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Aug 23 11:11:52 localhost.bj.intel.com dbus-daemon[282]: dbus[282]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Aug 23 11:11:52 localhost.bj.intel.com dbus[282]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' ... The second duplicate one is printed to stderr but also catched by systemd journal.
OK, this is invalid since 1.7.2. though the argument of is_daemon of _dbus_init_system_log() is a little misleading. In fact, it's is_test.
There was a reason why I called it is_daemon, but I can't remember it right now...
(In reply to comment #1) > OK, this is invalid since 1.7.2. though the argument of is_daemon of > _dbus_init_system_log() is a little misleading. In fact, it's is_test. No, if anything it's more like !is_test - dbus-daemon sets it TRUE and the regression test sets it FALSE. It appears I used is_daemon as a short form of "is a daemon whose stderr would go to the Journal if we are running under systemd", which is a bit long for a variable name :-) Rationale for that naming, rather than is_test with the opposite sense: imagine we added another daemon (perhaps a daemon used to implement service activation?) with syslog support, and a command-line tool with syslog support. For correct results, we would probably want the other daemon to call _dbus_init_system_log (TRUE) like dbus-daemon does, and we would want the command-line tool to call _dbus_init_system_log (FALSE) like the tests do. *** This bug has been marked as a duplicate of bug 61399 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.