bug#27620: systemd environment SSH_AUTH_SOCK in emacs.service

bug#27620: systemd environment SSH_AUTH_SOCK in emacs.service

[Alex Branham]

Hello -

The systemd service file "etc/emacs.service" sets the environmental variable SSH_AUTH_SOCK to "%t/keyring/ssh", which won't work for all users. I think that's a GNOME-specific thing, maybe?

In any case, it overwrites values of SSH_AUTH_SOCK that the user actually sets (in ~/.pam_environment, for example).

Would it be possible to remove that Environment line from the emacs.service file? Instead of guessing at what the value should be, maybe consider adding in the release notes or in the manual (if the systemd service has a section in the manual) that users can set the value of SSH_AUTH_SOCK by either 1) setting it session-wide in ~/.pam_environment, or 2) editing the emacs service file with "systemctl --user edit emacs.service" and adding something like below (replacing "%t/keyring/ssh" with the appropriate value):

[Service]
Environment="SSH_AUTH_SOCK=%t/keyring/ssh"

Thanks,
Alex

bug#27620: systemd environment SSH_AUTH_SOCK in emacs.service

[Lars Ingebrigtsen]

Alex Branham <alex.branham@gmail.com> writes:

> The systemd service file "etc/emacs.service" sets the environmental
> variable SSH_AUTH_SOCK to "%t/keyring/ssh", which won't work for all
> users. I think that's a GNOME-specific thing, maybe?
>
> In any case, it overwrites values of SSH_AUTH_SOCK that the user
> actually sets (in ~/.pam_environment, for example).
>
> Would it be possible to remove that Environment line from the
> emacs.service file?

I've now commented it out on the Emacs trunk, and added a comment saying
why.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no