rpc.statd port #, and other similar questions

DISCUSSION Steve Wolfe 2 participants 2 messages Sep 4, 2002 – Sep 5, 2002

Subsystems (2)

NFS client NFS server

lore

Share & tools

lore

Steve Wolfe

author

2002-09-04 17:13 UTC #0 lore raw

On some of my NFS client machines, rpc.statd is being started with "-p
777", and on others, it is not. The startup scripts used are the same, and some clients do have different versions of nfs-utils. Kernels are the same (2.4.18). Even when trying various combinations of nfs-utils versions, I cannot duplicate the behaviour on all of the machines.

I can't find reference to "-p 777" anywhere in the startup scripts, or
in the various rpc.* binaries. Can anyone clue me in with where this is coming from?

On a related note, is it possible to make the lock manager to also use a
low-numbered port for firewalling purposes?

steve

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

Neil Brown

2002-09-05 02:29 UTC #1 lore raw

Quoted 3 lines · On Wednesday September 4, [email protected] wrote:

On a related note, is it possible to make the lock manager to also use a
low-numbered port for firewalling purposes?

Kernel parameters: lockd.udpport=778 lockd.tcpport=778 Module parameters: nlm_udpport=778 nlm_tcpport=778

NeilBrown