Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu writes:
On Sat, 16 Feb 2013 15:30:55 -0700, Joel Uckelman said:
The second colon tells procmail to use a lockfile for this recipe, and
the path after that is the lockfile name. Messages can come in any
time; the lockfile ensures that two runs of rcvstore don't step on each
other's toes.
And the exact gotcha involved, from 'nman rcvstore':
BUGS
If you use the "Unseen-Sequence" profile entry, rcvstore could try to
update the context while another
nmh process is also trying to do so. This can cause the context to
become corrupted. To avoid this,
do not use rcvstore if you use the "Unseen-Sequence" profile entry.
What it doesn't mention is that the resulting train wreck can mangle other
sequences in the .mh_seq file as well. Also, should we change that text
to say "do not use rcvstore without an external locking mechanism'? It's
perfectly save to use it from procmail with unseen sequences as long as
procmail does the locking for you, so there's no need to scare off users.
Has anyone ever experienced this theoretical corruption? I haven't. I
use procmail's locking, but then other nmh programs don't use that same
locking mechanism.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
--
Bill Wohler <wohler(_at_)newt(_dot_)com> aka
<Bill(_dot_)Wohler(_at_)nasa(_dot_)gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers