[systemd-devel] How soon after login can I rely on systemd --user having reached sockets.target?

Damien Robert damien.olivier.robert at gmail.com
Sun Oct 26 12:47:52 PDT 2014


>From Lennart Poettering, Fri 24 Oct 2014 at 01:09:56 (+0200) :
> So, I really would prefer if this logic wasn't just a "hook", but
> actually the primary action of logging in graphically via a display
> manager.

Ok, and login off would just be something like 'systemctl stop gnome.target'?

> Note though that in the scheme I'd propose for GNOME we wouldn't
> support multiple parallel logins of the same user anymore. Instead, if
> you do this we'd add the seat you are logging into to your existing
> session.

I sometime login from the same seat multiple times (to test my X settings).
But I agree Xephyr would probably be better for this case.

> On multiseat setups you could hence merge multiple seats into
> a single meta-session with the workspace spanning all of the seats if
> you keep logging in with the same user.

I could imagine having several virtual machines that connects via ssh -X to
the main computer to launch graphical sessions (so that there is no need to
install it on the vms); in this case there would be a need to start the
same target but with different displays. And the solution I outlined on my
preceding mail using instances target templates work very well (and it does
since a long time, I was very impressed when I tried it and it worked out
of the box); but having 'hooks' on logind would help a bit.

But this is not really an important feature request for me, it was just an
idea in passing.

-- 
Damien Robert
http://www.normalesup.org/~robert/pro


More information about the systemd-devel mailing list