I think anytime that there is a possibility of multiple processes
writing to the same file, locking should be enableable. Even if
it's a command line switch (everyone likes to say use procmail, but
this is essentially what procmail does: locks file and folders by
default,
Not when
Michael Richardson [EMAIL PROTECTED] wrote:
Aside from trashing sequences (which I've experienced on occasion, no idea
why)
I've run into situations where I wind up doing an inc from two difference
sources into the same folder. Usually due to impatience on my part.
As far as I know, inc
On July 12, 2002 at 10:18, Neil W Rickert wrote:
That should not be possible. I haven't looked at the code. But it
should be opening the file with O_CREAT, which should fail if the
message already exists.
I think you mean O_CREAT|O_EXCL.
Unless there are major code deficiencies,
From: Earl Hood [EMAIL PROTECTED]
Date: Fri, 12 Jul 2002 14:59:12 -0500
It seems that the only real place that locking is needed is
for the .mh_sequences file. I.e. The use of locking can be
limited to areas where there is no non-locking method available
to prevent corruption.
Chris Garrigues [EMAIL PROTECTED] wrote:
I always call rcvstore with this wrapper:
#!/bin/bash
...
and it would be nice if it weren't needed.
I'm not convinced that it is needed.
The only risk is that your sequences might be corrupted. I prefer
that to the problems caused by
Aside from trashing sequences (which I've experienced on occasion, no idea
why)
I've run into situations where I wind up doing an inc from two difference
sources into the same folder. Usually due to impatience on my part.
The result was a mess of two processes using the same message
[In a message on Thu, 11 Jul 2002 14:29:20 EDT,
the pithy ruminations of Michael Richardson were:]
Aside from trashing sequences (which I've experienced on occasion, no idea
why)
I've run into situations where I wind up doing an inc from two difference
sources into the same folder.
From: Randy Primeaux [EMAIL PROTECTED]
Date: Tue, 09 Jul 2002 22:19:00 -0700
Here's a procmail recipe I use, including a procmail lockfile
before rcvstore is called. PATH is on Debian Linux.
PATH=/bin:/usr/bin:/usr/bin/mh:/usr/lib/mh:/etc/nmh:/usr/local/bin
LOCKEXT=.lock
:0 w:
Chris Garrigues [EMAIL PROTECTED] wrote:
I always call rcvstore with this wrapper:
#!/bin/bash
...
and it would be nice if it weren't needed.
I'm not convinced that it is needed.
The only risk is that your sequences might be corrupted. I prefer
that to the problems caused by stuck locks.
From: Neil W Rickert [EMAIL PROTECTED]
Date: Wed, 10 Jul 2002 10:16:03 -0500
Chris Garrigues [EMAIL PROTECTED] wrote:
I always call rcvstore with this wrapper:
#!/bin/bash
...
and it would be nice if it weren't needed.
I'm not convinced that it is needed.
The only risk is
I'm just a lurker here, but I'd like to say that I'm glad to see some work
being done to nmh once again.
I lurk because my C skills are poor, but that doesn't mean I can't put in a
request for those who have better C skills.
I always call rcvstore with this wrapper:
#!/bin/bash
11 matches
Mail list logo