2015-01-30 9:30 GMT+01:00 Simon McVittie <simon.mcvit...@collabora.co.uk>: > In principle, a PAM module or something could ensure that we have a > dbus-daemon per login session, even tty/ssh/cron login sessions > (which all go through PAM). In practice, nobody has ever cared enough to > implement this, so we're left with D-Bus autolaunch, which can't > actually work for tty sessions and had bad side-effects from its > attempts to do so, so I disabled it 3 years ago in favour of > recommending that users requiring a D-Bus session should start their own > and manage its lifetime themselves e.g. with dbus-run-session(1). >
Hi all, I've never understood why the session bus is started through dbus-launch. Leave it to the login manager (not PAM), or provide the socket and activate the session bus only when some app is connecting to it, which can be a graphical session, but may be also a console. Stef _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel