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 with my mail spool under > /var before. In fact, the whole reason for having a separate dotlock > program with its own priv permissions is specifically because of mail > spools under /var instead of $HOME.
I wasn't talking of a separate dotlock program. I just wanted Mutt to use the dotlock mechanism (preferably the internal one). > % MAILPATH="mailbox" > % > % Here, mailbox doesn't correspond to anything. So, is it a problem? > > What if you compile with HOMESPOOL turned off? With --with-homespool: +USE_DOTLOCK MAILPATH="mailbox" Without --with-homespool: -USE_DOTLOCK MAILPATH="" > % 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. > > Sounds good. Well, the lock manager has just been cleaned here, so fcntl is now OK (for the moment). -- Vincent Lef�vre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Math�matiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
