From: Luke Davis <ldavis@shellworld.net>
To: blinux-list@redhat.com
Subject: Re: pine and filters.
Date: Sat, 5 Oct 2002 04:14:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.44.0210050412120.83530-100000@server1.shellworld.net> (raw)
In-Reply-To: <200210051603.52333.valhalla@computerdatasafe.com.au>
I believe I have seen pine following the ".lock" standard which procmail
uses, and I believe it honors kernel locks, since sendmail has no problems
writing to the mail box concurrantly with pine and procmail.
I suggest you ask on:
procmail@lists.RWTH-Aachen.DE
(think it's a mailman list, so follow those subscription convensions)
Luke
On Sat, 5 Oct 2002, John wrote:
> On Saturday 05 October 2002 15:55, Luke Davis wrote:
> > I do that all of the time. Look into file locking (kernel and lockfiles),
> > if you do not understand why it works without trouble.
>
> I understand those topics. The documentation I've not seen relates to what
> locking conventions PINE follows.
>
> Kernel locks are not necessarily mandatory, and there have been particular
> problems with locking on NFS mounts.
>
> > Needless to say, large numbers of people have procmail deliver to folders
> > while pine is active constantly, and have no problems.
>
> True, I've not heard of problems, but the sceptic in me says that means "I've
> not heard of problems," and not that "there are no problems."
>
> Same applies to other client software that uses mbox-style files.
>
> I used to use cucipop too, and had not heard of problems with it. Indeed, I
> used it because my ISP (a large one by WA standards) did. I quit using it
> when I found it was severely broken - it didn't lock the mailbox.
>
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Nektarios Mallas
` cstrobel
` ddunfee..
` cstrobel
` Luke Davis
` Jude DaShiell
` David Csercsics
` Nektarios Mallas
` David Csercsics
` Gil Andre
` Nicolas Pitre
` Luke Davis
` Sacha Chua
` John
` Luke Davis
` John
` Luke Davis [this message]
` Gil Andre
` Jude DaShiell
` Janina Sajka
` Jude DaShiell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.44.0210050412120.83530-100000@server1.shellworld.net \
--to=ldavis@shellworld.net \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).