Using loopback pin entry with GnuPG 2.1

[Vinay Sajip]

Dear Werner,

> That is gpg-agent making a connection to itself to see whether its
> socket is still connected to self.  This is done once a minute.

> It seems your gpg is not using that agent.

> You can add "--debug ipc" to gpg to get gpg's site of the communication.

I did that, with no difference. After running my failed tests, I did

$ ps -ef | grep gpg-agent | grep -v grep
vinay     1863  1734  0 19:06 ?        00:00:00 gpg-agent --homedir /home/vinay/.gnupg --use-standard-socket --daemon
vinay     2343  1734 23 19:08 ?        00:00:04 gpg-agent --homedir /home/vinay/projects/python-gnupg/keys --use-standard-socket --daemon
vinay     2368  1734 29 19:08 ?        00:00:04 gpg-agent --homedir /home/vinay/projects/python-gnupg/keys --use-standard-socket --daemon
vinay     2415  1734 43 19:08 ?        00:00:03 gpg-agent --homedir /home/vinay/projects/python-gnupg/keys --use-standard-socket --daemon


Only the first line was present before I ran the tests. After a while, only two lines appear:

$ ps -ef | grep gpg-agent | grep -v grep
vinay     1863  1734  0 19:06 ?        00:00:00 gpg-agent --homedir /home/vinay/.gnupg --use-standard-socket --daemon
vinay     2415  1734  1 19:08 ?        00:00:03 gpg-agent --homedir /home/vinay/projects/python-gnupg/keys --use-standard-socket --daemon


I don't understand what invokes the additional gpg-agent invocations. The watchgnupg program only connects to the first agent (process 1863 above).

I appreciate your help.

Regards,

Vinay Sajip