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

[Colin Guthrie]

Hi,

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

This feels a bit like a "you shouldn't rely on that point in time..."
type answer is warrented, and when e.g. GNOME or KDE sessions fully use
systemd to bring themselves up it won't be an issue, but right now,
systemd --user is started by (I think) PAM.

I want to rely on systemd --user to handle PulseAudio's activation
(ditching the built in stuff) and but I'm worried that e.g. GNOME or KDE
might start up their own session stuff and spawn some PA consuming
process before systemd --user has reached it's sockets.target and is
thus ready and listening on PA's native socket.

Doesn't seem to be a problem on my machine here (it's working really
nicely actually!) but figured I should ask here too.

Cheers

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/