I've been working on autofs, but have run into a problem with nfs that I need to solve first.
On the server, I run the rpcbind and nfs-server scripts. server$: sudo exportfs -av exporting 192.168.0.0/24:/home/vmware On the client, I run the rpcbind and nfs-client scripts. When I try to do an nfs mount I get an error: $ sudo mount -t nfs server:/home/vmware /mnt mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified But statd is running on server and client: client root 21699 1 0 19:28 ? 00:00:00 /usr/sbin/rpc.statd root 21706 1 0 19:29 ? 00:00:00 rpc.statd --no-notify root 21716 1 0 19:36 ? 00:00:00 rpc.statd --no-notify root 628 2 0 Aug24 ? 00:00:00 [nfsiod] server root 420 2 0 Jul03 ? 00:00:00 [nfsiod] root 6333 2 0 14:27 ? 00:00:00 [nfsd] (8 instances) root 6310 1 0 14:27 ? 00:00:00 /usr/sbin/rpc.statd When I try: $ sudo mount -t nfs -o nolock server:/home/vmware /mnt It just hangs. Substituting the ip address for server gives the same result. I do have NFS built into both system kernels: 3.5.2 CONFIG_NFS_FS=y CONFIG_NFS_V2=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set # CONFIG_ROOT_NFS is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set CONFIG_NFS_COMMON=y 3.4.1 CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set CONFIG_NFS_COMMON=y Any ideas? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
