[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Locking In Scripts and nmh Locking
|
From: |
Paul Vixie |
|
Subject: |
Re: [Nmh-workers] Locking In Scripts and nmh Locking |
|
Date: |
Thu, 26 Apr 2012 14:27:40 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 |
On 2012-04-26 12:41 PM, address@hidden 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.