Bug 172126 - NFSv3 acl protocol does not register with the local portmapper
NFSv3 acl protocol does not register with the local portmapper
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-10-31 12:44 EST by Steve Dickson
Modified: 2012-06-20 11:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 11:59:09 EDT
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 Steve Dickson 2005-10-31 12:44:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020

Description of problem:
Like Solaris, the nfsacl protocol should register itself with
the local portmapper so rpc pings will show that the
protocol is supported.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpcinfo -t <server> 100227

Actual Results:  rpcinfo: RPC: Program not registered
program 100227 is not available

Expected Results:  program 100227 version 2 ready and waiting
program 100227 version 3 ready and waiting

Additional info:
Comment 1 Jiri Pallich 2012-06-20 11:59:09 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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