Bug 178831

Summary: Unable to configure a NFS share with different settings for different systems
Product: [Fedora] Fedora Reporter: Mike Jang <michael>
Component: system-config-nfsAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
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: 2006-01-24 17:47:19 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 Mike Jang 2006-01-24 17:46:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5

Description of problem:
Can't configure different settings for a share; when I try with NFS, one setting overwrites the other in /etc/exports. 

For example, if I want to configure (ro,sync) for *.example.com and (rw,sync) for Fedora.example.com, I'd go through the Add Share process twice.

The objective is to create the following in /etc/exports:

/mnt/share   *.example.com(ro,sync) Fedora.example.com(rw,sync)

This used to work with older versions of system-config-nfs, well at least on separate lines in /etc/exports, i.e.:

/mnt/share   *.example.com(ro,sync)
/mnt/share   Fedora.example.com(rw,sync)

Version-Release number of selected component (if applicable):
system-config-nfs-1.3.15-1

How reproducible:
Always

Steps to Reproduce:
1.Create a share with one set of NFS settings for one group of computers
2.Create the same share with different settings for a different group of computers
3.
  

Actual Results:  The second share overwrote the first in /etc/exports

Expected Results:  Two different settings for shares

Additional info:

Comment 1 Mike Jang 2006-01-24 17:47:19 UTC
I'm sorry, I accidently clicked twice.

*** This bug has been marked as a duplicate of 178830 ***