Mailinglist Archive: opensuse-bugs (15074 mails)
| < Previous | Next > |
[Bug 308661] New: NFS4_SUPPORT="no" does not work
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 7 Sep 2007 08:43:20 -0600 (MDT)
- Message-id: <bug-308661-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=308661
Summary: NFS4_SUPPORT="no" does not work
Product: openSUSE 10.2
Version: Final
Platform: i586
OS/Version: openSUSE 10.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: hubba@xxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Customer
Setting NFS4_SUPPORT="no" has no effect in openSuSE 10.2. Even though the
nfsserver start script attempts to echo the correct values inti
/proc/fs/nfsd/versions the start of rpc.nfsd still resets them. - rpc.nfsd has
changed and requires a --no-nfs-version flag during startup otherwise nfsv4
gets re enabled.
I am currently downloading the beta of OpenSuSE 10.3 to see what the state is
on that distro.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Summary: NFS4_SUPPORT="no" does not work
Product: openSUSE 10.2
Version: Final
Platform: i586
OS/Version: openSUSE 10.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: hubba@xxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: Customer
Setting NFS4_SUPPORT="no" has no effect in openSuSE 10.2. Even though the
nfsserver start script attempts to echo the correct values inti
/proc/fs/nfsd/versions the start of rpc.nfsd still resets them. - rpc.nfsd has
changed and requires a --no-nfs-version flag during startup otherwise nfsv4
gets re enabled.
I am currently downloading the beta of OpenSuSE 10.3 to see what the state is
on that distro.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |