On 14 June 2013 12:49, Simon McVittie <s...@debian.org> wrote: > On Fri, 14 Jun 2013 at 12:16:28 +0100, Simon McVittie wrote: >> On Thu, 13 Jun 2013 at 19:23:46 +0100, Dmitrijs Ledkovs wrote: >> > The upstart job attached will continue to honour existing >> > settings for additional parameters from /etc/default/dbus, just like >> > the current init.d script. >> >> Do/should we support that file at all? I can't see anything in dbus-daemon >> --help that you could put there without breaking system integration > > > Similarly, if you disable or alter the pidfile in the XML, sysvinit > and Upstart are not going to work correctly. systemd never needs the > pidfile (because it runs dbus-daemon with --nofork, so it's trivial > to know the pid), so it uses --nopidfile for a small performance boost. >
Upstart doesn't track pidfiles at all. At the moment it's set to fork, but could as well use --nofork & --nopidfile, for what performance boosts its worth. And upstart would then properly collect stdout/stderr into a logfile under /var/log/upstart/dbus.log. That does invalidate my pidfile hack in the postinst though. I guess it does makes sense to trigger it unconditionally as well. Regards Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
