[ic] [PATCH] [RFC] PGP hard failure workaround

John Beima interchange-users@icdevgroup.org
Sat Jun 7 18:58:00 2003


Quoting Jon Jensen <jon@endpoint.com>:

> On Thu, 5 Jun 2003, John Beima wrote:
> 
> > I have no idea why gngpg would "lock" a key when it is encrypting. It
> even
> > creates a lock file for it, in the .gnugpg folder where the key is
> stored.
> 
> Looking at "man gpg", there's a --lock-never option, which is probably 
> dangerous, but if you set the immutable bit (or the equivalent for your 
> system) on the files that take locks, secring.gpg, pubring.gpg, and 
> trustdb.gpg, I bet it'd be ok. Untested, of course. :)
> 
> Jon


Thanks Jon, I wasn't actually looking for a solution, since we just queued our
backups to then do one server after another instead of all of them at once.

But this should solve Dan's original problem.

You may even want to look at adding it to the default gpg call string in
Interchange, or at least a comment for busier sites...

Jon comes to the rescue again...


John Beima