Bug 130261 - NFS map_static option not working
Summary: NFS map_static option not working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 1
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-18 15:49 UTC by Don Walters
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-12 19:26:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Don Walters 2004-08-18 15:49:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; .NET 
CLR 1.1.4322)

Description of problem:
I put the following line in /etc/exports...

/home/user1 192.168.0.1(rw,map_static=/etc/exports.map)

When I restart NFS, I get the following error...

exportfs: /etc/exports:1: unknown 
keyword "map_static=/etc/exports.map"

Apparently the map_static keyword isn't recognized.  Removing it 
allows NFS to start normally.


Version-Release number of selected component (if applicable):
nfs-utils-1.0.6-1

How reproducible:
Always

Steps to Reproduce:
1.Add the map_static keywork into /etc/exports
2.Restart NFS (service nfs restart)
    

Actual Results:  Error message

Expected Results:  NFS start normally and allow user mapping

Additional info:

Comment 1 Steve Dickson 2004-10-12 19:26:17 UTC
Was map_static ever supported?

Comment 2 Don Walters 2004-10-12 20:52:09 UTC
Beats me!  I've only been working with RH since rel 9.

My take is... if you don't want to fix it, or don't think it should 
be fixed, the function should probably be removed from the 
documentation.

Comment 3 Steve Dickson 2004-10-12 22:32:57 UTC
Hey Don,

I've looked in the exportfs(8), exports(5) and nfsd(8) man
pages and could not find where map_static was talked about.
What documentation are you refereeing to?



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