Thanks for the responses............. I just received another response from Neil:
> > I noticed that when I set the lockd ports to specific port that the statd > port is set to the same port. This behavior is specific to SLES9 and SLES10. The kernels in those distributions contain statd functionality and use the same port as lockd uses. > > Should I also set statd to a specific unique port different from lockd ? > You cannot in SLES9/10. On other systems where statd is a user-space program, they cannot be the same port. > Is there any problem with statd using the same port as lockd ? Not on SLES9/10. ----------------------------------------------------------------------------- Alan responds: I think this will cause one of them to fail to function. You can't actually have two processes bind to one port. Even if you could, only one of them would get the connection. This might result in the client lock request going to the statd, or the client status request going to the lockd. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Terry Spaulding Sent: Thursday, August 30, 2007 9:56 AM To: LINUX-390@VM.MARIST.EDU Subject: NFS question on statd and lockd ports .... 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------------- 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