On Thu, 18 Sep 2008, Eve V. E. Kovacs wrote: > Has anyone tried to fix the ports that nfs uses for its various daemons? > Supposedly, by setting the environmental variables in/etc/sysconfig/nfs, > one can fix the ports on which the daemons listen. > > All of them work except for LOCKD_UDPPORT > No matter what port I set, when the system (SL5.2) boots, it just chooses > some random port for udp lockd. > Has anyone come across this? Any idea why it doesn't work? I came across this whilst trying to understand whilst lockd kept hanging (that turned out to be buzilla #453094 and #459083), although for me LOCKD_TCPPORT is not being honoured either. As I understand it rpcinfo -p | grep nlockmgr and /sbin/sysctl fs.nfs.nlm_tcpport fs.nfs.nlm_udpport should be two ways of reporting the ports that the kernel nfslock daemon uses, but the report different values for me: # /sbin/sysctl fs.nfs.nlm_tcpport fs.nfs.nlm_udpport fs.nfs.nlm_tcpport = 32803 fs.nfs.nlm_udpport = 32769 # rpcinfo -p |grep lock 100021 1 udp 37230 nlockmgr 100021 3 udp 37230 nlockmgr 100021 4 udp 37230 nlockmgr 100021 1 tcp 40626 nlockmgr 100021 3 tcp 40626 nlockmgr 100021 4 tcp 40626 nlockmgr Not sure whether this is a help or a red herring, but my copy of /etc/sysconfig/nfs includes this comment from a colleague: # Older kernels (2.6.18 is OK) don't seem to obey the above, # echo "options lockd nlm_udpport=6667 nlm_tcpport=6667" >> /etc/modprobe.conf # works on those kernels Maybe this feature was new in 2.6.18 with all the patches to the SL5.2 nfs code it has been lost ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [log in to unmask] http://www.dpmms.cam.ac.uk/~werdna