Re: "Waiting for lock....." Solved.

2007-04-26 Thread Ismael Valladolid Torres
Werner Koch escribe: > This is to gain exclusive access to that file. It is quite possible > that a second gpg process is running and trying to update trustdb at the > same time. This would lead to data corruption. AFAIK it can also happen if keyrings are placed in a FAT32 partition. You can al

Re: "Waiting for lock....." Solved.

2007-04-26 Thread Werner Koch
On Wed, 25 Apr 2007 21:22, [EMAIL PROTECTED] said: > Now everything works fine, but I would still like to know how and why > such a file 'trustdb.gpg.lock' was created in the first place. This is to gain exclusive access to that file. It is quite possible that a second gpg process is running and

"Waiting for lock....." Solved.

2007-04-25 Thread Charly Avital
My apologies, please disregard my previous query. I found and manually deleted in ~/.gnupg a file named 'trustdb.gpg.lock' Now everything works fine, but I would still like to know how and why such a file 'trustdb.gpg.lock' was created in the first place. Thanks, Charly ___