Messages in this thread | | | Date | Tue, 10 Apr 2001 21:45:16 +0300 (EEST) | From | Jussi Hamalainen <> | Subject | lockd trouble |
| |
I have two PCs running Slackware 7.1. I can't get lockd to work properly with NFS:
Apr 10 21:03:59 sputnik kernel: nsm_mon_unmon: rpc failed, status=-93 Apr 10 21:03:59 sputnik kernel: lockd: cannot monitor xxx.xxx.xxx.xxx Apr 10 21:03:59 sputnik kernel: lockd: failed to monitor xxx.xxx.xxx.xxx
Yet rpcinfo -p gives the following:
magellan:~$ rpcinfo -p mir program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 1024 nlockmgr 100021 3 udp 1024 nlockmgr 100005 1 udp 686 mountd 100005 2 udp 686 mountd 100005 1 tcp 689 mountd 100005 2 tcp 689 mountd 100003 2 udp 2049 nfs 100003 2 tcp 2049 nfs magellan:~$ rpcinfo -p sputnik program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 1024 nlockmgr 100021 3 udp 1024 nlockmgr 100005 1 udp 721 mountd 100005 2 udp 721 mountd 100005 1 tcp 724 mountd 100005 2 tcp 724 mountd 100003 2 udp 2049 nfs 100003 2 tcp 2049 nfs
The NFS share in question is mounted as locking. Every time procmail tries to get a kernel lock for a file in my home directory, I get an error as described above. Both boxes are running exactly the same 2.2.19 kernel. Am I doing something wrong or is this a bug?
-- -=[ Count Zero / TBH - Jussi Hämäläinen - email count@theblah.org ]=-
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |