Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / cvsup / draft / man1 / cvsup.1

.\" Copyright 1996,1997, 1998, 1999 John D. Polstra.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgment:
.\"      This product includes software developed by John D. Polstra.
.\" 4. The name of the author may not be used to endorse or promote products
.\"    derived from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id: cvsup.1,v 1.4 2003/12/12 13:06:57 takei Exp $
.\"
.\" translated Sun Jan 23 03:13:03 JST 2000
.\"         by FUJIWARA Teruyoshi <fujiwara@linux.or.jp>
.\"
.Dd August 31, 1999
.Os FreeBSD
.Dt CVSUP 1
.\"O .Sh NAME
.Sh ̾¾Î
.Nm cvsup
.\"O .Nd network distribution package for CVS repositories
.Nd CVS ¥ê¥Ý¥¸¥È¥êÍѤΥͥåȥ¥¯ÇÛÉۥѥ屡¼¥¸
.\"O .Sh SYNOPSIS
.Sh ½ñ¼°
.Nm
.Op Fl 1aDeEgksvzZ
.Op Fl A Ar addr
.Op Fl b Ar base
.Op Fl c Ar collDir
.Op Fl d Ar delLimit
.Op Fl h Ar host
.Op Fl i Ar pattern
.Op Fl l Ar lockfile
.Op Fl L Ar verbosity
.Op Fl p Ar port
.Op Fl P Ar m|a|port|lo-hi|-
.Op Fl r Ar maxRetries
.Ar supfile
.Op Ar destDir
.\"O .Sh DESCRIPTION
.Sh ²òÀâ
.\"O .Nm CVSup
.\"O is a software package for distributing and updating collections of files
.\"O across a network.
.Nm CVSup
¤Ï¡¢¥Õ¥¡¥¤¥ë·²¤ÎÇÛÉۤȹ¹¿·¤ò¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ç¹Ô¤¦¤¿¤á¤Î
¥½¥Õ¥È¥¦¥§¥¢¥Ñ¥Ã¥±¡¼¥¸¤Ç¤¹¡£
.\"O The name
.\"O .Nm CVSup
.\"O refers to the package as a whole.
.Nm CVSup
¤È¤¤¤¦Ì¾Á°¤Ï¥Ñ¥Ã¥±¡¼¥¸Á´ÂΤò»Ø¤·¤Þ¤¹¡£
.\"O It consists of a client program,
.\"O .Nm cvsup ,
.\"O and a server program,
.\"O .Nm cvsupd .
.Nm CVSup
¤Ï¥¯¥é¥¤¥¢¥ó¥È¥×¥í¥°¥é¥à¤Ç¤¢¤ë
.Nm cvsup
¤È¥µ¡¼¥Ð¥×¥í¥°¥é¥à¤Ç¤¢¤ë
.Nm cvsupd
¤«¤é¤Ç¤­¤Æ¤¤¤Þ¤¹¡£
.\"O This manual page describes the general aspects of the
.\"O .Nm CVSup
.\"O package, as well as the particulars of the
.\"O .Nm
.\"O client program.
¤³¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ï¡¢
.Nm CVSup
¥Ñ¥Ã¥±¡¼¥¸¤Î³µÍפòÀâÌÀ¤·¡¢¥¯¥é¥¤¥¢¥ó¥È¥×¥í¥°¥é¥à
.Nm cvsup
ÆÃÍ­¤Î»ö¹à¤âÀâÌÀ¤·¤Þ¤¹¡£
.\"O For detailed information about
.\"O .Nm cvsupd ,
.\"O see
.\"O .Xr cvsupd 8 .
.Nm cvsupd
¤Î¾Ü¤·¤¤ÀâÌÀ¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.Xr cvsupd 8
¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.Pp
.\"O Unlike more traditional network distribution packages, such as
.\"O .Nm rdist
.\"O and
.\"O .Nm sup ,
.\"O .Nm CVSup
.\"O is tailored specifically for distributing CVS repositories.
.Nm rdist
¤ä
.Nm sup
¤Î¤è¤¦¤Ê¡¢¤è¤êÅÁÅýŪ¤Ê¥Í¥Ã¥È¥ï¡¼¥¯ÇÛÉۥѥ屡¼¥¸¤È°Û¤Ê¤ê¡¢
.Nm CVSup
¤ÏÆÃ¤Ë CVS ¥ê¥Ý¥¸¥È¥ê¤ÎÇÛÉۤΤ¿¤á¤Ëºî¤é¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O .Nm CVSup
.\"O takes advantage of the properties of CVS repositories and the files they
.\"O contain (in particular, RCS files), enabling it to perform updates much
.\"O faster than traditional systems.
.Nm CVSup
¤Ï
CVS ¥ê¥Ý¥¸¥È¥ê¤È¥ê¥Ý¥¸¥È¥ê¤Ë´Þ¤Þ¤ì¤ë¥Õ¥¡¥¤¥ë(ÆÃ¤Ë RCS ¥Õ¥¡¥¤¥ë)¤Î
ÆÃÀ­¤òÀ¸¤«¤·¡¢ÅÁÅýŪ¤Ê¥·¥¹¥Æ¥à¤è¤ê¤â¤º¤Ã¤È¹â®¤Ê¹¹¿·¤ò²Äǽ¤Ë¤·¤Æ¤¤¤Þ¤¹¡£
.\"O .Sh OPTIONS
.Sh ¥ª¥×¥·¥ç¥ó
.\"O The client program
.\"O .Nm
.\"O requires at least a single argument,
.\"O .Ar supfile .
¥¯¥é¥¤¥¢¥ó¥È¥×¥í¥°¥é¥à
.Nm cvsup
¤Ï¡¢¾¯¤Ê¤¯¤È¤â°ì¤Ä¤Î°ú¿ô
.Ar supfile
¤òɬÍפȤ·¤Þ¤¹¡£
.\"O It names a file describing one or more collections of files to be
.\"O transferred and/or updated from the server.
¤³¤Î°ú¿ô¤¬»Ø¤¹¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
¥µ¡¼¥Ð¤«¤é¤ÎžÁ÷¤ä¹¹¿·¤ÎÂоݤȤʤë¥Õ¥¡¥¤¥ë¤¬µ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O The
.\"O .Ar supfile
.\"O has a format similar to the corresponding file used by
.\"O .Nm sup .
.Ar supfile
¤Ï¡¢
.Nm sup
¤Ç»È¤ï¤ì¤ëƱ¤¸ÌÜŪ¤Î¥Õ¥¡¥¤¥ë¤Ë»÷¤¿·Á¼°¤Ç¤¹¡£
.\"O In most cases,
.\"O .Nm
.\"O can use existing 
.\"O .Nm sup Ar supfiles .
¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢
.Nm cvsup
¤Ï´û¸¤Î
.Nm sup Ar supfiles
¤ò»È¤¨¤Þ¤¹¡£
.Pp
.\"O An optional argument
.\"O .Ar destDir
.\"O may also be specified.
°ú¿ô
.Ar destDir
¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹ (¤³¤Î°ú¿ô¤Ï¾Êά¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó)¡£
.\"O If given, it names a directory under which all updated files will be
.\"O placed.
»ØÄꤵ¤ì¤¿¾ì¹ç¤Ë¤Ï¡¢¤³¤Î°ú¿ô¤Ï¹¹¿·¤µ¤ì¤¿Á´¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬ÃÖ¤«¤ì¤ë
¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£
.\"O When
.\"O .Ar destDir
.\"O is specified, the client's original files are left untouched.
.Ar destDir
¤¬»ØÄꤵ¤ì¤ë¤È¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¸µ¤Î¥Õ¥¡¥¤¥ë¤Ï¤½¤Î¤Þ¤Þ»Ä¤µ¤ì¤Þ¤¹¡£
.\"O This feature is primarily intended for testing.
¤³¤Îµ¡Ç½¤Ï¼ç¤Ë¥Æ¥¹¥È¤Î¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£
.Pp
.\"O The following options are supported by
.\"O .Nm cvsup :
.Nm cvsup
¤Ï°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹:
.Bl -tag -width Fl
.It Fl 1
.\"O Disables automatic retries when transient failures occur and the GUI is
.\"O not being used.  Without this option, a transient failure such as a
.\"O dropped network connection causes
.\"O .Nm
.\"O to retry repeatedly, using randomized exponential backoff to space the
.\"O retries.
°ì»þŪ¤Ê¼ºÇÔ¤¬µ¯¤­¡¢¤«¤Ä GUI ¤¬»È¤ï¤ì¤Æ¤¤¤Ê¤¤»þ¤Î¼«Æ°¥ê¥È¥é¥¤¤ò̵¸ú¤Ë
¤·¤Þ¤¹¡£¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤¤È¡¢¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤ÎÀÚÃǤȤ¤¤Ã¤¿
°ì»þŪ¤Ê¼ºÇÔ¤¬µ¯¤­¤¿»þ¡¢
.Nm cvsup
¤Ï¥ê¥È¥é¥¤¤ò·«¤êÊÖ¤·¹Ô¤¤¤Þ¤¹¡£¥ê¥È¥é¥¤¤ÎºÝ¤Ë¤Ï
¡Ö¥é¥ó¥À¥à²½¤µ¤ì¤¿»Ø¿ôŪ¤Ê°ì»þÂàÈò(randomized exponential backoff)¡×
¥¢¥ë¥´¥ê¥º¥à¤òÍѤ¤¤Æ¥ê¥È¥é¥¤¤Î´Ö³Ö¤ò·è¤á¤Þ¤¹¡£
.\"O This option is equivalent to
.\"O .Fl r Cm 0,
.\"O and is implied when the GUI is used.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï
.Fl r Cm 0
¤ÈƱÅù¤Ç¤¢¤ê¡¢GUI ¤ò»È¤¦»þ¤Ë¤Ï°ÅÌÛŪ¤Ë»ØÄꤵ¤ì¤¿¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
.It Fl a
.\"O Requires the server to authenticate itself (prove its identity) to
.\"O the client.  If authentication of the server fails, the update is
.\"O canceled.  See
.\"O .Sx AUTHENTICATION ,
.\"O below.
¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¼«Ê¬¼«¿È¤Îǧ¾Ú (¼«Ê¬¤¬²¿¤Ç¤¢¤ë¤«¤ò¼¨¤¹¤³¤È)
¤ò¹Ô¤¦¤è¤¦¥µ¡¼¥Ð¤ËÍ׵ᤷ¤Þ¤¹¡£¥µ¡¼¥Ð¤Îǧ¾Ú¤¬¼ºÇÔ¤¹¤ë¤È¡¢¹¹¿·¤Ï¥­¥ã¥ó¥»¥ë
¤µ¤ì¤Þ¤¹¡£
¸å½Ò¤Î
.Sx ǧ¾Ú
¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
.It Fl A Ar addr
.\"O Specifies a local address (dotted quad or hostname) to bind to when
.\"O connecting to the server.  This may be useful on hosts which have
.\"O multiple IP addresses.
¥µ¡¼¥Ð¤ËÀܳ¤¹¤ë»þ¤Ë³ä¤êÅö¤Æ¤ë¥í¡¼¥«¥ë¤Î¥¢¥É¥ì¥¹
(¥É¥Ã¥È¶èÀÚ¤ê¤Î 4 ¤Ä¤Î¿ôÃÍ¡¢¤Þ¤¿¤Ï¥Û¥¹¥È̾)¤ò»ØÄꤷ¤Þ¤¹¡£¤³¤Î¥ª¥×¥·¥ç
¥ó¤Ï¡¢¥Û¥¹¥È¤¬Ê£¿ô¸Ä¤Î IP ¥¢¥É¥ì¥¹¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤ËÊØÍø¤Ç¤¹¡£
.It Fl b Ar base
.\"O Specifies the base directory under which
.\"O .Nm
.\"O will maintain its bookkeeping files, overriding any
.\"O .Cm base
.\"O specifications in the
.\"O .Ar supfile .
.Nm cvsup
¤¬´ÉÍý¤¹¤ëµ­Ï¿¥Õ¥¡¥¤¥ë¤òÃÖ¤¯¥Ù¡¼¥¹¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£
¤³¤ÎºÝ¤Ë¤Ï¡¢
.Ar supfile
¤Ë¤è¤ë
.Cm base
¤Î»ØÄê¤ÏÁ´¤Æ¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£
.It Fl c Ar collDir
.\"O Specifies the subdirectory of
.\"O .Ar base
.\"O where the information about the collections is maintained.
¥³¥ì¥¯¥·¥ç¥ó¤Ë´Ø¤¹¤ë¾ðÊó¤ò´ÉÍý¤¹¤ë¡¢
.Ar base
¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£
.\"O The default is
.\"O .Pa sup .
¥Ç¥Õ¥©¥ë¥ÈÃͤÏ
.Pa sup
¤Ç¤¹¡£
.It Fl d Ar delLimit
.\"O Specifies the maximum number of files that may be deleted in a
.\"O single update run.
¹¹¿·¤ò 1 ²ó¼Â¹Ô¤·¤¿ºÝ¤Ëºï½ü¤Ç¤­¤ë¥Õ¥¡¥¤¥ë¿ô¤Î¾å¸Â¤ò»ØÄꤷ¤Þ¤¹¡£
.\"O Any attempt to exceed the limit results in a fatal error.
¤³¤Î¾å¸Â¤òĶ¤¨¤ë¥Õ¥¡¥¤¥ëºï½ü¤Î»î¤ß¤ÏÃ×̿Ū¤Ê¥¨¥é¡¼¤È¤Ê¤ê¤Þ¤¹¡£
.\"O This can provide some protection against temporary configuration
.\"O mistakes on the server.
¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¡¢¥µ¡¼¥Ð¾å¤Î°ì»þŪ¤ÊÀßÄê¥ß¥¹¤Ë¤è¤ëÈï³²¤ò¡¢
¤¢¤ëÄøÅÙËɤ²¤Þ¤¹¡£
.\"O The default limit is infinity.
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï̵À©¸Â¤Ç¤¹¡£
.It Fl D
.\"O Causes
.\"O .Nm
.\"O to perform file deletions only, omitting all other kinds of updates.
.Nm cvsup
¤Ë¥Õ¥¡¥¤¥ë¤Îºï½ü¤À¤±¤ò¹Ô¤ï¤»¡¢¤É¤ó¤Ê¼ïÎà¤Î¹¹¿·¤â¹Ô¤¤¤Þ¤»¤ó¡£
.\"O This is useful in some situations where disk space on the client is
.\"O very limited.  One can first run
.\"O .Nm
.\"O with the
.\"O .Fl D
.\"O option, to free up as much space as possible.  Then a second run
.\"O can be made, this time without the
.\"O .Fl D
.\"O option.  If files or directories have been renamed on the server,
.\"O this technique ensures that all of the old files are deleted on
.\"O the client before any of the new ones are created.  This option
.\"O is not implemented yet for checkout mode.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤¬Èó¾ï¤Ë¾¯¤Ê¤¤¤è¤¦¤Ê¾ì¹ç¤Ë
Ìò¤ËΩ¤Á¤Þ¤¹¡£¥æ¡¼¥¶¤Ï¤Þ¤º
.Fl D
¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ
.Nm cvsup
¤ò¼Â¹Ô¤·¡¢¤Ç¤­¤ë¸Â¤ê¤ÎÍÆÎ̤ò¶õ¤±¤Þ¤¹¡£¼¡¤Ë¤â¤¦°ìÅÙ
.Nm cvsup
¤ò¼Â¹Ô¤·¤Þ¤¹¤¬¡¢º£ÅÙ¤Ï
.Fl D
¥ª¥×¥·¥ç¥ó¤Ï»È¤¤¤Þ¤»¤ó¡£¥µ¡¼¥Ð¾å¤Ç¥Õ¥¡¥¤¥ë¤ä¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤¬Êѹ¹¤µ
¤ì¤¿¾ì¹ç¤Ï¡¢¤³¤ÎÊýË¡¤ò¼è¤ë¤³¤È¤Ë¤è¤ê¡¢¥¯¥é¥¤¥¢¥ó¥È¾å¤Ç¿·¤·¤¤¥Õ¥¡¥¤¥ë¤¬
À¸À®¤µ¤ì¤ë¤è¤ê¤âÁ°¤Ë¡¢Á´¤Æ¤Î¸Å¤¤¥Õ¥¡¥¤¥ë¤¬ºï½ü¤µ¤ì¤ë¤³¤È¤¬Êݾڤµ¤ì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Á¥§¥Ã¥¯¥¢¥¦¥È¥â¡¼¥É¤Ç¤Ï¤Þ¤À¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
.It Fl e
.\"O Enables the execution of shell commands received from the server, as
.\"O if the
.\"O .Cm execute
.\"O keyword were added to every collection in the
.\"O .Ar supfile .
¥µ¡¼¥Ð¤«¤é¼õ¤±¼è¤Ã¤¿¥·¥§¥ë¥³¥Þ¥ó¥É¤Î¼Â¹Ô¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£
.Ar supfile
Ãæ¤ÎÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤Ë
.Cm execute
¥­¡¼¥ï¡¼¥É¤¬Äɲ䵤줿¾ì¹ç¤ÈƱ¤¸¤Ç¤¹¡£
.It Fl E
.\"O Disables the execution of shell commands received from the server, as
.\"O if the
.\"O .Cm execute
.\"O keyword were removed from every collection in the
.\"O .Ar supfile .
¥µ¡¼¥Ð¤«¤é¼õ¤±¼è¤Ã¤¿¥·¥§¥ë¥³¥Þ¥ó¥É¤Î¼Â¹Ô¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
.Ar supfile
Ãæ¤ÎÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤«¤é
.Cm execute
¥­¡¼¥ï¡¼¥É¤¬ºï½ü¤µ¤ì¤¿¾ì¹ç¤ÈƱ¤¸¤Ç¤¹¡£
.It Fl g
.\"O Disables the use of the graphical user interface.
GUI ¤ò»È¤ï¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O This option is implied if the
.\"O .Ev DISPLAY
.\"O environment variable is not set.
.Ev DISPLAY
´Ä¶­ÊÑ¿ô¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤¬°ÅÌÛŪ¤Ë»ØÄꤵ¤ì¤Þ¤¹¡£
.It Fl h Ar host
.\"O Specifies the server host to contact, overriding any
.\"O .Cm host
.\"O specifications in the
.\"O .Ar supfile .
Àܳ¤¹¤ë¥µ¡¼¥Ð¥Û¥¹¥È¤ò»ØÄꤷ¤Þ¤¹¡£
.Ar supfile
¤Ë¤ª¤±¤ë
.Cm host
¤Î»ØÄê¤ÏÁ´¤Æ¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£
.It Fl i Ar pattern
.\"O Causes
.\"O .Nm
.\"O to include only files and directories matching
.\"O .Ar pattern
.\"O in the update.  If a directory matches the pattern, then the entire
.\"O subtree rooted at the directory is included.  If this option is
.\"O specified multiple times, the patterns are combined using the
.\"O .Ql or
.\"O operation.  If no
.\"O .Fl i
.\"O options are given, the default is to update all files in each
.\"O collection.
.Ar pattern
¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤È¥Ç¥£¥ì¥¯¥È¥ê¤À¤±¤ò¹¹¿·Âоݤˤ¹¤ë¤è¤¦¤Ë
.Nm cvsup
¤Ë»ØÄꤷ¤Þ¤¹¡£¥Ç¥£¥ì¥¯¥È¥ê¤¬¥Ñ¥¿¡¼¥ó¤Ë¥Þ¥Ã¥Á¤¹¤ë¤È¡¢
¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò¥ë¡¼¥È¤È¤¹¤ë¥µ¥Ö¥Ä¥ê¡¼Á´ÂΤ¬Âоݤ˴ޤޤì¤Þ¤¹¡£
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Ê£¿ô²ó»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢¥Ñ¥¿¡¼¥ó¤Ï
.Ql or
Áàºî¤Ç·ë¹ç¤µ¤ì¤Þ¤¹¡£
.Fl i
¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç¤Î¥Ç¥Õ¥©¥ë¥ÈÆ°ºî¤Ç¤Ï¡¢³Æ¥³¥ì¥¯¥·¥ç¥ó¤Ë´Þ¤Þ
¤ì¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬¹¹¿·¤µ¤ì¤Þ¤¹¡£
.Pp
.\"O The
.\"O .Ar pattern
.\"O is a standard file name pattern.
.Ar pattern
¤Ïɸ½à¤Î¥Õ¥¡¥¤¥ë̾¥Ñ¥¿¡¼¥ó¤Ç¤¹¡£
.\"O It is interpreted relative to the collection's prefix directory.
¤³¤ì¤Ï¥³¥ì¥¯¥·¥ç¥ó¤Î¥×¥ì¥Õ¥£¥Ã¥¯¥¹¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤ÎÁêÂХѥ¹¤Ç
²ò¼á¤µ¤ì¤Þ¤¹¡£
.\"O Slash characters are matched only by explicit slashes in the pattern.
¥¹¥é¥Ã¥·¥åʸ»ú¤Ï¡¢¥Ñ¥¿¡¼¥óÃæ¤ËÌÀ¼¨Åª¤Ë¥¹¥é¥Ã¥·¥å¤¬½ñ¤«¤ì¤¿¾ì¹ç¤À¤±
¥Þ¥Ã¥Á¤·¤Þ¤¹¡£
.\"O Leading periods in file name are not treated specially.
¥Õ¥¡¥¤¥ë̾¤ÎÀèƬ¤Ë¥Ô¥ê¥ª¥É¤¬¤¢¤Ã¤Æ¤â¡¢ÆÃÊÌ°·¤¤¤Ï¤µ¤ì¤Þ¤»¤ó¡£
.Pp
.\"O The GUI has a type-in field where the patterns may be edited.
GUI ¤Ë¤Ï¡¢¥Ñ¥¿¡¼¥ó¤òÊÔ½¸¤Ç¤­¤ëÆþÎÏ¥Õ¥£¡¼¥ë¥É¤¬¤¢¤ê¤Þ¤¹¡£
.It Fl k
.\"O Causes
.\"O .Nm
.\"O to keep the temporary copies of any incorrectly edited files, in the
.\"O event of checksum mismatches.
¥Á¥§¥Ã¥¯¥µ¥à¤ÎÉÔ°ìÃפ¬µ¯¤­¤¿»þ¡¢´Ö°ã¤Ã¤ÆÊÔ½¸¤µ¤ì¤¿¥Õ¥¡¥¤¥ëÁ´¤Æ¤Î°ì»þŪ
¤Ê¥³¥Ô¡¼¤òÊݸ¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O This option is for debugging, to help determine why the files were
.\"O edited incorrectly.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥Ð¥Ã¥°ÍѤΤâ¤Î¤Ç¤¢¤ê¡¢¤É¤¦¤·¤Æ¥Õ¥¡¥¤¥ë¤¬¸í¤Ã¤ÆÊÔ½¸¤µ
¤ì¤¿¤Î¤«¤òÆͤ­»ß¤á¤ëÌò¤ËΩ¤Á¤Þ¤¹¡£
.\"O Regardless of whether this option is specified, the permanent versions
.\"O of faulty files are replaced with correct versions obtained by
.\"O transferring the files in their entirety.
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤«¤É¤¦¤«¤Ë´Ø¤ï¤é¤º¡¢ÉÔÀµ¤Ê¥Õ¥¡¥¤¥ë¤Î
ÊݸÈÇ (permanent version) ¤Ï¡¢¥Õ¥¡¥¤¥ëžÁ÷¤ò´Ý¤´¤È¹Ô¤Ã¤Æ¼èÆÀ¤·¤¿
Àµ¤·¤¤¥Õ¥¡¥¤¥ë¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£
.\"O Such transfers are called fixups.
¤³¤Î¤è¤¦¤ÊžÁ÷¤Ï¥Õ¥£¥Ã¥¯¥¹¥¢¥Ã¥×(fixup, ½¤Íý¤Î°ÕÌ£)¤È¸À¤¤¤Þ¤¹¡£
.It Fl l Ar lockfile
.\"O Creates and locks the
.\"O .Ar lockfile
.\"O while the update is in progress.
.Ar lockfile
¤òÀ¸À®¤·¡¢¤³¤ì¤ò¹¹¿·¤¬¹Ô¤ï¤ì¤Æ¤¤¤ë´Ö¥í¥Ã¥¯¤·¤Þ¤¹¡£
.\"O If
.\"O .Ar lockfile
.\"O is already locked,
.\"O .Nm
.\"O fails without performing automatic retries.
.Ar lockfile
¤¬´û¤Ë¥í¥Ã¥¯¤µ¤ì¤Æ¤¤¤ë¤È¡¢
.Nm
¤Ï¼«Æ°Åª¤Ê¥ê¥È¥é¥¤¤ò¹Ô¤¦¤³¤È¤Ê¤¯¼ºÇÔ¤·¤Þ¤¹¡£
.\"O This option is useful when
.\"O .Nm
.\"O is executed periodically from
.\"O .Nm cron .
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Ìò¤ËΩ¤Ä¤Î¤Ï¡¢
.Nm cron
¤ò»È¤Ã¤Æ
.Nm
¤òÄê´üŪ¤Ë¼Â¹Ô¤¹¤ë»þ¤Ç¤¹¡£
.\"O It prevents a job from interfering with an earlier job that is perhaps
.\"O taking extra long because of network problems.
¤³¤ì¤Ï¡¢¤¢¤ë¥¸¥ç¥Ö¤¬¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÌäÂê¤ÇͽÁ۰ʾå¤Î»þ´Ö¤¬¤«¤«¤Ã¤Æ¤¤¤ë
°ÊÁ°¤Î¥¸¥ç¥Ö¤Î¼ÙËâ¤ò¤¹¤ë¤Î¤òËɤ®¤Þ¤¹¡£
.Pp
.\"O POSIX-style file locking is used, as described in
.\"O .Xr fcntl 2 .
POSIX ·Á¼°¤Î¥Õ¥¡¥¤¥ë¥í¥Ã¥­¥ó¥°¤¬»È¤ï¤ì¤Þ¤¹¡£¤³¤ì¤Ï
.Xr fcntl 2
¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O The process-ID is written to the lock file in text form when the lock
.\"O is successfully acquired.
¥×¥í¥»¥¹ ID ¤Ï¡¢¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤¬Àµ¾ï¤Ë¼èÆÀ¤Ç¤­¤¿»þ¤Ë¡¢¤³¤Î¥Õ¥¡¥¤¥ë¤Ë
¥Æ¥­¥¹¥È·Á¼°¤Ç½ñ¤­¹þ¤Þ¤ì¤Þ¤¹¡£
.\"O Upon termination of the update, the lock file is removed.
¹¹¿·¤Î½ªÎ»»þ¤Ë¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ïºï½ü¤µ¤ì¤Þ¤¹¡£
.It Fl L Ar verbosity
.\"O Sets the verbosity level for non-GUI output.
GUI ¤Ç¤Ê¤¤½ÐÎϤξܤ·¤µ¤òÀßÄꤷ¤Þ¤¹¡£
.\"O A level of 0 causes
.\"O .Nm
.\"O to be completely silent unless errors occur.
¥ì¥Ù¥ë 0 ¤Ç¤Ï¡¢¥¨¥é¡¼¤¬µ¯¤³¤é¤Ê¤¤¸Â¤ê
.Nm
¤Ï²¿¤â½ÐÎϤ·¤Þ¤»¤ó¡£
.\"O A level of 1 (the default) causes each updated file to be listed.
¥ì¥Ù¥ë 1 (¥Ç¥Õ¥©¥ë¥ÈÃÍ)¤Ç¤Ï¡¢¹¹¿·¤µ¤ì¤¿¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£
.\"O A level of 2 provides more detailed information about the updates
.\"O performed on each file.
¥ì¥Ù¥ë 2 ¤Ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¹Ô¤ï¤ì¤¿¹¹¿·¤Ë´Ø¤¹¤ë¤µ¤é¤Ë
¾Ü¤·¤¤¾ðÊ󤬽ÐÎϤµ¤ì¤Þ¤¹¡£
.\"O All messages are directed to the standard output.
¥á¥Ã¥»¡¼¥¸¤ÏÁ´¤Æ¡¢É¸½à½ÐÎϤ˽ÐÎϤµ¤ì¤Þ¤¹¡£
.\"O This option is ignored when the GUI is used.
GUI ¤¬»È¤ï¤ì¤ë¾ì¹ç¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£
.It Fl p Ar port
.\"O Sets the TCP port to which
.\"O .Nm
.\"O attempts to connect on the server host.
.Nm cvsup
¤¬Àܳ¤ò»î¤ß¤ë¥µ¡¼¥Ð¥Û¥¹¥È¤Î TCP ¥Ý¡¼¥È¤òÀßÄꤷ¤Þ¤¹¡£
.\"O This feature is primarily for testing.  The default port is 5999.
¤³¤Îµ¡Ç½¤Ï¼ç¤Ë¥Æ¥¹¥ÈÍѤǤ¹¡£¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 5999 ¤Ç¤¹¡£
.\"O When not in passive mode (see the description of the
.\"O .Fl P
.\"O option), the server also uses the next lower port to establish a second
.\"O connection back to the client.
passive ¥â¡¼¥É(
.Fl P
¥ª¥×¥·¥ç¥ó¤ÎÀâÌÀ¤ò»²¾È)¤Ç¤Ê¤±¤ì¤Ð¡¢¥µ¡¼¥Ð¤Ï¤³¤ì¤è¤ê°ì¤Ä¾®¤µ¤¤ÈÖ¹æ¤Î
¥Ý¡¼¥È¤ò»È¤Ã¤Æ¡¢µÕ¸þ¤­¤Î 2 ¤ÄÌܤÎÀܳ¤ò³ÎΩ¤·¤Þ¤¹¡£
.It Fl P Ar m|a|port|lo-hi|-
.\"O Controls the establishment of the auxiliary TCP connection(s) used to
.\"O carry information between the client and the server.
¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð´Ö¤Î¾ðÊó¤Î¤ä¤ê¤È¤ê¤Ë»È¤¦Êä½õŪ¤Ê TCP Àܳ¤Î³ÎΩ¤ò
À©¸æ¤·¤Þ¤¹¡£
.\"O Altogether, the client and server require four unidirectional channels
.\"O to communicate: two from the client to the server, and two from the
.\"O server to the client.
Á´ÂΤǤϡ¢¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤ÏÄÌ¿®¤¹¤ë¤¿¤á¤Ë 4 ¤Ä¤ÎÊÒÊý¸þ¥Á¥ã¥Í¥ë¤ò
ɬÍפȤ·¤Þ¤¹: 2 ¤Ä¤Ï¥¯¥é¥¤¥¢¥ó¥È¤«¤é¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤Ç¡¢2 ¤Ä¤Ï¥µ¡¼¥Ð¤«¤é
¥¯¥é¥¤¥¢¥ó¥È¤Ø¤ÎÀܳ¤Ç¤¹¡£
.\"O These four unidirectional channels can be set up in different ways, to
.\"O support various firewall setups.
¿§¡¹¤ÊËɲÐÊɤÎÀßÄê¤ËÂбþ¤¹¤ë¤¿¤á¤Ë¡¢¤³¤ì¤é 4 ¤Ä¤ÎÊÒÊý¸þ¥Á¥ã¥Í¥ë¤Ë¤Ï¿§¡¹
¤ÊÀßÄ꤬¤Ç¤­¤Þ¤¹¡£
.\"O The modes provided for this are multiplexed mode, passive mode, SOCKS
.\"O mode, and active mode.
¤³¤Î¤¿¤á¤ËÍÑ°Õ¤µ¤ì¤¿¥â¡¼¥É¤Ï¡¢multiplexed ¥â¡¼¥É, passive ¥â¡¼¥É¡¢
SOCKS ¥â¡¼¥É¡¢active ¥â¡¼¥É¤Ç¤¹¡£
.\"O All but multiplexed mode are deprecated.
multiplexed ¥â¡¼¥É¤ò½ü¤¯Á´¤Æ¤Î¥â¡¼¥É¤Ï¡¢¸Å¤¤¤Î¤Ç¤ª´«¤á¤Ç¤­¤Þ¤»¤ó¡£
.\"O Multiplexed mode can handle any situation that the other modes can
.\"O handle.
multiplexed ¥â¡¼¥É¤Ï¡¢Â¾¤Î¥â¡¼¥É¤¬°·¤¨¤ëÁ´¤Æ¤Î¾õ¶·¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
.Pp
.\"O By default the channels are established in multiplexed mode, if the
.\"O server is new enough to support it.
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥µ¡¼¥Ð¤¬½½Ê¬¿·¤·¤±¤ì¤Ð¥Á¥ã¥Í¥ë¤Ï multiplexed ¥â¡¼¥É¤Ç
³ÎΩ¤·¤Þ¤¹¡£
.\"O Multiplexed mode uses a single TCP connection to implement the
.\"O four channels.
multiplexed ¥â¡¼¥É¤Ï¡¢1 ¤Ä¤Î TCP Àܳ¤òÍѤ¤¤Æ 4 ¤Ä¤Î¥Á¥ã¥Í¥ë¤òºî¤ê¤Þ¤¹¡£
.\"O A built-in packet layer multiplexes the different logical channels
.\"O on top of the TCP connection, in a manner not unlike
.\"O .Nm ssh Ns No \&'s
.\"O port forwarding feature.
ÁȤ߹þ¤ß¤Î¥Ñ¥±¥Ã¥ÈÁؤǡ¢TCP Àܳ¾å¤Ë¤¢¤ë°Û¤Ê¤ëÏÀÍý¥Á¥ã¥Í¥ë¤ò
¿½Å²½¤·¤Þ¤¹¡£¤³¤ì¤Ï
.Nm ssh Ns No \&'s
¤Î¥Ý¡¼¥ÈžÁ÷µ¡Ç½¤È¤Ï°Û¤Ê¤ë¤ä¤êÊý¤Ç¹Ô¤ï¤ì¤Þ¤¹¡£
.\"O This adds a very small amount of communication overhead (<1%) and a
.\"O little bit of CPU overhead, but it should work behind almost any
.\"O kind of firewall setup.
¤³¤ì¤Ë¤è¤ê¡¢Èó¾ï¤Ë¾®¤µ¤¤(1% ̤Ëþ)ÄÌ¿®¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤È¤´¤¯¤ï¤º¤«¤Î CPU 
Éé²Ù¤¬¤«¤«¤ê¤Þ¤¹¤¬¡¢¤Û¤È¤ó¤É¤É¤ó¤ÊËɲÐÊɤÎÃæ¤Ç¤âÆ°ºî¤¹¤ë¤Ï¤º¤Ç¤¹¡£
.\"O The firewall must permit the client host to initiate connections
.\"O to port 5999 of the server host;
ËɲÐÊɤϡ¢¥¯¥é¥¤¥¢¥ó¥È¥Û¥¹¥È¤¬¥µ¡¼¥Ð¥Û¥¹¥È¤Î 5999 È֥ݡ¼¥È¤ØÀܳ¤ò³«»Ï
¤¹¤ë¤³¤È¤òµö²Ä¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O beyond that, no special permissions are required.
¤³¤ì°Ê³°¤Ë¤Ï¡¢Æüì¤Êµö²Ä¤ÏÁ´¤¯É¬Íפ¢¤ê¤Þ¤»¤ó¡£
.\"O To explicitly force multiplexed mode, use the option
.\"O .Fl P Cm m .
ÌÀ¼¨Åª¤Ë multiplexed ¥â¡¼¥É¤ò»ØÄꤹ¤ë¤Ë¤Ï¡¢
.Fl P Cm m
¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£
.Pp
.\"O Multiplexed mode can be used in conjunction with a SOCKS proxy server.
multiplexed ¥â¡¼¥É¤Ï SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð¤ÈÁȤ߹ç¤ï¤»¤Æ»È¤¨¤Þ¤¹¡£
.\"O Simply run
.\"O .Nm
.\"O under the
.\"O .Nm m3socks
.\"O command, and specify the
.\"O .Fl P Cm m
.\"O option.
ÁȤ߹ç¤ï¤»¤Æ»È¤¦¤Ë¤Ï¡¢Ã±¤Ë
.Nm m3socks
¥³¥Þ¥ó¥É¤Ë³¤±¤Æ
.Nm cvsup
¤ò¼Â¹Ô¤·¡¢
.Fl P Cm m
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Þ¤¹¡£
.Pp
.\"O Active mode implements the four unidirectional channels using two
.\"O bidirectional TCP connections.
active ¥â¡¼¥É¤Ï¡¢ÁÐÊý¸þ¤Î TCP Àܳ¤ò 2 ¤Ä»È¤Ã¤Æ 4 ¤Ä¤ÎÊÒÊý¸þ¥Á¥ã¥Í¥ë¤ò
ºî¤ê¤Þ¤¹¡£
.\"O The original connection from the client to the server implements two
.\"O channels, and a second TCP connection implements the other two channels.
ºÇ½é¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é¥µ¡¼¥Ð¤Ø¤Ï¤é¤ì¤¿Àܳ¤Ç 2 ¤Ä¤Î¥Á¥ã¥Í¥ë¤òºî¤ê¡¢
2 ÈÖÌܤΠTCP Àܳ¤¬»Ä¤ê¤Î 2 ¤Ä¤Î¥Á¥ã¥Í¥ë¤òºî¤ê¤Þ¤¹¡£
.\"O To establish the second TCP connection, the server connects back to the
.\"O client.  With
.\"O .Fl P Ar a ,
.\"O the client listens for the connection on a port chosen
.\"O by the operating system.
2 ÈÖÌܤΠTCP Àܳ¤ò³ÎΩ¤¹¤ë¤¿¤á¤Ë¡¢¥µ¡¼¥Ð¤«¤é¥¯¥é¥¤¥¢¥ó¥È¤Ø¤ÎÀܳ¤¬¹Ô
¤ï¤ì¤Þ¤¹¡£
.Fl P Ar a
¤Ç¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬Áª¤ó¤À¥Ý¡¼¥È¾å¤Ç
Àܳ¤òÂÔ¤Á¤Þ¤¹¡£
.\"O Many operating systems use ports in the range 1024-5000 for this
.\"O purpose.
¿¤¯¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ï¡¢¤³¤ÎÌÜŪ¤Ë¤Ï 1024-5000 ¤ÎÈϰϤÎ
¥Ý¡¼¥È¤ò»È¤¤¤Þ¤¹¡£
.\"O The user can specify a particular port with
.\"O .Fl P Ar port ,
.\"O or a range of ports with
.\"O .Fl P Ar lo-hi .
¥æ¡¼¥¶¤Ï
.Fl P Ar port
¤ò»È¤Ã¤ÆÆÃÄê¤Î¥Ý¡¼¥È¤ò»ØÄê¤Ç¤­¤Þ¤¹¤·¡¢
.Fl P Ar lo-hi
¤ò»È¤Ã¤Æ¤¢¤ëÈϰϤΥݡ¼¥È¤â»ØÄê¤Ç¤­¤Þ¤¹¡£
.\"O These port specifications cannot be used through a SOCKS proxy
.\"O server.
¤³¤ì¤é¤Î¥Ý¡¼¥È»ØÄê¤Ï SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£
.Pp
.\"O Passive mode is similar in that it also uses two TCP connections to
.\"O implement the four unidirectional channels.
passive ¥â¡¼¥É¤Ï¡¢4 ¤Ä¤ÎÊÒÊý¸þ¥Á¥ã¥Í¥ë¤òºî¤ë¤¿¤á¤Ë TCP Àܳ¤ò»È¤¦¤È¤¤
¤¦ÅÀ¤Ç¤Ï»÷¤Æ¤¤¤Þ¤¹¡£
.\"O However, in passive mode the client connects to the server to create the
.\"O second TCP connection.
¤·¤«¤·¡¢passive ¥â¡¼¥É¤Ç¤Ï 2 ÈÖÌܤΠTCP Àܳ¤òºî¤ë¤¿¤á¤ÎÀܳ¤Ï
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¥µ¡¼¥Ð¤ËÂФ·¤Æ¹Ô¤ï¤ì¤Þ¤¹¡£
.\"O Passive mode can be useful when the client is behind a firewall that
.\"O allows outbound connections, but denies most incoming connections.
passive ¥â¡¼¥É¤Ï¡¢³°¸þ¤­¤ÎÀܳ¤Ïµö²Ä¤¹¤ë¤±¤ì¤ÉÆâ¸þ¤­¤ÎÀܳ¤Ï¶Ø»ß¤·¤Æ¤¤
¤ëËɲÐÊɤÎÃæ¤Ë¥¯¥é¥¤¥¢¥ó¥È¤¬¤¤¤ë¾ì¹ç¤ËÊØÍø¤Ç¤¹¡£
.\"O To select passive mode, use the option
.\"O .Fl P Cm - .
passive ¥â¡¼¥É¤òÁªÂò¤¹¤ë¤Ë¤Ï¡¢
.Fl P Cm -
¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£
.\"O Passive mode cannot be used through a SOCKS proxy server.
passive ¥â¡¼¥É¤Ï SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£
.Pp
.\"O SOCKS mode is an alternate mode for use with SOCKS proxy servers.
SOCKS ¥â¡¼¥É¤Ï SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð¤ò»È¤¦¤¿¤á¤ÎÊ̥⡼¥É¤Ç¤¹¡£
.\"O In SOCKS mode, four TCP connections are used, each in one direction
.\"O only.
SOCKS ¥â¡¼¥É¤Ç¤Ï¡¢4 ¤Ä¤Î TCP Àܳ¤¬»È¤ï¤ì¤Þ¤¹¡£¤³¤ì¤é¤ÏÁ´¤ÆÊÒÊý¸þÀܳ
¤À¤±¤Ç¤¹¡£
.\"O The use of four unidirectional TCP connections works around a limitation
.\"O in the SOCKS proxy server that would otherwise cause it to deadlock.
4 ¤Ä¤ÎÊÒÊý¸þ TCP Àܳ¤ò»È¤¦¤³¤È¤Ë¤è¤ê¡¢SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð¤ÎÀ©¸Â¤ò
²óÈò¤·¤Þ¤¹¡£¤³¤ì¤ò¹Ô¤ï¤Ê¤±¤ì¤Ð¡¢¥Ç¥Ã¥É¥í¥Ã¥¯¤¬µ¯¤³¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
.\"O (Believe it or not, the SOCKS server uses blocking I/O calls.)
(¿®¤¸¤ë¤«¤É¤¦¤«¤Ï¤´¼«Í³¤Ç¤¹¤¬¡¢SOCKS ¥µ¡¼¥Ð¤Ï¥Ö¥í¥Ã¥­¥ó¥° I/O ¥³¡¼¥ë¤ò»È¤¤
¤Þ¤¹¡£)
.\"O SOCKS mode is selected when
.\"O .Nm
.\"O is run under the
.\"O .Nm m3socks
.\"O command, and no
.\"O .Fl P
.\"O option is given.
SOCKS ¥â¡¼¥É¤Ï¡¢
.Nm cvsup
¤¬
.Nm m3socks
¥³¥Þ¥ó¥É¤Î²¼¤Ç¼Â¹Ô¤µ¤ì¡¢¤«¤Ä
.Fl P
¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤»þ¤ËÁªÂò¤µ¤ì¤Þ¤¹¡£
.\"O See also
.\"O .Sx USING CVSup WITH SOCKS ,
.\"O below.
¸å½Ò¤Î
.Sx SOCKS ¤ÈÁȤ߹ç¤ï¤»¤Æ¤Î CVSup ¤ÎÍøÍÑ
¤â¤´Í÷¤¯¤À¤µ¤¤¡£
.\"O NAKANO --MARK--
.It Fl r Ar maxRetries
.\"O Limits the number of automatic retries that will be attempted when
.\"O transient errors such as lost network connections are encountered.  By
.\"O default, when the GUI is not used,
.\"O .Nm
.\"O will retry indefinitely until an update is successfully completed.
¼«Æ°¥ê¥È¥é¥¤¤Î²ó¿ô¤òÀ©¸Â¤·¤Þ¤¹¡£¼«Æ°¥ê¥È¥é¥¤¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤¬
ÀÚ¤ì¤ë¤È¤¤¤Ã¤¿°ì»þŪ¤Ê¥¨¥é¡¼¤¬µ¯¤­¤¿»þ¤Ë»î¤ß¤é¤ì¤Þ¤¹¡£
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢GUI ¤ò»È¤Ã¤Æ¤¤¤Ê¤¤»þ¡¢
.Nm
¤Ï¹¹¿·¤¬¤¦¤Þ¤¯´°Î»¤¹¤ë¤Þ¤Ç²¿Å٤Ǥâ¥ê¥È¥é¥¤¤ò¹Ô¤¤¤Þ¤¹¡£
.\"O The retries are spaced using randomized exponential backoff.
¥ê¥È¥é¥¤¤Î´Ö³Ö¤Ï¡¢¥é¥ó¥À¥à²½¤µ¤ì¤¿»Ø¿ôŪ¤Ê°ì»þÂàÈò¥¢¥ë¥´¥ê¥º¥à¤ò»È¤Ã¤Æ
·è¤á¤é¤ì¤Þ¤¹¡£
.\"O Use of the GUI implies
.\"O .Fl r Cm 0 .
GUI ¤ò»È¤¦¤È¡¢°ÅÌÛŪ¤Ë
.Fl r Cm 0
¤¬»ØÄꤵ¤ì¤Þ¤¹¡£
.\"O Note that
.\"O .Fl r Cm 0
.\"O is equivalent to the
.\"O .Fl 1
.\"O option.
.Fl r Cm 0
¤Ï
.Fl 1
¥ª¥×¥·¥ç¥ó¤ÈƱ¤¸°ÕÌ£¤Ç¤¢¤ëÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
.It Fl s
.\"O Suppresses the check of each client file's status against what is
.\"O recorded in the list file.  Instead, the list file is assumed to be
.\"O accurate.  This option greatly reduces the amount of disk activity and
.\"O results in faster updates with less load on the client host.  However
.\"O it should only be used if client's files are never modified locally in
.\"O any way.  Mirror sites may find this option beneficial to reduce the
.\"O disk load on their systems.  For safety, even mirror sites should run
.\"O .Nm
.\"O occasionally (perhaps once a day) without the
.\"O .Fl s
.\"O option.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Îµ­Ï¿¤ËÂФ·¤Æ¤Î³Æ¥¯¥é¥¤¥¢¥ó¥È¥Õ¥¡¥¤¥ë¤Î¾õÂ֤ΥÁ¥§¥Ã¥¯¤ò
¹Ô¤¤¤Þ¤»¤ó¡£¥Á¥§¥Ã¥¯¤ò¤·¤Ê¤¤Âå¤ï¤ê¤Ë¡¢¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤ÏÀµ³Î¤Ç¤¢¤ë¤â¤Î¤È
²¾Äꤷ¤Þ¤¹¡£¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤ÎÎ̤òÂçÉý¤Ë¸º¤é¤·¡¢
¾®¤µ¤Ê¥¯¥é¥¤¥¢¥ó¥È¥Û¥¹¥È¤ÎÉé²Ù¤Ç¹â®¤Ë¹¹¿·¤ò¹Ô¤¤¤Þ¤¹¡£¤·¤«¤·¡¢
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥Õ¥¡¥¤¥ë¤¬¥í¡¼¥«¥ë¤Ç½¤Àµ¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì
¹ç¤Ë¸Â¤Ã¤Æ»È¤¦¤Ù¤­¤Ç¤¹¡£¥ß¥é¡¼¥µ¥¤¥È¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È
¥·¥¹¥Æ¥à¤Î¥Ç¥£¥¹¥¯Éé²Ù¤ò¸º¤ë¤Î¤ÇÍø±×¤¬¤¢¤ë¤Ç¤·¤ç¤¦¡£°ÂÁ´¤Î¤¿¤á¤Ë¡¢
¥ß¥é¡¼¥µ¥¤¥È¤Ç¤¢¤Ã¤Æ¤â»þ¡¹(°ìÆü°ìÅÙ¤¯¤é¤¤)¤Ï
.Fl s
¥ª¥×¥·¥ç¥ó¤Ê¤·¤Ç
.Nm
¤ò¼Â¹Ô¤¹¤Ù¤­¤Ç¤¹¡£
.Pp
.\"O Without the
.\"O .Fl s
.\"O option,
.\"O .Nm
.\"O performs a
.\"O .Xr stat 2
.\"O call on each file and verifies that its attributes match those
.\"O recorded in the list file.  This ensures that any file changes made
.\"O outside of
.\"O .Nm CVSup
.\"O are detected and corrected.
.Fl s
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤¤È¡¢
.Nm
¤Ï¥Õ¥¡¥¤¥ë¤´¤È¤Ë
.Xr stat 2
¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò¼Â¹Ô¤·¡¢¥Õ¥¡¥¤¥ë¤Î°À­¤¬¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Îµ­Ï¿¤È°ìÃפ¹¤ë
¤«¤É¤¦¤«¤ò³Îǧ¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢
.Nm CVSup
³°Éô¤Ç¤Î¥Õ¥¡¥¤¥ëÊѹ¹¤ÏÁ´¤Æ¸¡½Ð¡¦ÄûÀµ¤µ¤ì¤ë¤³¤È¤¬Êݾڤµ¤ì¤Þ¤¹¡£
.Pp
.\"O If the
.\"O .Fl s
.\"O option is used when one or more files have been modified locally, the
.\"O results are undefined.  Local file damage may remain uncorrected,
.\"O updates may be missed, or
.\"O .Nm
.\"O may abort prematurely.
.Fl s
¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¡¢¤«¤Ä¥í¡¼¥«¥ë¤Ç¥Õ¥¡¥¤¥ë¤¬ 1 ¤Ä°Ê¾åÊѹ¹¤µ¤ì¤¿»þ¤Î
·ë²Ì¤Ï̤ÄêµÁ¤Ç¤¹¡£¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¤Î»½ý¤¬ÄûÀµ¤µ¤ì¤Ê¤¤¤Þ¤Þ»Ä¤Ã¤¿¤ê¡¢
¹¹¿·¤ò¼è¤ê¤³¤Ü¤·¤¿¤ê¡¢
.Nm
¤¬¼Â¹ÔÅÓÃæ¤Ç°Û¾ï½ªÎ»¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
.It Fl v
.\"O Prints the version number and exits, without contacting the server.
¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤òɽ¼¨¤·¤Æ½ªÎ»¤·¤Þ¤¹¡£¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤Ï¹Ô¤¤¤Þ¤»¤ó¡£
.It Fl z
.\"O Enables compression for all collections, as if the
.\"O .Cm compress
.\"O keyword were added to every collection in the
.\"O .Ar supfile .
Á´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤Î°µ½Ì¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£¤³¤ÎÆ°ºî¤Ï¡¢
.Ar supfile
¤Ë¤ª¤¤¤Æ¡¢
.Cm compress
¥­¡¼¥ï¡¼¥É¤òÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤ËÄɲä·¤¿»þ¤ÈƱÍͤǤ¹¡£
.It Fl Z
.\"O Disables compression for all collections, as if the
.\"O .Cm compress
.\"O keyword were removed from every collection in the
.\"O .Ar supfile .
Á´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤Î°µ½Ì¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£¤³¤ÎÆ°ºî¤Ï¡¢
.Ar supfile
¤Ë¤ª¤¤¤Æ¡¢
.Cm compress
¥­¡¼¥ï¡¼¥É¤òÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤«¤éºï½ü¤·¤¿»þ¤ÈƱÍͤǤ¹¡£
.El
.Pp
.\"O The
.\"O .Ar supfile
.\"O is a text file which specifies the file collections to be updated.
.Ar supfile
¤Ï¡¢¹¹¿·¤¹¤Ù¤­¥Õ¥¡¥¤¥ë¤Î¥³¥ì¥¯¥·¥ç¥ó¤ò»ØÄꤹ¤ë¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Ç¤¹¡£
.\"O Comments begin with
.\"O .Ql #
.\"O and extend to the end of the line.  Lines that are empty except for
.\"O comments and white space are ignored.  Each remaining line begins
.\"O with the name of a server-defined collection of files.  Following the
.\"O collection name on the line are zero or more keywords or keyword=value
.\"O pairs.
¥³¥á¥ó¥È¤Ï
.Ql #
¤Ç»Ï¤Þ¤ê¡¢¤½¤Î¹Ô¤ÎºÇ¸å¤Þ¤Ç³¤­¤Þ¤¹¡£¥³¥á¥ó¥È¤È¶õÇò¤ò½ü¤¯¤È¶õ¤Ç¤¢¤ë¹Ô¤Ï
̵»ë¤µ¤ì¤Þ¤¹¡£»Ä¤ê¤Î¤½¤ì¤¾¤ì¤Î¹Ô¤Ï¡¢¥µ¡¼¥ÐÄêµÁ¤Î¥Õ¥¡¥¤¥ë¤Î¥³¥ì¥¯¥·¥ç¥ó
¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£¤³¤Î¹Ô¤Ç¥³¥ì¥¯¥·¥ç¥ó̾¤Î¸å¤Ë³¤¯¤Î¤Ï¡¢0 ¸Ä°Ê¾å¤Î¥­¡¼¥ï¡¼¥É
¤Þ¤¿¤Ï¡Ö¥­¡¼¥ï¡¼¥É=Ã͡פÎÁȤǤ¹¡£
.Pp
.\"O Default settings may be specified in lines whose collection name is
.\"O .Cm *default .
¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ï¡¢¥³¥ì¥¯¥·¥ç¥ó̾¤¬
.Cm *default
¤Ç¤¢¤ë¹Ô¤Ç»ØÄê¤Ç¤­¤Þ¤¹¡£
.\"O Such defaults will apply to subsequent lines in the
.\"O .Ar supfile .
¤³¤Î¥Ç¥Õ¥©¥ë¥È¤Ï¡¢
.Ar supfile
Æâ¤Î¤½¤ì°Ê¹ß¤Î¹Ô¤ËŬÍѤµ¤ì¤Þ¤¹¡£
.\"O Multiple
.\"O .Cm *default
.\"O lines may be present.
.Cm *default
¹Ô¤ÏÊ£¿ô¸Ä¤¢¤Ã¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£
.\"O New values augment or override any defaults specified earlier in the
.\"O .Ar supfile .
¿·¤·¤¤Ãͤϡ¢
.Ar supfile
¤ÇÁ°¤Ë»ØÄꤵ¤ì¤¿¥Ç¥Õ¥©¥ë¥ÈÃͤËÄɲ䵤ì¤ë¤«¡¢¥Ç¥Õ¥©¥ë¥ÈÃͤò¾å½ñ¤­¤·¤Þ¤¹¡£
.\"O Values specified explicitly for a collection override any default
.\"O values.
¥³¥ì¥¯¥·¥ç¥ó¤ËÂФ·¤ÆÌÀ¼¨Åª¤Ë»ØÄꤵ¤ì¤¿Ãͤϡ¢Á´¤Æ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤò
¾å½ñ¤­¤·¤Þ¤¹¡£
.Pp
.\"O The most commonly used keywords are:
Æäˤ褯»È¤ï¤ì¤ë¥­¡¼¥ï¡¼¥É¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:
.Bl -tag -width Fl
.It Cm release= Ns Ar releaseName
.\"O This specifies the release of the files within a collection.
¤³¤ì¤Ï¥³¥ì¥¯¥·¥ç¥óÆâ¤Î¥Õ¥¡¥¤¥ë¤Î¥ê¥ê¡¼¥¹¤ò»ØÄꤷ¤Þ¤¹¡£
.\"O Like collection names, release names are defined by the server
.\"O configuration files.  Usually there is only one release in each
.\"O collection, but there may be any number.  Collections which come from
.\"O a CVS repository often use
.\"O .Cm release=cvs
.\"O by convention.  Non-CVS collections conventionally use
.\"O .Cm release=current .
¥³¥ì¥¯¥·¥ç¥ó̾¤ÈƱ¤¸¤¯¡¢¥ê¥ê¡¼¥¹Ì¾¤â¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ëÆâ¤ÇÄêµÁ¤µ¤ì¤Æ
¤¤¤Þ¤¹¡£ÉáÄ̤ϳƥ³¥ì¥¯¥·¥ç¥óÆâ¤Ë 1 ¤Ä¤Î¥ê¥ê¡¼¥¹¤·¤«´Þ¤Þ¤ì¤Æ¤¤¤Þ¤»¤ó¤¬¡¢
²¿¸Ä´Þ¤ó¤Ç¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£CVS ¥ê¥Ý¥¸¥È¥ê¤«¤éÆÀ¤¿¥³¥ì¥¯¥·¥ç¥ó¤Ç¤Ï¡¢
´·½¬Åª¤Ë
.Cm release=cvs
¤ò¤è¤¯»È¤¤¤Þ¤¹¡£CVS ¤Ç¤Ê¤¤¥³¥ì¥¯¥·¥ç¥ó¤Ç¤Ï¡¢´·½¬Åª¤Ë
.Cm release=current
¤ò»È¤¤¤Þ¤¹¡£
.It Cm base= Ns Ar base
.\"O This specifies a directory under which
.\"O .Nm cvsup
.\"O will maintain its bookkeeping files, describing the state of each
.\"O collection on the client machine.
¤³¤ì¤Ï
.Nm cvsup
¤¬µ­Ï¿¥Õ¥¡¥¤¥ë¤òÃÖ¤¤¤Æ´ÉÍý¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£
µ­Ï¿¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Ë¤¢¤ë³Æ¥³¥ì¥¯¥·¥ç¥ó¤Î¾õÂÖ¤¬
½ñ¤«¤ì¤Þ¤¹¡£
.\"O The
.\"O .Ar base
.\"O directory must already exist;
.Ar base
¥Ç¥£¥ì¥¯¥È¥ê¤Ï´û¤Ë¸ºß¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O .Nm
.\"O will not create it.
.Nm
¤¬¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òºîÀ®¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.\"O The default
.\"O .Ar base
.\"O directory is
.\"O .Pa /usr/local/etc/cvsup .
.Ar base
¥Ç¥£¥ì¥¯¥È¥ê¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤÏ
.Pa /usr/local/etc/cvsup
¤Ç¤¹¡£
.It Cm prefix= Ns Ar prefix
.\"O This is the directory under which updated files will be placed.
¤³¤ì¤Ï¡¢¹¹¿·¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤¬ÃÖ¤«¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¹¡£
.\"O By default, it is the same as
.\"O .Ar base .
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¤³¤ì¤Ï
.Ar base
¤ÈƱ¤¸¤Ç¤¹¡£
.\"O If it is not an absolute pathname, it is interpreted relative to
.\"O .Ar base .
ÀäÂХѥ¹¤Ç»ØÄꤷ¤Ê¤±¤ì¤Ð¡¢
.Ar base
¤«¤é¤ÎÁêÂХѥ¹¤È²ò¼á¤µ¤ì¤Þ¤¹¡£
.\"O The
.\"O .Ar prefix
.\"O directory must already exist;
.Ar prefix
¥Ç¥£¥ì¥¯¥È¥ê¤Ï´û¤Ë¸ºß¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O .Nm
.\"O will not create it.
.Nm
¤¬¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òºîÀ®¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.Pp
.\"O As a special case, if
.\"O .Ar prefix
.\"O is a symbolic link pointing to a nonexistent file named
.\"O .Ql SKIP ,
.\"O then
.\"O .Nm
.\"O will skip the collection.
Æüì¤Ê¾ì¹ç¤È¤·¤Æ¡¢
.Ar prefix
¤¬
.Ql SKIP
¤È¤¤¤¦Ì¾¤Î¸ºß¤·¤Ê¤¤¥Õ¥¡¥¤¥ë¤ò»Ø¤¹¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ç¤¢¤ë¾ì¹ç¤Ï¡¢
.Nm
¤Ï¤½¤Î¥³¥ì¥¯¥·¥ç¥ó¤ò¥¹¥­¥Ã¥×¤·¤Þ¤¹¡£
.\"O The parameters associated with the collection are still checked for
.\"O validity, but none of its files will be updated.
¤³¤Î¾ì¹ç¤Ç¤â¥³¥ì¥¯¥·¥ç¥ó¤Ë´Ø·¸¤¹¤ë¥Ñ¥é¥á¡¼¥¿¤ÎÀµ¤·¤µ¤Ï¥Á¥§¥Ã¥¯¤µ¤ì¤Þ¤¹
¤¬¡¢¥³¥ì¥¯¥·¥ç¥ó¤Î¥Õ¥¡¥¤¥ë¤ÏÁ´¤¯¹¹¿·¤µ¤ì¤Þ¤»¤ó¡£
.\"O This feature allows a site to use a standard
.\"O .Ar supfile
.\"O on several machines, yet control which collections get updated on a
.\"O per-machine basis.
¤³¤Îµ¡Ç½¤ò»È¤¦¤È¡¢°ì¤Ä¤Î¥µ¥¤¥È¤ÎÊ£¿ô¤Î¥Þ¥·¥ó¤Çɸ½à¤Î
.Ar supfile
¤ò»È¤¤¤Ê¤¬¤é¡¢¹¹¿·¤¹¤ë¥³¥ì¥¯¥·¥ç¥ó¤ò¥Þ¥·¥ó¤´¤È¤ËÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.It Cm host= Ns Ar hostname
.\"O This specifies the server machine from which all files will be taken.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢Á´¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò¼è¤ê´ó¤»¤ë¸µ¤È¤Ê¤ë¥µ¡¼¥Ð¥Þ¥·¥ó¤ò
»ØÄꤷ¤Þ¤¹¡£
.\"O .Nm
.\"O requires that all collections in a single run come from the same host.
.Nm
¤Ï¡¢1 ²ó¤Î¼Â¹Ô¤Ë¤ª¤±¤ëÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤òƱ¤¸¥Û¥¹¥È¤«¤éÆÀ¤ë¤³¤È¤ò
ɬÍפȤ·¤Þ¤¹¡£
.\"O If you wish to update collections from several different hosts, you must
.\"O run
.\"O .Nm
.\"O several times.
°Û¤Ê¤ëÊ£¿ô¤Î¥Û¥¹¥È¤«¤é¥³¥ì¥¯¥·¥ç¥ó¤ò¹¹¿·¤·¤¿¤±¤ì¤Ð¡¢
.Nm
¤òÊ£¿ô²ó¼Â¹Ô¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.It Cm delete
.\"O The presence of this keyword gives
.\"O .Nm
.\"O permission to delete files.
¤³¤Î¥­¡¼¥ï¡¼¥É¤¬¤¢¤ë¤È¡¢
.Nm
¤Ï¥Õ¥¡¥¤¥ë¤Îºï½ü¤òµö²Ä¤·¤Þ¤¹¡£
.\"O If it is missing, no files will be deleted.
¤³¤Î¥­¡¼¥ï¡¼¥É¤¬¤Ê¤±¤ì¤Ð¡¢¥Õ¥¡¥¤¥ë¤ÏÁ´¤¯ºï½ü¤µ¤ì¤Þ¤»¤ó¡£
.Pp
.\"O The presence of the
.\"O .Cm delete
.\"O keyword puts
.\"O .Nm
.\"O into so-called
.\"O .Em exact
.\"O mode.  In exact mode,
.\"O .Nm CVSup
.\"O does its best to make the client's files correspond to those on the server.
.Cm delete
¥­¡¼¥ï¡¼¥É¤¬¤¢¤ë¤È¡¢
.Nm
¤Ï¤¤¤ï¤æ¤ë
.Em exact
¥â¡¼¥É¤ËÆþ¤ê¤Þ¤¹¡£exact ¥â¡¼¥É¤Ç¤Ï¡¢
.Nm CVSup
¤Ï¤Ç¤­¤ë¤À¤±¥¯¥é¥¤¥¢¥ó¥È¦¤Î¥Õ¥¡¥¤¥ë¤ò¥µ¡¼¥Ð¦¤Î¥Õ¥¡¥¤¥ë¤ËÂбþ¤µ¤»¤è¤¦
¤È¤·¤Þ¤¹¡£
.\"O This includes deleting individual deltas and symbolic tags from RCS
.\"O files, as well as deleting entire files.
¤³¤ì¤Ï¡¢RCS ¥Õ¥¡¥¤¥ë¤«¤é¸Ä¡¹¤Îº¹Ê¬¤È¥·¥ó¥Ü¥ê¥Ã¥¯¤Ê¥¿¥°¤ò¾Ã¤¹¤³¤È¤È¡¢
¥Õ¥¡¥¤¥ëÁ´ÂΤò¾Ã¤¹¤³¤È¤ò´Þ¤ß¤Þ¤¹¡£
.\"O In exact mode,
.\"O .Nm CVSup
.\"O verifies every edited file with a checksum, to ensure that the edits
.\"O have produced a file identical to the master copy on the server.
exact ¥â¡¼¥É¤Ç¤Ï¡¢
.Nm CVSup
¤ÏÊÔ½¸¤µ¤ì¤¿¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤ò¥Á¥§¥Ã¥¯¥µ¥à¤ò»È¤Ã¤ÆÄ´¤Ù¡¢ÊÔ½¸¤Ë¤è¤Ã¤Æ
¥µ¡¼¥Ð¾å¤Ë¤¢¤ë¥Þ¥¹¥¿¡¼¥³¥Ô¡¼¤ÈƱ°ì¤Î¥Õ¥¡¥¤¥ë¤¬¤Ç¤­¤ë¤³¤È¤òÊݾڤ·¤Þ¤¹¡£
.\"O If the checksum test fails for a file, then
.\"O .Nm CVSup
.\"O falls back upon transferring the entire file.
¤¢¤ë¥Õ¥¡¥¤¥ë¤Ë¤Ä¤¤¤Æ¥Á¥§¥Ã¥¯¥µ¥à¤Î¥Æ¥¹¥È¤¬¼ºÇÔ¤·¤¿¤é¡¢
.Nm CVSup
¤ÏºÇ¸å¤Î¼êÃʤȤ·¤Æ¥Õ¥¡¥¤¥ëÁ´ÂΤòžÁ÷¤·¤Þ¤¹¡£
.Pp
.\"O In general,
.\"O .Nm CVSup
.\"O deletes only files which are known to the server.
°ìÈÌŪ¤Ë¤Ï¡¢
.Nm CVSup
¤Ï¥µ¡¼¥Ð¤¬ÃΤäƤ¤¤ë¥Õ¥¡¥¤¥ë¤À¤±¤òºï½ü¤·¤Þ¤¹¡£
.\"O Extra files present in the client's tree are left alone, even in exact
.\"O mode.
¥¯¥é¥¤¥¢¥ó¥È¤Î¥Ä¥ê¡¼¤ËÆþ¤Ã¤Æ¤¤¤ëÄɲäΥե¡¥¤¥ë¤Ï¡¢excact ¥â¡¼¥É¤Ç¤¢¤Ã
¤Æ¤â¤½¤Î¤Þ¤Þ»Ä¤µ¤ì¤Þ¤¹¡£
.\"O More precisely,
.\"O .Nm CVSup
.\"O is willing to delete two classes of files:
¤è¤êÀµ³Î¤Ë½Ò¤Ù¤ë¤È¡¢
.Nm CVSup
¤¬¾Ã¤½¤¦¤È¤¹¤ë¥Õ¥¡¥¤¥ë¤Ï 2 ¼ïÎà¤Ç¤¹:
.Bl -bullet -compact
.It
.\"O Files that were previously created or updated by
.\"O .Nm CVSup
.\"O itself.
²áµî¤Ë
.Nm CVSup
¼«¿È¤¬À¸À®¤Þ¤¿¤Ï¹¹¿·¤·¤¿¥Õ¥¡¥¤¥ë¡£
.It
.\"O Checked-out versions of files which are marked as dead on the server.
¥µ¡¼¥Ð¾å¤ÇÉÔÍפΰõ¤¬ÉÕ¤±¤é¤ì¤¿¥Á¥§¥Ã¥¯¥¢¥¦¥ÈºÑ¤ß¥Ð¡¼¥¸¥ç¥ó¤Î¥Õ¥¡¥¤¥ë¡£
.El
.It Cm use-rel-suffix
.\"O Causes
.\"O .Nm
.\"O to append a suffix constructed from the release and tag to the name of
.\"O each list file that it maintains.
¥ê¥ê¡¼¥¹¤È¥¿¥°¤«¤éºî¤Ã¤¿¥µ¥Õ¥£¥Ã¥¯¥¹¤¬
.Nm
¤¬´ÉÍý¤·¤Æ¤¤¤ë³Æ¥Õ¥¡¥¤¥ë¤Î̾Á°¤ËÄɲ䵤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O See
.\"O .Sx THE LIST FILE
.\"O for details.
¾Ü¤·¤¯¤Ï
.Sx ¥ê¥¹¥È¥Õ¥¡¥¤¥ë
¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
.It Cm compress
.\"O This enables compression of all data sent across the network.
¥Í¥Ã¥È¥ï¡¼¥¯¾å¤ÇÁ÷¤é¤ì¤ë¥Ç¡¼¥¿¤¬Á´¤Æ°µ½Ì¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O Compression is quite effective, normally eliminating 65% to 75% of the
.\"O bytes that would otherwise need to be transferred.
°µ½Ì¤ÏÈó¾ï¤ËÍ­¸ú¤Ç¤¢¤ê¡¢°µ½Ì¤·¤Ê¤«¤Ã¤¿¾ì¹ç¤ËɬÍפÊžÁ÷Î̤ÈÈæ¤Ù¤Æ
ÉáÄÌ¤Ï 65% ¤«¤é 75% ¤Î¥Ð¥¤¥È¥Ç¡¼¥¿¤òºï¸º¤Ç¤­¤Þ¤¹¡£
.\"O However, it is costly in terms of CPU time on both the client and the
.\"O server.
¤·¤«¤·¡¢¥¯¥é¥¢¥¤¥ó¥È¤È¥µ¡¼¥ÐξÊý¤Î CPU »þ´Ö¤È¤¤¤¦ÅÀ¤Ç¤Ï¥³¥¹¥È¤¬¤«¤«¤ê
¤Þ¤¹¡£
.\"O On local area networks, compression is generally counter-productive; it
.\"O actually slows down file updates.
LAN ¤Ç¤Ï¡¢°µ½Ì¤Ï°ìÈÌŪ¤ËÀ¸»ºÀ­¤òÍî¤È¤·¤Þ¤¹¡£¼ÂºÝ¤Ë¤Ï¥Õ¥¡¥¤¥ë¤Î¹¹¿·¤¬
ÃÙ¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
.\"O On links with speeds of 56K bits/second or less, compression is almost
.\"O always beneficial.
56K ¥Ó¥Ã¥È/É䢤뤤¤Ï¤½¤ì°Ê²¼¤Î®ÅÙ¤ÎÀܳ¤Ç¤Ï¡¢°µ½Ì¤Ï¤Û¤Ü³Î¼Â¤Ë
ÆÀ¤Ë¤Ê¤ê¤Þ¤¹¡£
.\"O For network links with speeds between these two extremes, let
.\"O experimentation be your guide.
¤³¤ì¤éξ¶Ëü¤Ê¥±¡¼¥¹¤ÎÃæ´Ö¤Î®Å٤Υͥåȥ¥¯Àܳ¤Ç¤Ï¡¢¼Â¸³¤ò
¹Ô¤Ã¤Æ»²¹Í¤È¤·¤Þ¤·¤ç¤¦¡£
.Pp
.\"O The
.\"O .Fl z
.\"O command line option enables the
.\"O .Cm compress
.\"O keyword for all collections, regardless of what is specified in the supfile.
.Fl z
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ï¡¢Á´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤ËÂФ·¤Æ
.Cm compress
¥­¡¼¥ï¡¼¥É¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£supfile ¤Ç¤Î»ØÄê¤È¤Ï̵´Ø·¸¤Ç¤¹¡£
.\"O Likewise, the
.\"O .Fl Z
.\"O command line option disables the
.\"O .Cm compress
.\"O option for all collections.
ƱÍͤË
.Fl Z
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ï¡¢Á´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤ËÂФ·¤Æ
.Cm compress
¥ª¥×¥·¥ç¥ó¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
.It Cm norcs
.\"O Disables special processing for RCS files.  They will be treated the
.\"O same as other files.
RCS ¥Õ¥¡¥¤¥ë¤ÎÆÃÊÌ°·¤¤¤ò¤Ê¤¯¤·¤Þ¤¹¡£RCS ¥Õ¥¡¥¤¥ë¤Ï¾¤Î¥Õ¥¡¥¤¥ë¤È
Ʊ¤¸¤è¤¦¤Ë°·¤ï¤ì¤Þ¤¹¡£
.It Cm norsync
.\"O Disables the use of Tridgell & Mackerras'
.\"O .Em rsync
.\"O algorithm for updating regular (non-RCS) files.
Ä̾ï¤Î(RCS ¤Ç¤Ê¤¤)¥Õ¥¡¥¤¥ë¤Î¹¹¿·¤ÎºÝ¤Ë¡¢Tridgell ¤È Mackerras ¤Î
.Em rsync
¥¢¥ë¥´¥ê¥º¥à¤ò»È¤¤¤Þ¤»¤ó¡£
.\"O The algorithm works correctly for any kind of file, but it may be
.\"O ineffective and computationally expensive for files such as
.\"O compressed tar archives.
¤³¤Î¥¢¥ë¥´¥ê¥º¥à¤Ï¤É¤ó¤Ê¼ïÎà¤Î¥Õ¥¡¥¤¥ë¤Ç¤âÀµ¤·¤¯Æ°ºî¤·¤Þ¤¹¤¬¡¢
°µ½Ì¤µ¤ì¤¿ tar ¥¢¡¼¥«¥¤¥Ö¤Î¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¤Ï¡¢
¸úΨŪ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤··×»»Åª¤Ë¤â¥³¥¹¥È¤¬¹â¤¯ÉÕ¤­¤Þ¤¹¡£
.It Cm strictrcs
.\"O Causes updated RCS files to be checked using strict byte-by-byte MD5
.\"O checksums.  Normally,
.\"O .Nm CVSup
.\"O uses a looser checksum for RCS files, which ignores harmless
.\"O differences in white space.  Different versions of CVS and RCS produce
.\"O a variety of differences in white space for the same RCS files.  Thus
.\"O the strict checksum can report spurious mismatches for files which are
.\"O logically identical.  This can lead to numerous unneeded
.\"O .Dq fixups ,
.\"O and thus to slow updates.
¹¹¿·¤µ¤ì¤¿ RCS ¥Õ¥¡¥¤¥ë¤ò¥Ð¥¤¥Èñ°Ì¤Î¸·Ì©¤Ê MD5 ¥Á¥§¥Ã¥¯¥µ¥à¤Ç
³Îǧ¤·¤Þ¤¹¡£Ä̾
.Nm CVSup
¤Ï RCS ¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¤â¤Ã¤È´Ë¤¤¥Á¥§¥Ã¥¯¥µ¥à¤òÍѤ¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢
¶õÇòʸ»ú¤Ë¤è¤ë̵°ÕÌ£¤Ê°ã¤¤¤ò̵»ë¤·¤Þ¤¹¡£°Û¤Ê¤ë¥Ð¡¼¥¸¥ç¥ó¤Î
CVS ¤È RCS ¤Ï¡¢Æ±¤¸ RCS ¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¤â¶õÇò¤¬ÍÍ¡¹¤Ë°Û¤Ê¤ê¤Þ¤¹¡£
¤·¤¿¤¬¤Ã¤Æ¸·Ì©¤Ê¥Á¥§¥Ã¥¯¥µ¥à¤ò¼è¤ë¤È¡¢ÏÀÍýŪ¤Ë¤ÏƱ¤¸¤Ç¤¢¤ë¥Õ¥¡¥¤¥ë¤ËÂÐ
¤·¤Æ°ÕÌ£¤¬¤Ê¤¤ÉÔ°ìÃפòÊó¹ð¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤³¤ì¤Ë¤è¤êÉÔÍפÊ
.Dq fixups
¤¬ÂçÎ̤˹Ԥï¤ì¡¢¹¹¿·¤¬ÃÙ¤¯¤Ê¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.It Cm nocheckrcs
.\"O Disables the comparison of MD5 checksums for updated RCS files.
¹¹¿·¤µ¤ì¤¿ RCS ¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¡¢MD5 ¥Á¥§¥Ã¥¯¥µ¥à¤ÎÈæ³Ó¤ò¹Ô¤¤¤Þ¤»¤ó¡£
.\"O This option is turned on automatically if the
.\"O .Cm delete
.\"O keyword is not specified.
.Cm delete
¥­¡¼¥ï¡¼¥É¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤¬¼«Æ°Åª¤Ë
Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
.It Cm execute
.\"O Enables the execution of shell commands received from the server.
¥µ¡¼¥Ð¤«¤é¼õ¤±¼è¤Ã¤¿¥·¥§¥ë¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O This should be used with caution, since it may constitute a security
.\"O risk.
¤³¤Î¥ª¥×¥·¥ç¥ó¤ÏÃí°Õ¤·¤Æ»È¤¦¤Ù¤­¤Ç¤¹¡£¤È¤¤¤¦¤Î¤â¡¢¥»¥­¥å¥ê¥Æ¥£¤Ê´í¸±¤ò
µÚ¤Ü¤¹¤«¤â¤·¤ì¤Ê¤¤¤«¤é¤Ç¤¹¡£
.It Cm preserve
.\"O Causes
.\"O .Nm
.\"O to attempt to transfer all possible file attributes from the server
.\"O to the client.  The attributes supported depend on both the host
.\"O platform and the client platform.  On FreeBSD systems, the following
.\"O attributes are supported:
.Nm
¤Ë¡¢²Äǽ¤ÊÁ´¤Æ¤Î°À­¤ò¥µ¡¼¥Ð¤«¤é¥¯¥é¥¤¥¢¥ó¥È¤ËžÁ÷¤·¤è¤¦¤È»î¤ß¤µ¤»¤Þ¤¹¡£
¥µ¥Ý¡¼¥È¤µ¤ì¤ë°À­¤Ï¥Û¥¹¥È¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤È¥¯¥é¥¤¥¢¥ó¥È¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à
¤Ë°Í¸¤·¤Þ¤¹¡£FreeBSD ¥·¥¹¥Æ¥à¤Ç¤Ï¡¢°Ê²¼¤Î°À­¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹:
.Bl -bullet -compact
.It
.\"O Owner.
½êÍ­¼Ô
.It
.\"O Group.
¥°¥ë¡¼¥×
.It
.\"O Permissions.
¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó
.It
.\"O Flags.
¥Õ¥é¥°
.It
.\"O Modification time.
½¤Àµ»þ¹ï
.El
.Pp
.\"O Of these, the first four are controlled by the
.\"O .Cm preserve
.\"O keyword, while the fifth is preserved in all cases.
¤³¤ì¤é¤Î¤¦¤Á¡¢ºÇ½é¤Î 4 ¤Ä¤Î°À­¤Ï
.Cm preserve
¥­¡¼¥ï¡¼¥É¤ÇÀ©¸æ¤·¤Þ¤¹¡£5 ¤ÄÌܤϤɤó¤Ê¾ì¹ç¤Ç¤âÊݸ¤µ¤ì¤Þ¤¹¡£
.Pp
.\"O The
.\"O .Cm preserve
.\"O keyword is not intended to be used for updating user files or CVS
.\"O repositories.
.Cm preserve
¥­¡¼¥ï¡¼¥É¤Ï¡¢¥æ¡¼¥¶¥Õ¥¡¥¤¥ë¤ä CVS ¥ê¥Ý¥¸¥È¥ê¤Î¹¹¿·¤Ë»È¤¦¤¿¤á¤Î¤â¤Î¤Ç
¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.\"O It is intended only for specialized applications in which a host's entire
.\"O file tree is to be replicated exactly.
¤³¤ì¤Ï¡¢¥Û¥¹¥È¤ÎÁ´ÂΤΥե¡¥¤¥ë¥Ä¥ê¡¼¤òÀµ³Î¤ËÊ£À½¤¹¤ë¤È¤¤¤Ã¤¿Æüì¤ÊÌÜŪ
¤Î¤¿¤á¤À¤±¤Ë»È¤ï¤ì¤Þ¤¹¡£
.\"O Any differences between the server host and the client host can
.\"O cause problems if
.\"O .Cm preserve
.\"O is specified.
.Cm preserve
¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢¥µ¡¼¥Ð¥Û¥¹¥È¤È¥¯¥é¥¤¥¢¥ó¥È¥Û¥¹¥È¤Î²¿¤é¤«¤Î°ã¤¤¤¬
ÌäÂê¤òµ¯¤³¤¹¤«¤â¤·¤ì¤Þ¤»¤ó¡£
.\"O For example, if the client receives a file whose owner does not
.\"O exist on the client machine, it will be unable to preserve the
.\"O owner.
Î㤨¤Ð¡¢¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Ë¸ºß¤·¤Ê¤¤½êÍ­¼Ô¤¬½êÍ­¤¹¤ë¥Õ¥¡¥¤¥ë¤ò
¥¯¥é¥¤¥¢¥ó¥È¤¬¼õ¤±¼è¤Ã¤¿¾ì¹ç¡¢¥ª¡¼¥Ê¤òÊݸ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
.\"O This may in turn cause the permissions to have unintended meanings.
ƱÍͤˤ³¤ì¤Ë¤è¤Ã¤Æ°Õ¿Þ¤·¤Ê¤¤¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤¬ÀßÄꤵ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.\"O In addition, each subsequent update run will cause further unsuccessful
.\"O attempts to correct the file's owner on the client, wasting time
.\"O and bandwidth.
¤µ¤é¤Ë¡¢¤½¤ì°Ê¹ß¤Î¹¹¿·¤Ç¤Ï¡¢Ëè²ó¥¯¥é¥¤¥¢¥ó¥È¾å¤Î¥Õ¥¡¥¤¥ë¤Î½êÍ­¼Ô¤òÄûÀµ
¤·¤è¤¦¤È¤·¤Æ¼ºÇÔ¤·¡¢»þ´Ö¤ÈÂÓ°èÉý¤ò̵Â̤ˤ·¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£
.\"O Finally,
.\"O .Cm preserve
.\"O mode increases the network traffic and slows down updates.
ºÇ¸å¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢
.Cm preserve
¥â¡¼¥É¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥È¥é¥Õ¥£¥Ã¥¯¤òÁýÂ礵¤»¡¢¹¹¿·¤òÃÙ¤¯¤·¤Þ¤¹¡£
.Pp
.\"O For
.\"O .Cm preserve
.\"O mode to function properly, the client must be executed with root
.\"O access permissions.
.Cm preserve
¥â¡¼¥É¤òÀµ¤·¤¯µ¡Ç½¤µ¤»¤ë¤¿¤á¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï root ¤Î¥¢¥¯¥»¥¹¸¢¸Â¤Ç
¼Â¹Ô¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O If the client is not root, then attempts to preserve the owner,
.\"O group, and flags are suppressed.
¥¯¥é¥¤¥¢¥ó¥È¤¬ root ¤Ç¤Ê¤±¤ì¤Ð¡¢½êÍ­¼Ô¡¢¥°¥ë¡¼¥×¡¢¥Õ¥é¥°¤Î¾ðÊó¤òÊݸ¤·
¤è¤¦¤È¤¹¤ëµ¡Ç½¤Ï̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
.Pp
.\"O The
.\"O .Cm preserve
.\"O keyword is ignored in checkout mode.
.Cm preserve
¥­¡¼¥ï¡¼¥É¤Ï¡¢checkout ¥â¡¼¥É¤Ç¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£
.It Cm umask= Ns Ar n
.\"O Causes
.\"O .Nm
.\"O to use a umask value of
.\"O .Ar n
.\"O (an octal number) when updating the files in the collection.
¥³¥ì¥¯¥·¥ç¥óÆâ¤Î¥Õ¥¡¥¤¥ë¤ò¹¹¿·¤¹¤ë»þ¡¢
.Nm
¤Ë umask ÃÍ
.Ar n
(8 ¿ÊÃÍ)¤ò»È¤ï¤»¤Þ¤¹¡£
.\"O This option is ignored if
.\"O .Cm preserve
.\"O is specified.
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢
.Cm preserve
¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È̵»ë¤µ¤ì¤Þ¤¹¡£
.El
.Pp
.\"O Some additional, more specialized keywords are described below.
¤¤¤¯¤Ä¤«¤ÎÄɲÃŪ¤Ç¡¢¤è¤êÀìÌçŪ¤Ê¥­¡¼¥ï¡¼¥É¤Ë¤Ä¤¤¤Æ¤Ï¸å½Ò¤·¤Þ¤¹¡£
.\"O Unrecognized keywords are silently ignored for backward compatibility
.\"O with
.\"O .Nm sup .
.Nm sup
¤È¤Î¸åÊý¸ß´¹À­¤Î¤¿¤á¡¢Ç§¼±¤Ç¤­¤Ê¤«¤Ã¤¿¥­¡¼¥ï¡¼¥É¤ÏÌۤäÆ̵»ë¤µ¤ì¤Þ¤¹¡£
.\"O .Sh OPERATION
.Sh Áàºî
.\"O .Nm
.\"O includes a graphical user interface (GUI) which allows one to monitor its
.\"O progress and performance during an update.  The GUI is disabled if the
.\"O .Fl g
.\"O command line option is given, or if the
.\"O .Ev DISPLAY
.\"O environment variable is not set.
.Nm
¤Ï GUI(¥°¥é¥Õ¥£¥«¥ë¥æ¡¼¥¶¥¤¥ó¥¿¥Õ¥§¡¼¥¹)¤ò»ý¤Ã¤Æ¤ª¤ê¡¢¤³¤ì¤ò»È¤¦¤È¥æ¡¼
¥¶¤Ï¹¹¿·Ãæ¤Î¿Ê¹Ô¾õ¶·¤È½èÍý¤ò´Æ»ë¤Ç¤­¤Þ¤¹¡£¤³¤Î GUI ¤Ï¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó
¥ª¥×¥·¥ç¥ó
.Fl g
¤¬»ØÄꤵ¤ì¤ë¤«¡¢
.Ev DISPLAY
´Ä¶­ÊÑ¿ô¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£
.\"O The GUI includes a
.\"O .Dq Filter
.\"O type-in field, where patterns may be entered to restrict the files to
.\"O be updated.
GUI ¤Ë¤Ï¡¢
.Dq Filter
ÆþÎÏ¥Õ¥£¡¼¥ë¥É¤¬¤¢¤ê¤Þ¤¹¡£¤³¤³¤Ë¥Ñ¥¿¡¼¥ó¤òÆþÎϤ·¤Æ¡¢¹¹¿·¤¹¤ë¥Õ¥¡¥¤¥ë¤ò
À©¸Â¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O The patterns are as described for the
.\"O .Fl i
.\"O option.
¥Ñ¥¿¡¼¥ó¤Ï
.Fl i
¥ª¥×¥·¥ç¥ó¤Î»ØÄê¤ÈƱÍͤ˵­½Ò¤·¤Þ¤¹¡£
.\"O If multiple patterns are entered, they should be separated by white space.
Ê£¿ô¤Î¥Ñ¥¿¡¼¥ó¤òÆþÎϤ¹¤ëºÝ¤Ë¤Ï¡¢¶õÇò¤Ç¶èÀÚ¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.Pp
.\"O At present, the GUI does not support changing the parameters specified
.\"O in the
.\"O .Ar supfile .
¸½ºß¤Î¤È¤³¤í¤Ï¡¢
.Ar supfile
¤Ç»ØÄꤵ¤ì¤¿¥Ñ¥é¥á¡¼¥¿¤ò GUI ¤ÇÊѹ¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
.\"O That is planned for a future release.
¤³¤ÎÅÀ¤Ï¾­Íè¤Î¥ê¥ê¡¼¥¹¤Ç¤Î·×²è¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
.\"O Despite its relative uselessness, the GUI is fun to watch.
¤É¤Á¤é¤«¤È¤¤¤¦¤ÈɬÍפʤ¤¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤¹¤¬¡¢GUI ¤Ï¸«¤Æ³Ú¤·¤¤¤â¤Î¤Ç¤¹¡£
.\"O .Sh CVS MODE
.Sh CVS ¥â¡¼¥É
.\"O .Nm CVSup
.\"O supports two primary modes of operation.
.Nm CVSup
¤Ï¡¢2 ¤Ä¤Î¼ç¤ÊÆ°ºî¥â¡¼¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£
.\"O They are called
.\"O .Em CVS
.\"O mode and
.\"O .Em checkout
.\"O mode.
¤³¤ì¤é¤Ï
.Em CVS
¥â¡¼¥É¤È
.Em checkout
¥â¡¼¥É¤È¸Æ¤Ð¤ì¤ë¤â¤Î¤Ç¤¹¡£
.Pp
.\"O In CVS mode, the client receives copies of the actual RCS files making
.\"O up the master CVS repository.  CVS mode is the default mode of operation.
CVS ¥â¡¼¥É¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¥Þ¥¹¥¿¡¼¤Î CVS ¥ê¥Ý¥¸¥È¥ê¤ò¹½À®¤·¤Æ¤¤¤ë
¼ÂºÝ¤Î RCS ¥Õ¥¡¥¤¥ë¤Î¥³¥Ô¡¼¤ò¼õ¿®¤·¤Þ¤¹¡£CVS ¥â¡¼¥É¤Ï¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî
¥â¡¼¥É¤Ç¤¹¡£
.\"O It is appropriate when the user wishes to maintain a full copy of the
.\"O CVS repository on the client machine.
¤³¤Î¥â¡¼¥É¤Ï¡¢CVS ¥ê¥Ý¥¸¥È¥ê¤Î´°Á´¤Ê¥³¥Ô¡¼¤ò¥¯¥é¥¤¥¢¥ó¥È¥Þ¥·¥ó¾å¤Ç¥á¥ó
¥Æ¥Ê¥ó¥¹¤·¤è¤¦¤È¥æ¡¼¥¶¤¬¹Í¤¨¤Æ¤¤¤ë¾ì¹ç¤Ë¤ÏŬ¤·¤Æ¤¤¤Þ¤¹¡£
.Pp
.\"O CVS mode is also appropriate for file collections which are not
.\"O based upon a CVS repository.  The files are simply transferred
.\"O verbatim, without interpretation.
CVS ¥â¡¼¥É¤Ï¡¢CVS ¥ê¥Ý¥¸¥È¥ê¥Ù¡¼¥¹¤Ç¤Ê¤¤¥Õ¥¡¥¤¥ë¤Î¥³¥ì¥¯¥·¥ç¥ó¤ËÂФ·¤Æ
¤â¤¦¤Þ¤¯»È¤¨¤Þ¤¹¡£¤³¤Î¾ì¹ç¤Ë¤Ï¥Õ¥¡¥¤¥ë¤Ï²ò¼á¤µ¤ì¤ë¤³¤È¤Ê¤¯¡¢Ã±¤Ë¤½¤Î¤Þ
¤ÞžÁ÷¤µ¤ì¤Þ¤¹¡£
.\"O .Sh CHECKOUT MODE
.Sh checkout ¥â¡¼¥É
.\"O In checkout mode, the client receives specific revisions of files,
.\"O checked out directly from the server's CVS repository.
checkout ¥â¡¼¥É¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏÆÃÄê¤Î¥ê¥Ó¥¸¥ç¥ó¤Î¥Õ¥¡¥¤¥ë¤ò¼õ¿®¤·
¤Þ¤¹¡£¤³¤ì¤Ï¥µ¡¼¥Ð¤Î CVS ¥ê¥Ý¥¸¥È¥ê¤«¤éľÀÜ¥Á¥§¥Ã¥¯¥¢¥¦¥È¤µ¤ì¤Þ¤¹¡£
.\"O Checkout mode allows the client to receive any version from the
.\"O repository, without requiring any extra disk space on the server for
.\"O storing multiple versions in checked-out form.
checkout ¥â¡¼¥É¤ò»È¤¦¤È¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏǤ°Õ¤Î¥Ð¡¼¥¸¥ç¥ó¤ò¥ê¥Ý¥¸¥È¥ê¤«
¤é¼èÆÀ¤Ç¤­¤Þ¤¹¡£¤³¤ÎºÝ¡¢¥Á¥§¥Ã¥¯¥¢¥¦¥È¤µ¤ì¤ë»þ¤Î·Á¤ÇÊ£¿ô¸Ä¤Î¥Ð¡¼¥¸¥ç¥ó
¤ò¥µ¡¼¥Ð¾å¤Ë»ý¤ÄɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
.\"O Checkout mode provides much flexibility beyond that basic functionality,
.\"O however.
¤·¤«¤·¡¢checkout ¥â¡¼¥É¤Ç¤Ï¡¢¤½¤Î´ðËܵ¡Ç½¤è¤ê¤â¤º¤Ã¤È½ÀÆð¤ËÆ°ºî¤µ¤»¤ë
¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¤¤¤Þ¤¹¡£
.\"O The client can specify any CVS symbolic tag, or any date, or both, and
.\"O .Nm CVSup
.\"O will provide the corresponding checked-out versions of the files in the
.\"O repository.
¥¯¥é¥¤¥¢¥ó¥È¤Ï CVS ¤Î¥·¥ó¥Ü¥ê¥Ã¥¯¥¿¥°¤ò»ØÄê¤Ç¤­¤Þ¤¹¤·¡¢Ç¤°Õ¤ÎÆüÉդλØ
Äê¤â¤Ç¤­¤Þ¤¹¡£Î¾Êý¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤Þ¤¿
.Nm CVSup
¤Ï¡¢¤³¤Î»ØÄê¤ËÂбþ¤¹¤ë¥Õ¥¡¥¤¥ë¤ò¥ê¥Ý¥¸¥È¥êÆ⤫¤é¥Á¥§¥Ã¥¯¥¢¥¦¥È·Á¼°¤Ç¼è
¤ê½Ð¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.Pp
.\"O Checkout mode is selected on a per-collection basis, by the presence of
.\"O one or both of the following keywords in the
.\"O .Ar supfile :
checkout ¥â¡¼¥É¤Ï¥³¥ì¥¯¥·¥ç¥óÊ̤˻ØÄꤷ¤Þ¤¹¡£»ØÄê¤Ï¡¢
.Ar supfile
Æâ¤Ë°Ê²¼¤Î¥­¡¼¥ï¡¼¥É¤Î°ì¤Ä¤¢¤ë¤¤¤ÏξÊý¤ò´Þ¤á¤ë¤³¤È¤Ë¤è¤Ã¤Æ¹Ô¤¤¤Þ¤¹:
.Bl -tag -width Fl
.It Cm tag= Ns Ar tagname
.\"O This specifies a symbolic tag that should be used to select the
.\"O revisions that are checked out from the CVS repository.
¥·¥ó¥Ü¥ê¥Ã¥¯¥¿¥°¤ò»ØÄꤷ¤Þ¤¹¡£¤³¤Î¥¿¥°¤Ï¡¢CVS ¥ê¥Ý¥¸¥È¥ê¤«¤é¼è¤ê½Ð¤¹¥ê
¥Ó¥¸¥ç¥ó¤òÁªÂò¤¹¤ë¤¿¤á¤Ë»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O The tag may refer to either a branch or a specific revision.
¤³¤Î¥¿¥°¤Ï¥Ö¥é¥ó¥Á¤Þ¤¿¤ÏÆÃÄê¤Î¥ê¥Ó¥¸¥ç¥ó¤ò¼¨¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O It must be symbolic; numeric revision numbers are not supported.
¥¿¥°¤Ï¥·¥ó¥Ü¥ê¥Ã¥¯¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤Ä¤Þ¤ê¡¢¿ôÃͤΥê¥Ó¥¸¥ç¥óÈÖ¹æ¤Ï
¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
.Pp
.\"O For the FreeBSD source repository, the most commonly used tags will be:
FreeBSD ¤Î¥½¡¼¥¹¥ê¥Ý¥¸¥È¥ê¤Î¾ì¹ç¤Ï¡¢°Ê²¼¤Î¥¿¥°¤¬¤è¤¯»È¤ï¤ì¤Þ¤¹:
.Bl -tag -width RELENG_3
.It Li RELENG_3
.\"O The
.\"O .Ql stable
.\"O branch.
.Ql stable
¥Ö¥é¥ó¥Á¡£
.It Li \&.
.\"O The main branch (the
.\"O .Ql current
.\"O release).
¥á¥¤¥ó¥Ö¥é¥ó¥Á(
.Ql current
¥ê¥ê¡¼¥¹)¡£
.\"O This is the default, if only the
.\"O .Cm date
.\"O keyword is given.
.Cm date
¥­¡¼¥ï¡¼¥É¤À¤±¤¬»ØÄꤵ¤ì¤ë¤È¡¢¤³¤Á¤é¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£
.El
.Sm off
.It Xo Cm date=
.Op Ar cc
.Ar yy.mm.dd.hh.mm.ss
.Xc
.Sm on
.\"O This specifies a date that should be used to select the revisions that
.\"O are checked out from the CVS repository.
¤³¤ì¤Ï¡¢CVS ¥ê¥Ý¥¸¥È¥ê¤«¤é¥Á¥§¥Ã¥¯¥¢¥¦¥È¤¹¤ë¥ê¥Ó¥¸¥ç¥ó¤ÎÁªÂò¤Ë»È¤¦ÆüÉÕ
¤ò»ØÄꤷ¤Þ¤¹¡£
.\"O The client will receive the revisions that were in effect at the
.\"O specified date and time.
¥¯¥é¥¤¥¢¥ó¥È¤Ï¼ÂºÝ¤Ë¤Ï¡¢»ØÄꤵ¤ì¤¿ÆüÉդȻþ¹ï¤Î¥ê¥Ó¥¸¥ç¥ó¤ò¼õ¤±¼è¤ê¤Þ¤¹¡£
.Pp
.\"O At present, the date format is inflexible.  All 17 or 19 characters must
.\"O be specified, exactly as shown.
¸½»þÅÀ¤Ç¤Ï¡¢ÆüÉդΥե©¡¼¥Þ¥Ã¥È¤Ï½ÀÆð¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£17 ʸ»ú¤¢¤ë¤¤¤Ï 19 
ʸ»ú¤ÎÁ´¤Æ¤ò¡¢ÀâÌÀ¤·¤¿¥Õ¥©¡¼¥Þ¥Ã¥È¤ÇÀµ³Î¤Ë»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O For the years 2000 and beyond, specify the century
.\"O .Ar cc .
2000 ǯ°Ê¹ß¤Î¾ì¹ç¤Ï¡¢À¤µª¤ò
.Ar cc
¤Ç»ØÄꤷ¤Þ¤¹¡£
.\"O For earlier years, specify only the last two digits
.\"O .Ar yy .
¤³¤ì¤è¤êÁ°¤Îǯ¤Î¾ì¹ç¤Ï¡¢ºÇ¸å¤Î 2 ·å¤À¤±¤ò
.Ar yy
¤Ç»ØÄꤷ¤Þ¤¹¡£
.\"O Dates and times are considered to
.\"O be GMT.
ÆüÉդȻþ¹ï¤Ï GMT ¤Ç°·¤¤¤Þ¤¹¡£
.\"O The default date is
.\"O .Ql \&. ,
.\"O which means
.\"O .Dq as late as possible .
¥Ç¥Õ¥©¥ë¥È¤ÎÆüÉÕ¤Ï
.Ql \&.
¤Ç¤¹¡£¤³¤ì¤Ï
.Dq ¤Ç¤­¤ë¤À¤±¿·¤·¤¤¤â¤Î
¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£
.El
.Pp
.\"O To enable checkout mode, you must specify at least one of these keywords.
checkout ¥â¡¼¥É¤òÍ­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢¾¯¤Ê¤¯¤È¤â¤³¤ì¤é¤Î¥­¡¼¥ï¡¼¥É¤Î
¤¤¤º¤ì¤«¤ò»ØÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O If both are missing,
.\"O .Nm CVSup
.\"O defaults to CVS mode.
¤É¤Á¤é¤â»ØÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢
.Nm CVSup
¤Ï¥Ç¥Õ¥©¥ë¥È¤Î CVS ¥â¡¼¥É¤ÇÆ°ºî¤·¤Þ¤¹¡£
.Pp
.\"O If both a branch tag and a date are specified, then the revisions on the
.\"O given branch, as of the given date, will be checked out.  It is
.\"O permitted, but not particularly useful, to specify a date with a
.\"O specific release tag.
¥Ö¥é¥ó¥Á¥¿¥°¤ÈÆüÉÕ¤¬Î¾Êý¤È¤â»ØÄꤵ¤ì¤ë¤È¡¢»ØÄꤵ¤ì¤¿¥Ö¥é¥ó¥Á¾å¤Î
»ØÄꤵ¤ì¤¿ÆüÉդλþÅÀ¤Î¥ê¥Ó¥¸¥ç¥ó¤¬¥Á¥§¥Ã¥¯¥¢¥¦¥È¤µ¤ì¤Þ¤¹¡£
ÆüÉÕ¤òÆÃÄê¤Î¥ê¥ê¡¼¥¹¥¿¥°¤ËÉÕ¤±¤Æ»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢¤¢¤Þ¤êÌò¤Ë¤Ï
Ω¤¿¤Ê¤¤¤Ç¤·¤ç¤¦¡£
.Pp
.\"O In checkout mode, the tag and/or date may be changed between updates.
checkout ¥â¡¼¥É¤Ç¤Ï¡¢¥¿¥°¤äÆüÉÕ¤ò¹¹¿·¤È¹¹¿·¤Î´Ö¤ËÊѤ¨¤é¤ì¤Þ¤¹¡£
.\"O For example, suppose that a collection has been transferred using the
.\"O specification
.\"O .Ql tag=. .
Î㤨¤Ð¡¢
.Ql tag=.
¤È¤¤¤¦»ØÄê¤ò»È¤Ã¤Æ¥³¥ì¥¯¥·¥ç¥ó¤¬Å¾Á÷¤µ¤ì¤¿¤È¤·¤Þ¤·¤ç¤¦¡£
.\"O The user could later change the specification to
.\"O .Ql tag=RELENG_3 .
¥æ¡¼¥¶¤Ï¸å¤«¤é»ØÄê¤ò
.Ql tag=RELENG_3
¤ËÊѤ¨¤é¤ì¤Þ¤¹¡£
.\"O This would cause
.\"O .Nm CVSup
.\"O to edit the checked-out files in such a way as to transform them from the
.\"O .Ql current
.\"O versions to the
.\"O .Ql stable
.\"O versions.
¤³¤ì¤ò»ØÄꤹ¤ë¤È¡¢
.Nm CVSup
¤Ï¥Á¥§¥Ã¥¯¥¢¥¦¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¡¢
.Ql current
¥Ð¡¼¥¸¥ç¥ó¤¬
.Ql stable
¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ê¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
.\"O In general,
.\"O .Nm CVSup
.\"O is willing to transform any tag/date combination into any other tag/date
.\"O combination, by applying the intervening RCS deltas to the existing files.
°ìÈÌŪ¤Ë¤Ï¡¢
.Nm CVSup
¤Ï¤É¤ó¤Ê¥¿¥°/ÆüÉÕ¤ÎÁȹ礻¤Ç¤¢¤Ã¤Æ¤â¡¢Â¾¤Î¥¿¥°/ÆüÉÕ¤ÎÁȹ礻¤ËÊÑ´¹¤·¤Æ¤¯
¤ì¤Þ¤¹¡£ÊÑ´¹¤Ï¡¢Î¾¼Ô¤Î´Ö¤Ë¤¢¤ë RCS ¤Îº¹Ê¬¤ò´û¸¤Î¥Õ¥¡¥¤¥ë¤ËŬÍѤ¹¤ë¤³
¤È¤Ë¤è¤Ã¤Æ¹Ô¤¤¤Þ¤¹¡£
.Pp
.\"O When transforming a collection of checked-out files from one tag to
.\"O another, it is important to specify the
.\"O .Cm list
.\"O keyword in the
.\"O .Ar supfile ,
.\"O to ensure that the same list file is used both before and after the
.\"O transformation.
¥Á¥§¥Ã¥¯¥¢¥¦¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î¥³¥ì¥¯¥·¥ç¥ó¤ò¡¢¤¢¤ë¥¿¥°¤«¤éÊ̤Υ¿¥°¤Ë
ÊÑ´¹¤¹¤ë¤È¤­¤Ë¤Ï¡¢ÊÑ´¹¤ÎÁ°¸å¤Çɬ¤ºÆ±¤¸¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤¬»È¤ï¤ì¤ë¤è¤¦¤Ë¤¹
¤ë¤¿¤á¡¢
.Ar supfile
¥Õ¥¡¥¤¥ëÃæ¤Ç
.Cm list
¥­¡¼¥ï¡¼¥É¤ò»ØÄꤹ¤ë¤³¤È¤¬½ÅÍפǤ¹¡£
.\"O The list file is described in
.\"O .Sx THE LIST FILE ,
.\"O below.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Ï¼¡¤Î
.Sx ¥ê¥¹¥È¥Õ¥¡¥¤¥ë
¤ÎÀá¤ÇÀâÌÀ¤·¤Þ¤¹¡£
.\"O .Sh THE LIST FILE
.SH ¥ê¥¹¥È¥Õ¥¡¥¤¥ë
.\"O For efficiency,
.\"O .Nm
.\"O maintains a bookkeeping file for each collection, called the list file.
¸úΨ¤Î¤¿¤á¡¢
.Nm
¤Ï³Æ¥³¥ì¥¯¥·¥ç¥ó¤Ë¤Ä¤¤¤Æ¤Îµ­Ï¿¥Õ¥¡¥¤¥ë¤ò´ÉÍý¤·¤Æ¤¤¤Þ¤¹¡£
¤³¤ì¤ò¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤È¸Æ¤Ó¤Þ¤¹¡£
.\"O The list file contains information about which files and revisions the client
.\"O currently possesses.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬¸½ºß»ý¤Ã¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤È¥ê¥Ó¥¸¥ç¥ó¤Ë
´Ø¤¹¤ë¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
.\"O It also contains information used for verifying that the list file
.\"O is consistent with the actual files in the client's tree.
¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥Ä¥ê¡¼¤ËÆþ¤Ã¤Æ¤¤¤ë¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤È
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤¬°ìÃפ·¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤¹¤ë¤¿¤á¤Î¾ðÊó¤â½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
.Pp
.\"O The list file is not strictly necessary.  If it is deleted, or becomes
.\"O inconsistent with the actual client files,
.\"O .Nm
.\"O falls back upon a less efficient method of identifying the client's
.\"O files and performing its updates.
¸·Ì©¤Ë¸À¤¦¤È¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤ÏɬÍפǤϤ¢¤ê¤Þ¤»¤ó¡£¤³¤Î¥Õ¥¡¥¤¥ë¤¬ºï½ü¤µ¤ì
¤ë¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬»ý¤Ã¤Æ¤¤¤ë¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤È¤ÎÉÔ°ìÃפ¬µ¯¤³¤ë¤È¡¢
.Nm
¤ÏºÇ¸å¤Î¼êÃʤȤ·¤Æ¾¯¤·¸úΨ¤Î°­¤¤ÊýË¡¤Ç¥¯¥é¥¤¥¢¥ó¥È¦¤Î¥Õ¥¡¥¤¥ë¤Î¼±Ê̤È
¹¹¿·¤ò¹Ô¤¤¤Þ¤¹¡£
.\"O Depending on
.\"O .Nm CVSup Ns No 's
.\"O mode of operation, the fallback method employs time stamps, checksums, or
.\"O analysis of RCS files.
¤³¤ÎºÝ¤Ë¤Ï¡¢
.Nm CVSup
¤ÎÆ°ºî¥â¡¼¥É¤Ë¤è¤Ã¤Æ¡¢¥¿¥¤¥à¥¹¥¿¥ó¥×¡¢¥Á¥§¥Ã¥¯¥µ¥à¡¢RCS ¥Õ¥¡¥¤¥ë¤Î
²òÀÏ·ë²Ì¤Ê¤É¤¬»È¤ï¤ì¤Þ¤¹¡£
.Pp
.\"O Because the list file is not essential,
.\"O .Nm
.\"O is able to
.\"O .Dq adopt
.\"O an existing file tree acquired by FTP or from a CD-ROM.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤ÏÉԲķç¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢
.Nm
¤Ï FTP ¤ä CD-ROM ¤«¤éÆþ¼ê¤·¤¿´û¸¤Î¥Õ¥¡¥¤¥ë¥Ä¥ê¡¼¤ò¡ÖÍøÍѡפǤ­¤Þ¤¹¡£
.\"O .Nm
.\"O identifies the client's versions of the files, updates them as
.\"O necessary, and creates a list file for future use.
.Nm
¤Ï¥¯¥é¥¤¥¢¥ó¥È¦¤Î¥Õ¥¡¥¤¥ë¤Î¥Ð¡¼¥¸¥ç¥ó¤ò¼±Ê̤·¡¢É¬Íפ˱þ¤¸¤Æ¤³¤ì¤ò¹¹¿·
¤·¤Þ¤¹¡£¤µ¤é¤Ë¡¢¾­Íè»È¤¦¤¿¤á¤Ë¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤òÀ¸À®¤·¤Þ¤¹¡£
.\"O Adopting a foreign file tree is not as fast as performing a normal
.\"O update.
¾¤Î¥·¥¹¥Æ¥à¤¬ºî¤Ã¤¿¥Õ¥¡¥¤¥ë¥Ä¥ê¡¼¤ò»È¤¦¾ì¹ç¤ÎÆ°ºî¤Ï¡¢Ä̾ï¤Î¹¹¿·¤Û¤É
¹â®¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.\"O It also produces a heavier load on the server.
¤Þ¤¿¡¢¥µ¡¼¥Ð¤Ë¤«¤«¤ëÉé²Ù¤â¹â¤¯¤Ê¤ê¤Þ¤¹¡£
.\"O .Pp
.\"O The list file is stored in a collection-specific directory; see
.\"O .Sx FILES
.\"O for details.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Ï¥³¥ì¥¯¥·¥ç¥ó¸ÇÍ­¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÊݸ¤µ¤ì¤Þ¤¹¡£¾Ü¤·¤¯¤Ï
.Sx ¥Õ¥¡¥¤¥ë
¥»¥¯¥·¥ç¥ó¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.\"O Its name always begins with
.\"O .Ql checkouts .
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤Ïɬ¤º
.Ql checkouts
¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£
.\"O If the keyword
.\"O .Cm use-rel-suffix
.\"O is specified in the
.\"O .Ar supfile ,
.\"O a suffix, formed from the release and tag, is appended to the name.
.Ar supfile
Æâ¤Ç¥­¡¼¥ï¡¼¥É
.Cm use-rel-suffix
¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢¥ê¥ê¡¼¥¹¤È¥¿¥°¤«¤éºî¤Ã¤¿¥µ¥Õ¥£¥Ã¥¯¥¹¤¬¥Õ¥¡¥¤¥ë̾¤Ë
Äɲ䵤ì¤Þ¤¹¡£
.\"O The default suffix can be overridden by specifying an explicit suffix in
.\"O the
.\"O .Ar supfile :
¥Ç¥Õ¥©¥ë¥È¤Î¥µ¥Õ¥£¥Ã¥¯¥¹¤Ï¡¢
.Ar supfile 
¤ÇÌÀ¼¨Åª¤Ë¥µ¥Õ¥£¥Ã¥¯¥¹¤ò»ØÄꤹ¤ë¤³¤È¤Ë¤è¤ê¾å½ñ¤­¤µ¤ì¤Þ¤¹:
.Bl -tag -width Fl
.It Cm list= Ns Ar suffix
.\"O This specifies a suffix for the name of the list file.  A leading dot is
.\"O provided automatically.
¤³¤ì¤Ï¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤ËÉÕ¤±¤ë¥µ¥Õ¥£¥Ã¥¯¥¹¤Î»ØÄê¤Ç¤¹¡£¥µ¥Õ¥£¥Ã¥¯¥¹
¤ÎÀèƬ¤Î¥É¥Ã¥È¤Ï¼«Æ°Åª¤ËÉÕ¤±¤é¤ì¤Þ¤¹¡£
.\"O For example,
.\"O .Ql list=stable
.\"O would produce a list file named
.\"O .Pa checkouts.stable ,
.\"O regardless of the release, tag, or
.\"O .Cm use-rel-suffix
.\"O keyword.
Î㤨¤Ð¡¢
.Ql list=stable
¤È¤¹¤ë¤È¡¢
.Pa checkouts.stable
¤È¤¤¤¦Ì¾Á°¤Î¥ê¥¹¥È¥Õ¥¡¥¤¥ë¤¬ºî¤é¤ì¤Þ¤¹¡£¤³¤Î¾ì¹ç¤Ë¤Ï¡¢¥ê¥ê¡¼¥¹¡¢¥¿¥°¡¢
.Cm use-rel-suffix
¥­¡¼¥ï¡¼¥É¤Ï´Ø·¸¤¢¤ê¤Þ¤»¤ó¡£
.El
.\"O .Sh REFUSE FILES
.Sh refuse ¥Õ¥¡¥¤¥ë
.\"O The user can specify sets of files that he does not wish to receive.
¥æ¡¼¥¶¤Ï¼õ¤±¼è¤ê¤¿¤¯¤Ê¤¤¥Õ¥¡¥¤¥ë¤Î½¸¹ç¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£
.\"O The files are specified as file name patterns in so-called
.\"O .Em refuse
.\"O files.
¤³¤¦¤¤¤Ã¤¿¥Õ¥¡¥¤¥ë¤Ï¡¢¤¤¤ï¤æ¤ë
.Em refuse
¥Õ¥¡¥¤¥ëÆâ¤Ç¥Õ¥¡¥¤¥ë̾¥Ñ¥¿¡¼¥ó¤È¤·¤Æ»ØÄꤵ¤ì¤Þ¤¹¡£
.\"O The patterns are separated by whitespace, and multiple patterns are
.\"O permitted on each line.
¥Ñ¥¿¡¼¥ó¤Ï¶õÇòʸ»ú¤Ç¶èÀÚ¤é¤ì¡¢³Æ¹Ô¤Ë¤ÏÊ£¿ô¸Ä¤Î¥Ñ¥¿¡¼¥ó¤òÃÖ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O Files and directories matching the patterns are neither updated nor
.\"O deleted; they are simply ignored.
¥Ñ¥¿¡¼¥ó¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤È¥Ç¥£¥ì¥¯¥È¥ê¤Ï¡¢¹¹¿·¤âºï½ü¤â¤µ¤ì¤Þ¤»¤ó¡£
¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ïñ¤Ë̵»ë¤µ¤ì¤Þ¤¹¡£
.Pp
.\"O There is currently no provision for comments in refuse files.
¸½ºß¤Ï¡¢refuse ¥Õ¥¡¥¤¥ëÆâ¤Ë¥³¥á¥ó¥È¤Ë½ñ¤¯ÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.Pp
.\"O The patterns are similar to those of
.\"O .Xr sh 1 ,
.\"O except that there is no special treatment for slashes or for
.\"O filenames that begin with a period.
¥Ñ¥¿¡¼¥ó¤Ï
.Xr sh 1
¤Î¤½¤ì¤È»÷¤Æ¤¤¤Þ¤¹¤¬¡¢¥¹¥é¥Ã¥·¥å¤ÎÆÃÊÌ°·¤¤¤ä¡¢¥Ô¥ê¥ª¥É¤Ç»Ï¤Þ¤ë¥Õ¥¡¥¤¥ë
¤ÎÆÃÊÌ°·¤¤¤¬¤Ê¤¤ÅÀ¤¬°Û¤Ê¤ê¤Þ¤¹¡£
.\"O For example, the pattern
.\"O .Ql *.c
.\"O will match any file name ending with
.\"O .Ql \&.c
.\"O including those in subdirectories, such as
.\"O .Ql foo/bar/lam.c .
Î㤨¤Ð¡¢¥Ñ¥¿¡¼¥ó
.Ql *.c
¤Ï
.Ql \&.c
¤Ç½ª¤ï¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£¤³¤ì¤Ë¤Ï
.Ql foo/bar/lam.c
¤È¤¤¤Ã¤¿¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¥Õ¥¡¥¤¥ë¤â´Þ¤Þ¤ì¤Þ¤¹¡£
.\"O All patterns are interpreted relative to the collection's prefix
.\"O directory.
Á´¤Æ¤Î¥Ñ¥¿¡¼¥ó¤Ï¥³¥ì¥¯¥·¥ç¥ó¤Î¥×¥ì¥Õ¥£¥Ã¥¯¥¹¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤ÎÁêÂХѥ¹
¤È¤·¤Æ²ò¼á¤µ¤ì¤Þ¤¹¡£
.Pp
.\"O If the files are coming from a CVS repository, as is usually
.\"O the case, then they will be RCS files. These have a
.\"O .Ql \&,v
.\"O suffix which must be taken into account in the patterns. For
.\"O example, the FreeBSD documentation files are in a sub-directory of
.\"O .Ar base
.\"O called
.\"O .Ql doc .
¤³¤ì¤é¥Õ¥¡¥¤¥ë¤¬ CVS ¥ê¥Ý¥¸¥È¥ê¤«¤éÆÀ¤¿¤â¤Î¤Ê¤é¤Ð¡½¡½ÉáÄ̤Ϥ½¤¦¤Ê¤Î¤Ç¤¹
¤¬¡½¡½¤³¤ì¤é¤Ï RCS ¥Õ¥¡¥¤¥ë¤È¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢
.Ql \&,v
¤È¤¤¤¦¥µ¥Õ¥£¥Ã¥¯¥¹¤¬ÉÕ¤­¤Þ¤¹¡£¥Ñ¥¿¡¼¥ó¤Ë¤Ä¤¤¤Æ¤Ï¥µ¥Õ¥£¥Ã¥¯¥¹¤â¹Íθ¤ËÆþ
¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£Î㤨¤Ð¡¢FreeBSD ¤Îʸ½ñ¥Õ¥¡¥¤¥ë¤Ï
.Ql doc
¤È¤¤¤¦
.Ar base
¥Ç¥£¥ì¥¯¥È¥ê¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ËÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£
.\"O If
.\"O .Ql Makefile
.\"O from that directory is not required then the line
.\"O .Pp 
.\"O .Bl -item -compact -offset indent
.\"O .It 
.\"O .Pa doc/Makefile
.\"O .El
.\"O .Pp
.\"O will not work because the file on the server is called
.\"O .Ql Makefile,v.
¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë
.Ql Makefile
¤¬ÉÔÍפʾì¹ç¤Ë
.Pp 
.Bl -item -compact -offset indent
.It 
.Pa doc/Makefile
.El
.Pp
¤È»ØÄꤷ¤Æ¤â¤¦¤Þ¤¯Æ°ºî¤·¤Þ¤»¤ó¡£¤Ê¤¼¤Ê¤é¡¢¥µ¡¼¥Ð¾å¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤Ï
.Ql Makefile,v
¤À¤«¤é¤Ç¤¹¡£
.\"O A better solution would be
.\"O .Pp
.\"O .Bl -item -compact -offset indent
.\"O .It
.\"O .Pa doc/Makefile*
.\"O .El 
.\"O .Pp 
.\"O which will match whether
.\"O .Ql Makefile
.\"O is an RCS file or not.
¤â¤Ã¤È¤è¤¤²ò·èÊýË¡¤Ï¡¢
.Pp
.Bl -item -compact -offset indent
.It
.Pa doc/Makefile*
.El 
.Pp 
¤È»ØÄꤹ¤ë¤³¤È¤Ç¤¹¡£¤³¤Î»ØÄê¤Ç¤¢¤ì¤Ð¡¢
.Ql Makefile
¤¬ RCS ¥Õ¥¡¥¤¥ë¤Ç¤¢¤í¤¦¤È¤Ê¤«¤í¤¦¤È¥Þ¥Ã¥Á¤·¤Þ¤¹¡£
.Pp
.\"O As another example, to receive the FreeBSD documentation files without
.\"O the Japanese, Russian, and Chinese translations, create a refuse file
.\"O containing the following lines:
Ê̤ÎÎã¤È¤·¤Æ¤Ï¡¢ÆüËܸ졢¥í¥·¥¢¸ì¡¢Ãæ¹ñ¸ì¤ÎËÝÌõ¤òÈò¤±¤Æ FreeBSD ʸ½ñ
¥Õ¥¡¥¤¥ë¤ò¼èÆÀ¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¹Ô¤ò´Þ¤à refuse ¥Õ¥¡¥¤¥ë¤òºî¤ê¤Þ¤¹:
.Pp
.Bl -item -compact -offset indent
.It
.Pa doc/ja*
.It
.Pa doc/ru*
.It
.Pa doc/zh*
.El 
.Pp
.\"O As many as three refuse files are examined for each
.\"O .Ar supfile
.\"O line.
¤½¤ì¤¾¤ì¤Î
.Ar supfile
¹Ô¤Ï¡¢3 ¤Ä¤Î refuse ¥Õ¥¡¥¤¥ë¤Ë¤è¤Ã¤ÆÄ´¤Ù¤é¤ì¤Þ¤¹¡£
.\"O There can be a global refuse file named
.\"O .Sm off
.\"O .Ar base / Ar collDir Pa /refuse
.\"O .Sm on
.\"O which applies to all collections and releases.
Âç°èŪ¤Ê refuse ¥Õ¥¡¥¤¥ë¤È¤·¤Æ
.Sm off
.Ar base / Ar collDir Pa /refuse
.Sm on
¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ÏÁ´¤Æ¤Î¥³¥ì¥¯¥·¥ç¥ó¤È¥ê¥ê¡¼¥¹¤ËŬÍѤµ¤ì¤Þ¤¹¡£
.\"O There can be a per-collection refuse file named
.\"O .Sm off
.\"O .Xo Ar base / Ar collDir / Ar collection
.\"O .Pa /refuse
.\"O .Xc
.\"O .Sm on
.\"O which applies to a specific collection.
¥³¥ì¥¯¥·¥ç¥óÊ̤Πrefuse ¥Õ¥¡¥¤¥ë¤È¤·¤Æ
.Sm off
.Xo Ar base / Ar collDir / Ar collection
.Pa /refuse
.Xc
.Sm on
¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ÏÆÃÄê¤Î¥³¥ì¥¯¥·¥ç¥ó¤ËŬÍѤµ¤ì¤Þ¤¹¡£
.\"O Finally, there can be a per-release and tag refuse file which applies only
.\"O to a given release/tag combination within a collection.
ºÇ¸å¤Ë¡¢¥ê¥ê¡¼¥¹¤È¥¿¥°Ê̤Πrefuse ¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤Ï¡¢
¥³¥ì¥¯¥·¥ç¥óÆâ¤Î»ØÄꤵ¤ì¤¿¥ê¥ê¡¼¥¹/¥¿¥°¤ÎÁȤ߹ç¤ï¤»¤ËÂФ·¤Æ¤Î¤ßŬÍѤµ
¤ì¤Þ¤¹¡£
.\"O The name of the latter is formed by suffixing the name of the
.\"O per-collection refuse file in the same manner as described above for the
.\"O list file.
ºÇ¸å¤Î refuse ¥Õ¥¡¥¤¥ë¤Î̾Á°¤Ï¡¢¥³¥ì¥¯¥·¥ç¥óÊ̤Πrefuse ¥Õ¥¡¥¤¥ë¤Î̾
Á°¤Ë¥µ¥Õ¥£¥Ã¥¯¥¹¤ò²Ã¤¨¤ë¤³¤È¤Ë¤è¤Ã¤ÆÉÕ¤±¤é¤ì¤Þ¤¹¡£¤³¤ì¤ÏÀè¤ËÀâÌÀ¤·¤¿¥ê
¥¹¥È¥Õ¥¡¥¤¥ë¤ÈƱ¤¸ÊýË¡¤Ç¤¹¡£
.\"O None of the refuse files are required to exist.
¤É¤ó¤Ê¼ïÎà¤Î refuse ¥Õ¥¡¥¤¥ë¤â¸ºß¤·¤Ê¤¯¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£
.Pp
.\"O .Nm
.\"O has a built-in default value of
.\"O .Ar /usr/local/etc/cvsup
.\"O for
.\"O .Ar base
.\"O and
.\"O .Ar sup
.\"O for 
.\"O .Ar collDir
.\"O but it is possible to override both of these. The value of
.\"O .Ar base
.\"O can be changed using the
.\"O .Fl b
.\"O option or a
.\"O .Ar base=pathname
.\"O entry in the
.\"O .Ar supfile .
.Nm
¤Ï¡¢
.Ar collDir
¤ËÂФ¹¤ë
.Ar base
¤È
.Ar sup
¤ÎÁȤ߹þ¤ß¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤò
.Ar /usr/local/etc/cvsup
¤Ë»ý¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¤É¤Á¤é¤ÎÃͤâ¾å½ñ¤­²Äǽ¤Ç¤¹¡£
.Ar base
¤ÎÃͤÏ
.Fl b
¥ª¥×¥·¥ç¥ó¤Þ¤¿¤Ï
.Ar supfile
¥Õ¥¡¥¤¥ëÃæ¤Î
.Ar base=pathname
¥¨¥ó¥È¥ê¤ÇÊѹ¹¤Ç¤­¤Þ¤¹¡£
.\"O (If both are used the 
.\"O .Fl b
.\"O option will override the
.\"O .Ar supfile
.\"O entry.)  The value of 
.\"O .Ar collDir
.\"O can only be changed with the
.\"O .Fl c
.\"O option; there is no
.\"O .Ar supfile
.\"O command to change it.
(ξÊý»ØÄꤷ¤¿¾ì¹ç¤Ï¡¢
.Fl b
¥ª¥×¥·¥ç¥ó¤ÎÊý¤¬
.Ar supfile
¤Î¥¨¥ó¥È¥ê¤è¤ê¤âÍ¥À褵¤ì¤Þ¤¹¡£)
.Ar collDir
¤ÎÃͤÏ
.Fl c
¥ª¥×¥·¥ç¥ó¤Ç¤·¤«Êѹ¹¤Ç¤­¤Þ¤»¤ó¡£¤³¤ì¤òÊѹ¹¤¹¤ë
.Ar supfile
¥³¥Þ¥ó¥É¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.Pp
.\"O As an example, suppose that the
.\"O .Ar base
.\"O and
.\"O .Ar collDir
.\"O both have their default values, and that the collection and release are
.\"O .Ql src-all
.\"O and
.\"O .Ql cvs ,
.\"O respectively.
Î㤨¤Ð¡¢
.Ar base
¤È
.Ar collDir
¤ÎξÊý¤Ë¥Ç¥Õ¥©¥ë¥ÈÃͤ¬ÀßÄꤵ¤ì¤Æ¤ª¤ê¡¢¥³¥ì¥¯¥·¥ç¥ó¤¬
.Ql src-all
¤Ç¥ê¥ê¡¼¥¹¤¬
.Ql cvs
¤Ç¤¢¤ë¾ì¹ç¤ò¹Í¤¨¤Þ¤¹¡£
.\"O Assume further that checkout mode is being used with
.\"O .Ql tag=RELENG_3 .
¤µ¤é¤Ë¡¢
.Ql tag=RELENG_3
¤ËÂФ·¤Æ checkout ¥â¡¼¥É¤¬»È¤ï¤ì¤Æ¤¤¤ë¤â¤Î¤È¤·¤Þ¤¹¡£
.\"O The three possible refuse files would then be named:
¤³¤Î¾ì¹ç¡¢refuse ¥Õ¥¡¥¤¥ë¤Î̾Á°¤È¤·¤Æ¤Ï°Ê²¼¤Î 3 ¤Ä¤¬¹Í¤¨¤é¤ì¤Þ¤¹:
.Pp
.Bl -item -compact -offset indent
.It
.Pa /usr/local/etc/cvsup/sup/refuse
.It
.Pa /usr/local/etc/cvsup/sup/src-all/refuse
.It
.Pa /usr/local/etc/cvsup/sup/src-all/refuse.cvs:RELENG_3
.El
.Pp
.\"O If the
.\"O .Ar supfile
.\"O includes the command
.\"O .Ar base=/foo
.\"O the refuse files would be:
.Ar supfile
¤¬¥³¥Þ¥ó¥É
.Ar base=/foo
¤ò´Þ¤ó¤Ç¤¤¤ë¾ì¹ç¡¢refuse ¥Õ¥¡¥¤¥ë¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹:
.Pp
.Bl -item -compact -offset indent
.It
.Pa /foo/sup/refuse
.It
.Pa /foo/sup/src-all/refuse
.It
.Pa /foo/sup/src-all/refuse.cvs:RELENG_3
.El
.Pp
.\"O If
.\"O .Fl b
.\"O .Ar /bar
.\"O is used (even with
.\"O .Ar base=/foo
.\"O in the
.\"O .Ar supfile ) :
.Fl b
.Ar /bar
¤¬»È¤ï¤ì¤Æ¤¤¤ë¾ì¹ç(
.Ar supfile
¥Õ¥¡¥¤¥ëÃæ¤Ë
.Ar base=/foo
¥³¥Þ¥ó¥É¤¬¤¢¤Ã¤Æ¤â):
.Pp
.Bl -item -compact -offset indent
.It
.Pa /bar/sup/refuse                
.It
.Pa /bar/sup/src-all/refuse                
.It
.Pa /bar/sup/src-all/refuse.cvs:RELENG_3                
.El
.Pp
.\"O and with
.\"O .Fl c
.\"O .Ar stool
.\"O as well:
¤½¤·¤Æ
.Fl c
.Ar stool
¤â»È¤ï¤ì¤Æ¤¤¤ë¾ì¹ç:
.Pp
.Bl -item -compact -offset indent
.It
.Pa /bar/stool/refuse
.It 
.Pa /bar/stool/src-all/refuse
.It
.Pa /bar/stool/src-all/refuse.cvs:RELENG_3
.\"O .Sh AUTHENTICATION
.Sh ǧ¾Ú
.\"O .Nm CVSup
.\"O implements an authentication mechanism which can be used by the
.\"O client and server to verify each other's identities.  It uses a
.\"O challenge-response protocol which is immune to packet sniffing and
.\"O replay attacks.  No passwords are sent over the network in either
.\"O direction.  Both the client and the server can independently verify
.\"O the identities of each other.
.Nm CVSup
¤Ïǧ¾Úµ¡¹½¤òÈ÷¤¨¤Æ¤ª¤ê¡¢¤³¤ì¤ò»È¤Ã¤Æ¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤¬¤ª¸ß¤¤¤Î¿È¸µ
¤ò³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Îµ¡¹½¤Ï¡¢¥Ñ¥±¥Ã¥ÈÅðÄ°¤ä¥ê¥×¥ì¥¤¹¶·â¤Î±Æ¶Á
¤ò¼õ¤±¤Ê¤¤ challenge-response ¥×¥í¥È¥³¥ë¤òÍѤ¤¤Æ¤¤¤Þ¤¹¡£¥Í¥Ã¥È¥ï¡¼¥¯¾å
¤Ç¤Ï¡¢¥Ñ¥¹¥ï¡¼¥É¤Ï¤É¤Á¤é¤Î¸þ¤­¤Ë¤âή¤ì¤Þ¤»¤ó¡£¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤Î¤¤
¤º¤ì¤â¡¢¤ª¸ß¤¤¤Î¿È¸µ¤òÆÈΩ¤Ë³Îǧ¤Ç¤­¤Þ¤¹¡£
.Pp
.\"O The file
.\"O .Li $ Ns Ev HOME Ns Pa /.cvsup/auth
.\"O holds the information used for authentication.  This file contains a
.\"O record for each server that the client is allowed to access.  Each
.\"O record occupies one line in the file.  Lines beginning with
.\"O .Ql #
.\"O are ignored, as are lines containing only white space.  White space is
.\"O significant everywhere else in the file.  Fields are separated by
.\"O .Ql \&:
.\"O characters.
¥Õ¥¡¥¤¥ë
.Li $ Ns Ev HOME Ns Pa /.cvsup/auth
¤Ë¤Ïǧ¾Ú¤Ë»È¤ï¤ì¤ë¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È
¤¬¥¢¥¯¥»¥¹²Äǽ¤Ê³Æ¥µ¡¼¥Ð¤Ë¤Ä¤¤¤Æ¤Î¥ì¥³¡¼¥É¤¬Æþ¤Ã¤Æ¤¤¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î
¥ì¥³¡¼¥É¤Ï¡¢¥Õ¥¡¥¤¥ëÃæ¤Ë 1 ¹Ô¤Ç½ñ¤«¤ì¤Þ¤¹¡£
.Ql #
¤Ç»Ï¤Þ¤ë¹Ô¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£¶õÇòʸ»ú¤À¤±¤Î¹Ô¤âƱÍͤǤ¹¡£¤¿¤À¤·¡¢¥Õ¥¡¥¤¥ë
Ãæ¤Î¾¤Î¾ì½ê¤Ç¤Ï¶õÇòʸ»ú¤â°ÕÌ£¤ò»ý¤Á¤Þ¤¹¡£¥Õ¥£¡¼¥ë¥É¤Ï
.Ql \&:
ʸ»ú¤Ç¶èÀÚ¤é¤ì¤Þ¤¹¡£
.Pp
.\"O Each record of the file has the following form:
¥Õ¥¡¥¤¥ë¤Î³Æ¥ì¥³¡¼¥É¤Ï°Ê²¼¤Î·Á¼°¤Ç¤¹:
.Bd -literal -offset indent
.Sm off
.Xo Ar serverName No : Ar clientName No :
.Ar password No : Ar comment
.Xc
.Sm on 
.Ed 
.Pp 
.\"O All fields must be present even if some of them are empty.
¤¿¤È¤¨¶õ¤Ç¤¢¤Ã¤Æ¤â¡¢Á´¤Æ¤Î¥Õ¥£¡¼¥ë¥É¤Ï¸ºß¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O .Ar ServerName
.\"O is the name of the server to which the record applies.  By convention,
.\"O it is the canonical fully-qualified domain name of the server, e.g.,
.\"O .Ql CVSup177.FreeBSD.ORG .
.Ar ServerName
¤Ï¥ì¥³¡¼¥É¤¬Å¬ÍѤµ¤ì¤ë¥µ¡¼¥Ð̾¤Ç¤¹¡£´·½¬Åª¤Ë¡¢¤³¤ì¤Ï¥«¥Î¥Ë¥«¥ë¤«¤Ä´°Á´
¤Ë¥É¥á¥¤¥ó̾¤¬»ØÄꤵ¤ì¤¿¥µ¡¼¥Ð̾¤Ç¤¹(Îã:
.Ql CVSup177.FreeBSD.ORG
)¡£
.\"O This must agree with the server's own idea of its name.  The name is
.\"O case-insensitive.
¤³¤ì¤Ï¥µ¡¼¥Ð¤¬¼«Ê¬¤Î̾Á°¤È¹Í¤¨¤Æ¤¤¤ë¥Û¥¹¥È̾¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
̾Á°¤Ë¤Ä¤¤¤Æ¤ÏÂçʸ»ú¡¦¾®Ê¸»ú¤Ï¶èÊ̤µ¤ì¤Þ¤»¤ó¡£
.Pp
.\"O .Ar ClientName
.\"O is the name the client uses to gain access to the server.  By
.\"O convention, e-mail addresses are used for all client names, e.g.,
.\"O .Ql BillyJoe@FreeBSD.ORG .
.\"O Client names are case-insensitive.
.Ar ClientName
¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¸¢¤òÆÀ¤ë¤È¤­¤Ë»È¤¦Ì¾Á°¤Ç¤¹¡£´·½¬Åª¤Ë¡¢
¥¯¥é¥¤¥¢¥ó¥È̾¤Ë¤ÏÁ´¤Æ e-mail ¥¢¥É¥ì¥¹¤¬»È¤ï¤ì¤Þ¤¹(Îã:
.Ql BillyJoe@FreeBSD.ORG
)¡£¥¯¥é¥¤¥¢¥ó¥È̾¤Ç¤ÏÂçʸ»ú¡¦¾®Ê¸»ú¤Ï¶èÊ̤µ¤ì¤Þ¤»¤ó¡£
.Pp
.\"O .Ar Password
.\"O is a secret string of characters that the client uses to prove its
.\"O identity.  It may not contain any
.\"O .Ql \&:
.\"O or newline characters.
.Ar Password
¤ÏÈëÌ©¤Îʸ»úÎó¤Ç¤¢¤ê¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬¿È¸µ¤ò¾ÚÌÀ¤¹¤ë¤¿¤á¤Ë»È¤¤¤Þ¤¹¡£
¥Ñ¥¹¥ï¡¼¥Éʸ»úÎó¤Ï
.Ql \&:
¤ä²þ¹Ôʸ»ú¤ò´Þ¤ó¤Ç¤Ï¤¤¤±¤Þ¤»¤ó¡£
.Pp
.\"O .Ar Comment
.\"O may contain any additional information to identify the record.  It
.\"O is not interpreted by the program.
.Ar Comment
¤Ï¥ì¥³¡¼¥É¤ò¼±Ê̤¹¤ë¤¿¤á¤ÎÉÕ²ÃŪ¤Ê¾ðÊó¤ò»ý¤Á¤Þ¤¹¡£¥×¥í¥°¥é¥à¤Ë²ò¼á¤µ¤ì
¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
.Pp
.\"O To set up authentication for a given server, one must perform the
.\"O following steps:
»ØÄꤵ¤ì¤¿¥µ¡¼¥Ð¤ËÂФ¹¤ëǧ¾Ú¤ÎÀßÄê¤ò¹Ô¤¦¤Ë¤Ï¡¢°Ê²¼¤Î¼ê½ç¤ò¼Â¹Ô¤·¤Ê¤±¤ì
¤Ð¤Ê¤ê¤Þ¤»¤ó:
.Bl -enum
.It
.\"O Obtain the official
.\"O .Ar serverName
.\"O from the administrator of the server or from some other source.
¥µ¡¼¥Ð´ÉÍý¼Ô¤Þ¤¿¤ÏÊ̤ξðÊ󸻤«¤é¸ø¼°¤Ê
.Ar serverName
¤ò¼èÆÀ¤·¤Þ¤¹¡£
.It
.\"O Choose an appropriate
.\"O .Ar clientName .
ŬÀÚ¤Ê
.Ar clientName
¤òÁª¤Ó¤Þ¤¹¡£
.\"O It should be in the form of a valid e-mail address, to make it easy
.\"O for the server administrator to contact the user if necessary.
¤³¤ì¤ÏÍ­¸ú¤ÊÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Î·Á¼°¤Ë¤¹¤Ù¤­¤Ç¤¹¡£¤³¤ì¤Ï¡¢¥µ¡¼¥Ð´ÉÍý¼Ô
¤¬É¬Íפ˱þ¤¸¤Æ¥æ¡¼¥¶¤ËÏ¢Íí¤·¤ä¤¹¤¯¤¹¤ë¤¿¤á¤Ç¤¹¡£
.It
.\"O Choose an arbitrary secret
.\"O .Ar password .
ÈëÌ©¤Î
.Ar password
¤È¤·¤ÆǤ°Õ¤Îʸ»úÎó¤òÁª¤Ó¤Þ¤¹¡£
.It
.\"O Run the
.\"O .Nm cvpasswd
.\"O utility, and type in the
.\"O .Ar password
.\"O when prompted for it.  The utility will print out a line to send
.\"O to the server administrator, and instruct you how to modify your
.\"O .Li $ Ns Ev HOME Ns Pa /.cvsup/auth
.\"O file.  You should use a secure channel to send the line to the
.\"O server administrator.
.Nm cvpasswd
¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò¼Â¹Ô¤·¡¢¼ÁÌä¤ËÂФ·¤Æ
.Ar ¥Ñ¥¹¥ï¡¼¥É
¤òÆþÎϤ·¤Þ¤¹¡£¤³¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ï¥µ¡¼¥Ð¤Î´ÉÍý¼Ô¤ËÁ÷¤ë¹Ô¤ò½ÐÎϤ·¡¢
¤½¤ì¤«¤é¥æ¡¼¥¶¤Î
.Li $ Ns Ev HOME Ns Pa /.cvsup/auth
¥Õ¥¡¥¤¥ë¤Î½¤Àµ¼ê½ç¤ò¼¨¤·¤Þ¤¹¡£¤³¤Î¹Ô¤ò¥µ¡¼¥Ð´ÉÍý¼Ô¤ËÁ÷¤ë¤Ë¤Ï¡¢°ÂÁ´¤Ê
¼êÃʤò»È¤¦¤Ù¤­¤Ç¤¹¡£
.El
.Pp
.\"O Since
.\"O .Li $ Ns Ev HOME Ns Pa /.cvsup/auth
.\"O contains passwords, you should ensure that it is not readable by
.\"O anyone except yourself.
.Li $ Ns Ev HOME Ns Pa /.cvsup/auth
¤Ë¤Ï¥Ñ¥¹¥ï¡¼¥É¤¬Æþ¤Ã¤Æ¤¤¤ë¤Î¤Ç¡¢É¬¤º¼«Ê¬°Ê³°¤Ë¤Ïï¤âÆɤá¤Ê¤¤¤è¤¦¤Ë¤·¤Æ
¤¯¤À¤µ¤¤¡£
.Pp
.\"O Authentication works independently in both directions.  The server
.\"O administrator controls whether you must prove your identity.
ǧ¾Ú¤Ï¤½¤ì¤¾¤ì¤Î¸þ¤­¤ÇÆÈΩ¤ËÆ°ºî¤·¤Þ¤¹¡£¥µ¡¼¥Ð¤Î´ÉÍý¼Ô¤Ï¡¢
¥æ¡¼¥¶¤¬¿È¸µ¤ò¾ÚÌÀ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£
.\"O You control whether to check the server's identity, by means of the
.\"O .Fl a
.\"O command line option.
¥æ¡¼¥¶¤Ï¥µ¡¼¥Ð¤Î¿È¸µ¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£À©¸æ¤Ë¤Ï
.Fl a
¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£
.\"O .Sh USING CVSup FOR MIRRORING
.Sh ¥ß¥é¡¼¥ê¥ó¥°¤Î¤¿¤á¤Î CVSup ¤Î»ÈÍÑ
.\"O Although
.\"O .Nm CVSup
.\"O is optimized for CVS repositories, it works quite well as a general
.\"O purpose mirroring tool.
.Nm CVSup
¤Ï CVS ¥ê¥Ý¥¸¥È¥êÍѤ˺ÇŬ²½¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ÈÆÍÑŪ¤Ê¥ß¥é¡¼¥ê¥ó¥°¤È¤·¤Æ
Èó¾ï¤Ë¤¦¤Þ¤¯Æ°ºî¤·¤Þ¤¹¡£
.\"O It is able to update all types of files.
.Nm CVSup
¤Ï¤É¤ó¤Ê¼ïÎà¤Î¥Õ¥¡¥¤¥ë¤Î¹¹¿·¤Ë¤â»È¤¨¤Þ¤¹¡£
.Bl -bullet -compact
.It
.\"O RCS files are updated by transferring individual tags and deltas,
.\"O and merging them into the client file.
RCS ¥Õ¥¡¥¤¥ë¤Î¹¹¿·¤Ï¡¢¸Ä¡¹¤Î¥¿¥°¤Èº¹Ê¬¤ÎžÁ÷¤ª¤è¤Ó¡¢¤³¤ì¤é¤Î
¥¯¥é¥¤¥¢¥ó¥È¦¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥Þ¡¼¥¸¤Ë¤è¤Ã¤Æ¹Ô¤ï¤ì¤Þ¤¹¡£
.It
.\"O Regular files are updated using the rsync algorithm, if it is
.\"O enabled.
Ä̾ï¥Õ¥¡¥¤¥ë¤Ï¡¢²Äǽ¤Ç¤¢¤ì¤Ð rsync ¥¢¥ë¥´¥ê¥º¥à¤ò»È¤Ã¤Æ¹¹¿·¤µ¤ì¤Þ¤¹¡£
.\"O If the rsync algorithm is disabled, files which have had data appended
.\"O to them on the server (e.g., log files) receive only the new tail portion.
rsync ¥¢¥ë¥´¥ê¥º¥à¤¬Ìµ¸ú¤Ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢Äɲ䵤줿¥Ç¡¼¥¿¤ò»ý¤Ä¥µ¡¼¥Ð
¾å¤Î¥Õ¥¡¥¤¥ë(Îã: ¥í¥°¥Õ¥¡¥¤¥ë)¤Ï¡¢¿·¤·¤¯²Ã¤ï¤Ã¤¿ËöÈø¤ÎÉôʬ¤À¤±¤ò¼õ¤±¼è
¤ê¤Þ¤¹¡£
.\"O Other regular files are replaced in whole.
¾¤ÎÄ̾ï¥Õ¥¡¥¤¥ë¤Ï¤Þ¤ë¤´¤ÈÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£
.It
.\"O Empty directories are preserved.
¶õ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ï»Ä¤µ¤ì¤Þ¤¹¡£
.It
.\"O Symbolic links are updated as dictated by
.\"O .Cm symlink
.\"O and
.\"O .Cm rsymlink
.\"O commands in the server's configuration files.  See
.\"O .Xr cvsupd 8 .
¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Ï¡¢¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ëÆâ¤Ç
.Cm symlink
¤È
.Cm rsymlink
¥³¥Þ¥ó¥É¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¹¹¿·¤µ¤ì¤Þ¤¹¡£¾Ü¤·¤¯¤Ï
.Xr cvsupd 8
¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.It
.\"O Hard links are preserved within each collection, but not
.\"O between collections.
¥Ï¡¼¥É¥ê¥ó¥¯¤Ï¤½¤ì¤¾¤ì¤Î¥³¥ì¥¯¥·¥ç¥óÆâ¤Ç¤ÏÊݸ¤µ¤ì¤Þ¤¹¤¬¡¢¥³¥ì¥¯¥·¥ç¥ó
´Ö¤Ç¤ÏÊݸ¤µ¤ì¤Þ¤»¤ó¡£
.It
.\"O Device nodes are updated by major and minor device number.
¥Ç¥Ð¥¤¥¹¥Î¡¼¥É¤Ï¥á¥¸¥ã¡¼ÈÖ¹æ¤È¥Þ¥¤¥Ê¡¼ÈÖ¹æ¤ò»È¤Ã¤Æ¹¹¿·¤µ¤ì¤Þ¤¹¡£
.\"O This may not produce the desired results if the client host
.\"O and the server host run different operating systems.
¥¯¥é¥¤¥¢¥ó¥È¤Î¥Û¥¹¥È¤È¥µ¡¼¥Ð¤Î¥Û¥¹¥È¤Ç°Û¤Ê¤ë¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬
Æ°ºî¤·¤Æ¤¤¤ë¤È¡¢¤³¤ì¤Ï˾¤Þ¤·¤¤·ë²Ì¤È¤Ê¤é¤Ê¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
.El
.\"O .Sh CVSup AND FIREWALLS
.Sh CVSup ¤ÈËɲÐÊÉ
.\"O .Nm
.\"O provides a number of different modes designed to work thorough
.\"O various firewall setups.
.Nm
¤Ï¡¢ÍÍ¡¹¤ÊÀßÄê¤ÎËɲÐÊɤòĶ¤¨¤ë¤¿¤á¤Ë¿ô¿¤¯¤Î¥â¡¼¥É¤òÍÑ°Õ¤·¤Æ¤¤¤Þ¤¹¡£
.\"O These are controlled by the
.\"O .Fl P
.\"O option and by the use of the
.\"O .Nm m3socks
.\"O command.
¤³¤ì¤é¤Î¥â¡¼¥É¤Ï
.Fl P
¥ª¥×¥·¥ç¥ó¤«¡¢
.Nm m3socks
¥³¥Þ¥ó¥É¤ò»È¤Ã¤ÆÀ©¸æ¤Ç¤­¤Þ¤¹¡£
.\"O To allow
.\"O .Nm
.\"O to be used, the firewall must at a minimum permit outbound connections
.\"O to port 5999 of the server host.
.Nm
¤ò»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢ËɲÐÊɤϥµ¡¼¥Ð¥Û¥¹¥È¤Î 5999 È֥ݡ¼¥È¤Ø¤Î³°¸þ¤­
¤ÎÀܳ¤òºÇÄã¸Âµö²Ä¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O If this condition is met, then multiplexed mode
.\"O .Pq Fl P Cm m
.\"O should work, with or without SOCKS.
¤³¤Î¾ò·ï¤¬Ëþ¤¿¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢SOCKS ¤Î̵ͭ¤Ë´Ø¤ï¤é¤ºÂ¿½Å¥â¡¼¥É
.Pq Fl P Cm m
¤¬Æ°ºî¤¹¤ë¤Ï¤º¤Ç¤¹¡£
.Pp
.\"O With slightly more permissive firewall rules it may be possible to
.\"O use passive mode or one of the other modes, for a slight gain in
.\"O efficiency.
¤â¤¦¾¯¤·ËɲÐÊɤÎÀ©¸Â¤¬´Ë¤±¤ì¤Ð¡¢passive ¥â¡¼¥É¤ä¾¤Î¥â¡¼¥É¤Î°ì¤Ä¤ò»È¤Ã
¤Æ¡¢¸úΨ¤ò¾¯¤·¾å¤²¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
.\"O See the description of the
.\"O .Fl P
.\"O option for details.
¾Ü¤·¤¯¤Ï
.Fl P
¥ª¥×¥·¥ç¥ó¤ÎÀâÌÀ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.Pp
.\"O For more information on using CVSup with specific kinds of firewalls,
.\"O see the CVSup FAQ at
.\"O .Aq http://www.polstra.com/projects/freeware/CVSup/ .
ÆÃÄê¤Î¼ïÎà¤ÎËɲÐÊÉ¤È CVSup ¤òÁȤ߹ç¤ï¤»¤Æ»È¤¦ºÝ¤Î¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.Aq http://www.polstra.com/projects/freeware/CVSup/
¤Ë¤¢¤ë CVSup FAQ ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.\"O .Sh USING CVSup WITH SOCKS
.Sh SOCKS ¤ÈÁȤ߹ç¤ï¤»¤Æ¤Î CVSup ¤ÎÍøÍÑ
.\"O Communication through a SOCKS proxy server is currently supported only
.\"O under FreeBSD.
SOCKS ¥×¥í¥­¥·¥µ¡¼¥Ð·Ðͳ¤Ç¤ÎÄÌ¿®¤Ï¡¢¸½ºß¤Ï FreeBSD ¾å¤Ç¤·¤«¥µ¥Ý¡¼¥È¤µ
¤ì¤Æ¤¤¤Þ¤»¤ó¡£
.\"O It requires a modified Modula-3 runtime system as provided by the
.\"O .Pa lang/modula-3-lib
.\"O port, and an add-on SOCKS library from the
.\"O .Pa lang/modula-3-socks
.\"O port.
¤³¤ì¤òÍѤ¤¤ë¤¿¤á¤Ë¤Ï¡¢port ¤È¤·¤ÆÍÑ°Õ¤µ¤ì¤Æ¤¤¤ë
½¤ÀµÈǤΠModula-3 ¤Î¼Â¹Ô»þ¥·¥¹¥Æ¥à(
.Pa lang/modula-3-lib
)¤È¥¢¥É¥ª¥ó¤Î SOCKS ¥é¥¤¥Ö¥é¥ê(
.Pa lang/modula-3-socks
)¤¬É¬ÍפǤ¹¡£
.\"O Also, the SOCKS library uses dynamic linking techniques which require
.\"O that the
.\"O .Nm
.\"O executable be fully dynamic.
¤Þ¤¿¡¢SOCKS ¥é¥¤¥Ö¥é¥ê¤ÏưŪ¥ê¥ó¥¯µ»½Ñ¤ò»È¤¦¤Î¤Ç¡¢
.Nm
¤Î¼Â¹Ô¥Õ¥¡¥¤¥ë¤Ï´°Á´¤ËưŪ¥ê¥ó¥¯¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
.\"O The FreeBSD port
.\"O .Pa net/cvsup
.\"O links
.\"O .Nm
.\"O fully dynamic as required.
FreeBSD ¤Î port ¤Î
.Pa net/cvsup
¤Ï¡¢É¬Íפ˱þ¤¸¤Æ
.Nm
¤ò´°Á´¤ËưŪ¤Ë¥ê¥ó¥¯¤·¤Þ¤¹¡£
.Pp
.\"O To enable SOCKS operation, simply execute
.\"O .Nm
.\"O with the
.\"O .Cm m3socks
.\"O command provided in the
.\"O .Pa lang/modula-3-socks
.\"O package.
SOCKS ¤ÎÆ°ºî¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢Ã±¤Ë
.Pa lang/modula-3-socks
¥Ñ¥Ã¥±¡¼¥¸¤Ë´Þ¤Þ¤ì¤ë
.Cm m3socks
¤ÈÁȤ߹ç¤ï¤»¤Æ
.Nm
¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£
.\"O See
.\"O .Xr m3socks 1
.\"O for further details.
¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï
.Xr m3socks 1
¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
.\"O .Sh USING ssh PORT FORWARDING
.Sh ssh ¤ò»È¤Ã¤¿¥Ý¡¼¥ÈžÁ÷
.\"O As an alternative to SOCKS, a user behind a firewall can penetrate it
.\"O with the TCP port forwarding provided by the Secure Shell package
.\"O .Nm ssh .
ËɲÐÊɤÎÆ⦤Υ桼¥¶¤Ï¡¢SOCKS ¤ÎÂåÂØÉʤȤ·¤Æ¡¢Secure Shell ¥Ñ¥Ã¥±¡¼¥¸¤Î
.Nm ssh
¤¬»ý¤Ã¤Æ¤¤¤ë TCP ¥Ý¡¼¥ÈžÁ÷µ¡Ç½¤ò»È¤Ã¤ÆËɲÐÊɤòÄ̲á¤Ç¤­¤Þ¤¹¡£
.\"O The user must have a login account on the
.\"O .Nm CVSup
.\"O server host in order to do this.
¤³¤ì¤ò¹Ô¤¦¤¿¤á¤Ë¤Ï¡¢¥æ¡¼¥¶¤Ï
.Nm CVSup
¤Î¥µ¡¼¥Ð¥Û¥¹¥È¤Ë¥í¥°¥¤¥ó¥¢¥«¥¦¥ó¥È¤¬É¬ÍפǤ¹¡£
.\"O The procedure is as follows:
¼ê½ç¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:
.Bl -enum
.It
.\"O Establish a connection to the server host with
.\"O .Nm ssh ,
.\"O like this:
°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¡¢
.Nm ssh
¤ò»È¤Ã¤Æ¥µ¡¼¥Ð¥Û¥¹¥È¤È¤ÎÀܳ¤ò³ÎΩ¤·¤Þ¤¹:
.Bd -literal
ssh -f -x -L 5999:localhost:5999 serverhost sleep 60
.Ed
.Pp
.\"O Replace
.\"O .Ar serverhost
.\"O with the hostname of the CVSup server, but type
.\"O .Ql localhost
.\"O literally.
ÉáÄ̤Ï
.Ar serverhost
¤ò CVSup ¥µ¡¼¥Ð¤Î¥Û¥¹¥È̾¤ËÃÖ¤­´¹¤¨¤ë¤Î¤Ç¤¹¤¬¡¢¤³¤³¤Ç¤Ï
.Ql localhost
¤òÆþÎϤ·¤Þ¤¹¡£
.\"O This sets up the required port forwarding.
¤³¤ì¤Ë¤è¤ê¡¢¥Ý¡¼¥ÈžÁ÷¤ËɬÍפÊÀßÄ꤬¤Ç¤­¤Þ¤¹¡£
.\"O You must start
.\"O .Nm
.\"O before the 60-second
.\"O .Nm sleep
.\"O finishes.
60 É÷ФäÆ
.Nm sleep
¤¬½ª¤ï¤ë¤Þ¤Ç¤Ë
.Nm
¤òµ¯Æ°¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
.\"O Once the update has begun,
.\"O .Nm ssh
.\"O will keep the forwarded channels open as long as they are needed.
¤¤¤Ã¤¿¤ó¹¹¿·¤¬»Ï¤Þ¤ë¤È¡¢
.Nm ssh
¤ÏɬÍפʴ֡¢Å¾Á÷¥Á¥ã¥Í¥ë¤ò¥ª¡¼¥×¥ó¤·¤¿¾õÂÖ¤òÊݤÁ¤Þ¤¹¡£
.It
.\"O Run
.\"O .Nm
.\"O on the local host, including these arguments on the command line:
.\"O .Ql -h localhost -P m .
¥í¡¼¥«¥ë¥Û¥¹¥È¤Ç
.Nm
¤ò¼Â¹Ô¤·¤Þ¤¹¡£¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë¤Ï°Ê²¼¤Î¹Ô¤ò´Þ¤á¤Þ¤¹:
.Ql -h localhost -P m
.El
.\"O .Sh FILES
.Sh ¥Õ¥¡¥¤¥ë
.Bl -tag -width base/sup/collection/checkouts*xx -compact
.It Pa /usr/local/etc/cvsup
.\"O Default
.\"O .Ar base
.\"O directory.
¥Ç¥Õ¥©¥ë¥È¤Î
.Ar base
¥Ç¥£¥ì¥¯¥È¥ê¡£
.It Pa sup
.\"O Default
.\"O .Ar collDir
.\"O subdirectory.
¥Ç¥Õ¥©¥ë¥È¤Î
.Ar collDir
¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¡£
.Sm off
.It Xo Ar base / Ar collDir / Ar collection
.Pa /checkouts*
.Xc
.Sm on
.\"O List files.
¥ê¥¹¥È¥Õ¥¡¥¤¥ë¡£
.Sm off
.It Ar base / Ar collDir Pa /refuse
.Sm on
.\"O Global refuse file.
¥°¥í¡¼¥Ð¥ë¤Î refuse ¥Õ¥¡¥¤¥ë¡£
.Sm off
.It Xo Ar base / Ar collDir / Ar collection
.Pa /refuse*
.Xc
.Sm on
.\"O Per-collection and per-release and tag refuse files.
¥³¥ì¥¯¥·¥ç¥óÊ̤Πrefuse ¥Õ¥¡¥¤¥ë¤È¡¢¥ê¥ê¡¼¥¹¤È¥¿¥°Ê̤Πrefuse ¥Õ¥¡¥¤¥ë¡£
.It Li $ Ns Ev HOME Ns Pa /.cvsup/auth
.\"O Authentication password file.
ǧ¾ÚÍѤΥѥ¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¡£
.El
.\"O .Sh SEE ALSO
.Sh ´ØÏ¢¹àÌÜ
.Xr ctm 1 ,
.Xr cvpasswd 1 , 
.Xr cvs 1 ,
.Xr cvsupd 8 ,
.Xr m3socks 1 ,
.Xr rcsintro 1 ,
.\"O .Xr ssh 1 .
.Xr ssh 1
.Pp
.Bd -literal
http://www.polstra.com/projects/freeware/CVSup/
.Ed
.\"O .Sh AUTHORS
.Sh ºî¼Ô
.\"O .An John Polstra Aq jdp@polstra.com .
.An John Polstra Aq jdp@polstra.com
.\"O .Sh BUGS
.Sh ¥Ð¥°
.\"O An RCS file is not recognized as such unless its name ends with
.\"O .Ql \&,v .
RCS ¥Õ¥¡¥¤¥ë¤Ï
.Ql \&,v
¤Ç½ª¤ï¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð RCS ¥Õ¥¡¥¤¥ë¤Èǧ¼±¤µ¤ì¤Þ¤»¤ó¡£
.Pp
.\"O Any directory named
.\"O .Ql Attic
.\"O is assumed to be a CVS Attic, and is treated specially.
.Ql Attic
¤È¤¤¤¦Ì¾Á°¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ï CVS Attic ¤È¤·¤ÆÆÃÊÌ°·¤¤¤µ¤ì¤Þ¤¹¡£
.Pp
.\"O Because of bugs in the SOCKS library or server, most forms of the
.\"O .Fl P
.\"O option cannot be used with SOCKS.
SOCKS ¥é¥¤¥Ö¥é¥ê¤Þ¤¿¤Ï¥µ¡¼¥Ð¤Î¥Ð¥°¤Î¤¿¤á¡¢ÂçÉôʬ¤Î·Á¼°¤Î
.Fl P
¥ª¥×¥·¥ç¥ó¤Ï SOCKS ¤Ç¤Ï»È¤¨¤Þ¤»¤ó¡£
.\"O Multiplexed mode
.\"O .Pq Fl P Cm m
.\"O can be used, but the other forms of
.\"O .Fl P
.\"O are rejected.
¿½Å¥â¡¼¥É
.Pq Fl P Cm m
¤ò»È¤¨¤Þ¤¹¤¬¡¢Â¾¤Î·Á¼°¤Î
.Fl P
¥ª¥×¥·¥ç¥ó¤Ï¼õ¤±ÉÕ¤±¤é¤ì¤Þ¤»¤ó¡£
.Pp
.\"O The GUI interacts poorly with some window managers, notably FVWM.
GUI ¤È°ìÉô¤Î¥¦¥£¥ó¥É¥¦¥Þ¥Í¡¼¥¸¥ã(ÆÃ¤Ë FVWM)¤ÎÁêÀ­¤¬Îɤ¯¤¢¤ê¤Þ¤»¤ó¡£
.\"O There are problems with both versions 1 and 2 of FVWM,
.\"O though it appears that they are not as bad in version 2.
FVWM ¤Î¥Ð¡¼¥¸¥ç¥ó 1, 2 ¤Î¤É¤Á¤é¤Ç¤âÌäÂ꤬µ¯¤³¤ë¤Î¤Ç¤¹¤¬¡¢¥Ð¡¼¥¸¥ç¥ó 2
¤ÎÊý¤¬¤Þ¤À¤Þ¤·¤Î¤è¤¦¤Ç¤¹¡£
.\"O Adding the line
.\"O .Pp
.\"O .Dl Style \&"cvsup\&" ClickToFocus
.\"O .Pp
.\"O to FVWM2's
.\"O .Pa .fvwmrc
.\"O file helps quite a bit.
.Pp
.Dl Style \&"cvsup\&" ClickToFocus
.Pp
¤È¤¤¤¦¹Ô¤ò FVWM2 ¤Î
.Pa .fvwmrc
¤ËÄɲ乤ë¤È¤«¤Ê¤ê¤è¤¯¤Ê¤ê¤Þ¤¹¡£
.\"O The problem appears to be caused by window manager bugs, triggered by
.\"O the GUI's use of the
.\"O .Ql WM_TAKE_FOCUS
.\"O protocol.
¤³¤ÎÌäÂê¤Ï¤É¤¦¤ä¤é¥¦¥£¥ó¥É¥¦¥Þ¥Í¡¼¥¸¥ã¤Î¥Ð¥°¤¬¸¶°ø¤é¤·¤¯¡¢GUI ¤¬
.Ql WM_TAKE_FOCUS
¥×¥í¥È¥³¥ë¤ò»È¤¦¤Èµ¯¤³¤ë¤è¤¦¤Ç¤¹¡£
.\"O As a work-around, you can always use the
.\"O .Fl g
.\"O option to disable the GUI entirely.
²óÈòºö¤È¤·¤Æ¤Ï¡¢
.Fl g
¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢GUI ¤ò´°Á´¤Ë̵¸ú¤Ë¤¹¤ë¤È¤è¤¤¤Ç¤·¤ç¤¦¡£