On Wed, 19 Apr 2017 18:53, d...@fifthhorseman.net said: > I wouldn't want to encourage people to restart the daemons -- i'd rather > encourage them to terminate them and let the new versions be restarted
Right. > gpg: WARNING: server 'dirmngr' is older than us (2.1.17 < 2.1.18). Run > 'gpgconf --kill dirmngr' to terminate it. A new instance will be restarted > as needed. We already have some hints messages printed in --verbose mode, like: gpg: further info: Tor is not properly configured So I would suggest to print gpg: further info: A restart can be forced using "gpgconf --kill all" > Alternately, it might be nice for gpg to try to effect the restart > itself (though i worry that could get into a loop, since gpg itself is Not a good idea in case you have other sessions running or you need the cache. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpTU_SsvU0cH.pgp
Description: PGP signature
