[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] nmh-1.1-RC4 post /tmp/,LCK.* problem

From: Jeffrey C Honig
Subject: Re: [Nmh-workers] nmh-1.1-RC4 post /tmp/,LCK.* problem
Date: Mon, 14 Nov 2005 10:33:09 -0500

This is an issue with dot locking that I brought up about two years ago,
but apparently never opened a bug for.  This change in behavior is a
good reason not to use dot locking as the default.

I just opened a bug report for it:

I have been successfully using lockf locking over NFS for a couple



--- Begin Message --- Subject: Bug with dot locking in 1.1? Date: Wed, 22 Oct 2003 17:46:49 -0400
When running under mh-e, I set the MHCONTEXT environment variable to
/dev/null.  This prevents my mh-e context from confusing my command line

With 1.1 this breaks things.  With the default dot locking, this causes
lkopen_dot() to call lockit() which tries to mkstemp() a file in /dev
which I'm sure fails due to permission problems.  This results in
lkopen_dot() sleeping and looping.

I understand why this was done, but I think that the ability to set the
context to /dev/null is a useful and not unknown feature.  Any ideas on
how we can insure this continues to work?



Jeffrey C. Honig <address@hidden>
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>

--- End Message ---
Jeffrey C. Honig <address@hidden>
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]