Bug 3274

Summary: mountd with the new --port option only allows one version to start on a port
Product: [Retired] Red Hat Linux Reporter: keithu <keithu>
Component: nfs-utilsAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-24 18:07:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description keithu@parl.clemson.edu 1999-06-04 19:37:29 UTC 
I am grateful for the new knfsd-1.3.3 as it simplifies life
behind our firewall.  Unfortunately, when starting mountd
with the --port option, it attempts to start both version 1
and version 2 of mountd on that port and the daemon does not
seem to be designed to handle both versions on a single
port.  This results in a failed start with an error message
that the address is already in use.  A work around is to
start just the verson 1 server (this seems to be the one
most applications care about), or to use multiple
invocations to get multiple versions (each listening on a
different port).  However, it would be nice for mountd to
maintain the behavior of the user level nfs-server and start
both (all) versions on the single port.
Comment 1 Cristian Gafton 2000-08-09 02:35:00 UTC 
assigned to johnsonm
Comment 2 Stephen John Smoogen 2003-01-24 18:07:56 UTC 
Bug 3274 is being closed as it seems that this has been fixed in the latest
versions of nfs-utils.