Hi. On Fri, 27 Jan 2017 17:05:42 +0000 Bob Brewer <ipcop-de...@grantura.co.uk> wrote:
> Reco wrote: > > > Hi. > > > > On Fri, 27 Jan 2017 15:40:27 +0000 > > Bob Brewer <debian-u...@grantura.co.uk> 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. > >> > >> Any suggestions where to look for the cause of the syslog error and > >> prevent my SSD from being worn out? > > > > echo disable-scdaemon >> $HOME/.gnupg/gpg-agent.conf > > > > Also, gpg-agent(1). > > > > > > Thanks Reco I had tried logging out but it seems I had to reboot to stop the > error messages. I had missed the reference to "Note, that enabling this > option at runtime does not kill an already forked scdaemon" in the man page. You're welcome. All those options (in gpg-agent(1)) do not apply to running instances of gpg-agent if specified in a configuration file. Reco