On Sun, 13 Feb 2000, Martin Bertilsson Haagen wrote:
> lockd: failed to monitor 192.168.2.1
> fcntl: No locks available (errno 37)
> I have used this NFS configuration for quite a while without any
> problems at all, so my conclutions is that it is mutt thats causing
> it.
> Is there any way to fix this?
You didn't tell us what operation system and what NFS server you are
using on the server. In the header I read "Linux 2.2.12", so this
seems to be your client machine.
Wild guess: You are using an NFS server which doesn't support
locking (like the Linux userspace nfsd). In this case you have to
tell your client machine (Linux 2.2.10, which has NFS locking switched
on by default), to mount the NFS filesystem with locking disabled.
For this you have to add the option "nolock" to the entry in your
fstab. Then mutt won't complain about locks not being available.
*ATTENTION* You should upgrade your client kernel to at least
*ATTENTION* 2.2.13, because the NFS caching in 2.2.x (x<=12) is
*ATTENTION* broken when you are using "nolock", which leads to mail
*ATTENTION* loss, if client and server are writing to the same file!
To get rid of all these problems, you can alternatively install a nfs
server with locking support on the server like the Linux knfsd.
Ciao
Roland
--
* [EMAIL PROTECTED] * http://www.spinnaker.de/ *
