Bug 4804 - man 5 exports includes link_relative -- exportfs refuses it
Summary: man 5 exports includes link_relative -- exportfs refuses it
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-08-31 14:46 UTC by jonathan
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-09 14:50:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description jonathan 1999-08-31 14:46:38 UTC
The use of the link_relative keyword in /etc/exports
no longer works (it did in RH 5.2).  Yet the man page for
exports still refers to this keyword.

Either the manpage should be altered to remove the text
about this option, or else knfsd and exportfs need to be
taught to make use of it once more.

Jonathan Marsden <jonathan@xc.org>

Comment 1 jonathan 1999-08-31 14:49:59 UTC
This problem remains in knfsd-1.4.7-2 in Rawhide.

Jonathan Marsden <jonathan@xc.org>

Comment 2 Cristian Gafton 2000-08-09 02:34:57 UTC
assigned to johnsonm

Comment 3 jonathan 2000-08-09 14:50:11 UTC
I think Red Hat's bug tracking has let it down somehow.
This problem was reported a year ago for RH 6.0.
It was long since fixed (in 6.1 or 6.2, I forget which).
Yet now it is being assigned as a Pinstripe Beta bug?  Why?

I recommend this be closed as fixed.
The link_relative keyword is no longer in the man 5 exports page.

Jonathan Marsden <jonathan@xc.org>


Comment 4 Karsten Hopp 2000-08-14 12:32:40 UTC
link_relative is no longer supported. The reference in the manpage
has been removed


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