On Fri, 3 Nov 2017 06:20, robb...@gentoo.org said: > Presently, the code is effectively this: > ...cat-list-of-fingerprints... | xargs gpg --recv > > This has the downside of causing many execs.
Right after a clean startup of your user session you will see these execs: 1. xargs execs gpg 2. gpg execs gpg-agent 3. gpg execs dirmngr If xargs needs to exec another gpg you won't see new execs for gpg-agent or dirmngr. And the startup time of gpg can be neglecated compared to the latency of the keyservers. Or may it be that you are using gpg 1.4 or 2.0? Those invoke keyserver helpers and that may very well be one exec per supplied fingerprint. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpuQqL_bOgma.pgp
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
