> It is, and always was, designed as a --user daemon, just like the name > suggests, not as a session daemon. With the upcoming kdbus work, > systemd --user will be the creator and owner of the user's bus, and > there can and should only be one per user and no per session.
I understand this. But.. That's sad, when really good user expierence throwed away. Have no idea what to do with per-user daemon, that is unattached to any session. > Apps/services are per user, right, not per session. Currently most apps are per-session, or at least heavily linked with it (connected to keychain manager, i/o console etc) > Right, it's nothing that works out of the box today, but we will get > there. Is there any place where I can get info about expected end point of that process? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
