gdm registers its login screen as a session because it *is* in essence a regular (if trimmed down) GNOME session. It follows the same logind rules for accessing the display, audio out, etc.
Various desktop services and recently even programs use DBus activation – instead of launching them directly, the consumer app tells DBus to start them (either explicitly or just by trying to talk to the activatable service). So usually you'd see quite a few processes as children of dbus-daemon. * If your distro has switched to the "user bus" model, then dbus-daemon will be running as a systemd --user service, and therefore under user@. * In addition to that, some apps have their own systemd --user services, and DBus uses those to start the app. On Tue, May 23, 2017, 12:12 Олег Гаврильченко <[email protected]> wrote: > > > > > *From:* Олег Гаврильченко [mailto:[email protected]] > *Sent:* Monday, May 22, 2017 6:17 PM > *To:* '[email protected]' < > [email protected]> > *Subject:* Question about systemd sessions > > > > Hello! > > I have question about systemd user sessions. > > When I start my systemd system and login to it I see 2 user sessions: c1 > for user gdm and c2 for my user. I see 2 ([email protected] and > [email protected]) slices and 2 scopes(session-c1.scope and > session-c2.scope). Several programs or deamons reside in [email protected], > other in session-c*.scope. > I don't understend and can not find in documentation, why is there 2 and > not 1 session in system? And why does several programs reside in > [email protected] and other in session-c*.scope? > _______________________________________________ > systemd-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- Mantas Mikulėnas <[email protected]> Sent from my phone
_______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
