dbus failure to start after crash

[ld-temp-q6x8@…]

There is already a ticket (#14163) related to this issue, but it hasn't been updated in 2 months and I can't figure out how to annotate it. After a forced reboot, dbus doesn't automatically restart because the PID file, /opt/local/var/run/dbus/pid, doesn't get deleted. Since dbus is running as a launchd job, this file isn't needed and shouldn't exist. The launchd item itself and the system.conf files also need to be changed. There's no need for the dbus.wrapper script, which seems to be a relic of pre-launchd times. dbus-daemon should be called directly from org.macports.dbus.plist, and the lines in system.conf that cause it to drop privileges, fork into the background, and write a PID file should be removed. I'll try to attach proposed replacements for org.macports.dbus.plist and system.conf to this ticket. Thanks.

[ld-temp-q6x8@…]

dbus config files

[rhwood@…]

Cc Me!

[rhwood@…]

You may want to engage the upstream dbus developers since they are almost all linux developers and launchd is unique to the Mac OS X.

[vaulse@…]

Replying to rhwood@macports.org:

You may want to engage the upstream dbus developers since they are almost all linux developers and launchd is unique to the Mac OS X.

For that very reason, why would they care? I'm proposing to change the launchd item, which is Mac-specific, and the config file in a Mac-specific way. Only a few lines need to be changed. I've been running dbus this way for months and it works fine.