On Sun, Feb 06, 2005 at 03:13:00AM +0100, Kurt Roeckx wrote: > On Sat, Feb 05, 2005 at 07:51:07PM -0500, David Shaw wrote: > > > > Please try the 1.4.1 release candidate from > > > > ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.1rc1.tar.bz2 > > and > > ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.1rc1.tar.bz2.sig > > > > I believe this bug was already fixed there. > > It now doesn't give the error I reported anymore, but I do not > believe it is fixed. It now shows this after all the rest: > gpg: keyserver timed out > gpg: keyserver refresh failed: keyserver error > > It also says: > gpg: Total number processed: 1170 > > While I was expecting a number in the 2000.
The original problem was a bug, but believe it or not, this one is a feature. There is a 2-minute timeout on keyserver operations (in your example, 2 minutes per key when doing a --refresh-keys). At a guess, the keyserver from the subkeys.pgp.net rotation you happened to land on was unreachable and didn't answer within 2 minutes. You can change the timeout with the keyserver-option "timeout": i.e. for 1 hour timeout: --keyserver-option timeout=3600 for no timeout at all: --keyserver-option no-timeout David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
