Bug 11791

Summary: lockd: failed to monitor 10.0.0.1
Product: [Retired] Red Hat Linux Reporter: Giovanni <cedatec>
Component: nfs-utilsAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-18 17:30:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Giovanni 2000-05-31 14:58:49 UTC 
hi,
PC running RH6.0 acts as an NFS server. Another PC, with RH6.1 mounts a
drive from RH6.0. Mount works fine.
Problems with file locking between the two. (setiathome refuses to execute
in RH6.1 client against mounted NFS drive from RH6.0 server).

On RH6.1,after boot, on tty0, I find the line:

machine login: lockd: failed to monitor 10.0.0.1

where 10.0.0.1 is the RH6.0 NFS server.

Tried 'man lockd'. No entry for lockd.

So, what's lockd ? Wath is it good for?

BTW, I can ping RH6.0 NFS server from RH6.1 client, both by IP address and
by name.

Thank You

Giovanni (cedatec)
Comment 1 Cristian Gafton 2000-08-09 02:34:50 UTC 
assigned to johnsonm
Comment 2 Alan Cox 2000-08-18 17:30:29 UTC 
It tries to do NFS locking with the 6.0 box which didnt support it so couldnt
monitor it
Thats fine
Comment 3 Alan Cox 2000-08-18 17:30:41 UTC 
It tries to do NFS locking with the 6.0 box which didnt support it so couldnt
monitor it
Thats fine