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 +0000, 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 (graziano@smtp.ucsd.edu):
> > 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 <cistron.19990908123509.A20086@sport750.mia.duc>,
> > > Obi <graziano@cs.ucsd.edu> 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"
Reply to: