You are not logged in.

#1 2024-07-15 13:57:36

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 179
Website

systemd file and non-default GnuPG home directory

I use a non-default GnuPG home directory, $HOME/.config/gnupg. Gnupg is aware of this folder and works fine.
Reading the wiki about gpg-agent, it is specified that in case of non-default home directory I shall edit the ListenStream  of the systemd .socket files. Concretely, for gpg-agent.socket i need to modify this line:  ListenStream=%f/S.gpg-agent. I can't figure out how to replace the line in my case.
Thank you for help

Offline

#2 2024-07-22 14:12:48

ua4000
Member
Registered: 2015-10-14
Posts: 479

Re: systemd file and non-default GnuPG home directory

Maybe a simpler idea: symbolic link: ln -s
pointing from  $HOME/gnupg to $HOME/.config/gnupg

Offline

#3 2024-07-23 11:35:17

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 12,824

Re: systemd file and non-default GnuPG home directory

gabx wrote:

Concretely, for gpg-agent.socket i need to modify this line:  ListenStream=%f/S.gpg-agent. I can't figure out how to replace the line in my case.

A drop-in file seems the best solution .
Note that the link describes that process for system services, not user services .

Try something like systemctl edit --user gpg-agent.socket --drop-in=change_gpg_listenstream .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB