Date: Wed, 15 May 2002 11:35:30 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: "Jack L. Stone" <jackstone@sage-one.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Zapping Email Box Message-ID: <20020515163530.GQ8958@dan.emsphone.com> In-Reply-To: <3.0.5.32.20020515111503.0301aa40@mail.sage-one.net> References: <3.0.5.32.20020515094741.0118be50@mail.sage-one.net> <3.0.5.32.20020515094741.0118be50@mail.sage-one.net> <3.0.5.32.20020515111503.0301aa40@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 15), Jack L. Stone said: > At 10:58 AM 5.15.2002 -0500, Dan Nelson wrote: > > So lock the mailbox while you're messing with it. The procmail > > port provides a "lockfile" command that will dotlock any arbitrary > > file, with special flags for handling /var/mail/$USERNAME. I use > > it in all my mail-archiving scripts. In general, you should lock a > > mailbox any time you read or write to it. > > Yes, you are right.... the "lock" is the answer, and lack of it is > what concerned me about my method..... but I don't use procmail..... > I use Pine... > > I could install procmail I suppose, but just for this one thing seems > overkill. Will the procmail launch by a cron launch... or other > wise??? You don't have to use procmail at all; just install the port and use the lockfile command in your scripts. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020515163530.GQ8958>