On Mon 2017-02-06 12:34:36 -0500, Yuri D'Elia wrote: > On Mon, Feb 06 2017, Michael Biebl wrote: >>> These are all single processes just waiting. >>> So for gpg purposes, the agent is working as intended. >>> However, I'm perplexed as of why I have so many running. >> >> I guess all of this could be solved if gnupg-agent was using >> exit-on-idle (with some sensible default for the timeout). Or is there a >> reason why you want/need to keep gnupg-agent running all time? > > To do the right thing, you'd need to consider the current timeout > settings for each key currently in the agent.
Right, the right thing to do there would be to have gpg-agent itself
just terminate quietly and cleanly when all of its caches expire, if
it's not keeping any state. It'll get re-launched anyway when needed.
I've just raised this upstream at:
https://bugs.gnupg.org/gnupg/issue2946
Regards,
--dkg
signature.asc
Description: PGP signature
