--- /dev/null
+.\"
+.\" 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 Sat Jan 12 19:02:55 JST 2002
+.\" by Yuichi SATO <ysato@h4.dion.ne.jp>
+.\" Modified Wed 9 Oct 2002 by NAKANO Takeo <nakano@apm.seikei.ac.jp>
+.\" Updated & Modified Sun 26 Mar 2006 by Yuichi SATO <ysato444@yahoo.co.jp>
+.\"
+.TH EXPORTS 5 "28 October 1999"
+.UC 5
+.\"O .SH NAME
+.\"O exports \- NFS file systems being exported (for Kernel based NFS)
+.SH ̾Á°
+exports \- (¥«¡¼¥Í¥ë¥Ù¡¼¥¹¤Î NFS ¤Ç) ¥¨¥¯¥¹¥Ý¡¼¥È (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 exported to NFS clients. It is used by
+.\"O .IR exportfs (8)
+.\"O to give information to
+.\"O .IR mountd (8)
+.\"O and to the kernel based NFS file server daemon
+.\"O .IR nfsd (8).
+.I /etc/exports
+¥Õ¥¡¥¤¥ë¤Ï¡¢
+NFS ¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ë¤É¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¨¥¯¥¹¥Ý¡¼¥È (export) ¤·¤Æ¤è¤¤¤«¡¢
+¤È¤¤¤¦¥¢¥¯¥»¥¹¥³¥ó¥È¥í¡¼¥ë¥ê¥¹¥È¤òÍ¿¤¨¤ë¡£
+¤³¤ì¤Ï
+.BR exportfs (8)
+¤Ë¤è¤Ã¤Æ»ÈÍѤµ¤ì¡¢NFS ¥Þ¥¦¥ó¥È¥Ç¡¼¥â¥ó
+.BR mountd (8)
+¤È¡¢¥«¡¼¥Í¥ë¥Ù¡¼¥¹¤Î NFS ¥Õ¥¡¥¤¥ë¥µ¡¼¥Ð¥Ç¡¼¥â¥ó
+.BR nfsd (8)
+¤È¤Ë¾ðÊó¤òÍ¿¤¨¤ë¡£
+.PP
+.\"O The file format is similar to the SunOS
+.\"O .I exports
+.\"O file. Each line contains an export point and a whitespace-separated list
+.\"O of clients allowed to mount the file system at that point. Each listed
+.\"O client may be immediately followed by a parenthesized, comma-separated
+.\"O list of export options for that client. No whitespace is permitted
+.\"O between a client and its option list.
+¤³¤Î¥Õ¥¡¥¤¥ë¤Î½ñ¼°¤Ï SunOS ¤Î
+.I exports
+¥Õ¥¡¥¤¥ë¤È»÷¤Æ¤¤¤ë¡£
+¤½¤ì¤¾¤ì¤Î¹Ô¤Ë¤Ï¡¢¥¨¥¯¥¹¥Ý¡¼¥È¥Ý¥¤¥ó¥È¤È¡¢
+¤½¤Î¥Ý¥¤¥ó¥È¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤Ç¤¤ë¥¯¥é¥¤¥¢¥ó¥È¤ò
+¥¹¥Ú¡¼¥¹¤Ç¶èÀڤäƻØÄꤷ¤¿¥ê¥¹¥È¤¬½ñ¤«¤ì¤Æ¤¤¤ë¡£
+¥ê¥¹¥È¤µ¤ì¤¿¥¯¥é¥¤¥¢¥ó¥È¤Îľ¸å¤Ë¤Ï¡¢
+¤½¤Î¥¯¥é¥¤¥¢¥ó¥È¸þ¤±¤Î¥¨¥¯¥¹¥Ý¡¼¥È¥ª¥×¥·¥ç¥ó¤ò¥³¥ó¥Þ¤Ç¶èÀڤäƥꥹ¥È»ØÄꤷ¡¢
+¥ê¥¹¥ÈÁ´ÂΤò³ç¸Ì¤Ç³ç¤Ã¤ÆÃÖ¤¯¤³¤È¤â¤Ç¤¤ë¡£
+¥¯¥é¥¤¥¢¥ó¥È̾¤È¤³¤Î¥ª¥×¥·¥ç¥ó¥ê¥¹¥È¤È¤Î´Ö¤Ë¤Ï¥¹¥Ú¡¼¥¹¤òÆþ¤ì¤Æ¤Ï¤¤¤±¤Ê¤¤¡£
+.PP
+.\"O Blank lines are ignored. A pound sign ("#") introduces a comment to the
+.\"O end of the line. Entries may be continued across newlines using a
+.\"O backslash. If an export name contains spaces it should be quoted using
+.\"O double quotes. You can also specify spaces or other unusual character in
+.\"O the export name using a backslash followed by the character code as three
+.\"O octal digits.
+¶õ¹Ô¤Ï̵»ë¤µ¤ì¡¢# °Ê¹ß¹ÔËö¤Þ¤Ç¤Ï¥³¥á¥ó¥È¤È¤ß¤Ê¤µ¤ì¤ë¡£
+¹ÔËö¤Ë¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤ò¤ª¤±¤Ð¡¢¥¨¥ó¥È¥ê¤Ï¼¡¤Î¹Ô¤Ë·Ñ³¤Ç¤¤ë¡£
+¥¨¥¯¥¹¥Ý¡¼¥È̾¤Ë¶õÇò¤¬´Þ¤Þ¤ì¤ë¾ì¹ç¤Ï¡¢¥À¥Ö¥ë¥¯¥©¡¼¥È¤Ç³ç¤ë¡£
+¥¨¥¯¥¹¥Ý¡¼¥È¥Ñ¥¹Ì¾¤Ë¤Ï¡¢
+¶õÇò¤ä¤½¤Î¾Ä̾ï¤Ï»È¤ï¤ì¤Ê¤¤Ê¸»ú¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤¤ë¡£
+¤³¤Î¤è¤¦¤Êʸ»ú¤ò»È¤¦¾ì¹ç¤Ï¡¢¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Î¸å¤Ë
+3 ·å¤Î 8 ¿Ê¿ô¤Çʸ»ú¥³¡¼¥É¤ò»ØÄꤹ¤ë¡£
+.\"O .PP
+.\"O .SS Machine Name Formats
+.SS ¥Þ¥·¥ó̾¤Î¥Õ¥©¡¼¥Þ¥Ã¥È
+.\"O NFS clients may be specified in a number of ways:
+NFS ¥¯¥é¥¤¥¢¥ó¥È¤Ï¤¤¤í¤¤¤í¤ÊÊýË¡¤Ç»ØÄê¤Ç¤¤ë¡£
+.\"O .IP "single host
+.IP "single host"
+.\"O This is the most common format. You may specify a host either by an
+.\"O abbreviated name recognized be the resolver, the fully qualified domain
+.\"O name, or an IP address.
+¤³¤ì¤Ï¤â¤Ã¤È¤âÉáÄ̤Υե©¡¼¥Þ¥Ã¥È¤Ç¤¢¤ë¡£¥Û¥¹¥È¤Î»ØÄê¤Ë¤Ï¡¢
+¥ì¥¾¥ë¥Ð¤¬Ç§¼±¤Ç¤¤ë¾Êά·Á¡¢FQDN¡¢IP ¥¢¥É¥ì¥¹¤Î¤É¤ì¤òÍѤ¤¤Æ¤â¤è¤¤¡£
+.\"O .IP "netgroups
+.IP "netgroups"
+.\"O NIS netgroups may be given as
+.\"O .IR @group .
+.\"O Only the host part of each
+.\"O netgroup members is consider in checking for membership. 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
+.\"O \fIcs.foo.edu\fR. As these characters also match the dots in a domain
+.\"O name, the given pattern will also match all hosts within any subdomain
+.\"O of \fIcs.foo.edu\fR.
+¥Þ¥·¥ó̾¤Î»ØÄê¤Ë¤Ï¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤È¤·¤Æ \fI*\fP ¤È \fI?\fP ¤ò
+ÍѤ¤¤ë¤³¤È¤¬¤Ç¤¤ë¡£¤³¤ì¤é¤ò»È¤¦¤È \fIexports\fR ¥Õ¥¡¥¤¥ë¤ò¥³¥ó¥Ñ¥¯¥È¤Ë¤Ç¤¤ë¡£
+Î㤨¤Ð \fI*.cs.foo.edu\fR ¤Ï¥É¥á¥¤¥ó \fIcs.foo.edu\fR ¤Ë¤¢¤ë¤¹¤Ù¤Æ¤Î
+¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¡£
+¤³¤ì¤é¤Î¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤Ï¥É¥á¥¤¥ó̾¤Î¥É¥Ã¥È (.) ¤Ë¤â¥Þ¥Ã¥Á¤¹¤ë¤Î¤Ç¡¢
+¤³¤³¤Ç»ØÄꤵ¤ì¤¿¥Ñ¥¿¡¼¥ó¤Ï \fIcs.foo.edu\fR ¤ÎǤ°Õ¤Î¥µ¥Ö¥É¥á¥¤¥óÆâ¤Î
+Á´¤Æ¤Î¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¡£
+.\"O .IP "IP networks
+.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
+.\"O where the netmask can be specified in dotted-decimal format, or as a
+.\"O contiguous mask length (for example, either `/255.255.252.0' or `/22' appended
+.\"O to the network base address result in identical subnetworks with 10 bits of
+.\"O host). Wildcard characters generally do not work on IP addresses, though they
+.\"O may work by accident when reverse DNS lookups fail.
+¥Ç¥£¥ì¥¯¥È¥ê¤ò IP ¤Î (¥µ¥Ö) ¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¸ºß¤¹¤ë¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ë
+Ʊ»þ¤Ë¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤³¤È¤â¤Ç¤¤ë¡£
+¤³¤ì¤Ë¤Ï IP ¥¢¥É¥ì¥¹¤È¥Í¥Ã¥È¥Þ¥¹¥¯¤Î¥Ú¥¢¤ò
+.I address/netmask
+¤Î¤è¤¦¤Ë»ØÄꤹ¤ì¤Ð¤è¤¤¡£
+¤³¤³¤Ç netmask ¤Ï 10 ¿Ê¿ô¤ò¥É¥Ã¥È¤Ç¶èÀڤäƻØÄꤹ¤ë¤³¤È¤â¤Ç¤¤ë¤·¡¢
+Ϣ³¤¹¤ë¥Þ¥¹¥¯¤ÎŤµ¤Ç»ØÄꤹ¤ë¤³¤È¤â¤Ç¤¤ë
+(Î㤨¤Ð¡¢¥Í¥Ã¥È¥ï¡¼¥¯¥Ù¡¼¥¹¥¢¥É¥ì¥¹¤Ë `/255.255.252.0' ¤òÄɲä·¤¿¾ì¹ç¤Ç¤â¡¢
+`/22' ¤òÄɲä·¤¿¾ì¹ç¤Ç¤â¡¢¥Û¥¹¥ÈÉô¤¬ 10 ¥Ó¥Ã¥È¤ÎƱ¤¸¥µ¥Ö¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤Ê¤ë)¡£
+¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤Ï¡¢Ä̾ï IP ¥¢¥É¥ì¥¹¤ËÂФ·¤Æ¤ÏÆ°ºî¤·¤Ê¤¤¡£
+¤¿¤À¤· DNS ¤ÎµÕ°ú¤¤¬¼ºÇÔ¤¹¤ë¤È¡¢¤¿¤Þ¤¿¤ÞÆ°ºî¤·¤Æ¤·¤Þ¤¦¤³¤È¤â¤¢¤êÆÀ¤ë¡£
+'''.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 ¤ÎÊ£¿ô»ØÄê¤Ï̵»ë¤µ¤ì¤ë¡£
+.\"O .PP
+.\"O .SS RPCSEC_GSS security
+.SS RPCSEC_GSS ¥»¥¥å¥ê¥Æ¥£
+.\"O To restrict access to an export using rpcsec_gss security, use the special
+.\"O string "gss/krb5" as the client. It is not possible to simultaneously require
+.\"O rpcsec_gss and to make requirements on the IP address of the client.
+¥¨¥¯¥¹¥Ý¡¼¥È¤Ø¤Î¥¢¥¯¥»¥¹¤ò rpcsec_gss ¥»¥¥å¥ê¥Æ¥£¤ò»È¤Ã¤ÆÀ©¸Â¤¹¤ë¤Ë¤Ï¡¢
+¥¯¥é¥¤¥¢¥ó¥È¤È¤·¤ÆÆÃÊ̤Êʸ»úÎó "gss/krb5" ¤ò»È¤¦¤³¤È¡£
+rpcsec_gss ¤È¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹¤Ë¤è¤ë»ñ³Ê¤ò
+Ʊ»þ¤ËÍ׵᤹¤ë¤³¤È¤Ï¤Ç¤¤Ê¤¤¡£
+.PP
+.\"O .SS General Options
+.SS °ìÈÌŪ¤Ê¥ª¥×¥·¥ç¥ó
+.\"O .IR exportfs
+.\"O understands the following export options:
+.I exportfs
+¤Ï°Ê²¼¤Î¥¨¥¯¥¹¥Ý¡¼¥È¥ª¥×¥·¥ç¥ó¤ò¼õ¤±ÉÕ¤±¤ë¡£
+.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 ¥Ý¡¼¥È¤«¤éȯ¤·¤¿¥ê¥¯¥¨¥¹¥È¤·¤«¼õ¤±¤Ä¤±¤Ê¤¤¡£
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç͸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£
+̵¸ú¤Ë¤¹¤ë¤Ë¤Ï
+.I insecure
+¤È»ØÄꤹ¤ë¡£
+.TP
+.I rw
+.\"O Allow both read and write requests on this NFS volume. The
+.\"O default is to disallow any request which changes the filesystem.
+.\"O This can also be made explicit by using
+.\"O the
+.\"O .IR ro " option.
+¤³¤Î NFS ¥Ü¥ê¥å¡¼¥à¤ËÂФ·¤Æ¡¢½ñ¤¹þ¤ß¤ÈÆɤ߽Ф·¥ê¥¯¥¨¥¹¥È¤ÎξÊý¤òµö²Ä¤¹¤ë¡£
+¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÊѹ¹¤¹¤ëÁ´¤Æ¤Î½ñ¤¹þ¤ß¤òµñÈݤ¹¤ë
+(¤³¤ì¤Ï
+.I ro
+¥ª¥×¥·¥ç¥ó¤ÇÌÀ¼¨¤·¤¿¾ì¹ç¤âƱ¤¸)¡£
+.TP
+.I async
+.\"O This option allows the NFS server to violate the NFS protocol and
+.\"O reply to requests before any changes made by that request have been
+.\"O committed to stable storage (e.g. disc drive).
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï NFS ¥µ¡¼¥Ð¤ò NFS ¥×¥í¥È¥³¥ë¤Ë°ãÈ¿¤µ¤»¡¢
+¤¢¤ë¥ê¥¯¥¨¥¹¥È¤Ë¤è¤Ã¤Æ¤Ê¤µ¤ì¤¿Êѹ¹¤¬°ÂÄꤷ¤¿Êݸ¾ì½ê
+(Î㤨¤Ð¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö) ¤ËÅϤµ¤ì¤ëÁ°¤Ë¡¢
+¤½¤Î¥ê¥¯¥¨¥¹¥È¤Ë±þ¤¨¤ë¤è¤¦¤Ë¤¹¤ë¡£
+
+.\"O Using this option usually improves performance, but at the cost that
+.\"O an unclean server restart (i.e. a crash) can cause data to be lost or
+.\"O corrupted.
+¤³¤Î¥ª¥×¥·¥ç¥ó¤òÍѤ¤¤ë¤ÈÄ̾ï¤ÏÀǽ¤¬¸þ¾å¤¹¤ë¤¬¡¢
+¥¯¥ê¡¼¥ó¤Ç¤Ê¤¤¥µ¡¼¥Ð¤ÎºÆµ¯Æ° (¤Ä¤Þ¤ê¥¯¥é¥Ã¥·¥å)
+¤Ë¤è¤Ã¤Æ¥Ç¡¼¥¿¤¬¼º¤ï¤ì¤¿¤êÇ˲õ¤µ¤ì¤¦¤ë¤È¤¤¤¦Âå½þ¤òȼ¤¦¡£
+
+.\"O In releases of nfs-utils upto and including 1.0.0, this option was the
+.\"O default. In this and future releases,
+.\"O .I sync
+.\"O is the default, and
+.\"O .I async
+.\"O must be explicit requested if needed.
+.\"O To help make system adminstrators aware of this change, 'exportfs'
+.\"O will issue a warning if neither
+.\"O .I sync
+.\"O nor
+.\"O .I async
+.\"O is specified.
+nfs-utils ¤Î 1.0.0 ¤Þ¤Ç¤Ç¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤Ã¤¿¡£
+¤³¤Î¥ê¥ê¡¼¥¹°Ê¹ß¤Ï
+.I sync
+¤¬¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ê¡¢
+.I async
+¤ÏɬÍפʾì¹ç¤ÏÌÀ¼¨Åª¤Ë»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+¥·¥¹¥Æ¥à´ÉÍý¼Ô¤Ë¤³¤ÎÊѹ¹¤òÃΤ餻¤ë¤¿¤á¡¢
+.I sync
+¤È
+.I async
+¤Î¤¤¤º¤ì¤â»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢`exportfs' ¤Ï·Ù¹ð¤òȯ¤¹¤ë¡£
+.TP
+.I no_wdelay
+.\"O This option has no effect if
+.\"O .I async
+.\"O is also set. The NFS server will normally delay committing a write request
+.\"O to disc slightly if it suspects that another related write request may be in
+.\"O progress or may arrive soon.
+¤³¤Î¥ª¥×¥·¥ç¥ó¤ÏƱ»þ¤Ë
+.I async
+¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¸ú²Ì¤ò»ý¤¿¤Ê¤¤¡£
+NFS ¥µ¡¼¥Ð¤Ï¡¢½ñ¤¹þ¤ßÍ×µá¤ò¼õ¤±¤¿¤È¤¡¢
+´ØÏ¢¤·¤¿Ê̤νñ¤¹þ¤ßÍ׵᤬¼Â¹ÔÃæ¤Ç¤¢¤ë (¤Þ¤¿¤Ï¶á¡¹ÅþÃ夹¤ë) ¤ÈͽÁÛ¤·¤¿¾ì¹ç¡¢
+¤½¤ÎÍ×µá¤Î¥Ç¥£¥¹¥¯¤Ø¤ÎÈ¿±Ç¤ò¾¯¤·Ã٤餻¤ë¡£
+.\"O This allows multiple write requests to
+.\"O be committed to disc with the one operation which can improve
+.\"O performance. If an NFS server received mainly small unrelated
+.\"O requests, this behaviour could actually reduce performance, so
+.\"O .IR no_wdelay
+.\"O is available to turn it off.
+¤³¤ì¤Ë¤è¤ê°ìÅÙ¤ÎÁàºî¤ÇÊ£¿ô¤Î½ñ¤¹þ¤ßÍ׵᤬
+¥Ç¥£¥¹¥¯¤ËÈ¿±Ç¤µ¤ì¤ë¤Î¤Ç¡¢Àǽ¤¬¸þ¾å¤¹¤ë¡£
+NFS ¥µ¡¼¥Ð¤¬¼õ¤±¼è¤ë¥Ç¡¼¥¿¤Î½ñ¤¹þ¤ßÍ׵᤬¡¢
+¼ç¤È¤·¤Æ´ØÏ¢À¤Î¤Ê¤¤¾®¤µ¤Ê¤â¤Î¤Î¾ì¹ç¤Ë¤Ï¡¢
+¤³¤ÎÆ°ºî¤Ï¼ÂºÝ¤Ë¤ÏÀǽ¤òÄã²¼¤µ¤»¤Æ¤·¤Þ¤¦¤Î¤Ç¡¢
+.I no_wdelay
+¤ò»ØÄꤷ¤Æ̵¸ú¤Ë¤Ç¤¤ë¡£
+.\"O The default can be explicitly requested with the
+.\"O .IR wdelay " option.
+¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤ò
+.I wdelay
+¥ª¥×¥·¥ç¥ó¤ÇÌÀ¼¨Åª¤Ë»ØÄꤹ¤ë¤³¤È¤â¤Ç¤¤ë¡£
+.TP
+.I nohide
+.\"O This option is based on the option of the same name provided in IRIX
+.\"O NFS. Normally, if a server exports two filesystems one of which is
+.\"O mounted on the other, then the client will have to mount both
+.\"O filesystems explicitly to get access to them. If it just mounts the
+.\"O parent, it will see an empty directory at the place where the other
+.\"O filesystem is mounted. That filesystem is "hidden".
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï IRIX NFS ¤ÇÄ󶡤µ¤ì¤ëƱ̾¤Î¥ª¥×¥·¥ç¥ó¤ò¸µ¤Ë¤·¤Æ¤¤¤ë¡£
+¥µ¡¼¥Ð¤¬ 2 ¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥¨¥¯¥¹¥Ý¡¼¥È¤·¡¢
+¤½¤Î¤¦¤Á¤Î 1 ¤Ä¤¬Â¾Êý¤Ë¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
+¥¯¥é¥¤¥¢¥ó¥È¤¬Î¾¼Ô¤Ë¥¢¥¯¥»¥¹¤ò¹Ô¤¦¤Ë¤Ï¡¢
+ξÊý¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÌÀ¼¨Åª¤Ë¥Þ¥¦¥ó¥È¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+¿Æ¤ÎÊý¤ò¥Þ¥¦¥ó¥È¤·¤¿¤À¤±¤Ç¤Ï¡¢
+¤â¤¦°ìÊý¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ï¶õ¤Ë¸«¤¨¤ë¡£
+¤³¤Î¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï "hidden" ¤È¤¤¤ï¤ì¤ë¡£
+
+.\"O Setting the
+.\"O .I nohide
+.\"O option on a filesystem causes it not to be hidden, and an
+.\"O appropriately authorised client will be able to move from the parent to
+.\"O that filesystem without noticing the change.
+hidden ¤Ë¤·¤¿¤¯¤Ê¤¤¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë
+.I nohide
+¥ª¥×¥·¥ç¥ó¤òÀßÄꤹ¤ì¤Ð¡¢
+ŬÀڤʸ¢¸Â¤Î¤¢¤ë¥¯¥é¥¤¥¢¥ó¥È¤ÏÊѹ¹¤òÃΤ餵¤ì¤ë¤³¤È¤Ê¤¯¡¢
+¿Æ¤«¤é»Ò¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë°ÜÆ°¤Ç¤¤ë¡£
+
+.\"O However, some NFS clients do not cope well with this situation as, for
+.\"O instance, it is then possible for two files in the one apparent
+.\"O filesystem to have the same inode number.
+¤·¤«¤· NFS ¥¯¥é¥¤¥¢¥ó¥È¤Î¤Ê¤«¤Ë¤Ï¡¢
+¤³¤Î¤è¤¦¤Ê¾õ¶· (Î㤨¤Ð¡¢¸«¤«¤±¾å 1 ¤Ä¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç
+2 ¤Ä¤Î¥Õ¥¡¥¤¥ë¤¬Æ±¤¸ inode ÈÖ¹æ¤ò»ý¤Ä¤è¤¦¤Ê¾õ¶·)
+¤Ç¤Ï¤¦¤Þ¤¯Æ°ºî¤·¤Ê¤¤¤â¤Î¤â¤¢¤ë¡£
+
+.\"O The
+.\"O .I nohide
+.\"O option is currently only effective on
+.\"O .I "single host
+.\"O exports. It does not work reliably with netgroup, subnet, or wildcard
+.\"O exports.
+.I nohide
+¥ª¥×¥·¥ç¥ó¤Ï¸½ºß¤Î¤È¤³¤í
+.I "single host"
+¥¨¥¯¥¹¥Ý¡¼¥È¤Ç¤·¤«¸ú²Ì¤¬¤Ê¤¤¡£
+¤³¤Î¥ª¥×¥·¥ç¥ó¤ÎÆ°ºî¤Ï¡¢
+netgroup, subnet, wildcard
+¤Ê¤É¤Ë¤è¤ë¥¨¥¯¥¹¥Ý¡¼¥È¤Ç¤Ï¿®ÍêÀ¤¬¤Ê¤¤¡£
+
+.\"O This option can be very useful in some situations, but it should be
+.\"O used with due care, and only after confirming that the client system
+.\"O copes with the situation effectively.
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¾õ¶·¤Ë¤è¤Ã¤Æ¤Ï¤È¤Æ¤âÊØÍø¤Ç¤¢¤ë¤¬¡¢¤è¤¯Ãí°Õ¤·¤Æ¡¢
+¤«¤Ä¥¯¥é¥¤¥¢¥ó¥È¥·¥¹¥Æ¥à¤¬¤½¤Î¾õ¶·²¼¤Ç¸ú²ÌŪ¤ËÆ°ºî¤¹¤ë¤³¤È¤ò³Îǧ¤·¤¿¸å¤Ç
+»È¤¦¤Ù¤¤Ç¤¢¤ë¡£
+
+.\"O The option can be explicitly disabled with
+.\"O .IR hide .
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
+.I hide
+¤ÇÌÀ¼¨Åª¤Ë̵¸ú¤Ë¤Ç¤¤ë¡£
+.TP
+.I no_subtree_check
+.\"O This option disables subtree checking, which has mild security
+.\"O implications, but can improve reliability is some circumstances.
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Î¥µ¥Ö¥Ä¥ê¡¼¤Î¥Á¥§¥Ã¥¯¤ò̵¸ú¤Ë¤¹¤ë¡£
+¤³¤ì¤Ë¤Ï´Êñ¤Ê¥»¥¥å¥ê¥Æ¥£¤Î°ÕÌ£¤â¤¢¤ë¤¬¡¢
+´Ä¶¤Ë¤è¤Ã¤Æ¤Ï¿®ÍêÀ¤ò¸þ¾å¤µ¤»¤ë¤³¤È¤â¤Ç¤¤ë¡£
+
+.\"O If a subdirectory of a filesystem is exported, but the whole
+.\"O filesystem isn't then whenever a NFS request arrives, the server must
+.\"O check not only that the accessed file is in the appropriate filesystem
+.\"O (which is easy) but also that it is in the exported tree (which is
+.\"O harder). This check is called the
+.\"O .IR subtree_check .
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤¬¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¤¬¡¢
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÁ´ÂΤ¬¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
+NFS ¥ê¥¯¥¨¥¹¥È¤¬¤¯¤ë¤È¡¢¥µ¡¼¥Ð¤ÏÂбþ¤¹¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë
+¥¢¥¯¥»¥¹¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤¬¤¢¤ë¤«¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤À¤±¤Ç¤Ê¤¯ (¤³¤ì¤Ï´Êñ)¡¢
+¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤¿¥Ä¥ê¡¼¤Î¤Ê¤«¤Ë¤¢¤ë¤«¤â¥Á¥§¥Ã¥¯¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
+(¤³¤ì¤ÏÆñ¤·¤¤)¡£
+¤³¤Î¥Á¥§¥Ã¥¯¤Ï
+.I subtree_check
+¤È¤è¤Ð¤ì¤ë¡£
+
+.\"O In order to perform this check, the server must include some
+.\"O information about the location of the file in the "filehandle" that is
+.\"O given to the client. This can cause problems with accessing files that
+.\"O are renamed while a client has them open (though in many simple cases
+.\"O it will still work).
+¤³¤Î¥Á¥§¥Ã¥¯¤ò¹Ô¤¦¤Ë¤Ï¡¢¥µ¡¼¥Ð¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÅϤ¹
+¡Ö¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¡×¤Ë¡¢¥Õ¥¡¥¤¥ë¤Î¾ì½ê¤Ë´Ø¤¹¤ë¾ðÊó¤òÆþ¤ì¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+¤³¤¦¤¹¤ë¤È¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬¥Õ¥¡¥¤¥ë¤ò¥ª¡¼¥×¥ó¤·¤Æ¤¤¤ë´Ö¤Ë¡¢
+¥¢¥¯¥»¥¹¤·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤¬Êѹ¹¤µ¤ì¤ë¤ÈÌäÂ꤬µ¯¤³¤ë
+(¤¿¤À¤·Â¿¤¯¤Î´Êñ¤Ê¥±¡¼¥¹¤Ç¤ÏÆ°ºî¤¹¤ë)¡£
+
+.\"O subtree checking is also used to make sure that files inside
+.\"O directories to which only root has access can only be accessed if the
+.\"O filesystem is exported with
+.\"O .I no_root_squash
+.\"O (see below), even the file itself allows more general access.
+¥µ¥Ö¥Ä¥ê¡¼¤Î¥Á¥§¥Ã¥¯¤Ï¡¢
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬
+.I no_root_squash
+(²¼µ»²¾È) ¤Ç¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Æ¡¢
+¥Õ¥¡¥¤¥ë¼«¿È¤Ë¤Ï¤è¤ê°ìÈÌŪ¤Ê¥¢¥¯¥»¥¹¸¢¤¬¤¢¤ë¾ì¹ç¤Ë¡¢
+root ¤·¤«¥¢¥¯¥»¥¹¤Ç¤¤Ê¤¤¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¥Õ¥¡¥¤¥ë¤¬
+root ¤Ë¤è¤Ã¤Æ¤Î¤ß¥¢¥¯¥»¥¹¤µ¤ì¤Æ¤¤¤ë¤«¤ò³Îǧ¤¹¤ë¤Î¤Ë¤â»È¤¨¤ë¡£
+
+.\"O As a general guide, a home directory filesystem, which is normally
+.\"O exported at the root and may see lots of file renames, should be
+.\"O exported with subtree checking disabled. A filesystem which is mostly
+.\"O readonly, and at least doesn't see many file renames (e.g. /usr or
+.\"O /var) and for which subdirectories may be exported, should probably be
+.\"O exported with subtree checks enabled.
+.\"O
+.\"O exported at the root ¤Î°ÕÌ£¤¬¤è¤¯¤ï¤«¤é¤Ê¤¤¡£
+.\"O
+°ìÈÌŪ¤Ê»Ø¿Ë¤È¤·¤Æ¡¢¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ï
+¥µ¥Ö¥Ä¥ê¡¼¤Î¥Á¥§¥Ã¥¯¤ò̵¸ú¤Ë¤·¤Æ¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤Ù¤¤Ç¤¢¤ë
+(Ä̾ï³Æ¥æ¡¼¥¶¤Î¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ì¥Ù¥ë¤Ç¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¡¢
+¤«¤Ä¥Õ¥¡¥¤¥ë̾¤ÎÊѹ¹¤¬Â¿¤¤¤¿¤á)¡£
+ÂçÄñ¤ÏÆɤ߹þ¤ß¤Î¤ß¤Ç¡¢¤Û¤È¤ó¤É¥Õ¥¡¥¤¥ë̾¤ÎÊѹ¹¤¬¹Ô¤ï¤ì¤Ê¤¤
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à (¤¿¤È¤¨¤Ð /usr ¤ä /var) ¤Ç¡¢
+¤½¤ì¤é¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤¬¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï¡¢
+¥µ¥Ö¥Ä¥ê¡¼¤Î¥Á¥§¥Ã¥¯¤ò͸ú¤Ë¤·¤Æ¥¨¥¯¥¹¥Ý¡¼¥È¤·¤¿Êý¤¬¤è¤¤¤«¤â¤·¤ì¤Ê¤¤¡£
+
+.\"O The default of having subtree checks enabled, can be explicitly
+.\"O requested with
+.\"O .IR subtree_check .
+¥µ¥Ö¥Ä¥ê¡¼¤Î¥Á¥§¥Ã¥¯¤ò¹Ô¤¦¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ï¡¢
+.I subtree_check
+¤ÇÌÀ¼¨Åª¤Ë»ØÄꤹ¤ë¤³¤È¤â¤Ç¤¤ë¡£
+
+.TP
+.I insecure_locks
+.TP
+.I no_auth_nlm
+.\"O This option (the two names are synonymous) tells the NFS server not to require authentication of
+.\"O locking requests (i.e. requests which use the NLM protocol). Normally
+.\"O the NFS server will require a lock request to hold a credential for a
+.\"O user who has read access to the file. With this flag no access checks
+.\"O will be performed.
+¤³¤Î¥ª¥×¥·¥ç¥ó (2 ¤Ä¤Î¥ª¥×¥·¥ç¥ó̾¤ÏƱ¤¸°ÕÌ£) ¤ò»ØÄꤹ¤ë¤È¡¢
+NFS ¤Ï¥í¥Ã¥¯Í×µá (NLM ¥×¥í¥È¥³¥ë¤ò»È¤Ã¤¿Í×µá)
+¤ÎºÝ¤Ëǧ¾Ú¤òɬÍפȤ·¤Ê¤¯¤Ê¤ë¡£
+Ä̾ï NFS ¥µ¡¼¥Ð¤Ï¡¢¥Õ¥¡¥¤¥ë¤ÎÆɤ߼è¤ê¥¢¥¯¥»¥¹¸¢¸Â¤ò»ý¤Ä¥æ¡¼¥¶¤ËÂФ·¡¢
+¿®ÍѾÚÌÀ (credential) ¤òÊÝ»ý¤¹¤ë¤¿¤á¤Ë¡¢¥í¥Ã¥¯Í×µá¤òɬÍפȤ¹¤ë¡£
+¤³¤Î¥Õ¥é¥°¤ò»ØÄꤹ¤ë¤È¡¢¥¢¥¯¥»¥¹¥Á¥§¥Ã¥¯¤¬¹Ô¤ï¤ì¤Ê¤¤¡£
+
+.\"O Early NFS client implementations did not send credentials with lock
+.\"O requests, and many current NFS clients still exist which are based on
+.\"O the old implementations. Use this flag if you find that you can only
+.\"O lock files which are world readable.
+½é´ü¤Î NFS ¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÂÁõ¤Ç¤Ï¥í¥Ã¥¯Í×µá¤ÎºÝ¤Ë¿®ÍѾÚÌÀ¤òÁ÷¤é¤Ê¤«¤Ã¤¿¤¬¡¢
+¸½ºß¤Ç¤â¤³¤Î¤è¤¦¤ÊÀΤμÂÁõ¤ò¸µ¤Ë¤·¤¿Â¿¤¯¤Î NFS ¥¯¥é¥¤¥¢¥ó¥È¤¬Â¸ºß¤¹¤ë¡£
+Á´¤Æ¤Î¿Í¤¬Æɤ߹þ¤ß²Äǽ¤Ê¥Õ¥¡¥¤¥ë¤Î¤ß¤ò¥í¥Ã¥¯¤·¤¿¤¤¾ì¹ç¤Ï¡¢
+¤³¤Î¥Õ¥é¥°¤ò»È¤¦¤³¤È¡£
+
+.\"O The default behaviour of requiring authentication for NLM requests can
+.\"O be explicitly requested with either of the synonymous
+.\"O .IR auth_nlm ,
+.\"O or
+.\"O .IR secure_locks .
+NLM Í×µá¤ÎºÝ¤Ëǧ¾Ú¤òµá¤á¤ë¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ï¡¢
+Ʊ¤¸°ÕÌ£¤ò¤â¤Ä
+.I auth_nlm
+¤Þ¤¿¤Ï
+.I secure_locks
+¤Î¤É¤Á¤é¤« (°ÕÌ£¤ÏÁ´¤¯Æ±¤¸) ¤ÇÌÀ¼¨Åª¤Ë»ØÄê¤Ç¤¤ë¡£
+
+'''.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
+.TP
+.IR mountpoint= path
+.TP
+.I mp
+.\"O This option makes it possible to only export a directory if it has
+.\"O successfully been mounted.
+.\"O If no path is given (e.g.
+.\"O .IR mountpoint " or " mp )
+.\"O then the export point must also be a mount point. If it isn't then
+.\"O the export point is not exported. This allows you to be sure that the
+.\"O directory underneath a mountpoint will never be exported by accident
+.\"O if, for example, the filesystem failed to mount due to a disc error.
+¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¥Þ¥¦¥ó¥È¤ËÀ®¸ù¤·¤¿¾ì¹ç¤Ë¤Î¤ß¡¢
+¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò¥¨¥¯¥¹¥Ý¡¼¥È¤Ç¤¤ë¡£
+¥Ñ¥¹¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç (¤¿¤È¤¨¤Ð
+.IR mountpoint " ¤Þ¤¿¤Ï " mp
+¤Î¾ì¹ç)¡¢¥¨¥¯¥¹¥Ý¡¼¥È¥Ý¥¤¥ó¥È¤Ï¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢¥¨¥¯¥¹¥Ý¡¼¥È¥Ý¥¤¥ó¥È¤Ï¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Ê¤¤¡£
+¤³¤ì¤Ë¤è¤ê¡¢¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È°Ê²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¤¬¡¢
+»ö¸Î¤Ë¤è¤Ã¤Æ¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Æ¤·¤Þ¤ï¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤¤ë¡£
+¤³¤³¤Ç¤¤¤¦»ö¸Î¤È¤Ï¡¢Î㤨¤Ð¥Ç¥£¥¹¥¯¥¨¥é¡¼¤Ë¤è¤Ã¤Æ
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Þ¥¦¥ó¥È¤Ë¼ºÇÔ¤¹¤ë¤è¤¦¤Ê¾ì¹ç¤Ç¤¢¤ë¡£
+
+.\"O If a path is given (e.g.
+.\"O .IR mountpoint= "/path or " mp= /path)
+.\"O then the nominted path must be a mountpoint for the exportpoint to be
+.\"O exported.
+.\"Osato:
+.\"Osato: nominted ¤Ï mounted ¤Î´Ö°ã¤¤¡©
+.\"Osato: ¤³¤³¤ÎÌõ¤ÏÁ´ÂÎŪ¤Ë¼«¿È¤Ê¤·¡£
+.\"Osato:
+¥Ñ¥¹¤¬»ØÄꤵ¤ì¤ë¾ì¹ç (¤¿¤È¤¨¤Ð
+.IR mountpoint= "/path ¤Þ¤¿¤Ï " mp= /path
+¤Î¾ì¹ç)¡¢¥Þ¥¦¥ó¥È¤µ¤ì¤ë¥Ñ¥¹¤Ï¡¢
+¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¥¨¥¯¥¹¥Ý¡¼¥È¥Ý¥¤¥ó¥È¤ËÂбþ¤¹¤ë
+¥Þ¥¦¥ó¥È¥Ý¥¤¥ó¥È¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+
+.TP
+.IR fsid= num
+.\"O This option forces the filesystem identification portion of the file
+.\"O handle and file attributes used on the wire to be
+.\"O .I num
+.\"O instead of a number derived from the major and minor number of the
+.\"O block device on which the filesystem is mounted. Any 32 bit number
+.\"O can be used, but it must be unique amongst all the exported filesystems.
+.\"Osato:
+.\"Osato: filesystem identification porting ¤¬
+.\"Osato: file handle, file attributes ¤ÎξÊý¤Ë¤«¤«¤Ã¤Æ¤¤¤ë¤È
+.\"Osato: ¹Í¤¨¤ÆÌõ¤·¤Æ¤¤¤ë¤¬¡¢Àµ¤·¤¤¤«¼«¿È¤Ê¤·¡£
+.\"Osato: on the wire ¤ÎÌõ¤Ï¡ÖÄÌ¿®¤Ç»È¤ï¤ì¤ë¡×¤Ç¤è¤¤¤«¡£
+.\"Osato:
+¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢ÄÌ¿®¤Ç»ÈÍѤµ¤ì¤ë¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤È¥Õ¥¡¥¤¥ë°À¤Î
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¼±ÊÌÉô¤È¤·¤Æ¡¢
+¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¤Î
+¥á¥¸¥ã¡¼ÈÖ¹æ¤È¥Þ¥¤¥Ê¡¼Èֹ椫¤éƳ¤½Ð¤µ¤ì¤¿¿ô¤Ç¤Ï¤Ê¤¯¡¢
+.I num
+¤ò»È¤¦¡£
+Ǥ°Õ¤Î 32 ¥Ó¥Ã¥È¤Î¿ôÃͤ¬»È¤¨¤ë¤¬¡¢
+¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à´Ö¤Ç°ì°Õ (unique) ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+
+.\"O This can be useful for NFS failover, to ensure that both servers of
+.\"O the failover pair use the same NFS file handles for the shared filesystem
+.\"O thus avoiding stale file handles after failover.
+¤³¤ì¤Ï NFS ¤Î¥Õ¥§¥¤¥ë¥ª¡¼¥Ð¡¼ (failover, ÂåÂØ°ú¤·Ñ¤®) ¤ÇÌòΩ¤Ä¡£
+¥Õ¥§¥¤¥ë¥ª¡¼¥Ð¡¼¤Î¥Ú¥¢¤È¤Ê¤ëξÊý¤Î¥µ¡¼¥Ð¡¼¤¬¡¢
+¶¦Í¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ
+Ʊ¤¸ NFS ¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤ò»È¤¦¤³¤È¤¬Êݾڤµ¤ì¤ë¤Î¤Ç¡¢
+¥Õ¥§¥¤¥ë¥ª¡¼¥Ð¡¼¸å¤Ë¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤¬¼º¸ú¤¹¤ë¤Î¤òÈò¤±¤ë¤³¤È¤¬¤Ç¤¤ë¡£
+
+.\"O Some Linux filesystems are not mounted on a block device; exporting
+.\"O these via NFS requires the use of the
+.\"O .I fsid
+.\"O option (although that may still not be enough).
+Linux ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÃæ¤Ë¤Ï¡¢
+¥Ö¥í¥Ã¥¯¥Ç¥Ð¥¤¥¹¤Ë¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤Ê¤¤¤â¤Î¤â¤¢¤ë¡£
+¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò NFS ¤Ç¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤Ë¤Ï¡¢
+.I fsid
+¥ª¥×¥·¥ç¥ó¤ò»È¤¦É¬Íפ¬¤¢¤ë (¤¿¤À¤·¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¤Þ¤À½¼Ê¬¤Ç¤Ï¤Ê¤¤)¡£
+
+.\"O The value 0 has a special meaning when use with NFSv4. NFSv4 has a
+.\"O concept of a root of the overall exported filesystem. The export point
+.\"O exported with fsid=0 will be used as this root.
+ÃÍ 0 ¤Ï NFSv4 ¤Ç»È¤¦¾ì¹ç¤Ë¤ÏÆÃÊ̤ʰÕÌ£¤ò»ý¤Ä¡£
+NFSv4 ¤Ë¤Ï¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÁ´ÂΤΥ롼¥È¤È¤¤¤¦³µÇ°¤¬¤¢¤ë¡£
+fsid=0 ¤Ç¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤¿¥¨¥¯¥¹¥Ý¡¼¥È¥Ý¥¤¥ó¥È¤Ï¡¢
+¤³¤Î¥ë¡¼¥È¤È¤·¤Æ»ÈÍѤµ¤ì¤ë¡£
+
+.\"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 .I exportfs
+.\"O chooses a uid and gid
+.\"O of -2 (i.e. 65534) for squashed access. These values can also be overridden by
+.\"O the
+.\"O .IR anonuid " and " anongid
+.\"O options.
+¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢
+''' .I nfsd
+''' ¤Ï
+''' µ¯Æ°»þ¤Ë password ¥Õ¥¡¥¤¥ëÃæ¤Î
+''' .I nobody
+''' ¥æ¡¼¥¶¤ò»²¾È¤·¤Æ¡¢
+''' anonymous ¤Î uid ¤È gid ¤òÆÀ¤è¤¦¤È¤¹¤ë¡£
+''' ¤â¤·¤½¤ì¤¬¸«¤Ä¤«¤é¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
+.I exportfs
+¤Ï squash ¥¢¥¯¥»¥¹¤Ë -2 (¤Ä¤Þ¤ê 65534) ¤È¤¤¤¦ uid ¤È gid ¤òÍѤ¤¤ë¡£
+¤³¤ì¤é¤Î¿ôÃͤÏ
+.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.
+.\"O 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
+.I 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
+.I 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
+.I 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 ¤Î¥¹¥×¡¼¥ë¥Ç¥£¥ì¥¯¥È¥êÅù¤ËÊØÍø¤Ç¤¢¤ë¡£
+¤³¤ì¤ÈµÕ¤Î¥ª¥×¥·¥ç¥ó¤Ï
+.I 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 ¤òÊѤ¨¤Ê¤¤
+''' .IR 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.
+.\"O '''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 ¥µ¡¼¥Ð¤Î¼ÂÁõ¤È°ã¤¤¡¢
+''' ¤³¤Î
+''' .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
+''' ¤Î¥¨¥ó¥È¥ê¤Ç¤¢¤¿¤¨¤é¤ì¤¿ ¥Þ¥¦¥ó¥È¥ª¥×¥·¥ç¥ó¤¬Å¬ÍѤµ¤ì¤ë¡£
+''' ¤³¤ì¤Ï¥¨¥ó¥È¥ê¤Î¥Û¥¹¥È»ØÄ꤬¥ï¥¤¥ë¥É¥«¡¼¥É(wildcard) ¤â¤·¤¯¤Ï netgroup
+''' ¤Î¾ì¹ç¤Ç¤â¿¿¤Ç¤¢¤ë¡£
+.\"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)
+''' ¤Ë¡¢Æ±¤¸¥Ñ¥é¥á¡¼¥¿¤ÇÊó¹ð¤µ¤ì¤ë¡£
OSDN Git Service
