Re: Mutt and NFS
On Tue, Apr 03, 2001 at 06:37:22PM -0500, Cheng H. Lee wrote: Hi all, I have a question about running Mutt and NFS together. My current mail setup has procmail delivering mail to ~/mail and mutt reading the mail boxes from there. However, when I'm reading mail from my other box (which has /home mounted from NFS), mutt always open my mail-boxes read-only. I've read the Readme.NFS that came with mutt but would rather not have to mount the entire /home tree with the 'nolock' option. Also, the mutt FAQ says that I can get around this by configuring mutt using the '--with-homespool' option, but I haven't figure out how to do this. Any hints/advice? Both boxes are currently running unstable. i don't have problems with mutt and nfs, other then it not detecting new mail in my marked mailboxes very consistently (i think this is a meta data caching issue) i have verified that locking works correctly on my nfs setup. you should not use kernels older then 2.2.18 on either server or client, and you must run lockd and statd. verify that they are running and things should work correctly. also you should use NFSv3, which you may have to enable experimental options in your kernel config to see. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpRj3uKpreYy.pgp Description: PGP signature
Re: Mutt and NFS
Hello Cheng, * Cheng H. Lee wrote: Hi all, I have a question about running Mutt and NFS together. My current mail setup has procmail delivering mail to ~/mail and mutt reading the mail boxes from there. However, when I'm reading mail from my other box (which has /home mounted from NFS), mutt always open my mail-boxes read-only. I've read the Readme.NFS that came with mutt but would rather not have to mount the entire /home tree with the 'nolock' option. If you use user-space NFS daemon, there's no ther way then to mount with nolock, because Userspace NFS supports not really a good filelocking mechanism. IMHO Also, the mutt FAQ says that I can get around this by configuring mutt using the '--with-homespool' option, but I haven't figure out how to do this. Any hints/advice? Both boxes are currently running unstable. Try to use Kernel NFS. ciao Waldemar -- * Ein gutes Kryptographieprogramm: | (o_ * * http://www.gnupg.org | //\ * * Linux rulez!;-)| V_/_ * * GnuPG-Key: 0xBE21BD90 | Tux: #155220 | ICQ: 64035650 *
Re: Mutt and NFS
On Tue, Apr 03, 2001 at 06:37:22PM -0500, Cheng H. Lee wrote: Hi all, I have a question about running Mutt and NFS together. My current mail setup has procmail delivering mail to ~/mail and mutt reading the mail boxes from there. However, when I'm reading mail from my other box (which has /home mounted from NFS), mutt always open my mail-boxes read-only. I've read the Readme.NFS that came with mutt but would rather not have to mount the entire /home tree with the 'nolock' option. FWIW I'm using mutt with NFS-mounted /var/mail (with nolock) and I haven't lost any mail so far. Also, the mutt FAQ says that I can get around this by configuring mutt using the '--with-homespool' option, but I haven't figure out how to do this. They are referring to compile-time configuration. You'll need to get mutt source package and build it yourself. Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key The wombat is a mixture of chalk and clay used for respiration.-- MegaHal
Re: Mutt and NFS (reprise)
Thanks! It actually works ... only if I mount that directly but it doesn't work if I use amd specifying nolock! I'll figure it out though. Thanks again graziano On Wed, Sep 08, 1999 at 11:51:28PM +0200, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Obi [EMAIL PROTECTED] wrote: Hi all, I know this topic already showed up on the mailing list but the solutions weren't really up to mu case: that is having the file on the local FS!! The situation is /home NFS mounted and mutt refusing to do anything to every file in the home directory because of the dreaded locking mechanism. THe server is a Debian stable machine and the client is an unstable Debian client. What can I do? If you're running a 2.2 kernel on the NFS client, it tries to do NFS locking by default. If your server doesn't support that you have to mount the NFS partition with the option nolock. That's all. Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, The Terrible Thunderlizards
Re: Mutt and NFS (reprise)
I'm having problems with mutt and NFS too. I mount /var/spool/mail by NFS and cant delete mails. How to fix this? Thanks, Paulo Henrique Quoting Obi ([EMAIL PROTECTED]): Thanks! It actually works ... only if I mount that directly but it doesn't work if I use amd specifying nolock! I'll figure it out though. Thanks again graziano On Wed, Sep 08, 1999 at 11:51:28PM +0200, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Obi [EMAIL PROTECTED] wrote: Hi all, I know this topic already showed up on the mailing list but the solutions weren't really up to mu case: that is having the file on the local FS!! The situation is /home NFS mounted and mutt refusing to do anything to every file in the home directory because of the dreaded locking mechanism. THe server is a Debian stable machine and the client is an unstable Debian client. What can I do? If you're running a 2.2 kernel on the NFS client, it tries to do NFS locking by default. If your server doesn't support that you have to mount the NFS partition with the option nolock. That's all. Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, The Terrible Thunderlizards
Re: Mutt and NFS (reprise)
I fixed that with the nolock options as suggested by Miquel. My problem was that mutt couldn't lock the file (you see an error 37), so I couldn't modify the mailbox at all. graziano On Fri, Sep 10, 1999 at 02:18:09PM +, Paulo Henrique Baptista de Oliveira wrote: I'm having problems with mutt and NFS too. I mount /var/spool/mail by NFS and cant delete mails. How to fix this? Thanks, Paulo Henrique Quoting Obi ([EMAIL PROTECTED]): Thanks! It actually works ... only if I mount that directly but it doesn't work if I use amd specifying nolock! I'll figure it out though. Thanks again graziano On Wed, Sep 08, 1999 at 11:51:28PM +0200, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Obi [EMAIL PROTECTED] wrote: Hi all, I know this topic already showed up on the mailing list but the solutions weren't really up to mu case: that is having the file on the local FS!! The situation is /home NFS mounted and mutt refusing to do anything to every file in the home directory because of the dreaded locking mechanism. THe server is a Debian stable machine and the client is an unstable Debian client. What can I do? If you're running a 2.2 kernel on the NFS client, it tries to do NFS locking by default. If your server doesn't support that you have to mount the NFS partition with the option nolock. That's all. Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, The Terrible Thunderlizards
Re: Mutt and NFS (reprise)
In article [EMAIL PROTECTED], Obi [EMAIL PROTECTED] wrote: Hi all, I know this topic already showed up on the mailing list but the solutions weren't really up to mu case: that is having the file on the local FS!! The situation is /home NFS mounted and mutt refusing to do anything to every file in the home directory because of the dreaded locking mechanism. THe server is a Debian stable machine and the client is an unstable Debian client. What can I do? If you're running a 2.2 kernel on the NFS client, it tries to do NFS locking by default. If your server doesn't support that you have to mount the NFS partition with the option nolock. That's all. Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, The Terrible Thunderlizards
