On Mon, 14 Aug 2006 14:37, martin f krafft said: > -rw------- 1 madduck madduck 16490496 2006-08-13 14:36 pubring.gpg > -rw------- 1 madduck madduck 3546722 2006-08-14 08:23 pubring.gpg.tmp > -rw------- 1 madduck madduck 17968679 2006-08-12 18:53 pubring.gpg~
FYI: When updating a keyring, gpg works like this: sed -e edit_stuff < pubring.gpg > pubring.gpg.tmp \ && mv pubring.gpg pubring.gpg~ \ && mv pubring.gpg.tmp pubring.gpg Pretty standard me things. The whole thing is locked using a lock file named pubring.gpg.lock. > gpg: /home/madduck/.gnupg/pubring.gpg: copy to > `/home/madduck/.gnupg/pubring.gpg.tmp' failed: file read error gpg: Read errors might happen if another process writes/truncates pubring.gpg while we are editing it. However, the lock should prevent it. Unless someone uses the --lock-never option. An strace should indeed give better insight. Salam-Shalom, Werner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
