[SOLVED] no rpc.lockd on slackware 13

nortonlui · 05-22-2010, 05:44 AM

Hi,

I can't mount nfs directory without option "-o nolock"

NFS server is slackware 11 and client is Slackware 13 (full installation).

I tested with Centos 5.4 and works fine. Using which rpc.lockd print is no rpc.lockd and slackware 11 is /usr/sbin/rpc.lockd.

following services starting on client using rc.rpc ( rpc.statd and rpc.portmap )

Thanks,

Norton Luiz.

disturbed1 · 05-22-2010, 06:22 AM

rpc.lockd was removed after Slackware 11.
You need to start /etc/rc.d/rc.rpc

Code:

$ mount backend:/mnt/myth/5TB /mnt/tmp/
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.
$ rpcinfo -p
rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

$ sh /etc/rc.d/rc.rpc start
Starting RPC portmapper:  /sbin/rpc.portmap
Starting RPC NSM (Network Status Monitor):  /sbin/rpc.statd
$
$ mount backend:/mnt/myth/5TB /mnt/tmp/

$ rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  33807  status
    100024    1   tcp  34357  status
    100021    1   udp  48516  nlockmgr
    100021    3   udp  48516  nlockmgr
    100021    4   udp  48516  nlockmgr
    100021    1   tcp  34679  nlockmgr
    100021    3   tcp  34679  nlockmgr
    100021    4   tcp  34679  nlockmgr

Changelog for Slackware 12

Quote:

n/nfs-utils-1.1.0-i486-1.tgz: Upgraded to nfs-utils-1.1.0. This no longer
tries to use "rpc.lockd" (nor contains it), so be sure to upgrade to the new
versions of the init scripts. Thanks to Jonathan Woithe for the hint about
linking with -lnsl after -lwrap, and for passing along a small patch for a
memory leak in mountd.

allend · 05-22-2010, 06:25 AM

The best way is to make /etc/rc.d/rc.nfsd executable with 'chmod +x /etc/rc.d/rc.nfsd'. All the appropriate NFS daemons will then be started at boot time.