Robert Tarrall <tarrall(_at_)xxxx(_dot_)neighborhoodlink(_dot_)com> wrote:
Support item 103005 (link above) includes a patch to sbr/lock_file.c
which simply skips locking if the file is /dev/null. That's one
solution... a more general solution might be to skip locking if
permissions won't allow the lock file to be created.
An MHCONTEXT file of /dev/null is a special case. But, is it the only
one? There may be other cases where we try to create a dot-lock file
but do not have permissions. We should insure that we handle that
properly. Do we try to lock files that are writable in directories that
are not writable? How do we handle that?
If creation of the dot-lock file fails due to permissions retrying is
not likely to help, we should take a more appropriate action.
Thanks.
Jeff
--
Jeffrey C. Honig <jch(_at_)honig(_dot_)net>
http://www.honig.net/jch
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
http://lists.nongnu.org/mailman/listinfo/nmh-workers