I have posted this question to : [EMAIL PROTECTED] with no
response yet.
Any assistance on this would be appreciated.
I noticed that when I set the lockd (lockmngr) ports to a specific static
port that the statd (status) port is set to the same port.
Should I also set statd (status) to a specific unique port different from
the lockd (lockmngr) port ?
Is there any problem with statd (status) using the same port as lockd
(lockmngr) ?
SLES9 SP3 plus maintenance.
My current NFS Server:
linux01:/ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 2 udp 6001 mountd
100005 2 tcp 6001 mountd
100005 3 udp 6001 mountd
100005 3 tcp 6001 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 3 udp 2049 nfs_acl
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100024 1 udp 6002 status
100021 1 udp 6002 nlockmgr
100021 3 udp 6002 nlockmgr
100021 4 udp 6002 nlockmgr
100024 1 tcp 6002 status
100021 1 tcp 6002 nlockmgr
100021 3 tcp 6002 nlockmgr
100021 4 tcp 6002 nlockmgr
100005 1 udp 6001 mountd
linux01:/ #
NFS Client:
linux02:~ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 6002 status
100021 1 udp 6002 nlockmgr
100021 3 udp 6002 nlockmgr
100021 4 udp 6002 nlockmgr
100024 1 tcp 6002 status
100021 1 tcp 6002 nlockmgr
100021 3 tcp 6002 nlockmgr
100021 4 tcp 6002 nlockmgr
linux02:~ #
tia ....................
Regards,
Terry L. Spaulding
[EMAIL PROTECTED]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
