Bug 3274 - mountd with the new --port option only allows one version to start on a port
mountd with the new --port option only allows one version to start on a port
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-06-04 15:37 EDT by keithu@parl.clemson.edu
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-24 13:07:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description keithu@parl.clemson.edu 1999-06-04 15:37:29 EDT
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-08 22:35:00 EDT
assigned to johnsonm
Comment 2 Stephen John Smoogen 2003-01-24 13:07:56 EST
Bug 3274 is being closed as it seems that this has been fixed in the latest
versions of nfs-utils. 

Note You need to log in before you can comment on or make changes to this bug.