On Thu, 2009-01-29 at 12:21 -0600, Andy Feldt wrote: > 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? >
Try this bug: https://bugzilla.redhat.com/show_bug.cgi?id=434795 looks queued for 5.4 -- Matthew Kent \ SA \ bravenet.com _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
