On Mon, Aug 21, 2006 at 11:37:49AM +0100, martin f krafft wrote: > also sprach Werner Koch <[EMAIL PROTECTED]> [2006.08.21.1045 +0100]: > > 28203 rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0 > > 28203 unlink("/home/madduck/.gnupg/pubring.gpg.lock") = 0 > > 28203 unlink("/home/madduck/.gnupg/.#lk0x81281d8.lapse.28203") = 0 > > > > and it cleaned up the lock file. The .tmp file won't get cleaned up > > in such a case. > > Ah, good to know. > > > Thus, this does not show your problem > > > > gpg: /home/madduck/.gnupg/pubring.gpg: copy to > > `/home/madduck/.gnupg/pubring.gpg.tmp' failed: file read error gpg: > > error writing keyring `/home/madduck/.gnupg/pubring.gpg': file read > > error > > Well, this is not the actual problem I am trying to isolate, it's > only a secondary one. My actual problem is that GPG truncates my > pubring.gpg every once in a while. And yes, that may well be because > I interrupt it when it takes too long to download a key while > reading mailing lists.
Put this in your gpg.conf: keyserver-options timeout=xxxx xxx is in seconds. The default is 120 seconds. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]