On Mon, 20.10.14 20:36, Mantas Mikulėnas (graw...@gmail.com) wrote: > On Mon, Oct 20, 2014 at 7:59 PM, Lennart Poettering > <lenn...@poettering.net> wrote: > > > > On Sun, 19.10.14 15:58, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) > > wrote: > > > > > > > PAM creates sessions by calling into systemd's pam-module, which then > > > > > uses CreateSession() (internal api!). This call does not return until > > > > > the job of user@.service is done. `systemd --user` notifies READY=1 > > > > > only after "default.target" is ready. > > > > > > Hm, this seems a bit excessive, because default.target can take > > > a while. basic.target would seem more natural. > > > > Excessive? Why would default.target take so long? Note that this is > > not supposed to pull up a full GNOME session or so. In most cases > > default.target would be very little more than basic.target... > > > > That said, I am not really opposed to changing this to basic.target. The > > important thing I guess is that after login all services are > > connectable, hence socket.target and busnames.target should have been > > reached at least, which basic.target delivers as much as > > default.target does... > > Personal user services (dropbox, krenew, mpd...)?
They should probably adopt socket activation anyway, otherwise they'd be quite annoying on multi-user systems if lingering is used. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
