[systemd-devel] Questions regarding dbus started via systemd --user
tomek at pipebreaker.pl
Fri Jan 9 07:26:04 PST 2015
On Fri, Jan 09, 2015 at 09:56:27AM +0000, Colin Guthrie wrote:
> You don't really need to use abstract sockets here, you can use known
> socket paths in $XDG_RUNTIME_DIR these days as we can rely on it.
> As pam_systemd will set XDG_RUNTIME_DIR to /run/user/$UID/ we can easily
> just mandate that ssh agent is always on /run/user/$UID/ssh-agent
> socket, and forgo any env vars.
> We can also then teach ssh-agent to be socket activatable, and then
> simply write ssh-agent.socket and ssh-agent.service systemd units
> accordingly and it will be autolaunched by systemd on-demand. Teach it
> to exit after a timeout and it'll quit and save resources when not
> needed too.
> This is likely the way forward IMO. Ditto for gpg-agent.
> (this isn't really different to what you say in principle, just a little
> detail about the implementation)
For the sake of googlers, there is Envoy (ssh/gpg-agent wrapper with socket activation):
(Fedora user can get RPM from my copr: https://copr.fedoraproject.org/coprs/ttorcz/envoy/ )
Tomasz Torcz To co nierealne -- tutaj jest normalne.
xmpp: zdzichubg at chrome.pl Ziomale na życie mają tu patenty specjalne.
More information about the systemd-devel