Zbigniew Jędrzejewski-Szmek wrote in message <20141019135812.gu29...@in.waw.pl>: >> > 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.
But isn't using default.target more flexible than basic.target? When basic.target is activated I expect at least socket.target, timers.target and path.target to get activated too; whereas I could imagine an user wanting a completly empty user session [*], which could be done with an empty default.target [#]. [*] I don't use cron anymore, so I don't know if a cron session goes through systemd's pam module in my distribution's pam settings default, but I could imagine that if it were the case we would want a mostly empty user session in this case. [#] With DefaultDependencies=false Right now by default default.target is a symlink to basic.target. It seems natural that the user session starts default.target, like the system session does. Otherwise what would be the meaning of default.target? Something started by the DM when the user logs in rather than by pam? (Actually now that user sessions are getting more used, it would indeed be nice to standardize a name of a target to start when a graphical login is used!) _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel