Re: NFS lockd problems
>The problem is that file locking does not work. If I upgrade mutt
>to one of the newer versions (e.g., 1.0pre3-1.2), mutt attempts to
>lock my mailbox even though I'm using Maildir and not mbox format.
>(See bug #44386.) I've also experienced a "hang" when Angband (variants)
>attempt to lock the high score file, which I believe is the same problem
>(no locking over NFS).
>
>So I thought I'd be clever and fix the problem myself by upgrading the
>NFS server box to 2.2.12. That went well enough, but the file locking
>*still* doesn't work.
>
>If I reboot the system, there's a [lockd] process, but locking doesn't
>work.
>
>If I manually stop NFS services (/etc/init.d/nfs-server stop;
>/etc/init.d/nfs-common stop), and kill (-9) the lockd process, then
>I cannot restart lockd. Any attempt to do so gives me this:
>
>dwarf:/home/greg# rpc.lockd
>lockdsvc: Function not implemented
>
>In "strace rpc.lockd":
>
>SYS_169(0x10000, 0xbffff23c, 0, 0x2fe, 0x699) = -1 ENOSYS (Function not implemented)
>
>(or, after upgrading strace:)
>
>nfsservctl(0x10000, 0xbffff25c, 0) = -1 ENOSYS (Function not implemented)
>
>I'm going to try knfs next....
I have heard that file locking is not implemented in the user
level server, but you need the kernel level server instead.
Don't ask me what the lockd deamon is doing... Actually, I am a bit
confused myself.
--
Brian May <bam@snoopy.apana.org.au>
Reply to: