Bob Brewer [2017-01-27 15:40:27Z] wrote:
> I'm running up-to-date Debian Sid and since gnupg-agent was upgraded from
> gnupg-agent:amd64 (2.1.17-3), I have been seeing the following error in
> syslog:
>
> gpg-agent[7545]: can't connect to the SCdaemon: IPC connect call failed
>
> this is repeated every 2 seconds.
>
> I have tried killing gpg-agent with gpgconf --kill gpg-agent but it
> immediately restarts presumably called by systemd but I can't find any
> config files associated with gpg-agent to see where scdaemon is being
> called. scdaemon isn't installed.
If you want to prevent gpg-agent from starting you can do it with this:
$ systemctl --user mask --now gpg-agent.service gpg-agent.socket \
gpg-agent-ssh.socket gpg-agent-extra.socket \
gpg-agent-browser.socket
See /usr/share/doc/gnupg/README.Debian
> Any suggestions where to look for the cause of the syslog error and
> prevent my SSD from being worn out?
To just prevent log spamming I think this will do it: Create file
~/.config/systemd/user/gpg-agent.service.d/logspam.conf with the
following content (without the four-space indentation):
[Service]
StandardOutput=null
StandardError=null
And then:
$ systemctl --user daemon-reload
$ systemctl --user stop gpg-agent.service
--
/// Teemu Likonen - .-.. <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
Attachment:
signature.asc
Description: PGP signature