Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / nfs-server / draft / man5 / exports.5

.\"
.\" Original manual page is a part of nfs-server package.
.\" Following is a exerpt from README of version 2.2beta47.
.\" 
.\" 7.  Copyright
.\" 
.\" Much of the code in this package was originally  written  by
.\" Mark Shand, and is placed under the following copyright:
.\" 
.\"    This  software may be used for any purpose provided
.\"    the above  copyright  notice  is  retained.  It  is
.\"    supplied  as  is,  with  no warranties expressed or
.\"    implied.
.\" 
.\" Other code, especially that written by Rick Sladkey and some
.\" replacement routines included from the GNU libc, are covered
.\" by the GNU General Public License, version 2,  or  (at  your
.\" option) any later version.
.\" 
.\" Japanese Version Copyright (c) 1997 ISHIOKA Takashi
.\"         all rights reserved.
.\" Translated Mon Sep  8 14:02:18 1997
.\"         by ISHIOKA Takashi
.\" Mon Feb  9 15:16:20 1998: correction
.\" Modified Wed 11 Nov 1998 by NAKANO Takeo <nakano@apm.seikei.ac.jp>
.\" Updated & Modified Sun Jan 27 17:30:35 JST 2002
.\"         by Yuichi SATO <ysato@h4.dion.ne.jp>
.\" Modified Tue Feb 19 19:06:53 JST 2002 by Yuichi SATO
.\"
.TH EXPORTS 5 "11 August 1997"
.UC 5
.\"O .SH NAME
.\"O exports \- NFS file systems being exported
.SH ̾Á°
exports \- ¥¨¥¯¥¹¥Ý¡¼¥È (export) ¤µ¤ì¤ë NFS ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à
.\"O .SH SYNOPSIS
.SH ½ñ¼°
.B /etc/exports
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O The file
.\"O .I /etc/exports
.\"O serves as the access control list for file systems which may be
.\"O exported to NFS clients.  It it used by both the NFS mount daemon,
.\"O .IR mountd (8)
.\"O and the NFS file server daemon
.\"O .IR nfsd (8).
.I /etc/exports
¥Õ¥¡¥¤¥ë¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¢¥¯¥»¥¹¥³¥ó¥È¥í¡¼¥ë¥ê¥¹¥È¤Ç¡¢
¤É¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò NFS ¥¯¥é¥¤¥¢¥ó¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È (export) ¤·¤Æ¤è¤¤¤«¡¢
¤È¤¤¤¦¾ðÊó¤òÍ¿¤¨¤ë¡£
¤³¤ì¤Ï NFS mount ¥Ç¡¼¥â¥ó
.BR mountd (8)
¤Ê¤é¤Ó¤Ë
NFS file server ¥Ç¡¼¥â¥ó
.BR nfsd (8)
¤ÎÁÐÊý¤ÇÍѤ¤¤é¤ì¤ë¡£
.PP
.\"O The file format is similar to the SunOS
.\"O .I exports
.\"O file, except that several additional options are permitted.  Each line
.\"O contains a mount point and a list of machine or netgroup names allowed
.\"O to mount the file system at that point.  An optional parenthesized list
.\"O of mount parameters may follow each machine name.  Blank lines are
.\"O ignored, and a # introduces a comment to the end of the line. Entries may
.\"O be continued across newlines using a backslash.
¤³¤Î¥Õ¥¡¥¤¥ë¤Î½ñ¼°¤Ï SunOS ¤Î
.I exports
¥Õ¥¡¥¤¥ë¤È¤Û¤ÜƱ¤¸¤Ç¤¢¤ë¡£¤¿¤À¤·»ØÄê¤Ç¤­¤ë¥ª¥×¥·¥ç¥ó¤¬
¤¤¤¯¤Ä¤«Äɲ䵤ì¤Æ¤¤¤ë¡£
¤½¤ì¤¾¤ì¤Î¹Ô¤Ë¤Ï¡¢¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤È¡¢
¤½¤Î¥Ý¥¤¥ó¥È¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤Ç¤­¤ë
¥Þ¥·¥ó¤ä¥Í¥Ã¥È¥°¥ë¡¼¥×¤Î¥ê¥¹¥È¤¬½ñ¤«¤ì¤Æ¤¤¤ë¡£
¥Þ¥¦¥ó¥È¥Ñ¥é¥á¡¼¥¿¤Î¥ê¥¹¥È¤ò³ç¸Ì¤Ç¤¯¤¯¤Ã¤¿¤â¤Î¤ò¡¢
¤½¤ì¤¾¤ì¤Î¥Þ¥·¥ó¤Î̾Á°¤Î¸å¤ËÃÖ¤¯¤³¤È¤â¤Ç¤­¤ë¡£
¶õ¹Ô¤Ï̵»ë¤µ¤ì¡¢# °Ê¹ß¹ÔËö¤Þ¤Ç¤Ï¥³¥á¥ó¥È¤È¤ß¤Ê¤µ¤ì¤ë¡£
¹ÔËö¤Ë¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤ò¤ª¤±¤Ð¡¢¥¨¥ó¥È¥ê¤Ï¼¡¤Î¹Ô¤Ë·Ñ³¤Ç¤­¤ë¡£
.PP
.\"O .SS Machine Name Formats
.SS ¥Þ¥·¥ó̾¤Î¥Õ¥©¡¼¥Þ¥Ã¥È
.\"O NFS clients may be specified in a number of ways:
NFS ¥¯¥é¥¤¥¢¥ó¥È¤Ï¤¤¤í¤¤¤í¤ÊÊýË¡¤Ç»ØÄê¤Ç¤­¤ë¡£
.IP "single host
.\"O This is the most common format. You may specify a host either by an
.\"O abbreviated name recognizued be the resolver, the fully qualified domain
.\"O name, or an IP address.
¤³¤ì¤Ï¤â¤Ã¤È¤âÉáÄ̤Υե©¡¼¥Þ¥Ã¥È¤Ç¤¢¤ë¡£¥Û¥¹¥È¤Î»ØÄê¤Ë¤Ï¡¢
¥ì¥¾¥ë¥Ð¤¬Ç§¼±¤Ç¤­¤ë¾Êά·Á¡¢FQDN¡¢IP ¥¢¥É¥ì¥¹¤Î¤É¤ì¤òÍѤ¤¤Æ¤â¤è¤¤¡£
.IP "netgroups
.\"O NIS netgroups may be given as
.\"O .IR @group .
.\"O Only the host part of all
.\"O netgroup members is extracted and added to the access list. Empty host
.\"O parts or those containing a single dash (\-) are ignored.
NIS ¤Î¥Í¥Ã¥È¥°¥ë¡¼¥×¤ò
.I @group
¤Î¤è¤¦¤ËÍ¿¤¨¤ë¤³¤È¤¬¤Ç¤­¤ë¡£¥Í¥Ã¥È¥°¥ë¡¼¥×¤Î¤¹¤Ù¤Æ¤Î¥á¥ó¥Ð¡¼¤Î¤¦¤Á¡¢
¥Û¥¹¥È¤ÎÉôʬ¤À¤±¤¬¼è¤ê½Ð¤µ¤ì¡¢¥¢¥¯¥»¥¹¥ê¥¹¥È¤ËÄɲ䵤ì¤ë¡£
¥Û¥¹¥È¤ÎÉôʬ¤¬¶õ¤À¤Ã¤¿¤ê¡¢Ã±°ì¤Î¥À¥Ã¥·¥å (\-) ¤À¤Ã¤¿¤â¤Î¤Ï̵»ë¤µ¤ì¤ë¡£
.\"O .IP "wildcards
.IP ¥ï¥¤¥ë¥É¥«¡¼¥É
.\"O Machine names may contain the wildcard characters \fI*\fR and \fI?\fR.
.\"O This can be used to make the \fIexports\fR file more compact; for instance,
.\"O \fI*.cs.foo.edu\fR matches all hosts in the domain \fIcs.foo.edu\fR. However,
.\"O these wildcard characters do not match the dots in a domain name, so the
.\"O above pattern does not include hosts such as \fIa.b.cs.foo.edu\fR.
¥Þ¥·¥ó̾¤Î»ØÄê¤Ë¤Ï¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤È¤·¤Æ
\fI*\fP ¤È \fI?\fP ¤òÍѤ¤¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¤³¤ì¤é¤ò»È¤¦¤È \fIexports\fR ¥Õ¥¡¥¤¥ë¤ò¥³¥ó¥Ñ¥¯¥È¤Ë¤Ç¤­¤ë¡£
Î㤨¤Ð \fI*.cs.foo.edu\fR ¤Ï¥É¥á¥¤¥ó \fIcs.foo.edu\fR ¤Ë¤¢¤ë
¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¡£
¤¿¤À¤·¡¢¤³¤ì¤é¤Î¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤Ï¥É¥á¥¤¥ó̾¤Î¥É¥Ã¥È (.) ¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Ê¤¤¡£
¤·¤¿¤¬¤Ã¤Æ¾åµ­¤Î¥Ñ¥¿¡¼¥ó¤Ï¡¢¥É¥á¥¤¥óÆâ¤Î
\fIa.b.cs.foo.edu\fR ¤Î¤è¤¦¤Ê¥Û¥¹¥È¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Ê¤¤¡£
.IP "IP networks
.\"O You can also export directories to all hosts on an IP (sub-) network
.\"O simultaneously. This is done by specifying an IP address and netmask pair
.\"O as
.\"O .IR address/netmask .
¥Ç¥£¥ì¥¯¥È¥ê¤ò IP ¤Î (¥µ¥Ö) ¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¸ºß¤¹¤ë¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ë
Ʊ»þ¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¤³¤ì¤Ë¤Ï IP ¥¢¥É¥ì¥¹¤È¥Í¥Ã¥È¥Þ¥¹¥¯¤Î¥Ú¥¢¤ò
.I address/netmask
¤Î¤è¤¦¤Ë»ØÄꤹ¤ì¤Ð¤è¤¤¡£
.TP
.B =public
.\"O This is a special ``hostname'' that identifies the given directory name
.\"O as the public root directory (see the section on WebNFS in
.\"O .BR nfsd (8)
.\"O for a discussion of WebNFS and the public root handle). When using this
.\"O convention,
.\"O .B =public
.\"O must be the only entry on this line, and must have no export options
.\"O associated with it. Note that this does
.\"O .I not
.\"O actually export the named directory; you still have to set the exports
.\"O options in a separate entry.
¤³¤ì¤ÏÆüì¤Ê°ÕÌ£¤ò»ý¤Ä¡Ö¥Û¥¹¥È̾¡×¤Ç¡¢¤½¤ÎÁ°¤ËÍ¿¤¨¤é¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê
¤¬ public root ¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¢¤ë¤³¤È¤ò¼¨¤¹
(WebNFS ¤È public root ¥Ï¥ó¥É¥ë¤Î¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï
.BR nfsd (8)
¤Î WebNFS ¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤Î¤³¤È)¡£
¤³¤Î½ñ¼°¤òÍѤ¤¤ëºÝ¤Ë¤Ï¡¢
.B =public
¤¬¤½¤Î¹Ô¤Ç¤ÎÍ£°ì¤Î¥Û¥¹¥È̾¥¨¥ó¥È¥ê¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¤Þ¤¿¥¨¥¯¥¹¥Ý¡¼¥È¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
¤³¤Î»ØÄê¤Ë¤è¤Ã¤Æ¡¢
¥Ç¥£¥ì¥¯¥È¥ê¤¬¼ÂºÝ¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¤ï¤±¤Ç¤Ï\fB¤Ê¤¤\fP¤³¤È¤ËÃí°Õ¤¹¤ë¤³¤È¡£
¥¨¥¯¥¹¥Ý¡¼¥È¥ª¥×¥·¥ç¥ó¤Ï¡¢¤³¤ì¤È¤ÏÊ̤Υ¨¥ó¥È¥ê¤Ç»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¡£
.PP
.\"O The public root path can also be specified by invoking
.\"O .I nfsd
.\"O with the
.\"O .B \-\-public\-root
.\"O option. Multiple specifications of a public root will be ignored.
public root ¥Ñ¥¹¤Ï
.I nfsd
¤ò
.B \-\-public\-root
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æµ¯Æ°¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¤â»ØÄê¤Ç¤­¤ë¡£
public root ¤ÎÊ£¿ô»ØÄê¤Ï̵»ë¤µ¤ì¤ë¡£
.PP
.\"O .SS General Options
.SS °ìÈÌŪ¤Ê¥ª¥×¥·¥ç¥ó
.\"O .IR mountd " and " nfsd
.\"O understand the following export options:
.IR mountd " ¤È " nfsd
¤Ï°Ê²¼¤Î¥¨¥¯¥¹¥Ý¡¼¥È¥ª¥×¥·¥ç¥ó¤ò¼õ¤±ÉÕ¤±¤ë¡£
.TP
.IR secure "\*d
.\"O This option requires that requests originate on an internet port less
.\"O than IPPORT_RESERVED (1024). This option is on by default. To turn it
.\"O off, specify
.\"O .IR insecure .
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢IPPORT_RESERVED (1024) ¤è¤ê¾®¤µ¤Ê
internet ¥Ý¡¼¥È¤«¤éȯ¤·¤¿¥ê¥¯¥¨¥¹¥È¤·¤«¼õ¤±¤Ä¤±¤Ê¤¤¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£
̵¸ú¤Ë¤¹¤ë¤Ë¤Ï
.IR insecure
¤È»ØÄꤹ¤ë¡£
.TP
.IR rw
.\"O Allow the client to modify files and directories. The default is to
.\"O restrict the client to read-only request, which can be made explicit
.\"O by using the
.\"O .IR ro " option.
¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤ë¥Õ¥¡¥¤¥ë¤È¥Ç¥£¥ì¥¯¥È¥ê¤ÎÊѹ¹¤òµö²Ä¤¹¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏÆɤ߹þ¤ß¤Î¥ê¥¯¥¨¥¹¥È¤À¤±¤ËÀ©¸Â¤µ¤ì¤Æ¤¤¤ë¡£
(¤³¤ì¤Ï
.I ro
¥ª¥×¥·¥ç¥ó¤ÇÌÀ¼¨¤·¤¿¾ì¹ç¤âƱ¤¸)¡£
.TP
.I noaccess
.\"O This makes everything below the directory inaccessible for the named
.\"O client.  This is useful when you want to export a directory hierarchy to
.\"O a client, but exclude certain subdirectories. The client's view of a
.\"O directory flagged with noaccess is very limited; it is allowed to read
.\"O its attributes, and lookup `.' and `..'. These are also the only entries
.\"O returned by a readdir.
¤³¤Î¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤¿¥¯¥é¥¤¥¢¥ó¥È¤Ï¡¢
¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¥¢¥¯¥»¥¹¤Ç¤­¤Ê¤¯¤Ê¤ë¡£
¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê³¬Áؤò¥¯¥é¥¤¥¢¥ó¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤È¤­¡¢
ÆÃÄê¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ò½ü¤­¤¿¤¤¾ì¹ç¤Ê¤É¤ËÊØÍø¤Ç¤¢¤ë¡£
noaccess ¥Õ¥é¥°¤¬ÉÕ¤¤¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Î¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¸«¤¨Êý¤Ï¡¢
Èó¾ï¤ËÀ©¸Â¤µ¤ì¤¿¤â¤Î¤È¤Ê¤ë¡£
¥Ç¥£¥ì¥¯¥È¥ê°À­¤È¡¢`.' ¤ª¤è¤Ó `..' ¤Î±ÜÍ÷¤À¤±¤¬µö¤µ¤ì¤ë¡£
readdir ¤ËÂФ·¤ÆÊÖ¤µ¤ì¤ë¥¨¥ó¥È¥ê¤â¤³¤Î 2 ¤Ä¤À¤±¤Ë¤Ê¤ë¡£
.TP
.IR link_relative
.\"O Convert absolute symbolic links (where the link contents start with a
.\"O slash) into relative links by prepending the necessary number of ../'s
.\"O to get from the directory containing the link to the root on the
.\"O server.  This has subtle, perhaps questionable, semantics when the file
.\"O hierarchy is not mounted at its root.
ÀäÂХѥ¹·Á¼°¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤òÁêÂХѥ¹·Á¼°¤Î¥ê¥ó¥¯¤ËÊÑ´¹¤¹¤ë
(ÀäÂХѥ¹·Á¼°¤È¤Ï¡¢¥ê¥ó¥¯¤ÎÆâÍƤ¬ "/" ¤Ç»Ï¤Þ¤ë¤â¤Î¤Ç¤¢¤ë)¡£
ÊÑ´¹¤Ï¼¡¤Î¤è¤¦¤Ë¹Ô¤ï¤ì¤ë¡£
¤Þ¤º¥ê¥ó¥¯¤¬ÃÖ¤«¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î¡¢¥µ¡¼¥Ð¤Î¥ë¡¼¥È¤«¤é¤Î
¿¼¤µ¤ò¼èÆÀ¤¹¤ë¡£¤½¤·¤Æ¤½¤Î¿ô¤À¤± '../' ¤òÀäÂÐ¥ê¥ó¥¯¤ÎÁ°¤ËÉղ乤롣
¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Î¥ë¡¼¥È¤«¤é¤Î°ÌÃÖ¤¬°Û¤Ê¤ë¾ì¹ç¡¢
¤³¤ÎÊÑ´¹¤Ë¤ÏÈù̯¤Ê (¤ª¤½¤é¤¯¾ã³²¤Î¸¶°ø¤È¤Ê¤ë)
¤¢¤¤¤Þ¤¤¤µ¤¬´Þ¤Þ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ë¡£
.TP
.IR link_absolute
.\"O Leave all symbolic link as they are. This is the default operation.
Á´¤Æ¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤½¤Î¤Þ¤Þ¤Ë¤¹¤ë¡£¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤ë¡£
.\"O .SS User ID Mapping
.SS ¥æ¡¼¥¶ ID ¤Î¥Þ¥Ã¥Ô¥ó¥°
.PP
.\"O .I nfsd
.\"O bases its access control to files on the server machine on the uid and
.\"O gid provided in each NFS RPC request. The normal behavior a user would
.\"O expect is that she can access her files on the server just as she would
.\"O on a normal file system. This requires that the same uids and gids are
.\"O used on the client and the server machine. This is not always true, nor
.\"O is it always desirable.
¥µ¡¼¥Ð¥Þ¥·¥ó¾å¤Î¥Õ¥¡¥¤¥ë¤ËÂФ¹¤ë
.I nfsd
¤Ë¤è¤ë¥¢¥¯¥»¥¹¥³¥ó¥È¥í¡¼¥ë¤Ï¡¢
¤½¤ì¤¾¤ì¤Î NFS RPC request ¤ÎºÝ¤ËÍ¿¤¨¤é¤ì¤ë uid ¤È gid ¤Ë´ð¤Å¤¤¤Æ¤¤¤ë¡£
¥æ¡¼¥¶¤ÏÄ̾¥µ¡¼¥Ð¾å¤Ë¤¢¤ë¼«Ê¬¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
¤½¤ì¤¬ÉáÄ̤Υե¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë¤¢¤ë¤Î¤ÈƱÍͤË
¥¢¥¯¥»¥¹²Äǽ¤Ç¤¢¤ë¤³¤È¤ò´üÂÔ¤·¤Æ¤¤¤ë¡£
¤³¤ì¤Ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¾å¤ÇÍѤ¤¤é¤ì¤ë
uid ¤È gid ¤¬¤½¤ì¤¾¤ìƱ¤¸¤Ç¤¢¤ëɬÍפ¬¤¢¤ë¤¬¡¢
¤³¤ì¤Ï¾ï¤Ë¿¿¤Ç¤¢¤ë¤È¤Ï¸Â¤é¤º¡¢Ë¾¤Þ¤·¤¤¤È¤â¸Â¤é¤Ê¤¤¡£
.PP
.\"O Very often, it is not desirable that the root user on a client machine
.\"O is also treated as root when accessing files on the NFS server. To this
.\"O end, uid 0 is normally mapped to a different id: the so-called
.\"O anonymous or
.\"O .I nobody
.\"O uid. This mode of operation (called `root squashing') is the default,
.\"O and can be turned off with
.\"O .IR no_root_squash .
¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¤Î root ¤¬ NFS ¥µ¡¼¥Ð¤Î¥Õ¥¡¥¤¥ë¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤È¤­¡¢
¥µ¡¼¥Ð¤Î root ¤È¤·¤Æ°·¤ï¤ì¤Æ¤·¤Þ¤¦¤Î¤Ï¡¢¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ï˾¤Þ¤·¤¯¤Ê¤¤¡£
¤³¤Î¤¿¤á uid 0 ¤ÏÉáÄ̤ÏÊ̤Πid (anonymous ¤ä
.I nobody
uid) ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤µ¤ì¤ë¡£
¤³¤ÎÆ°ºî¤Ï  `root squashing' ¤È¸Æ¤Ð¤ì¤ë¤¬¡¢¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤ë¡£
.I no_root_squash 
¤ò»È¤¨¤Ð¥ª¥Õ¤Ë¤Ç¤­¤ë¡£
.PP
.\"O By default,
.\"O .I nfsd
.\"O tries to obtain the anonymous uid and gid by looking up user
.\"O .I nobody
.\"O in the password file at startup time. If it isn't found, a uid and gid
.\"O of -2 (i.e. 65534) is used. These values can also be overridden by
.\"O the
.\"O .IR anonuid " and " anongid
.\"O options.
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢
.I nfsd
¤Ïµ¯Æ°»þ¤Ë password ¥Õ¥¡¥¤¥ëÃæ¤Î
.I nobody
¥æ¡¼¥¶¤ò»²¾È¤·¤Æ¡¢
anonymous ¤Î uid ¤È gid ¤òÆÀ¤è¤¦¤È¤¹¤ë¡£
¤â¤·¤½¤ì¤¬¸«¤Ä¤«¤é¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
uid ¤È gid ¤È¤·¤Æ -2 (¤Ä¤Þ¤ê 65534) ¤òÍѤ¤¤ë¡£
¤³¤ì¤é¤Î¿ôÃÍ¤Ï 
.IR anonuid " ¤È " anongid
¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤ÆÊѹ¹¤Ç¤­¤ë¡£
.PP
.\"O In addition to this, 
.\"O .I nfsd
.\"O lets you specify arbitrary uids and gids that should be mapped to user
.\"O nobody as well. Finally, you can map all user requests to the
.\"O anonymous uid by specifying the
.\"O .IR all_squash " option.
¤³¤ì¤Ë²Ã¤¨¡¢
.I nfsd
¤Ë¤è¤Ã¤Æ nobody ¤Ë³ä¤êÅö¤Æ¤ë¤Ù¤­Å¬Åö¤Ê uid ¤È gid ¤È¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤ë¡£
ºÇ¸å¤Ë¡¢
.I all_squash
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ì¤Ð¡¢
Á´¤Æ¤Î user request ¤ò anonymous uid ¤Ë³ä¤êÅö¤Æ¤ë¤³¤È¤â¤Ç¤­¤ë¡£
.PP 
.\"O For the benefit of installations where uids differ between different
.\"O machines, 
.\"O .I nfsd
.\"O provides several mechanism to dynamically map server uids to client
.\"O uids and vice versa: static mapping files, NIS-based mapping, and
.\"O .IR ugidd -based
.\"O mapping.
¥Þ¥·¥ó¤´¤È¤Ë uid ¤¬°Û¤Ê¤ë¤è¤¦¤Ê¾ì¹ç¤Ø¤ÎƳÆþ¤òÍưפˤ¹¤ë¤¿¤á¡¢
.I nfsd
¤Ç¤Ï¥µ¡¼¥Ð¤Î uid ¤ò¥¯¥é¥¤¥¢¥ó¥È¤Î uid ¤Ë (¤¢¤ë¤¤¤Ï¤½¤ÎµÕ¤Ë) 
ưŪ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤¹¤ë¼êË¡¤ò¤¤¤¯¤Ä¤«Ä󶡤·¤Æ¤¤¤ë¡£
ÀÅŪ¤Ê¥Þ¥Ã¥Ô¥ó¥°¥Õ¥¡¥¤¥ë¡¢NIS ¥Ù¡¼¥¹¤Î¥Þ¥Ã¥Ô¥ó¥°¡¢
.I ugidd
¥Ù¡¼¥¹¤Î¥Þ¥Ã¥Ô¥ó¥°¡¢¤Ç¤¢¤ë¡£
.PP
.\"O .IR ugidd -based
.\"O mapping is enabled with the 
.\"O .I map_daemon
.\"O option, and uses the UGID RPC protocol. For this to work, you have to run
.\"O the
.\"O .IR ugidd (8)
.\"O mapping daemon on the client host. It is the least secure of the three methods,
.\"O because by running
.\"O .IR ugidd ,
.\"O everybody can query the client host for a list of valid user names. You
.I ugidd
¥Ù¡¼¥¹¤Î¥Þ¥Ã¥Ô¥ó¥°¤Ï
.I map_daemon
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ UGID RPC ¥×¥í¥È¥³¥ë¤ò»È¤¨¤Ð²Äǽ¤È¤Ê¤ë¡£
¤³¤Î¥×¥í¥È¥³¥ë¤òÆ°¤«¤¹¤Ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ç
.IR ugidd (8)
mapping ¥Ç¡¼¥â¥ó¤òÆ°ºî¤µ¤»¤ëɬÍפ¬¤¢¤ë¡£
¤³¤ì¤Ï 3 ¤Ä¤¢¤ëÊýË¡¤ÎÃæ¤Ç¡¢¥»¥­¥å¥ê¥Æ¥£Åª¤Ë¤ÏºÇ°­¤Ç¤¢¤ë¡£
¤Ê¤¼¤Ê¤é
.I ugidd
¤òÆ°ºî¤µ¤»¤ë¤È¡¢Ã¯¤Ç¤â¥¯¥é¥¤¥¢¥ó¥È¤ËÌ䤤¹ç¤ï¤»¤Æ¡¢
Í­¸ú¤Ê¥æ¡¼¥¶Ì¾¤Î¥ê¥¹¥È¤òÆþ¼ê¤Ç¤­¤Æ¤·¤Þ¤¦¤«¤é¤Ç¤¢¤ë¡£
.\"O can protect yourself by restricting access to
.\"O .I ugidd
.\"O to valid hosts only. This can be done by entering the list of valid
.\"O hosts into the
.\"O .I hosts.allow
.\"O or 
.\"O .I hosts.deny
.\"O file. The service name is
.\"O .IR ugidd .
.\"O For a description of the file's syntax, please read
.\"O .IR hosts_access (5).
.I ugidd
¤Ø¤Î¥¢¥¯¥»¥¹¤òÆÃÄê¤Î¥Û¥¹¥È¤Î¤ß¤ËÀ©¸Â¤·¤Æ¡¢¿È¤ò¼é¤ë¤³¤È¤â¤Ç¤­¤ë¡£
¤³¤ì¤Ë¤Ïµö²Ä¤¹¤ë¥Û¥¹¥È¤Î¥ê¥¹¥È¤ò
.I hosts.allow
¤Þ¤¿¤Ï
.I hosts.deny
¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤¹¤ì¤Ð¤è¤¤¡£¥µ¡¼¥Ó¥¹Ì¾¤Ï
.I ugidd
¤Ç¤¢¤ë¡£¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Îʸˡ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.IR hosts_access (5)
¤ò»²¾È¤·¤Æ¤Û¤·¤¤¡£
.PP
.\"O Static mapping is enabled by using the
.\"O .I map_static
.\"O option, which takes a file name as an argument that describes the mapping.
.\"O NIS-based mapping queries the client's NIS server to obtain a mapping from
.\"O user and group names on the server host to user and group names on the
.\"O client.
ÀÅŪ¤Ê¥Þ¥Ã¥Ô¥ó¥°¤Ï
.I map_static
¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤ÆÆ°ºî¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Þ¥Ã¥Ô¥ó¥°¤òµ­½Ò¤·¤¿¥Õ¥¡¥¤¥ë¤Î̾Á°¤ò°ú¿ô¤Ë¤È¤ë¡£
NIS ¥Ù¡¼¥¹¤Î¥Þ¥Ã¥Ô¥ó¥°¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î NIS ¥µ¡¼¥Ð¤ËÌ䤤¹ç¤ï¤»¤Æ¡¢
¥µ¡¼¥Ð¡¼¥Û¥¹¥È¤Ç¤Î¥æ¡¼¥¶Ì¾¤ª¤è¤Ó¥°¥ë¡¼¥×̾¤«¤é
¥¯¥é¥¤¥¢¥ó¥È¤Ç¤Î¥æ¡¼¥¶Ì¾¤ª¤è¤Ó¥°¥ë¡¼¥×̾¤Ø¤Î¡¢
¥Þ¥Ã¥Ô¥ó¥°¾ðÊó¤òÆþ¼ê¤¹¤ë¡£
.PP
.\"O Here's the complete list of mapping options:
°Ê²¼¤Ë¥Þ¥Ã¥Ô¥ó¥°¥ª¥×¥·¥ç¥ó¤Î´°Á´¤Ê¥ê¥¹¥È¤ò¤¢¤²¤ë:
.TP
.IR root_squash
.\"O Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does
.\"O not apply to any other uids that might be equally sensitive, such as user
.\"O .IR bin .
uid/gid ¤¬ 0 ¤Î¥ê¥¯¥¨¥¹¥È¤ò annonymous uid/gid ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤¹¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢root °Ê³°¤Î uid ¤Ë¤ÏŬÍѤµ¤ì¤Ê¤¤¡£
¾¤Ë¤âÃí°Õ¤¹¤Ù¤­ uid ¤Ï¸ºß¤¹¤ë (Î㤨¤Ð
.I bin 
¤Ê¤É) ¤Î¤Ç¡¢Ãí°Õ¤¹¤ëɬÍפ¬¤¢¤ë¡£
.TP
.IR no_root_squash
.\"O Turn off root squashing. This option is mainly useful for diskless clients.
root squashing ¤ò̵¸ú¤Ë¤¹¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¼ç¤Ë¥Ç¥£¥¹¥¯¥ì¥¹¥¯¥é¥¤¥¢¥ó¥È¤Ë¤È¤Ã¤ÆÊØÍø¤Ç¤¢¤ë¡£
.TP
.IR squash_uids " and " squash_gids
.\"O This option specifies a list of uids or gids that should be subject to
.\"O anonymous mapping. A valid list of ids looks like this:
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢annonymous ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤µ¤ì¤ë
uid ¤ä gid ¤Î¥ê¥¹¥È¤òÌÀ¼¨¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¢¤ë¡£
id ¤Î¥ê¥¹¥È¤È¤·¤Æ¤Ï°Ê²¼¤Î¤è¤¦¤Ê»ØÄ꤬ͭ¸ú¤Ç¤¢¤ë:
.IP
.IR squash_uids=0-15,20,25-50
.IP
.\"O Usually, your squash lists will look a lot simpler.
Ä̾ï¤Î squash ¥ê¥¹¥È¤Ï¤â¤Ã¤È¤º¤Ã¤È´Êñ¤Ê¤â¤Î¤Ë¤Ê¤ë¤À¤í¤¦¤¬¡£
.TP
.IR all_squash
.\"O Map all uids and gids to the anonymous user. Useful for NFS-exported
.\"O public FTP directories, news spool directories, etc. The opposite option
.\"O is 
.\"O .IR no_all_squash ,
.\"O which is the default setting.
Á´¤Æ¤Î uid ¤Ègid ¤ò anonymous ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤¹¤ë¡£
¤³¤ì¤Ï NFS ¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤¿¸ø³« FTP ¥Ç¥£¥ì¥¯¥È¥ê¤ä¡¢
news ¤Î¥¹¥×¡¼¥ë¥Ç¥£¥ì¥¯¥È¥êÅù¤ËÊØÍø¤Ç¤¢¤ë¡£
¤³¤ì¤ÈµÕ¤Î¥ª¥×¥·¥ç¥ó¤Ï
.IR no_all_squash 
¤Ç¤¢¤ê¡¢¤³¤Á¤é¤¬¥Ç¥Õ¥©¥ë¥È¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£
.TP
.IR map_daemon
.\"O This option turns on dynamic uid/gid mapping. Each uid in an NFS request
.\"O will be translated to the equivalent server uid, and each uid in an
.\"O NFS reply will be mapped the other way round. This option requires that
.\"O .IR rpc.ugidd (8)
.\"O runs on the client host. The default setting is
.\"O .IR map_identity ,
.\"O which leaves all uids untouched. The normal squash options apply regardless
.\"O of whether dynamic mapping is requested or not.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï ưŪ¤Ê uid/gid ¤Î¥Þ¥Ã¥Ô¥ó¥°¤òÍ­¸ú¤Ë¤¹¤ë¡£
NFS request Ãæ¤Î¤½¤ì¤¾¤ì¤Î uid ¤Ï¥µ¡¼¥Ð¾å¤ÎÂбþ¤¹¤ë uid ¤ËÊÑ´¹¤µ¤ì¡¢
NFS reply Ãæ¤Î uid ¤Ï¤½¤ì¤¾¤ìµÕ¤ËÊÑ´¹¤µ¤ì¤ë¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤ë¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¥Û¥¹¥È¤Ç
.BR rpc.ugidd (8)
¤¬Æ°ºî¤·¤Æ¤¤¤ë¤³¤È¤¬É¬ÍפǤ¢¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢Á´¤Æ¤Î uid ¤òÊѤ¨¤Ê¤¤
.I map_identity 
¤È¤Ê¤Ã¤Æ¤¤¤ë¡£
ÉáÄ̤Πsquash ¥ª¥×¥·¥ç¥ó¤Ï¡¢
ưŪ¤Ê¥Þ¥Ã¥Ô¥ó¥°¤«Èݤ«¤òµ¤¤Ë¤¹¤ë¤³¤È¤Ê¤¯Å¬ÍѤǤ­¤ë¡£
.TP
.IR map_static
.\"O This option enables static mapping. It specifies the name of the file
.\"O that describes the uid/gid mapping, e.g.
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤ÈÀÅŪ¤Ê¥Þ¥Ã¥Ô¥ó¥°¤¬²Äǽ¤È¤Ê¤ë¡£
uid/gid ¥Þ¥Ã¥Ô¥ó¥°¤¬µ­½Ò¤µ¤ì¤¿¥Õ¥¡¥¤¥ë̾¤ò°Ê²¼¤Î¤è¤¦¤Ë»ØÄꤹ¤ë¡£
.IP
.IR map_static=/etc/nfs/foobar.map
.IP
.\"O The file's format looks like this
¥Õ¥¡¥¤¥ë¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï°Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤¢¤ë¡£
.IP
.nf
.ta +3i
# Mapping for client foobar:
#    remote     local
uid  0-99       -       # squash these
uid  100-500    1000    # map 100-500 to 1000-1400
gid  0-49       -       # squash these
gid  50-100     700     # map 50-100 to 700-750
.fi
.TP
.IR map_nis
.\"O This option enables NIS-based uid/gid mapping. For instance, when
.\"O the server encounters the uid 123 on the server, it will obtain the
.\"O login name associated with it, and contact the NFS client's NIS server
.\"O to obtain the uid the client associates with the name.
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È NIS ¥Ù¡¼¥¹¤Î uid/gid ¥Þ¥Ã¥Ô¥ó¥°¤¬²Äǽ¤È¤Ê¤ë¡£
Î㤨¤Ð¡¢¥µ¡¼¥Ð¤¬ uid 123 ¤Î»ØÄê¤ò¼õ¤±¤ë¤È¡¢
¥µ¡¼¥Ð¤Ï¤Þ¤º¤½¤Î uid ¤ËÂбþ¤¹¤ë¥í¡¼¥«¥ë¤Î¥í¥°¥¤¥ó̾¤òÄ´¤Ù¤ë¡£
¼¡¤Ë NFS ¥¯¥é¥¤¥¢¥ó¥È¤Î NIS ¥µ¡¼¥Ð¤ËÀܳ¤·¤Æ¡¢
¤½¤Î¥í¥°¥¤¥ó̾¤ËÂбþ¤¹¤ë uid ¤ò¼èÆÀ¤¹¤ë¡£
.IP
.\"O In order to do this, the NFS server must know the client's NIS domain.
.\"O This is specified as an argument to the
.\"O .I map_nis
.\"O options, e.g.
¤³¤ì¤ò¹Ô¤¦¤Ë¤Ï¡¢NFS ¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤Î NIS ¥É¥á¥¤¥ó¤ò
ÃΤäƤ¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¤³¤Î¥É¥á¥¤¥ó¤Ï
.I map_nis
¥ª¥×¥·¥ç¥ó¤Î°ú¿ô¤È¤·¤Æ°Ê²¼¤Î¤è¤¦¤Ë»ØÄꤹ¤ë¡£
.IP
.I map_nis=foo.com
.IP
.\"O Note that it may not be sufficient to simply specify the NIS domain
.\"O here; you may have to take additional actions before
.\"O .I nfsd
.\"O is actually able to contact the server. If your distribution uses
.\"O the NYS library, you can specify one or more NIS servers for the
.\"O client's domain in
.\"O .IR /etc/yp.conf .
¤¿¤À¤³¤³¤Ë NIS ¥É¥á¥¤¥ó¤òµ­½Ò¤¹¤ë¤À¤±¤Ç¤Ï¡¢Ä̾ï¤Ï½¼Ê¬¤Ç¤Ï¤Ê¤¤¡£
.I nfsd
¤¬ NIS ¥µ¡¼¥Ð¤Ë¥³¥ó¥¿¥¯¥È¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢
¾¤Îºî¶È¤¬É¬ÍפȤʤë¤À¤í¤¦¡£
ÍøÍѤ·¤Æ¤¤¤ë¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤¬ NYS ¥é¥¤¥Ö¥é¥ê¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
¥¯¥é¥¤¥¢¥ó¥È¤Î¥É¥á¥¤¥ó¤Î¥µ¡¼¥Ð¤ò
.I /etc/yp.conf
¤Ë°ì¤Ä°Ê¾å»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤À¤í¤¦¡£
.\"O If you are using a different NIS library, you may have to obtain a
.\"O special
.\"O .IR ypbind (8)
.\"O daemon that can be configured via
.\"O .IR yp.conf .
¾¤Î NIS ¥é¥¤¥Ö¥é¥ê¤òÍѤ¤¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
.I yp.conf
¤Ë¤è¤Ã¤ÆÀßÄê¤Ç¤­¤ë¤è¤¦¤Ê¡¢Æüì¤Ê
.IR ypbind (8)
¤òÆþ¼ê¤¹¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Ê¤¤¡£
.TP
.\"O .IR anonuid " and " anongid
.IR anonuid " ¤ª¤è¤Ó " anongid
.\"O These options explicitly set the uid and gid of the anonymous account.
.\"O This option is primarily useful for PC/NFS clients, where you might want
.\"O all requests appear to be from one user. As an example, consider the
.\"O export entry for
.\"O .B /home/joe
.\"O in the example section below, which maps all requests to uid 150 (which
.\"O is supposedly that of user joe).
¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤Ï anonymous ¥¢¥«¥¦¥ó¥È¤Î uid ¤È gid ¤òÌÀ¼¨Åª¤Ë¥»¥Ã¥È¤¹¤ë¡£
¤³¤ì¤Ï¡¢Á´¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤¬°ì¿Í¤Î¥æ¡¼¥¶¤«¤é¤Ë¤Ê¤ë¤è¤¦¤Ê
PC/NFS clients ¤Ë¤È¤Ã¤Æ¼ç¤ËÍ­¸ú¤Ç¤¢¤ë¡£
Î㤨¤Ð¡¢°Ê²¼¤Î¡ÖÎã¡×¤Î¥»¥¯¥·¥ç¥ó¤Ç¤Î
.I /home/joe
¤È¤¤¤¦¥¨¥¯¥¹¥Ý¡¼¥È¥¨¥ó¥È¥ê¤ò¸«¤Æ¤Û¤·¤¤¡£
¤³¤ÎÎã¤Ç¤Ï¡¢(joe ¤«¤é¤Î¤â¤Î¤Ç¤¢¤ë¤È»×¤ï¤ì¤ë) Á´¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤¬
uid 150 ¤Ë¥Þ¥Ã¥Ô¥ó¥°¤µ¤ì¤ë¡£
.IP
.\"O .SH EXAMPLE
.SH Îã
.PP
.nf
.ta +3i
# sample /etc/exports file
/               master(rw) trusty(rw,no_root_squash)
/projects       proj*.local.domain(rw)
/usr            *.local.domain(ro) @trusted(rw)
/home/joe       pc001(rw,all_squash,anonuid=150,anongid=100)
/pub            (ro,insecure,all_squash)
/pub/private    (noaccess)
.fi
.PP
.\"O The first line exports the entire filesystem to machines master and trusty.
.\"O In addition to write access, all uid squashing is turned off for host
.\"O trusty. The second and third entry show examples for wildcard hostnames
.\"O and netgroups (this is the entry `@trusted'). The fourth line shows the
.\"O entry for the PC/NFS client discussed above. Line 5 exports the
.\"O public FTP directory to every host in the world, executing all requests
.\"O under the nobody account. The
.\"O .I insecure 
.\"O option in this entry also allows clients with NFS implementations that
.\"O don't use a reserved port for NFS. The last line denies all NFS clients
.\"O access to the private directory.
1 ¹ÔÌܤϡ¢master ¤È trusty ¤ËÂФ·¤Æ¡¢
¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Þ¥¦¥ó¥Èµö²Ä¤ò½Ð¤·¤Æ¤¤¤ë¡£
½ñ¤­¹þ¤ß¤Îµö²Ä¤Ë²Ã¤¨¡¢¤µ¤é¤Ë trusty ¤ËÂФ·¤Æ¤Ï¡¢
¤¹¤Ù¤Æ¤Î uid squashing ¤â̵¸ú¤Ë¤·¤Æ¤¤¤ë¡£
2 ¹ÔÌÜ¤È 3 ¹ÔÌܤϡ¢¥Û¥¹¥È̾¤Ø¤Î¥ï¥¤¥ë¥É¥«¡¼¥É¤ÎÍøÍѤȡ¢
¥Í¥Ã¥È¥°¥ë¡¼¥× (@trusted' ¤Î¥¨¥ó¥È¥ê) ¤ÎÎã¤Ç¤¢¤ë¡£
4 ¹ÔÌܤϡ¢¾å¤Ç½Ò¤Ù¤¿ PC/NFS ¥¯¥é¥¤¥¢¥ó¥ÈÍÑ¥¨¥ó¥È¥ê¤ÎÎã¤Ç¤¢¤ë¡£
5 ¹ÔÌܤϡ¢¸ø³« FTP ¥Ç¥£¥ì¥¯¥È¥ê¤òÀ¤³¦Ãæ¤ÎÁ´¤Æ¤Î¥Û¥¹¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤·¤Æ¤¤¤ë¡£
¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤Ï nobody ¥¢¥«¥¦¥ó¥È¤Ç¼Â¹Ô¤µ¤ì¤ë¡£
¤Þ¤¿¤³¤Î¥¨¥ó¥È¥êÃæ¤Î
.I insecure 
¥ª¥×¥·¥ç¥ó¤Ë¤è¤Ã¤Æ¡¢NFS ÍÑ port ¤ò»È¤ï¤Ê¤¤¤è¤¦¤Ë¼ÂÁõ¤µ¤ì¤¿ NFS
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥¢¥¯¥»¥¹¤âµö²Ä¤·¤Æ¤¤¤ë¡£
ºÇ¸å¤Î¹Ô¤Ç¤Ï¡¢private ¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤ò¤¹¤Ù¤Æ¤Î
¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤ÆµñÈݤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¤¤ë¡£
.\"O .SH CAVEATS
.SH ·Ù¹ð
.\"O Unlike other NFS server implementations, this
.\"O .I nfsd
.\"O allows you to export both a directory and a subdirectory thereof to
.\"O the same host, for instance 
.\"O .IR /usr " and " /usr/X11R6 .
¾¤Î NFS Server ¤Î¼ÂÁõ¤È°ã¤¤¡¢
¤³¤Î
.B nfsd
¤Ç¤Ï¡¢Î㤨¤Ð
.IR /usr " ¤È " /usr/X11R6 
¤Î¤è¤¦¤Ë¡¢¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤È¤ÎξÊý¤ò
Ʊ¤¸¥Û¥¹¥È¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.\"O In this case, the mount options of the most specific entry apply. For
.\"O instance, when a user on the client host accesses a file in 
.\"O .IR /usr/X11R6 ,
.\"O the mount options given in the 
.\"O .I /usr/X11R6 
.\"O entry apply. This is also true when the latter is a wildcard or netgroup
.\"O entry.
¤³¤Î¾ì¹ç¡¢ÆÃÄê¤ÎÅٹ礬¤â¤Ã¤È¤â¹â¤¤¥¨¥ó¥È¥ê¤Î¥Þ¥¦¥ó¥È¥ª¥×¥·¥ç¥ó¤¬Å¬ÍѤµ¤ì¤ë¡£
Î㤨¤Ð¥¯¥é¥¤¥¢¥ó¥È¥Û¥¹¥È¾å¤Î¥æ¡¼¥¶¤¬
.IR /usr/X11R6 
¤Î¥Õ¥¡¥¤¥ë¤Ë¥¢¥¯¥»¥¹¤¹¤ë¾ì¹ç¤Ï¡¢
.I /usr/X11R6 
¤Î¥¨¥ó¥È¥ê¤Ç¤¢¤¿¤¨¤é¤ì¤¿ ¥Þ¥¦¥ó¥È¥ª¥×¥·¥ç¥ó¤¬Å¬ÍѤµ¤ì¤ë¡£
¤³¤Î¥ë¡¼¥ë¤Ï¡¢¥¨¥ó¥È¥ê¤Î¥Û¥¹¥È»ØÄ꤬
¥ï¥¤¥ë¥É¥«¡¼¥É¤ä¥Í¥Ã¥È¥°¥ë¡¼¥×¤Î¤È¤­¤Ë¤âŬÍѤµ¤ì¤ë¡£
.\"O .SH FILES
.SH ¥Õ¥¡¥¤¥ë
/etc/exports
.\"O .SH DIAGNOSTICS
.SH ÊÖ¤êÃÍ
.\"O An error parsing the file is reported using syslogd(8) as level NOTICE from
.\"O a DAEMON whenever nfsd(8) or mountd(8) is started up.  Any unknown
.\"O host is reported at that time, but often not all hosts are not yet known
.\"O to named(8) at boot time, thus as hosts are found they are reported
.\"O with the same syslogd(8) parameters.
.BR nfsd (8)
¤«
.BR mountd (8)
¤¬µ¯Æ°¤·¤Æ¤¤¤ì¤Ð¡¢
¥Õ¥¡¥¤¥ë¤Î²ò¼áÃæ¤Î¥¨¥é¡¼¤Ï¾ï¤Ë
.BR syslogd (8)
¤òÍѤ¤¤ÆÊó¹ð¤µ¤ì¤ë¡£
DAEMON ¤«¤é¤Î NOTICE ¥ì¥Ù¥ë¤È¤Ê¤ë¡£
¤½¤Î¤È¤­¡¢Ì¤ÃΤΥۥ¹¥ÈÁ´¤Æ¤¬Êó¹ð¤µ¤ì¤ë¡£
¤·¤«¤·µ¯Æ°»þ¤Ë¤Ï
.BR named (8)
¤¬Á´¤Æ¤Î¥Û¥¹¥È¤òÃΤé¤Ê¤¤¾ì¹ç¤â¤¢¤ê¤¦¤ë¡£
¤·¤¿¤¬¤Ã¤Æ¥Û¥¹¥È¤¬¸«¤Ä¤«¤ë¤¿¤Ó¤Ë¡¢¤½¤ì¤é¤Ï
.BR syslogd (8)
¤Ë¡¢Æ±¤¸¥Ñ¥é¥á¡¼¥¿¤ÇÊó¹ð¤µ¤ì¤ë¡£
.\"O .SH SEE ALSO
.SH ´ØÏ¢¹àÌÜ 
mountd(8), nfsd(8)