Paulo Martinez wrote:
Am 29.01.2009 um 19:21 schrieb Andy Feldt:
Folks,
I have updated a couple of test machines to RHEL 5.3 and find that
the mechanism for choosing a fixed TCP port for NFS file locking
has apparently changed. With 5.2, I could set the variable:
LOCKD_TCPPORT
in /etc/sysconfig/nfs and I could add a 'modprobe lockd' statement
in the /etc/init.d/nfslock file (just before the sysctl executions so
that they could work) and all was well.
This no longer works and the output of:
rpcinfo -p localhost | grep lock
shows that nlockmgr is not using the TCP port we specify.
This causes problems with a variety of programs (like Firefox)
for users whose home directories are on an NFS mounted
file system served by a RHEL 5.3 server (with a restrictive
firewall that intends to only allow the minimum of ports
needed).
Has anyone solved this already?
Hi Andy , it seems that while booting the module
is loaded and ignoring /etc/sysconfig/nfs.
Restarting manually with init-scripts (unload the module
before) will take the entries of /etc/sysconfig/nfs.
Anyway - for a persistent solution:
touch /etc/modprobe.d/nfs-lockd
and add
options lockd nlm_udpport=xxxxx nlm_tcpport=xxxxx
into it and finish with
depmod -a
Regards
P.M.
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
Paulo,
Thanks! This works properly (tho' it does require a
reboot since it is not easily possible to unload the
lockd module) and can be incorporated into our
system initialization scripts for new systems.
Andy
--
Andy Feldt
Senior System Support Programmer
Affiliate Assistant Professor
Homer L. Dodge Department of Physics and Astronomy
The University of Oklahoma
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
