On 2012-04-26 12:41 PM, norm(_at_)dad(_dot_)org wrote:
... that would require locking?
They include adding to mail drops, moving files between and within
folders and editing context files (mostly to rename or remove sequences).
I don't know which of these things require what kinds of locking.
I don't want to learn. And most importantly I shouldn't have to know.
What I need is a single locking mechanism that incorporates all internal
locks and that would allow me to know I wasn't stepping on any nmh things
going on and that they wouldn't mess with me. I understand that this
would often result in unnecessary locking.
this reminds me of the old c-news "lockfile" utility, which would
acquire a lock, run the command you gave it on its command line, then
release the lock, then exit. if it exited prematurely it would also
release the lock.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers