Mailing List Archive: GnuPG: devel

Feature Request: Parseable output if gpg waits for lock

Index | Next | Previous | View Threaded

patrick at mozilla-enigmail

May 8, 2009, 8:01 AM

Post #1 of 3 (649 views)
Permalink

Feature Request: Parseable output if gpg waits for lock

Every now and then some user reports a problem to Enigmail because gpg
is hanging for no obvious reason, which then turns out to be gpg waiting
for the lock files to be deleted. The problem is that the output of gpg
("gpg: waiting for lock (held by NNNN - probably dead) ...") is on
STDERR, and there is no parseable output available via --status-fd X.

Would it be possible to add a status message, such as
[GNUPG:] WAITFORLOCK <pid>

It would enable applications to help users resolve the issue.

Thanks,
Patrick

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

wk at gnupg

May 9, 2009, 11:50 AM

Post #2 of 3 (597 views)
Permalink

Re: Feature Request: Parseable output if gpg waits for lock [In reply to]

On Fri, 8 May 2009 17:01, patrick [at] mozilla-enigmail said:

> Would it be possible to add a status message, such as
> [GNUPG:] WAITFORLOCK <pid>

In theory yes, but I don't like it.

gpg2 already uses a better algorithm to detected stalled processes
holding a lock. For gpg1 I implemented that algorithm a few days ago.

I believe that this will solve the problem.

The original problem was that gpg did not remove the lock file even it
the process claiming to hold the process already died - It could be
mounted on NFS and thus gpg had no chance to reliable detect a stalled
process. The fix implemented stores the node name in the lockfile

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

patrick at mozilla-enigmail

May 11, 2009, 1:23 AM

Post #3 of 3 (597 views)
Permalink

Re: Feature Request: Parseable output if gpg waits for lock [In reply to]

Werner Koch wrote:
> On Fri, 8 May 2009 17:01, patrick [at] mozilla-enigmail said:
>
>> Would it be possible to add a status message, such as
>> [GNUPG:] WAITFORLOCK <pid>
>
> In theory yes, but I don't like it.
>
> gpg2 already uses a better algorithm to detected stalled processes
> holding a lock. For gpg1 I implemented that algorithm a few days ago.
>
> I believe that this will solve the problem.
>
> The original problem was that gpg did not remove the lock file even it
> the process claiming to hold the process already died - It could be
> mounted on NFS and thus gpg had no chance to reliable detect a stalled
> process. The fix implemented stores the node name in the lockfile

Even better, then I won't need to worry anymore :-)

-Patrick

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads