SCIENTIFIC-LINUX-USERS Archives

May 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Fri, 4 May 2012 05:48:52 +0900
Reply-To:
Content-Transfer-Encoding:
7bit
Subject:
From:
Content-Type:
text/plain; charset=UTF-8; format=flowed
In-Reply-To:
MIME-Version:
1.0
Comments:
To: SL Users <[log in to unmask]>
Parts/Attachments:
text/plain (22 lines)
>> [root@services sysconfig]# vim nfs
>> #######################################FILE##########################################
>> SECURE_NFS="yes"
>> #
>> # Define which protocol versions mountd
>> # will advertise. The values are "no" or "yes"
>> # with yes being the default
>> MOUNTD_NFS_V1="no"
>> MOUNTD_NFS_V2="no"
>> MOUNTD_NFS_V3="no"
>
> I'm not sure whether this is still the case but you used to need a
> "yes" for one of these because nfsv4 needs mountd to export mounts
> even though mounted isn't used for mounting an export and doesn't need
> to be allowed through the firewall.

Fortunately this is no longer the case -- NFSv4 is much more 
self-contained/simpler than previous versions and a lot of this is due 
to simplification of the formerly bizaar mountd baggage it used to 
carry. Of course, all that goes out the window if you need to export to 
any clients < v4.

ATOM RSS1 RSS2