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: nmh-workers/$LOCKEXT * ^TO_.*nmh-workers | rcvstore +in-nmh-workers Would that be a possible solution for you? Chris Garrigues writes: > --==_Exmh_-908326259P > Content-Type: text/plain; charset=us-ascii > > 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 > > PATH=/usr/lib/nmh:$PATH > export PATH > > lockfile $HOME/Mail/$1/.lock > echo $@ > rcvstore +"$@" > rm -f $HOME/Mail/$1/.lock > > > and it would be nice if it weren't needed. Is anyone interested in adding fi > le > locking to rcvstore. The lockfile executable that I call comes with procmail > and > I suppose it wouldn't be unreasonable to do the locking in a way that was > compatible with procmail. procmail is under the GPL artistic license, so I g > uess > you can't just borrow the code due to license pollution, but how hard could > lockfile be to implement? > > Chris > > -- > Chris Garrigues http://www.DeepEddy.Com/~cwg/ > virCIO http://www.virCIO.Com > 716 Congress, Suite 200 > Austin, TX 78701 +1 512 374 0500 > > World War III: The Wrong-Doers Vs. the Evil-Doers. > > > > > --==_Exmh_-908326259P > Content-Type: application/pgp-signature > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: Exmh version 2.2_20000822 06/23/2000 > > iD8DBQE9K06zK9b4h5R0IUIRAh42AJ42fi3+QW39/H96+GUfY8N/bftamACfRt/+ > 99bx/OIBtxfreRMT0ip/m2w= > =crF0 > -----END PGP SIGNATURE----- > > --==_Exmh_-908326259P-- -- Randy Primeaux [EMAIL PROTECTED] [EMAIL PROTECTED]
