* On Mon, Aug 09, 2010 09:20PM +0100 Chris G (c...@isbd.net) muttered:
> If I open the mbox file with mutt and have mutt displaying the index
> of messages and then the python script tries to write a new message to
> the mailbox I would expect the python script to see the file is locked
> and wait
Quoth Chris G on Monday, 09 August 2010:
> On Mon, Aug 09, 2010 at 02:23:17PM -0700, Chip Camden wrote:
> > Quoth Chris G on Monday, 09 August 2010:
> > > On Mon, Aug 09, 2010 at 09:20:05PM +0100, Chris G wrote:
> > > [snip my mutt/mbox/NFS issues]
> > >
> > > Can someone clarify something for me
On Mon, Aug 09, 2010 at 02:23:17PM -0700, Chip Camden wrote:
> Quoth Chris G on Monday, 09 August 2010:
> > On Mon, Aug 09, 2010 at 09:20:05PM +0100, Chris G wrote:
> > [snip my mutt/mbox/NFS issues]
> >
> > Can someone clarify something for me please, ignore NFS and assume I'm
> > running mutt an
Quoth Chris G on Monday, 09 August 2010:
> On Mon, Aug 09, 2010 at 09:20:05PM +0100, Chris G wrote:
> [snip my mutt/mbox/NFS issues]
>
> Can someone clarify something for me please, ignore NFS and assume I'm
> running mutt and the mail delivery agent on the same system on a local
> hard disk.
>
>
On Mon, Aug 09, 2010 at 09:20:05PM +0100, Chris G wrote:
[snip my mutt/mbox/NFS issues]
Can someone clarify something for me please, ignore NFS and assume I'm
running mutt and the mail delivery agent on the same system on a local
hard disk.
If I open my inbox with mutt and leave it displaying the
On Mon, Jul 22, 2002 at 22:25:58 -0500, Derrick 'dman' Hudson wrote:
> On Mon, Jul 22, 2002 at 04:21:24PM +0200, Vincent Lefevre wrote:
> | On Mon, Jul 22, 2002 at 08:58:42 -0500, Derrick 'dman' Hudson wrote:
> | > On Mon, Jul 22, 2002 at 09:39:52AM +0200, Vincent Lefevre wrote:
> | > | I prefer t
On Mon, Jul 22, 2002 at 04:21:24PM +0200, Vincent Lefevre wrote:
| On Mon, Jul 22, 2002 at 08:58:42 -0500, Derrick 'dman' Hudson wrote:
| > On Mon, Jul 22, 2002 at 09:39:52AM +0200, Vincent Lefevre wrote:
| > | I prefer to keep the mbox format for these mailboxes, because this
| > | makes easier f
On Mon, Jul 22, 2002 at 10:00:09 -0500, David T-G wrote:
> Vincent --
>
> ...and then Vincent Lefevre said...
> %
> % It seems that to force the dotlock locking strategy, one needs to use
> % the --with-homespool option. But then, mutt -v says:
>
> That doesn't make sense; I've had dotlocking w
On Mon, Jul 22, 2002 at 10:25:08 -0500, David T-G wrote:
> Hmmm... I see what you mean; there's not --use-dotlock switch. Well,
> you could
>
> --enable-external-dotlock
>
> to force it, even though you'd then have the external program. [Why
> don't you like that, though?]
An additional --
Vincent --
...and then Vincent Lefevre said...
%
% On Mon, Jul 22, 2002 at 10:00:09 -0500, David T-G wrote:
% >
% > ...and then Vincent Lefevre said...
% > %
% > % It seems that to force the dotlock locking strategy, one needs to use
% > % the --with-homespool option. But then, mutt -v says:
%
Vincent --
...and then Vincent Lefevre said...
%
% It seems that to force the dotlock locking strategy, one needs to use
% the --with-homespool option. But then, mutt -v says:
That doesn't make sense; I've had dotlocking with my mail spool under
/var before. In fact, the whole reason for havin
On Mon, Jul 22, 2002 at 08:58:42 -0500, Derrick 'dman' Hudson wrote:
> On Mon, Jul 22, 2002 at 09:39:52AM +0200, Vincent Lefevre wrote:
> | I prefer to keep the mbox format for these mailboxes, because this
> | makes easier for other operations (like grepping or copying them).
>
> grep -r
>
On Mon, Jul 22, 2002 at 09:39:52AM +0200, Vincent Lefevre wrote:
| On Mon, Jul 22, 2002 at 16:49:09 +1000, David Clarke wrote:
| > Perhaps try maildir mailboxes for the mailboxes on NFS, that should help
| > prevent problems with locking.
|
| I prefer to keep the mbox format for these mailboxes,
On Mon, Jul 22, 2002 at 16:49:09 +1000, David Clarke wrote:
> Perhaps try maildir mailboxes for the mailboxes on NFS, that should help
> prevent problems with locking.
I prefer to keep the mbox format for these mailboxes, because this
makes easier for other operations (like grepping or copying th
On Mon, 22 Jul 2002, Vincent Lefevre wrote:
> Note that my only spool mailbox is an IMAP mailbox. But I need a locking
> strategy for the postpone and archive mailboxes (under NFS). As fcntl is
> not reliable here, I think I'll disable it and use dotlocking only.
>
Perhaps try maildir mailboxes
> >So I recompiled: ./configure --with-flock --enable-nfs-fix
> Don't use flock for locking mail folders accessed via NFS. Fcntl
> was the right thing to do. I'd guess that some part of your NFS
> locking is screwed up.
For the benefit of the archives, I resolved the issue by disabling both
Steve, et al --
...and then Steve Kennedy said...
% On Mon, Dec 03, 2001 at 07:45:45PM -0500, David T-G wrote:
%
% > % I would not design a production quality mail setup that relied on it
% > % if that is what you are asking.
% > Well, that's one way to answer it :-) I don't know enough to know
On Mon, Dec 03, 2001 at 07:45:45PM -0500, David T-G wrote:
> % I would not design a production quality mail setup that relied on it
> % if that is what you are asking.
> Well, that's one way to answer it :-) I don't know enough to know
> whether there are "right" and "wrong" ways to implement NF
On 2001-12-03 13:36:30 -0600, Aaron Goldblatt wrote:
>So I recompiled: ./configure --with-flock --enable-nfs-fix
Don't use flock for locking mail folders accessed via NFS. Fcntl
was the right thing to do. I'd guess that some part of your NFS
locking is screwed up.
What kind of NFS server a
Cliff --
...and then Cliff Sarginson said...
% On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote:
% >
% > ...and then Cliff Sarginson said...
% > % File Locking + NFS = very bad news
...
% > % It is inherently unreliable.
% >
% > Always?
% >
% I would not design a production quality ma
On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote:
> Cliff --
>
> ...and then Cliff Sarginson said...
> % File Locking + NFS = very bad news
>
> Agreed. If he has to use an mbox, though, he may not have many choices
> (my drop-in-mbox+run-razor+move-to-maildir kludge being one of them).
Cliff --
...and then Cliff Sarginson said...
% File Locking + NFS = very bad news
Agreed. If he has to use an mbox, though, he may not have many choices
(my drop-in-mbox+run-razor+move-to-maildir kludge being one of them).
%
% It is inherently unreliable.
Always?
%
% --
% Regards
% Clif
File Locking + NFS = very bad news
It is inherently unreliable.
--
Regards
Cliff
Aaron --
...and then Aaron Goldblatt said...
% > mutt -v
%
% Okay.
%
% bash-2.05$ mutt -v
% Mutt 1.3.24i (2001-11-29)
...
% -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE
% +USE_FCNTL -USE_FLOCK
...
So that tells us how you can lock. Good.
%
%
% So I recompiled: ./configure -
> mutt -v
Okay.
bash-2.05$ mutt -v
Mutt 1.3.24i (2001-11-29)
Copyright (C) 1996-2001 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for de
Aaron --
...and then Aaron Goldblatt said...
% I'm having an oddball problem with locking. Mutt 1.3.24i on RedHat 7.2
% Linux 2.4.16. The mailboxes in question are mbox format on an NFS
% server running Slackware 8.0 Linux 2.4.16.
...
% There are no obvious conflicts in /var/lock/. Manually op
Mike --
...and then Mike A. Oligny said...
% Is there any way to have Mutt warn me if I am opening a second
% session? I find sometimes flags don't get updated because I've
In general, no; mutt not only doesn't care but in fact handles multiple
"sessions", or copies running against the same mai
Maybe this seems a little obvious, but you could invoke mutt via a
wrapper shell script. It would be very, very simple.
* if exists $lockfile
echo "warning"; exit;
* else:
touch $lockfile; /usr/bin/real-mutt; rm $lockfile
I dont think this functionality exists internally, maybe I'm wron
Mike A. Oligny <[EMAIL PROTECTED]> said something to this effect on 11/26/2001:
> Is there any way to have Mutt warn me if I am opening a second
> session? I find sometimes flags don't get updated because I've
> had two or three copies of the client running unintentionally...
> (I know--don't do
29 matches
Mail list logo