+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Table of Contents]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf002.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P><HR>
-AFS<BR>
-Administration Reference<BR>
-<P>Version 3.6
-<P>Document Number GC09-4562-00
-<P>
-<BR>
-<P><B>First Edition (April 2000)</B>
-<P>This edition applies to:
-<DL COMPACT>
-<DD>IBM AFS for AIX, Version 3.6
-<DD>IBM AFS for Digital Unix, Version 3.6
-<DD>IBM AFS for HP-UX, Version 3.6
-<DD>IBM AFS for Linux, Version 3.6
-<DD>IBM AFS for SGI IRIX, Version 3.6
-<DD>IBM AFS for Solaris, Version 3.6
-</DL>
-<P>and to all subsequent releases and modifications until otherwise indicated
-in new editions.
-<P>This softcopy version is based on the printed edition of this book.
-Some formatting amendments have been made to make this information more
-suitable for softcopy.
-<P>Order publications through your IBM representative or through the IBM
-branch office serving your locality.
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Table of Contents]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf002.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf000.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf003.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<H2><A NAME="ToC">Table of Contents</A></H2>
-<P><B><A NAME="ToC_1" HREF="auarf003.htm#HDRTLIST_START">Tables</A></B><BR>
-<P><B><A NAME="ToC_2" HREF="auarf004.htm#Header_2">About This Manual</A></B><BR>
-<MENU>
-<LI><A NAME="ToC_3" HREF="auarf005.htm#HDRWQ1">Audience and Purpose</A>
-<LI><A NAME="ToC_4" HREF="auarf006.htm#HDRWQ2">Organization</A>
-<LI><A NAME="ToC_5" HREF="auarf007.htm#HDRWQ3">How to Use This Document</A>
-<LI><A NAME="ToC_6" HREF="auarf008.htm#HDRWQ4">Related Documents</A>
-<LI><A NAME="ToC_7" HREF="auarf009.htm#HDRTYPO_CONV">Typographical Conventions</A>
-</MENU>
-<P><B><A NAME="ToC_8" HREF="auarf010.htm#Header_8">AFS System Files</A></B><BR>
-<MENU>
-<LI><A NAME="ToC_9" HREF="auarf011.htm#HDRFILESINTRO">afs_file_intro</A>
-<LI><A NAME="ToC_10" HREF="auarf012.htm#HDRAUTHLOG">AuthLog</A>
-<LI><A NAME="ToC_11" HREF="auarf013.htm#HDRWQ5">AuthLog.dir, AuthLog.pag</A>
-<LI><A NAME="ToC_12" HREF="auarf014.htm#HDRBACKUPLOG">BackupLog</A>
-<LI><A NAME="ToC_13" HREF="auarf015.htm#HDRBOSLOG">BosLog</A>
-<LI><A NAME="ToC_14" HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<LI><A NAME="ToC_15" HREF="auarf017.htm#HDRCACHEITEMS">CacheItems</A>
-<LI><A NAME="ToC_16" HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>
-<LI><A NAME="ToC_17" HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<LI><A NAME="ToC_18" HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<LI><A NAME="ToC_19" HREF="auarf021.htm#HDRFILELOG">FileLog</A>
-<LI><A NAME="ToC_20" HREF="auarf022.htm#HDRFORCESALVAGE">FORCESALVAGE</A>
-<LI><A NAME="ToC_21" HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<LI><A NAME="ToC_22" HREF="auarf024.htm#HDRCLI_NETINFO">NetInfo (client version)</A>
-<LI><A NAME="ToC_23" HREF="auarf025.htm#HDRSV_NETINFO">NetInfo (server version)</A>
-<LI><A NAME="ToC_24" HREF="auarf026.htm#HDRCLI_NETRESTRICT">NetRestrict (client version)</A>
-<LI><A NAME="ToC_25" HREF="auarf027.htm#HDRSV_NETRESTRICT">NetRestrict (server version)</A>
-<LI><A NAME="ToC_26" HREF="auarf028.htm#HDRNOAUTH">NoAuth</A>
-<LI><A NAME="ToC_27" HREF="auarf029.htm#HDRSALVAGEFS">SALVAGE.fs</A>
-<LI><A NAME="ToC_28" HREF="auarf030.htm#HDRSALVAGELOG">SalvageLog</A>
-<LI><A NAME="ToC_29" HREF="auarf031.htm#HDRTE">TE_<I>device_name</I></A>
-<LI><A NAME="ToC_30" HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<LI><A NAME="ToC_31" HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<LI><A NAME="ToC_32" HREF="auarf034.htm#HDRTL">TL_<I>device_name</I></A>
-<LI><A NAME="ToC_33" HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<LI><A NAME="ToC_34" HREF="auarf036.htm#HDRVN">V<I>n</I></A>
-<LI><A NAME="ToC_35" HREF="auarf037.htm#HDRVVOLID">V<I>vol_ID</I>.vol</A>
-<LI><A NAME="ToC_36" HREF="auarf038.htm#HDRVLLOG">VLLog</A>
-<LI><A NAME="ToC_37" HREF="auarf039.htm#HDRVOLSERLOG">VolserLog</A>
-<LI><A NAME="ToC_38" HREF="auarf040.htm#HDRVOLUMEITEMS">VolumeItems</A>
-<LI><A NAME="ToC_39" HREF="auarf041.htm#HDRAFSZCM">afszcm.cat</A>
-<LI><A NAME="ToC_40" HREF="auarf042.htm#HDRBDBDB">bdb.DB0 and bdb.DBSYS1</A>
-<LI><A NAME="ToC_41" HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<LI><A NAME="ToC_42" HREF="auarf044.htm#HDRFMSLOG">fms.log</A>
-<LI><A NAME="ToC_43" HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<LI><A NAME="ToC_44" HREF="auarf046.htm#HDRKASERVERAUXDB">kaserverauxdb</A>
-<LI><A NAME="ToC_45" HREF="auarf047.htm#HDRPRDBDB">prdb.DB0 and prdb.DBSYS1</A>
-<LI><A NAME="ToC_46" HREF="auarf048.htm#HDRSALVAGELOCK">salvage.lock</A>
-<LI><A NAME="ToC_47" HREF="auarf049.htm#HDRSYSID">sysid</A>
-<LI><A NAME="ToC_48" HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<LI><A NAME="ToC_49" HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<LI><A NAME="ToC_50" HREF="auarf052.htm#HDRAFSMONCONFIG">afsmonitor Configuration File</A>
-<LI><A NAME="ToC_51" HREF="auarf053.htm#HDRPACKAGECONFIG">package Configuration File</A>
-<LI><A NAME="ToC_52" HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>
-<LI><A NAME="ToC_53" HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-</MENU>
-<P><B><A NAME="ToC_54" HREF="auarf056.htm#Header_54">AFS System Commands</A></B><BR>
-<MENU>
-<LI><A NAME="ToC_55" HREF="auarf057.htm#HDRAFSINTRO">afs_intro</A>
-<LI><A NAME="ToC_72" HREF="auarf058.htm#HDRAFSD">afsd</A>
-<LI><A NAME="ToC_73" HREF="auarf059.htm#HDRAFSMONITOR">afsmonitor</A>
-<LI><A NAME="ToC_74" HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<LI><A NAME="ToC_75" HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<LI><A NAME="ToC_76" HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<LI><A NAME="ToC_77" HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<LI><A NAME="ToC_78" HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<LI><A NAME="ToC_79" HREF="auarf065.htm#HDRBK_APROPOS">backup apropos</A>
-<LI><A NAME="ToC_80" HREF="auarf066.htm#HDRBK_DBVERIFY">backup dbverify</A>
-<LI><A NAME="ToC_81" HREF="auarf067.htm#HDRBK_DELDUMP">backup deldump</A>
-<LI><A NAME="ToC_82" HREF="auarf068.htm#HDRBK_DELETEDUMP">backup deletedump</A>
-<LI><A NAME="ToC_83" HREF="auarf069.htm#HDRBK_DELHOST">backup delhost</A>
-<LI><A NAME="ToC_84" HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<LI><A NAME="ToC_85" HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<LI><A NAME="ToC_86" HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<LI><A NAME="ToC_87" HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<LI><A NAME="ToC_88" HREF="auarf074.htm#HDRBK_DUMPINFO">backup dumpinfo</A>
-<LI><A NAME="ToC_89" HREF="auarf075.htm#HDRBK_HELP">backup help</A>
-<LI><A NAME="ToC_90" HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<LI><A NAME="ToC_91" HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<LI><A NAME="ToC_92" HREF="auarf078.htm#HDRBK_KILL">backup kill</A>
-<LI><A NAME="ToC_93" HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
-<LI><A NAME="ToC_94" HREF="auarf080.htm#HDRBK_LISTDUMPS">backup listdumps</A>
-<LI><A NAME="ToC_95" HREF="auarf081.htm#HDRBK_LISTHOSTS">backup listhosts</A>
-<LI><A NAME="ToC_96" HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<LI><A NAME="ToC_97" HREF="auarf083.htm#HDRBK_QUIT">backup quit</A>
-<LI><A NAME="ToC_98" HREF="auarf084.htm#HDRBK_READLABEL">backup readlabel</A>
-<LI><A NAME="ToC_99" HREF="auarf085.htm#HDRBK_RESTOREDB">backup restoredb</A>
-<LI><A NAME="ToC_100" HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<LI><A NAME="ToC_101" HREF="auarf087.htm#HDRBK_SCANTAPE">backup scantape</A>
-<LI><A NAME="ToC_102" HREF="auarf088.htm#HDRBK_SETEXP">backup setexp</A>
-<LI><A NAME="ToC_103" HREF="auarf089.htm#HDRBK_STATUS">backup status</A>
-<LI><A NAME="ToC_104" HREF="auarf090.htm#HDRBK_VOLINFO">backup volinfo</A>
-<LI><A NAME="ToC_105" HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<LI><A NAME="ToC_106" HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<LI><A NAME="ToC_107" HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<LI><A NAME="ToC_108" HREF="auarf094.htm#HDRBOS_ADDHOST">bos addhost</A>
-<LI><A NAME="ToC_109" HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<LI><A NAME="ToC_110" HREF="auarf096.htm#HDRBOS_ADDUSER">bos adduser</A>
-<LI><A NAME="ToC_111" HREF="auarf097.htm#HDRBOS_APROPOS">bos apropos</A>
-<LI><A NAME="ToC_112" HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<LI><A NAME="ToC_113" HREF="auarf099.htm#HDRBOS_DELETE">bos delete</A>
-<LI><A NAME="ToC_114" HREF="auarf100.htm#HDRBOS_EXEC">bos exec</A>
-<LI><A NAME="ToC_115" HREF="auarf101.htm#HDRBOS_GETDATE">bos getdate</A>
-<LI><A NAME="ToC_116" HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<LI><A NAME="ToC_117" HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<LI><A NAME="ToC_118" HREF="auarf104.htm#HDRBOS_HELP">bos help</A>
-<LI><A NAME="ToC_119" HREF="auarf105.htm#HDRBOS_INSTALL">bos install</A>
-<LI><A NAME="ToC_120" HREF="auarf106.htm#HDRBOS_LISTHOSTS">bos listhosts</A>
-<LI><A NAME="ToC_121" HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<LI><A NAME="ToC_122" HREF="auarf108.htm#HDRBOS_LISTUSERS">bos listusers</A>
-<LI><A NAME="ToC_123" HREF="auarf109.htm#HDRBOS_PRUNE">bos prune</A>
-<LI><A NAME="ToC_124" HREF="auarf110.htm#HDRBOS_REMOVEHOST">bos removehost</A>
-<LI><A NAME="ToC_125" HREF="auarf111.htm#HDRBOS_REMOVEKEY">bos removekey</A>
-<LI><A NAME="ToC_126" HREF="auarf112.htm#HDRBOS_REMOVEUSER">bos removeuser</A>
-<LI><A NAME="ToC_127" HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<LI><A NAME="ToC_128" HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<LI><A NAME="ToC_129" HREF="auarf115.htm#HDRBOS_SETAUTH">bos setauth</A>
-<LI><A NAME="ToC_130" HREF="auarf116.htm#HDRBOS_SETCELLNAME">bos setcellname</A>
-<LI><A NAME="ToC_131" HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<LI><A NAME="ToC_132" HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<LI><A NAME="ToC_133" HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<LI><A NAME="ToC_134" HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<LI><A NAME="ToC_135" HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<LI><A NAME="ToC_136" HREF="auarf122.htm#HDRBOS_STOP">bos stop</A>
-<LI><A NAME="ToC_137" HREF="auarf123.htm#HDRBOS_UNINSTALL">bos uninstall</A>
-<LI><A NAME="ToC_138" HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<LI><A NAME="ToC_139" HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<LI><A NAME="ToC_140" HREF="auarf126.htm#HDRBUTC">butc</A>
-<LI><A NAME="ToC_141" HREF="auarf127.htm#HDRDLOG">dlog</A>
-<LI><A NAME="ToC_142" HREF="auarf128.htm#HDRDPASS">dpass</A>
-<LI><A NAME="ToC_143" HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<LI><A NAME="ToC_144" HREF="auarf130.htm#HDRFMS">fms</A>
-<LI><A NAME="ToC_145" HREF="auarf131.htm#HDRFS_INTRO">fs</A>
-<LI><A NAME="ToC_146" HREF="auarf132.htm#HDRFS_APROPOS">fs apropos</A>
-<LI><A NAME="ToC_147" HREF="auarf133.htm#HDRFS_CHECKSERVERS">fs checkservers</A>
-<LI><A NAME="ToC_148" HREF="auarf134.htm#HDRFS_CHECKVOLUMES">fs checkvolumes</A>
-<LI><A NAME="ToC_149" HREF="auarf135.htm#HDRFS_CLEANACL">fs cleanacl</A>
-<LI><A NAME="ToC_150" HREF="auarf136.htm#HDRFS_COPYACL">fs copyacl</A>
-<LI><A NAME="ToC_151" HREF="auarf137.htm#HDRFS_DISKFREE">fs diskfree</A>
-<LI><A NAME="ToC_152" HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<LI><A NAME="ToC_153" HREF="auarf139.htm#HDRFS_EXPORTAFS">fs exportafs</A>
-<LI><A NAME="ToC_154" HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<LI><A NAME="ToC_155" HREF="auarf141.htm#HDRFS_FLUSHMOUNT">fs flushmount</A>
-<LI><A NAME="ToC_156" HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<LI><A NAME="ToC_157" HREF="auarf143.htm#HDRFS_GETCACHEPARMS">fs getcacheparms</A>
-<LI><A NAME="ToC_158" HREF="auarf144.htm#HDRFS_GETCELLSTATUS">fs getcellstatus</A>
-<LI><A NAME="ToC_159" HREF="auarf145.htm#HDRFS_GETCLIENTADDRS">fs getclientaddrs</A>
-<LI><A NAME="ToC_160" HREF="auarf146.htm#HDRFS_GETSERVERPREFS">fs getserverprefs</A>
-<LI><A NAME="ToC_161" HREF="auarf147.htm#HDRFS_HELP">fs help</A>
-<LI><A NAME="ToC_162" HREF="auarf148.htm#HDRFS_LISTACL">fs listacl</A>
-<LI><A NAME="ToC_163" HREF="auarf149.htm#HDRFS_LISTCELLS">fs listcells</A>
-<LI><A NAME="ToC_164" HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<LI><A NAME="ToC_165" HREF="auarf151.htm#HDRFS_LSMOUNT">fs lsmount</A>
-<LI><A NAME="ToC_166" HREF="auarf152.htm#HDRFS_MESSAGES">fs messages</A>
-<LI><A NAME="ToC_167" HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<LI><A NAME="ToC_168" HREF="auarf154.htm#HDRFS_NEWCELL">fs newcell</A>
-<LI><A NAME="ToC_169" HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<LI><A NAME="ToC_170" HREF="auarf156.htm#HDRFS_RMMOUNT">fs rmmount</A>
-<LI><A NAME="ToC_171" HREF="auarf157.htm#HDRFS_SETACL">fs setacl</A>
-<LI><A NAME="ToC_172" HREF="auarf158.htm#HDRFS_SETCACHESIZE">fs setcachesize</A>
-<LI><A NAME="ToC_173" HREF="auarf159.htm#HDRFS_SETCELL">fs setcell</A>
-<LI><A NAME="ToC_174" HREF="auarf160.htm#HDRFS_SETCLIENTADDRS">fs setclientaddrs</A>
-<LI><A NAME="ToC_175" HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<LI><A NAME="ToC_176" HREF="auarf162.htm#HDRFS_SETSERVERPREFS">fs setserverprefs</A>
-<LI><A NAME="ToC_177" HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<LI><A NAME="ToC_178" HREF="auarf164.htm#HDRFS_STOREBEHIND">fs storebehind</A>
-<LI><A NAME="ToC_179" HREF="auarf165.htm#HDRFS_SYSNAME">fs sysname</A>
-<LI><A NAME="ToC_180" HREF="auarf166.htm#HDRFS_WHEREIS">fs whereis</A>
-<LI><A NAME="ToC_181" HREF="auarf167.htm#HDRFS_WHICHCELL">fs whichcell</A>
-<LI><A NAME="ToC_182" HREF="auarf168.htm#HDRFS_WSCELL">fs wscell</A>
-<LI><A NAME="ToC_183" HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<LI><A NAME="ToC_184" HREF="auarf170.htm#HDRFSTRACE_APROPOS">fstrace apropos</A>
-<LI><A NAME="ToC_185" HREF="auarf171.htm#HDRFSTRACE_CLEAR">fstrace clear</A>
-<LI><A NAME="ToC_186" HREF="auarf172.htm#HDRFSTRACE_DUMP">fstrace dump</A>
-<LI><A NAME="ToC_187" HREF="auarf173.htm#HDRFSTRACE_HELP">fstrace help</A>
-<LI><A NAME="ToC_188" HREF="auarf174.htm#HDRFSTRACE_LSLOG">fstrace lslog</A>
-<LI><A NAME="ToC_189" HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<LI><A NAME="ToC_190" HREF="auarf176.htm#HDRFSTRACE_SETLOG">fstrace setlog</A>
-<LI><A NAME="ToC_191" HREF="auarf177.htm#HDRFSTRACE_SETSET">fstrace setset</A>
-<LI><A NAME="ToC_192" HREF="auarf178.htm#HDRFTPD">ftpd (AFS version)</A>
-<LI><A NAME="ToC_193" HREF="auarf179.htm#HDRINETD">inetd (AFS version)</A>
-<LI><A NAME="ToC_194" HREF="auarf180.htm#HDRKADB_CHECK">kadb_check</A>
-<LI><A NAME="ToC_195" HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<LI><A NAME="ToC_196" HREF="auarf182.htm#HDRKAS_APROPOS">kas apropos</A>
-<LI><A NAME="ToC_197" HREF="auarf183.htm#HDRKAS_CREATE">kas create</A>
-<LI><A NAME="ToC_198" HREF="auarf184.htm#HDRKAS_DELETE">kas delete</A>
-<LI><A NAME="ToC_199" HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<LI><A NAME="ToC_200" HREF="auarf186.htm#HDRKAS_FORGETTICKET">kas forgetticket</A>
-<LI><A NAME="ToC_201" HREF="auarf187.htm#HDRKAS_HELP">kas help</A>
-<LI><A NAME="ToC_202" HREF="auarf188.htm#HDRKAS_INTERACTIVE">kas interactive</A>
-<LI><A NAME="ToC_203" HREF="auarf189.htm#HDRKAS_LIST">kas list</A>
-<LI><A NAME="ToC_204" HREF="auarf190.htm#HDRKAS_LISTTICKETS">kas listtickets</A>
-<LI><A NAME="ToC_205" HREF="auarf191.htm#HDRKAS_NOAUTH">kas noauthentication</A>
-<LI><A NAME="ToC_206" HREF="auarf192.htm#HDRKAS_QUIT">kas quit</A>
-<LI><A NAME="ToC_207" HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<LI><A NAME="ToC_208" HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<LI><A NAME="ToC_209" HREF="auarf195.htm#HDRKAS_STATISTICS">kas statistics</A>
-<LI><A NAME="ToC_210" HREF="auarf196.htm#HDRKAS_STRINGTOKEY">kas stringtokey</A>
-<LI><A NAME="ToC_211" HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<LI><A NAME="ToC_212" HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<LI><A NAME="ToC_213" HREF="auarf199.htm#HDRKDB">kdb</A>
-<LI><A NAME="ToC_214" HREF="auarf200.htm#HDRKLOG">klog</A>
-<LI><A NAME="ToC_215" HREF="auarf201.htm#HDRKNFS">knfs</A>
-<LI><A NAME="ToC_216" HREF="auarf202.htm#HDRKPASSWD">kpasswd</A>
-<LI><A NAME="ToC_217" HREF="auarf203.htm#HDRKPWVALID">kpwvalid</A>
-<LI><A NAME="ToC_218" HREF="auarf204.htm#HDRPACKAGE">package</A>
-<LI><A NAME="ToC_219" HREF="auarf205.htm#HDRPACKAGE_APROPOS">package apropos</A>
-<LI><A NAME="ToC_220" HREF="auarf206.htm#HDRPACKAGE_HELP">package help</A>
-<LI><A NAME="ToC_221" HREF="auarf207.htm#HDRPACKAGE_TEST">package_test</A>
-<LI><A NAME="ToC_222" HREF="auarf208.htm#HDRPAGSH">pagsh</A>
-<LI><A NAME="ToC_223" HREF="auarf209.htm#HDRPRDB_CHECK">prdb_check</A>
-<LI><A NAME="ToC_224" HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<LI><A NAME="ToC_225" HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<LI><A NAME="ToC_226" HREF="auarf212.htm#HDRPTS_APROPOS">pts apropos</A>
-<LI><A NAME="ToC_227" HREF="auarf213.htm#HDRPTS_CHOWN">pts chown</A>
-<LI><A NAME="ToC_228" HREF="auarf214.htm#HDRPTS_CREATEGROUP">pts creategroup</A>
-<LI><A NAME="ToC_229" HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<LI><A NAME="ToC_230" HREF="auarf216.htm#HDRPTS_DELETE">pts delete</A>
-<LI><A NAME="ToC_231" HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<LI><A NAME="ToC_232" HREF="auarf218.htm#HDRPTS_HELP">pts help</A>
-<LI><A NAME="ToC_233" HREF="auarf219.htm#HDRPTS_LISTENTRIES">pts listentries</A>
-<LI><A NAME="ToC_234" HREF="auarf220.htm#HDRPTS_LISTMAX">pts listmax</A>
-<LI><A NAME="ToC_235" HREF="auarf221.htm#HDRPTS_LISTOWNED">pts listowned</A>
-<LI><A NAME="ToC_236" HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<LI><A NAME="ToC_237" HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<LI><A NAME="ToC_238" HREF="auarf224.htm#HDRPTS_RENAME">pts rename</A>
-<LI><A NAME="ToC_239" HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<LI><A NAME="ToC_240" HREF="auarf226.htm#HDRPTS_SETMAX">pts setmax</A>
-<LI><A NAME="ToC_241" HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<LI><A NAME="ToC_242" HREF="auarf228.htm#HDRRCP">rcp (AFS version)</A>
-<LI><A NAME="ToC_243" HREF="auarf229.htm#HDRRSH">rsh (AFS version)</A>
-<LI><A NAME="ToC_244" HREF="auarf230.htm#HDRRUNNTP">runntp</A>
-<LI><A NAME="ToC_245" HREF="auarf231.htm#HDRRXDEBUG">rxdebug</A>
-<LI><A NAME="ToC_246" HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<LI><A NAME="ToC_247" HREF="auarf233.htm#HDRSCOUT">scout</A>
-<LI><A NAME="ToC_248" HREF="auarf234.htm#HDRSYS">sys</A>
-<LI><A NAME="ToC_249" HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<LI><A NAME="ToC_250" HREF="auarf236.htm#HDRTRANSLATE_ET">translate_et</A>
-<LI><A NAME="ToC_251" HREF="auarf237.htm#HDRUDEBUG">udebug</A>
-<LI><A NAME="ToC_252" HREF="auarf238.htm#HDRUNLOG">unlog</A>
-<LI><A NAME="ToC_253" HREF="auarf239.htm#HDRUP">up</A>
-<LI><A NAME="ToC_254" HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<LI><A NAME="ToC_255" HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<LI><A NAME="ToC_256" HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<LI><A NAME="ToC_257" HREF="auarf243.htm#HDRUSS_ADD">uss add</A>
-<LI><A NAME="ToC_258" HREF="auarf244.htm#HDRUSS_APROPOS">uss apropos</A>
-<LI><A NAME="ToC_259" HREF="auarf245.htm#HDRUSS_BULK">uss bulk</A>
-<LI><A NAME="ToC_260" HREF="auarf246.htm#HDRUSS_DELETE">uss delete</A>
-<LI><A NAME="ToC_261" HREF="auarf247.htm#HDRUSS_HELP">uss help</A>
-<LI><A NAME="ToC_262" HREF="auarf248.htm#HDRVLDB_CHECK">vldb_check</A>
-<LI><A NAME="ToC_263" HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<LI><A NAME="ToC_264" HREF="auarf250.htm#HDRVOLINFO">volinfo</A>
-<LI><A NAME="ToC_265" HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<LI><A NAME="ToC_266" HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<LI><A NAME="ToC_267" HREF="auarf253.htm#HDRVOS_ADDSITE">vos addsite</A>
-<LI><A NAME="ToC_268" HREF="auarf254.htm#HDRVOS_APROPOS">vos apropos</A>
-<LI><A NAME="ToC_269" HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<LI><A NAME="ToC_270" HREF="auarf256.htm#HDRVOS_BACKUPSYS">vos backupsys</A>
-<LI><A NAME="ToC_271" HREF="auarf257.htm#HDRVOS_CHANGEADDR">vos changeaddr</A>
-<LI><A NAME="ToC_272" HREF="auarf258.htm#HDRVOS_CREATE">vos create</A>
-<LI><A NAME="ToC_273" HREF="auarf259.htm#HDRVOS_DELENTRY">vos delentry</A>
-<LI><A NAME="ToC_274" HREF="auarf260.htm#HDRVOS_DUMP">vos dump</A>
-<LI><A NAME="ToC_275" HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<LI><A NAME="ToC_276" HREF="auarf262.htm#HDRVOS_HELP">vos help</A>
-<LI><A NAME="ToC_277" HREF="auarf263.htm#HDRVOS_LISTADDRS">vos listaddrs</A>
-<LI><A NAME="ToC_278" HREF="auarf264.htm#HDRVOS_LISTPART">vos listpart</A>
-<LI><A NAME="ToC_279" HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<LI><A NAME="ToC_280" HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<LI><A NAME="ToC_281" HREF="auarf267.htm#HDRVOS_LOCK">vos lock</A>
-<LI><A NAME="ToC_282" HREF="auarf268.htm#HDRVOS_MOVE">vos move</A>
-<LI><A NAME="ToC_283" HREF="auarf269.htm#HDRVOS_PARTINFO">vos partinfo</A>
-<LI><A NAME="ToC_284" HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<LI><A NAME="ToC_285" HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<LI><A NAME="ToC_286" HREF="auarf272.htm#HDRVOS_REMSITE">vos remsite</A>
-<LI><A NAME="ToC_287" HREF="auarf273.htm#HDRVOS_RENAME">vos rename</A>
-<LI><A NAME="ToC_288" HREF="auarf274.htm#HDRVOS_RESTORE">vos restore</A>
-<LI><A NAME="ToC_289" HREF="auarf275.htm#HDRVOS_STATUS">vos status</A>
-<LI><A NAME="ToC_290" HREF="auarf276.htm#HDRVOS_SYNCSERV">vos syncserv</A>
-<LI><A NAME="ToC_291" HREF="auarf277.htm#HDRVOS_SYNCVLDB">vos syncvldb</A>
-<LI><A NAME="ToC_292" HREF="auarf278.htm#HDRVOS_UNLOCK">vos unlock</A>
-<LI><A NAME="ToC_293" HREF="auarf279.htm#HDRVOS_UNLOCKVLDB">vos unlockvldb</A>
-<LI><A NAME="ToC_294" HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<LI><A NAME="ToC_295" HREF="auarf281.htm#HDRXFS_SIZE_CHECK">xfs_size_check</A>
-<LI><A NAME="ToC_296" HREF="auarf282.htm#HDRXSTAT_CM_TEST">xstat_cm_test</A>
-<LI><A NAME="ToC_297" HREF="auarf283.htm#HDRXSTAT_FS_TEST">xstat_fs_test</A>
-</MENU>
-<P><B><A NAME="ToC_298" HREF="auarf284.htm#HDRINDEX">Index</A></B><BR>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf000.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf003.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf002.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf004.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<HR><H1><A NAME="HDRTLIST_START" HREF="auarf002.htm#ToC_1">Tables</A></H1>
-<OL>
-<LI><A NAME="FT_TBLFILESERVER-ARGS" HREF="auarf129.htm#TBLFILESERVER-ARGS" >File Server configuration parameters</A></LI>
-</OL>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf002.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf004.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf003.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf005.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<HR><H1><A NAME="Header_2" HREF="auarf002.htm#ToC_2">About This Manual</A></H1>
-<P>This chapter describes the purpose, organization, and conventions of this
-document.
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf003.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf005.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf004.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf006.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H2><A NAME="HDRWQ1" HREF="auarf002.htm#ToC_3">Audience and Purpose</A></H2>
-<P>This reference manual details the syntax of each
-AFS<SUP><SUP>(R)</SUP></SUP> command and is intended for the experienced AFS
-administrator, programmer, or user.
-<P>In general, this document does not explain when to use a command or its
-place in the sequence of commands that make up a complete procedure.
-For that type of information, refer to the <I>IBM AFS Administration
-Guide</I>.
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf004.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf006.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf005.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf007.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H2><A NAME="HDRWQ2" HREF="auarf002.htm#ToC_4">Organization</A></H2>
-<P>This document presents AFS files and commands in separate
-sections, with the files or commands in alphabetical order.
-<P>The following sections of each reference page provide the indicated type of
-information:
-<UL>
-<P><LI><B>Purpose</B> briefly describes the command's function.
-<P><LI><B>Synopsis</B> displays the complete syntax statement for a command,
-which specifies the required order for all options, using the same notation as
-the AFS online help. If abbreviating the command name and option names
-is acceptable, as it is for most commands, a second statement specifies the
-shortest acceptable abbreviation of each name. If the command has an
-alias, it also appears in this section.
-<P><LI><B>Description</B> describes the file or command's function in
-detail.
-<P><LI><B>Cautions</B> describes restrictions, requirements, and potential
-complications in use of the command. It appears only when
-necessary.
-<P><LI><B>Options</B> describes the function and required form of each
-argument and flag.
-<P><LI><B>Output</B> describes any output the command writes to the standard
-output stream. This section does not appear if the command does not
-produce output or if the only output is a message confirming the
-command's success.
-<P><LI><B>Examples</B> provides one or more sample commands and resulting
-output.
-<P><LI><B>Privilege Required</B> lists each privilege required to perform the
-command.
-<P><LI><B>Related Information</B> lists related commands and files, if
-any.
-</UL>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf005.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf007.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf006.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf008.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H2><A NAME="HDRWQ3" HREF="auarf002.htm#ToC_5">How to Use This Document</A></H2>
-<P>Refer to this document when you need detailed information
-about a specific command. For a description of all the steps in a
-procedure, refer to the <I>IBM AFS Administration Guide</I>.
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf006.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf008.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf007.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf009.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H2><A NAME="HDRWQ4" HREF="auarf002.htm#ToC_6">Related Documents</A></H2>
-<P>The following documents are included in the AFS documentation
-set.
-<P><I>IBM AFS Administration Guide</I>
-<P>This guide describes the concepts and procedures that a system
-administrator must know to manage an AFS cell. It assumes familiarity
-with UNIX, but requires no previous knowledge of AFS.
-<P>The first chapters of the <I>IBM AFS Administration Guide</I> present
-basic concepts and guidelines. Understanding them is crucial to
-successful administration of an AFS cell. The remaining chapters in the
-guide provide step-by-step instructions for specific administrative tasks,
-along with discussions of the concepts important to that particular
-task.
-<P><I>IBM AFS Quick Beginnings</I>
-<P>This guide provides instructions for installing AFS server and client
-machines. It is assumed that the installer is an experienced UNIX<SUP>
-<SUP>(R)</SUP></SUP> system administrator.
-<P>For predictable performance, machines must be installed and configured in
-accordance with the instructions in this guide.
-<P><I>IBM AFS Release Notes</I>
-<P>This document provides information specific to each release of AFS, such as
-a list of new features and commands, a list of requirements and limitations,
-and instructions for upgrading server and client machines.
-<P><I>IBM AFS User Guide</I>
-<P>This guide presents the basic concepts and procedures necessary for using
-AFS effectively. It assumes that the reader has some experience with
-UNIX, but does not require familiarity with networking or AFS.
-<P>The guide explains how to perform basic functions, including
-authenticating, changing a password, protecting AFS data, creating groups, and
-troubleshooting. It provides illustrative examples for each function
-and describes some of the differences between the UNIX file system and
-AFS.
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf007.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf009.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf008.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf010.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H2><A NAME="HDRTYPO_CONV" HREF="auarf002.htm#ToC_7">Typographical Conventions</A></H2>
-<P>This document uses the following typographical
-conventions:
-<UL>
-<P><LI>Command and option names appear in <B>bold type</B> in syntax
-definitions, examples, and running text. Names of directories, files,
-machines, partitions, volumes, and users also appear in <B>bold
-type</B>.
-<P><LI>Variable information appears in <I>italic type</I>. This
-includes user-supplied information on command lines and the parts of prompts
-that differ depending on who issues the command. New terms also appear
-in <I>italic type</I>.
-<P><LI>Examples of screen output and file contents appear in <TT>monospace
-type</TT>.
-</UL>
-<P>In addition, the following symbols appear in command syntax definitions,
-both in the documentation and in AFS online help statements. When
-issuing a command, do not type these symbols.
-<UL>
-<P><LI>Square brackets <B>[ ]</B> surround optional items.
-<P><LI>Angle brackets <B>< ></B> surround user-supplied values in AFS
-commands.
-<P><LI>A superscripted plus sign <B>+</B> follows an argument that accepts
-more than one value.
-<P><LI>The percent sign <TT>%</TT> represents the regular command shell
-prompt. Some operating systems possibly use a different character for
-this prompt.
-<P><LI>The number sign <TT>#</TT> represents the command shell prompt for the
-local superuser <B>root</B>. Some operating systems possibly use a
-different character for this prompt.
-<P><LI>The pipe symbol <B> |</B> in a command syntax statement separates
-mutually exclusive values for an argument.
-</UL>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf008.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf010.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf009.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf011.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H1><A NAME="Header_8" HREF="auarf002.htm#ToC_8">AFS System Files</A></H1>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf009.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf011.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf010.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf012.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFILESINTRO" HREF="auarf002.htm#ToC_9">afs_file_intro</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to AFS files
-<P><STRONG>Description</STRONG>
-<P>A number of files must reside on the local disk of AFS server and client
-machines. They belong to the following general categories:
-<UL>
-<P><LI><I>Configuration files</I> define configuration parameters for
-specific server and kernel processes such as the Backup System Tape
-Coordinator or the Cache Manager
-<P><LI><I>Administrative files</I> list information used in administration of
-server machines, such as a list of privileged users or server encryption keys
-<P><LI><I>Cache-related files</I> contain cached data or information about
-cached data, on client machines
-<P><LI><I>Log files</I> contain tracing messages about the operation of a
-specific process
-<P><LI><I>Database files</I> contain database records used to administer the
-AFS cell
-<P><LI><I>Controller files</I> control the behavior of a process
-<P><LI><I>Volume header files</I> represent AFS volumes on server partitions
-</UL>
-<P>For a description of the format and contents of each file, see its
-reference page.
-<P><B>Note for Windows users:</B> Some files described in this
-document possibly do not exist on machines that run a Windows operating
-system. Also, Windows uses a backslash
-( <B>\</B> ) rather than a forward slash
-( <B>/</B> ) to separate the elements in a
-pathname.
-<P><STRONG>Related Information</STRONG>
-<P><B>Configuration files:</B>
-<A NAME="IDX3862"></A>
-<DL>
-<DD><P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<DD><P><A HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>
-<DD><P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<DD><P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<DD><P><A HREF="auarf024.htm#HDRCLI_NETINFO">NetInfo (client version)</A>
-<DD><P><A HREF="auarf025.htm#HDRSV_NETINFO">NetInfo (server version)</A>
-<DD><P><A HREF="auarf026.htm#HDRCLI_NETRESTRICT">NetRestrict (client version)</A>
-<DD><P><A HREF="auarf027.htm#HDRSV_NETRESTRICT">NetRestrict (server version)</A>
-<DD><P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<DD><P><A HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<DD><P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<DD><P><A HREF="auarf049.htm#HDRSYSID">sysid</A>
-<DD><P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<DD><P><A HREF="auarf053.htm#HDRPACKAGECONFIG">package Configuration File</A>
-<DD><P><A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-<DD><P><A HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>
-</DL>
-<P><B>Administrative files:</B>
-<A NAME="IDX3863"></A>
-<DL>
-<DD><P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<DD><P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-</DL>
-<P><B>Cache-related files:</B>
-<A NAME="IDX3864"></A>
-<DL>
-<DD><P><A HREF="auarf017.htm#HDRCACHEITEMS">CacheItems</A>
-<DD><P><A HREF="auarf036.htm#HDRVN">V<I>n</I></A>
-<DD><P><A HREF="auarf040.htm#HDRVOLUMEITEMS">VolumeItems</A>
-</DL>
-<P><B>Log files:</B>
-<A NAME="IDX3865"></A>
-<DL>
-<DD><P><A HREF="auarf012.htm#HDRAUTHLOG">AuthLog</A>
-<DD><P><A HREF="auarf014.htm#HDRBACKUPLOG">BackupLog</A>
-<DD><P><A HREF="auarf015.htm#HDRBOSLOG">BosLog</A>
-<DD><P><A HREF="auarf021.htm#HDRFILELOG">FileLog</A>
-<DD><P><A HREF="auarf030.htm#HDRSALVAGELOG">SalvageLog</A>
-<DD><P><A HREF="auarf031.htm#HDRTE">TE_<I>device_name</I></A>
-<DD><P><A HREF="auarf034.htm#HDRTL">TL_<I>device_name</I></A>
-<DD><P><A HREF="auarf038.htm#HDRVLLOG">VLLog</A>
-<DD><P><A HREF="auarf039.htm#HDRVOLSERLOG">VolserLog</A>
-<DD><P><A HREF="auarf044.htm#HDRFMSLOG">fms.log</A>
-</DL>
-<P><B>Database files:</B>
-<A NAME="IDX3866"></A>
-<DL>
-<DD><P><A HREF="auarf042.htm#HDRBDBDB">bdb.DB0 and bdb.DBSYS1</A>
-<DD><P><A HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<DD><P><A HREF="auarf046.htm#HDRKASERVERAUXDB">kaserverauxdb</A>
-<DD><P><A HREF="auarf047.htm#HDRPRDBDB">prdb.DB0 and prdb.DBSYS1</A>
-<DD><P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-</DL>
-<A NAME="IDX3867"></A>
-<P><B>Controller files:</B>
-<DL>
-<DD><P><A HREF="auarf022.htm#HDRFORCESALVAGE">FORCESALVAGE</A>
-<DD><P><A HREF="auarf028.htm#HDRNOAUTH">NoAuth</A>
-<DD><P><A HREF="auarf029.htm#HDRSALVAGEFS">SALVAGE.fs</A>
-<DD><P><A HREF="auarf048.htm#HDRSALVAGELOCK">salvage.lock</A>
-</DL>
-<P><B>Volume header files:</B>
-<DL>
-<DD><P><A HREF="auarf037.htm#HDRVVOLID">V<I>vol_ID</I>.vol</A>
-</DL>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf010.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf012.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf011.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf013.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAUTHLOG" HREF="auarf002.htm#ToC_10">AuthLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3868"></A>
-<A NAME="IDX3869"></A>
-<A NAME="IDX3870"></A>
-<P>Traces Authentication Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>AuthLog</B> file records a trace of Authentication Server
-(<B>kaserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>AuthLog</B> file does not exist in the
-<B>/usr/afs/logs</B> directory when the Authentication Server starts, the
-server process creates it and writes initial start-up messages to it.
-If there is an existing file, the Authentication Server renames it to
-<B>AuthLog.old</B>, overwriting the existing
-<B>AuthLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the server
-machine and use a text editor or a file display command such as the UNIX
-<B>cat</B> command. By default, the mode bits on the
-<B>AuthLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The Authentication Server records operations only as it completes them, and
-cannot recover from failures by reviewing the file. The log contents
-are useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf011.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf013.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf012.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf014.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRWQ5" HREF="auarf002.htm#ToC_11">AuthLog.dir, AuthLog.pag</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3871"></A>
-<A NAME="IDX3872"></A>
-<A NAME="IDX3873"></A>
-<P>Records privileged operations performed by the Authentication Server
-<P><STRONG>Description</STRONG>
-<P>The <B>AuthLog.dir</B> and <B>AuthLog.pag</B> files
-record a trace of privileged operations performed by the Authentication Server
-(<B>kaserver</B> process) on the local machine. If the files do not
-exist when the Authentication Server starts, it creates them in the
-<B>/usr/afs/logs</B> directory as necessary.
-<P>The files are in binary format. To display their contents, use the
-<B>kdb</B> command, which requires being logged in to the local machine as
-the local superuser <B>root</B>.
-<P><STRONG>Cautions</STRONG>
-<P>The Authentication Server is possibly unable to create these files on some
-operating systems that AFS otherwise supports, making the <B>kdb</B>
-command inoperative. See the <I>IBM AFS Release Notes</I> for
-details.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf199.htm#HDRKDB">kdb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf012.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf014.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf013.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf015.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBACKUPLOG" HREF="auarf002.htm#ToC_12">BackupLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3874"></A>
-<A NAME="IDX3875"></A>
-<A NAME="IDX3876"></A>
-<P>Traces Backup Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>BackupLog</B> file records a trace of Backup Server
-(<B>buserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>BackupLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the Backup Server starts, the server
-process creates it and writes initial start-up messages to it. If there
-is an existing file, the Backup Server renames it to
-<B>BackupLog.old</B>, overwriting the existing
-<B>BackupLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log on to the machine
-and use a text editor or a file display command such as the UNIX
-<B>cat</B> command. By default, the mode bits on the
-<B>BackupLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The Backup Server records operations only as it completes them, and so
-cannot recover from failures by reviewing the file. The log contents
-are useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf013.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf015.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf014.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf016.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOSLOG" HREF="auarf002.htm#ToC_13">BosLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3877"></A>
-<A NAME="IDX3878"></A>
-<A NAME="IDX3879"></A>
-<P>Traces BOS Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>BosLog</B> file records a trace of Basic OverSeer (BOS) Server
-(<B>bosserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>BosLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the BOS Server starts, the server
-process creates it and writes initial start-up messages to it. If there
-is an existing file, the BOS server renames it to
-<B>BosLog.old</B>, overwriting the existing
-<B>BosLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the server
-machine and use a text editor or a file display command such as the UNIX
-<B>cat</B> command. By default, the mode bits on the
-<B>BosLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The BOS Server records operations only as it completes them, and cannot
-recover from failures by reviewing the file. The log contents are
-useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf014.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf016.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf015.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf017.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOSCONFIG" HREF="auarf002.htm#ToC_14">BosConfig</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3880"></A>
-<A NAME="IDX3881"></A>
-<A NAME="IDX3882"></A>
-<A NAME="IDX3883"></A>
-<P>Defines server processes for the BOS Server to monitor
-<P><STRONG>Description</STRONG>
-<P>The <B>BosConfig</B> file lists the processes that the Basic OverSeer
-(BOS) Server monitors on its server machine, and thus defines which AFS server
-processes run on the machine. It specifies how the BOS Server reacts
-when a process fails, and also defines the times at which the BOS Server
-automatically restarts processes as part of performance maintenance.
-The file must reside in the <B>/usr/afs/local</B> directory on each AFS
-server machine.
-<P>A server process entry in the <B>BosConfig</B> file records the
-following information:
-<UL>
-<P><LI>The<VAR> entry type</VAR>, which is one of the following:
-<A NAME="IDX3884"></A>
-<A NAME="IDX3885"></A>
-<DL>
-<P><DT><B>cron
-<A NAME="IDX3886"></A>
-</B><DD>Designates a server process that runs periodically instead of
-continuously. The BOS Server starts a cron process only at specified
-times, not whenever it fails. All standard AFS process entries except
-<B>fs</B> are simple (there are no standard cron processes).
-<P><DT><B>fs
-<A NAME="IDX3887"></A>
-<A NAME="IDX3888"></A>
-<A NAME="IDX3889"></A>
-<A NAME="IDX3890"></A>
-</B><DD>Designates a group of interdependent server processes. If one of
-the processes fails, the BOS Server must coordinate its restart with the
-restart of the other processes in the group, possibly by stopping them
-first.
-<P>There is only one standard entry of this type, for which the conventional
-name is <B>fs</B>. It combines three server processes: the
-File Server (<B>fileserver</B> process), the Volume Server
-(<B>volserver</B> process), and the Salvager (<B>salvager</B>
-process). These processes all operate on the same data--the AFS
-data stored on an AFS server machine's <B>/vicep</B> partitions and
-mounted in the AFS filespace--but in different ways. Grouping the
-processes prevents them from attempting to access the same data
-simultaneously, which can cause corruption.
-<P>During normal operation, the Salvager process is not active. If the
-File Server process fails, however, the BOS Server stops the Volume Server
-process and runs the Salvager process to correct any corruption that resulted
-from the failure. (The administrator can also issue the <B>bos
-salvage</B> command to invoke the Salvager process.) If the Volume
-Server fails, the BOS Server can restart it without stopping the File Server
-or running the Salvager.
-<P><DT><B>simple
-<A NAME="IDX3891"></A>
-</B><DD>Designates a server process that runs independently of any other on the
-server machine. If a simple process fails, the BOS Server does not have
-to coordinate its restart with any other process.
-</DL>
-<P><LI>The <VAR>entry name</VAR>. The conventional name for an entry in the
-<B>BosConfig</B> file and the associated process matches the binary
-filename. When issuing any <B>bos</B> command that takes the
-<B>-instance</B> argument, identify each process by the name used in the
-<B>BosConfig</B> file. For a list of the names, see the <B>bos
-create</B> reference page.
-<P><LI>The process's <VAR>status flag</VAR>, which determines whether the BOS
-Server attempts to start the process in two cases: each time the BOS
-Server itself restarts, and when the process fails. The
-<B>BosConfig</B> file currently uses a binary notation to indicate whether
-the BOS Server attempts to restart the process as necessary or does not
-monitor it at all. For the sake of clarity, the AFS documentation
-refers to the flags as <B>Run</B> and <B>NotRun</B> instead.
-Only a system administrator, not the BOS Server, can change the flag.
-<A NAME="IDX3892"></A>
-<A NAME="IDX3893"></A>
-<P><LI>One or more <VAR>command parameters</VAR> which the BOS Server invokes to
-start the process or processes associated with the entry:
-<UL>
-<P><LI>A <B>cron</B> entry has two command parameters, the first the complete
-pathname to the program, and the second the time at which the BOS Server
-invokes the program.
-<P><LI>The <B>fs</B> entry has three command parameters, each the complete
-pathname to the <B>fileserver</B>, <B>volserver</B>, and
-<B>salvager</B> programs, in that order.
-<P><LI>A <B>simple</B> entry has only one command parameter, the complete
-pathname to the program.
-</UL>
-</UL>
-<P>In addition to server process entries, the <B>BosConfig</B> file
-specifies the times at which the BOS Server performs two types of automatic
-process restarts:
-<UL>
-<P><LI>The <VAR>general restart</VAR> time at which the BOS Server restarts itself
-and then each process for which the entry in the <B>BosConfig</B> file has
-status flag <B>Run</B>. The default setting is Sunday at 4:00
-a.m.
-<P><LI>The <VAR>binary restart</VAR> time at which the BOS Server restarts any
-server process for which the time stamp on the binary file in the
-<B>/usr/afs/bin</B> directory is later than the last restart time for the
-process. The default is 5:00 a.m.
-</UL>
-<P>Although the <B>BosConfig</B> file is in ASCII format, do not use a
-text editor to alter it. Its format is subject to change and
-incorrectly formatted entries can prevent server startup in ways that are
-difficult to diagnose. Instead always use the appropriate commands from
-the <B>bos</B> command suite:
-<UL>
-<P><LI>The <B>bos create</B> command to create an entry in the file and start
-the associated process
-<P><LI>The <B>bos delete</B> command to remove an entry from the file after
-the <B>bos stop</B> command is used to stop the associated process
-<P><LI>The <B>bos getrestart</B> command to display the times at which the
-BOS Server performs automatic restarts
-<P><LI>The <B>bos setrestart</B> command to set the times at which the BOS
-Server performs automatic process restarts
-<P><LI>The <B>bos start</B> command to change an entry's status flag to
-<B>Run</B> and start the associated process
-<P><LI>The <B>bos status</B> command to display all processes listed in the
-file
-<P><LI>The <B>bos stop</B> command to change an entry's status flag to
-<B>NotRun</B> and stop the associated process
-</UL>
-<P>There are also <B>bos</B> commands that start and stop processes
-without changing entries in the <B>BosConfig</B> file. The BOS
-Server reads the <B>BosConfig</B> file only when it starts, transferring
-the information into its memory. Thus a process's status as
-represented in the BOS Server's memory can diverge from its status in the
-<B>BosConfig</B> file. The following commands change a
-process's status in the BOS Server's memory only:
-<A NAME="IDX3894"></A>
-<A NAME="IDX3895"></A>
-<A NAME="IDX3896"></A>
-<UL>
-<P><LI>The <B>bos restart</B> command restarts a specified set of processes,
-all processes, or all processes other than the BOS Server
-<P><LI>The <B>bos shutdown</B> command stops a process
-<P><LI>The <B>bos startup</B> command starts a process
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf099.htm#HDRBOS_DELETE">bos delete</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P><A HREF="auarf122.htm#HDRBOS_STOP">bos stop</A>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf015.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf017.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf016.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf018.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCACHEITEMS" HREF="auarf002.htm#ToC_15">CacheItems</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3897"></A>
-<A NAME="IDX3898"></A>
-<A NAME="IDX3899"></A>
-<P>Records information about each <B>V</B><VAR>n</VAR> file in a disk cache
-<P><STRONG>Description</STRONG>
-<P>The <B>CacheItems</B> file records information about each file in the
-disk cache on a client machine (each <B>V</B><VAR>n</VAR> file). The
-information includes the file ID number and associated volume version number
-of the AFS file currently stored in the <B>V</B><VAR>n</VAR> file, which
-enables the Cache Manager to determine which <B>V</B><VAR>n</VAR> file
-contains the AFS data it needs to present to an application.
-<P>As it initializes, the Cache Manager creates the binary-format
-<B>CacheItems</B> file in the same local disk cache directory as the
-<B>V</B><VAR>n</VAR> files that the <B>CacheItems</B> file describes,
-and it must always remain there. The conventional directory name is
-<B>/usr/vice/cache</B>, but it is acceptable to use a directory on a
-partition with more available space.
-<P><STRONG>Cautions</STRONG>
-<P>Editing or removing the <B>CacheItems</B> file can cause a kernel
-panic. If the contents of <B>V</B><VAR>n</VAR> files seem out of
-date, clear the files by using the <B>fs flush</B> or <B>fs
-flushvolume</B> command. If the <B>CacheItems</B> file is
-accidentally modified or deleted, rebooting the machine usually restores
-normal performance.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf036.htm#HDRVN">V<I>n</I></A>
-<P><A HREF="auarf040.htm#HDRVOLUMEITEMS">VolumeItems</A>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<P><A HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf016.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf018.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf017.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf019.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCFG" HREF="auarf002.htm#ToC_16">CFG_<I>device_name</I></A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3900"></A>
-<A NAME="IDX3901"></A>
-<A NAME="IDX3902"></A>
-<A NAME="IDX3903"></A>
-<A NAME="IDX3904"></A>
-<P>Defines Tape Coordinator configuration instructions for automated tape
-devices
-<P><STRONG>Description</STRONG>
-<P>The <B>CFG_</B><VAR>device_name</VAR> file includes instructions that
-configure a Tape Coordinator for use with automated backup devices such as
-tape stackers and jukeboxes, enable the Tape Coordinator to dump and restore
-data to a <I>backup data file</I> on a local disk device, and enable
-greater automation of other aspects of the backup process.
-<P>There is a separate configuration file for each tape device or backup data
-file. Creating the file is optional, and unnecessary if none of the
-instructions it can include pertain to a given tape device. The
-ASCII-format file must reside in the <B>/usr/afs/backup</B> directory on
-the Tape Coordinator machine if it exists.
-<P>The <B>CFG_</B><VAR>device_name</VAR> file does not replace the
-<B>/usr/afs/backup/tapeconfig</B> file, a single copy of which still must
-exist on every Tape Coordinator machine.
-<P>To enable the Tape Coordinator to locate the configuration file, construct
-the variable part of the filename, <VAR>device_name</VAR>, as follows:
-<UL>
-<P><LI>For a tape device, strip off the initial <B>/dev/</B> string from the
-device name, and replace any other slashes in the name with
-underscores. For example, <B>CFG_rmt_4m</B> is the appropriate
-filename for a device called <B>/dev/rmt/4m</B>.
-<P><LI>For a backup data file, strip off the initial slash (/) and replace any
-other slashes in the name with underscores. For example,
-<B>CFG_var_tmp_FILE</B> is the appropriate filename for a backup data file
-called <B>/var/tmp/FILE</B>.
-</UL>
-<P>The <B>CFG_</B><VAR>device_name</VAR> file lists one or more of the
-following instructions, each on its own line. All are optional, and
-they can appear in any order. A more detailed description of each
-instruction follows the list:
-<DL>
-<P><DT><B>ASK
-</B><DD>Controls whether the Tape Coordinator prompts for guidance when it
-encounters error conditions
-<P><DT><B>AUTOQUERY
-</B><DD>Controls whether the Tape Coordinator prompts for the first tape
-<P><DT><B>BUFFERSIZE
-</B><DD>Sets the size of the memory buffer the Tape Coordinator uses when
-transferring data
-<P><DT><B>FILE
-</B><DD>Controls whether the dump is written to a tape device or a file
-<P><DT><B>MOUNT
-</B><DD>Identifies the file that contains routines for inserting tapes into the
-device's drive
-<P><DT><B>NAME_CHECK
-</B><DD>Controls whether the Tape Coordinator verifies that a tape's AFS tape
-name matches the dump being written
-<P><DT><B>UNMOUNT
-</B><DD>Identifies the file that contains routines for removing tapes from the
-device's drive
-</DL>
-<A NAME="IDX3905"></A>
-<P><B>The ASK Instruction</B>
-<P>The <B>ASK</B> instruction takes a boolean value as its argument, in
-the following format:
-<PRE> ASK {<B>YES</B> | <B>NO</B>}
-
-</PRE>
-<P>When the value is <B>YES</B>, the Tape Coordinator generates a prompt
-in its window, requesting a response to the error cases described in the
-following list. This is the default behavior if the ASK instruction
-does not appear in the <B>CFG_</B><VAR>device_name</VAR> file.
-<P>When the value is <B>NO</B>, the Tape Coordinator does not prompt in
-error cases, but instead uses the automatic default responses described in the
-following list. The Tape Coordinator also logs the error in the
-<B>TE_</B><VAR>device_name</VAR> file. Suppressing the prompts
-enables the Tape Coordinator to run unattended, though it still prompts for
-insertion of tapes unless the <B>MOUNT</B> instruction is used.
-<P>The error cases controlled by this instruction are the following:
-<UL>
-<P><LI>The Backup System is unable to dump a volume while running the <B>backup
-dump</B> command. With a <B>YES</B> value, the Tape Coordinator
-prompts to offer three choices: try to dump the volume again
-immediately, omit the volume from the dump but continue the operation, or
-terminate the operation. With a <B>NO</B> value, the Tape
-Coordinator omits the volume from the dump and continues the operation.
-<P><LI>The Backup System is unable to restore a volume while running the
-<B>backup diskrestore</B>, <B>backup volrestore</B>, or <B>backup
-volsetrestore</B> command. With a <B>YES</B> value, the Tape
-Coordinator prompts to offer two choices: omit the volume and continue
-restoring the other volumes, or terminate the operation. With a
-<B>NO</B> value, it continues the operation without prompting, omitting
-the problematic volume but restoring the remaining ones.
-<P><LI>The Backup System cannot determine if the dump set includes any more
-tapes, while running the <B>backup scantape</B> command (the reference
-page for that command discusses possible reasons for this problem).
-With a <B>YES</B> value, the Tape Coordinator prompts to ask if there are
-more tapes to scan. With a <B>NO</B> value, it proceeds as though
-there are more tapes and invokes the routine named by the <B>MOUNT</B>
-instruction in the configuration file, or prompts the operator to insert the
-next tape.
-<P><LI>The Backup System determines that the tape contains an unexpired dump
-while running the <B>backup labeltape</B> command. With a
-<B>YES</B> value, the Tape Coordinator prompts to offer two choices:
-continue or terminate the labeling operation. With a <B>NO</B>
-value, it terminates the operation without relabeling the tape.
-</UL>
-<A NAME="IDX3906"></A>
-<P><B>The AUTOQUERY Instruction</B>
-<P>The <B>AUTOQUERY</B> instruction takes a boolean value as its argument,
-in the following format:
-<PRE> AUTOQUERY {<B>YES</B> | <B>NO</B>}
-
-</PRE>
-<P>When the value is <B>YES</B>, the Tape Coordinator checks for the
-<B>MOUNT</B> instruction in the configuration file when it needs to read
-the first tape involved in an operation. As described for that
-instruction, it then either prompts for the tape or invokes the specified
-routine to mount the tape. This is the default behavior if the
-<B>AUTOQUERY</B> instruction does not appear in the configuration
-file.
-<P>When the value is <B>NO</B>, the Tape Coordinator assumes that the
-first tape required for an operation is already in the drive. It does
-not prompt the operator or invoke the <B>MOUNT</B> routine unless there is
-an error in accessing the first tape. This setting is equivalent in
-effect to including the <B>-noautoquery</B> flag to the <B>butc</B>
-command.
-<P>Note that the setting of the <B>AUTOQUERY</B> instruction controls the
-Tape Coordinator's behavior only with respect to the first tape required
-for an operation. For subsequent tapes, the Tape Coordinator always
-checks for the <B>MOUNT</B> instruction. It also refers to the
-<B>MOUNT</B> instruction if it encounters an error while attempting to
-access the first tape.
-<A NAME="IDX3907"></A>
-<P><B>The BUFFERSIZE Instruction</B>
-<P>The <B>BUFFERSIZE</B> instruction takes an integer value, and
-optionally units, in the following format:
-<PRE> BUFFERSIZE <VAR>size</VAR>[{<B>k</B> | <B>K</B> | <B>m</B> | <B>M</B> | <B>g</B> | <B>G</B>}]
-
-</PRE>
-<P>where<VAR> size</VAR> specifies the amount of memory the Tape Coordinator
-allocates to use as a buffer during both dump and restore operations.
-The default unit is bytes, but use <B>k</B> or <B>K</B> to specify
-kilobytes, <B>m</B> or <B>M</B> for megabytes, and <B>g</B> or
-<B>G</B> for gigabytes. There is no space between the
-<VAR>size</VAR>value and the units letter.
-<P>By default, the Tape Coordinator uses a 16 KB buffer during dump
-operations. As it receives volume data from the Volume Server, the Tape
-Coordinator gathers 16 KB of data in the buffer before transferring the entire
-16 KB to the tape device or backup data file. Similarly, during a
-restore operation the Tape Coordinator by default buffers 32 KB of data from
-the tape device or backup data file before transferring the entire 32 KB to
-the Volume Server for restoration into the file system. Buffering makes
-the volume of data flowing to and from a tape device more even and so promotes
-tape streaming, which is the most efficient way for a tape device to
-operate.
-<P>In a normal network configuration, the default buffer sizes are usually
-large enough to promote tape streaming. If the network between the Tape
-Coordinator machine and file server machines is slow, it can help to increase
-the buffer size.
-<A NAME="IDX3908"></A>
-<P><B>The FILE Instruction</B>
-<P>The <B>FILE</B> instruction takes a boolean value as its argument, in
-the following format:
-<PRE> FILE {<B>NO</B> | <B>YES</B>}
-
-</PRE>
-<P>When the value is <B>NO</B>, the Tape Coordinator writes to a tape
-device during a dump operation and reads from one during a restore
-operation. This is the default behavior if the <B>FILE</B>
-instruction does not appear in the configuration file.
-<P>When the value is <B>YES</B>, the Tape Coordinator writes volume data
-to a backup data file on the local disk during a dump operation and reads
-volume data from a file during a restore operation. If the file does
-not exist when the Tape Coordinator attempts to access it to write a dump, the
-Tape Coordinator creates it. For a restore operation to succeed, the
-file must exist and contain volume data previously written to it by a
-<B>backup dump</B> operation.
-<P>When the value is <B>YES</B>, the backup data file's complete
-pathname must appear (instead of a tape drive device name) in the third field
-of the corresponding port offset entry in the local
-<B>/usr/afs/backup/tapeconfig</B> file. If the field instead refers
-to a tape device, dump operations appear to succeed but are
-inoperative. It is not possible to restore data that was accidently
-dumped to a tape device while the <B>FILE</B> instruction was set to
-<B>YES</B>. (In the same way, if the <B>FILE</B> instruction is
-set to <B>NO</B>, the <B>tapeconfig</B> entry must refer to an actual
-tape device.)
-<P>Rather than put an actual file pathname in the third field of the
-<B>tapeconfig</B> file, however, the recommended configuration is to
-create a symbolic link in the <B>/dev</B> directory that points to the
-actual file pathname, and record the symbolic link in this field. This
-configuration has a couple of advantages:
-<UL>
-<P><LI>It makes the <VAR>device_name</VAR> portion of the
-<B>CFG_</B><VAR>device_name</VAR>, <B>TE_</B><VAR>device_name</VAR>, and
-<B>TL_</B><VAR>device_name</VAR> names as short as possible. Because
-the symbolic link is in the <B>/dev</B> directory as though it were a tape
-device, the device configuration file's name is constructed by stripping
-off the entire <B>/dev/</B> prefix, instead of just the initial
-slash. If, for example, the symbolic link is called
-<B>/dev/FILE</B>, the device configuration file name is
-<B>CFG_FILE</B>, whereas if the actual pathname <B>/var/tmp/FILE</B>
-appears in the <B>tapeconfig</B> file, the file's name must be
-<B>CFG_var_tmp_FILE</B>.
-<P><LI>It provides for a more graceful, and potentially automated, recovery if
-the Tape Coordinator cannot write a complete dump into the backup data file
-(because the partition housing the backup data file becomes full, for
-example). The Tape Coordinator's reaction to this problem is to
-invoke the <B>MOUNT</B> script, or to prompt the operator if the
-<B>MOUNT</B> instruction does not appear in the configuration file.
-<UL>
-<P><LI>If there is a <B>MOUNT</B> routine, the operator can prepare for this
-situation by adding a subroutine that changes the symbolic link to point to
-another backup data file on a partition where there is space available.
-<P><LI>If there is no <B>MOUNT</B> instruction, the prompt enables the
-operator manually to change the symbolic link to point to another backup data
-file, then press <<B>Return</B>> to signal that the Tape Coordinator
-can continue the operation.
-</UL>
-</UL>
-<P>If the third field in the <B>tapeconfig</B> file names the actual file,
-there is no way to recover from exhausting the space on the partition that
-houses the backup data file. It is not possible to change the
-<B>tapeconfig</B> file in the middle of an operation.
-<P>When writing to a backup data file, the Tape Coordinator writes data at 16
-KB offsets. If a given block of data (such as the marker that signals
-the beginning or end of a volume) does not fill the entire 16 KB, the Tape
-Coordinator still skips to the next offset before writing the next
-block. In the output of a <B>backup dumpinfo</B> command issued
-with the <B>-id</B> option, the value in the <TT>Pos</TT> column is the
-ordinal of the 16-KB offset at which the volume data begins, and so is not
-generally only one higher than the position number on the previous line, as it
-is for dumps to tape.
-<A NAME="IDX3909"></A>
-<P><B>The MOUNT Instruction</B>
-<P>The <B>MOUNT</B> instruction takes a pathname as its argument, in the
-following format:
-<PRE>
- MOUNT <VAR>filename</VAR>
-
-</PRE>
-<P>The referenced executable file must reside on the local disk and contain a
-shell script or program that directs an automated tape device, such as a
-jukebox or stacker, to mount a tape (insert it into the tape reader).
-The operator must write the routine to invoke the mount command specified by
-the device's manufacturer; AFS does not include any scripts,
-although an example appears in the following <B>Examples</B>
-section. The script or program inherits the Tape Coordinator's AFS
-authentication status.
-<P>When the Tape Coordinator needs to mount a tape, it checks the
-configuration file for a <B>MOUNT</B> instruction. If there is no
-<B>MOUNT</B> instruction, the Tape Coordinator prompts the operator to
-insert a tape before it attempts to open the tape device. If there is a
-<B>MOUNT</B> instruction, the Tape Coordinator executes the routine in the
-referenced file. The routine invoked by the <B>MOUNT</B>
-instruction inherits the local identity (UNIX UID) and AFS tokens of the
-<B>butc</B> command's issuer.
-<P>There is an exception to this sequence: if the <B>AUTOQUERY
-NO</B> instruction appears in the configuration file, or the
-<B>-noautoquery</B> flag was included on the <B>butc</B> command, then
-the Tape Coordinator assumes that the operator has already inserted the first
-tape needed for a given operation. It attempts to read the tape
-immediately, and only checks for the <B>MOUNT</B> instruction or prompts
-the operator if the tape is missing or is not the required one.
-<P>When the Tape Coordinator invokes the routine indicated by the
-<B>MOUNT</B> instruction, it passes the following parameters to the
-routine in the indicated order:
-<OL TYPE=1>
-<P><LI>The tape device or backup data file's pathname, as recorded in the
-<B>/usr/afs/backup/tapeconfig</B> file.
-<P><LI>The tape operation, which (except for the exceptions noted in the
-following list) matches the <B>backup</B> command operation code used to
-initiate the operation:
-<UL>
-<P><LI><B>appenddump</B> (when a <B>backup dump</B> command includes the
-<B>-append</B> flag)
-<P><LI><B>dump</B> (when a <B>backup dump</B> command does not include
-the <B>-append</B> flag)
-<P><LI><B>labeltape</B>
-<P><LI><B>readlabel</B>
-<P><LI><B>restore</B> (for a <B>backup diskrestore</B>, <B>backup
-volrestore</B>, or <B>backup volsetrestore</B> command)
-<P><LI><B>restoredb</B>
-<P><LI><B>savedb</B>
-<P><LI><B>scantape</B>
-</UL>
-<P><LI>The number of times the Tape Coordinator has attempted to open the tape
-device or backup data file. If the open attempt returns an error, the
-Tape Coordinator increments this value by one and again invokes the
-<B>MOUNT</B> instruction.
-<P><LI>The tape name. For some operations, the Tape Coordinator passes the
-string <TT>none</TT>, because it does not know the tape name (when running
-the <B>backup scantape</B> or <B>backup readlabel</B>, for example),
-or because the tape does not necessarily have a name (when running the
-<B>backup labeltape</B> command, for example).
-<P><LI>The tape ID recorded in the Backup Database. As with the tape name,
-the Backup System passes the string <TT>none</TT> for operations where it
-does not know the tape ID or the tape does not necessarily have an ID.
-</OL>
-<P>The routine invoked by the <B>MOUNT</B> instruction must return an exit
-code to the Tape Coordinator:
-<UL>
-<P><LI>Code <B>0</B> (zero) indicates that the routine successfully mounted
-the tape. The Tape Coordinator continues the backup operation.
-If the routine invoked by the <B>MOUNT</B> instruction does not return
-this exit code, the Tape Coordinator never calls the <B>UNMOUNT</B>
-instruction.
-<P><LI>Code <B>1</B> (one) indicates that the routine failed to mount the
-tape. The Tape Coordinator terminates the operation.
-<P><LI>Any other code indicates that the routine was not able to access the
-correct tape. The Tape Coordinator prompts the operator to insert the
-correct tape.
-</UL>
-<P>If the <B>backup</B> command was issued in interactive mode and the
-operator issues the <B>(backup) kill</B> command while the
-<B>MOUNT</B> routine is running, the Tape Coordinator passes the
-termination signal to the routine; the entire operation
-terminates.
-<A NAME="IDX3910"></A>
-<P><B>The NAME_CHECK Instruction</B>
-<P>The <B>NAME_CHECK</B> instruction takes a boolean value as its
-argument, in the following format:
-<PRE> NAME_CHECK {<B>YES</B> | <B>NO</B>}
-
-</PRE>
-<P>When the value is <B>YES</B> and the tape does not have a permanent
-name, the Tape Coordinator checks the AFS tape name when dumping a volume in
-response to the <B>backup dump</B> command. The AFS tape name must
-be <TT><NULL></TT> or match the tape name that the <B>backup dump</B>
-operation assigns based on the volume set and dump level names. This is
-the default behavior if the <B>NAME_CHECK</B> instruction does not appear
-in the configuration file.
-<P>When the value is <B>NO</B>, the Tape Coordinator does not check the
-AFS tape name before writing to the tape.
-<P>The Tape Coordinator always checks that all dumps on the tape are expired,
-and refuses to write to a tape that contains unexpired dumps.
-<A NAME="IDX3911"></A>
-<P><B>The UNMOUNT Instruction</B>
-<P>The <B>UNMOUNT</B> instruction takes a pathname as its argument, in the
-following format:
-<PRE> UNMOUNT <VAR>filename</VAR>
-
-</PRE>
-<P>The referenced executable file must reside on the local disk and contain a
-shell script or program that directs an automated tape device, such as a
-jukebox or stacker, to unmount a tape (remove it from the tape reader).
-The operator must write the routine to invoke the unmount command specified by
-the device's manufacturer; AFS does not include any scripts,
-although an example appears in the following <B>Examples</B>
-section. The script or program inherits the Tape Coordinator's AFS
-authentication status.
-<P>After closing a tape device, the Tape Coordinator checks the configuration
-file for an <B>UNMOUNT</B> instruction, whether or not the
-<B>close</B> operation succeeds. If there is no <B>UNMOUNT</B>
-instruction, the Tape Coordinator takes no action, in which case the operator
-must take the action necessary to remove the current tape from the drive
-before another can be inserted. If there is an <B>UNMOUNT</B>
-instruction, the Tape Coordinator executes the referenced file. It
-invokes the routine only once, passing in the following parameters:
-<UL>
-<P><LI>The tape device pathname (as specified in the
-<B>/usr/afs/backup/tapeconfig</B> file)
-<P><LI>The tape operation (always <B>unmount</B>)
-</UL>
-<P><STRONG>Privilege Required</STRONG>
-<P>The file is protected by UNIX mode bits. Creating the file requires
-the <B>w</B> (<B>write</B>) and <B>x</B> (<B>execute</B>)
-permissions on the <B>/usr/afs/backup</B> directory. Editing the
-file requires the <B>w</B> (<B>write</B>) permission on the
-file.
-<P><STRONG>Examples</STRONG>
-<P>The following example configuration files demonstrate one way to structure
-a configuration file for a stacker or backup dump file. The examples
-are not necessarily appropriate for a specific cell; if using them as
-models, be sure to adapt them to the cell's needs and equipment.
-<P><B>Example</B> <B>CFG_</B><VAR>device_name</VAR> <B>File for
-Stackers</B>
-<P>In this example, the administrator creates the following entry for a tape
-stacker called <B>stacker0.1</B> in the
-<B>/usr/afs/backup/tapeconfig</B> file. It has port offset
-0.
-<PRE> 2G 5K /dev/stacker0.1 0
-
-</PRE>
-<P>The administrator includes the following five lines in the
-<B>/usr/afs/backup/CFG_stacker0.1</B> file. To review the
-meaning of each instruction, see the preceding <B>Description</B>
-section.
-<PRE> MOUNT /usr/afs/backup/stacker0.1
- UNMOUNT /usr/afs/backup/stacker0.1
- AUTOQUERY NO
- ASK NO
- NAME_CHECK NO
-
-</PRE>
-<P>Finally, the administrator writes the following executable routine in the
-<B>/usr/afs/backup/stacker0.1</B> file referenced by the
-<B>MOUNT</B> and <B>UNMOUNT</B> instructions in the
-<B>CFG_stacker0.1</B> file.
-<PRE> #! /bin/csh -f
-
- set devicefile = $1
- set operation = $2
- set tries = $3
- set tapename = $4
- set tapeid = $5
-
- set exit_continue = 0
- set exit_abort = 1
- set exit_interactive = 2
-
- #--------------------------------------------
-
- if (${tries} > 1) then
- echo "Too many tries"
- exit ${exit_interactive}
- endif
-
- if (${operation} == "unmount") then
- echo "UnMount: Will leave tape in drive"
- exit ${exit_continue}
- endif
-
- if ((${operation} == "dump") |\
- (${operation} == "appenddump") |\
- (${operation} == "savedb")) then
-
- stackerCmd_NextTape ${devicefile}
- if (${status} != 0)exit${exit_interactive}
- echo "Will continue"
- exit ${exit_continue}
- endif
-
- if ((${operation} == "labeltape") |\
- (${operation} == "readlabel")) then
- echo "Will continue"
- exit ${exit_continue}
- endif
-
- echo "Prompt for tape"
- exit ${exit_interactive}
-
-</PRE>
-<P>This routine uses two of the parameters passed to it by the Backup
-System: <TT>tries</TT> and <TT>operation</TT>. It follows the
-recommended practice of prompting for a tape if the value of the
-<TT>tries</TT> parameter exceeds one, because that implies that the stacker
-is out of tapes.
-<P>For a <B>backup dump</B> or <B>backup savedb</B> operation, the
-routine calls the example <B>stackerCmd_NextTape</B> function provided by
-the stacker's manufacturer. Note that the final lines in the file
-return the exit code that prompts the operator to insert a tape; these
-lines are invoked when either the stacker cannot load a tape or a the
-operation being performed is not one of those explicitly mentioned in the file
-(such as a restore operation).
-<P><B>Example CFG_</B><VAR>device_name</VAR> <B>File for Dumping to a
-Backup Data File</B>
-<P>In this example, the administrator creates the following entry for a backup
-data file called <B>HSM_device</B> in the
-<B>/usr/afs/backup/tapeconfig</B> file. It has port offset
-20.
-<PRE> 1G 0K /dev/HSM_device 20
-
-</PRE>
-<P>The administrator includes the following lines in the
-<B>/usr/afs/backup/CFG_HSM_device</B> file. To review the meaning
-of each instruction, see the preceding <B>Description</B> section.
-<PRE> MOUNT /usr/afs/backup/file
- FILE YES
- ASK NO
-
-</PRE>
-<P>Finally, the administrator writes the following executable routine in the
-<B>/usr/afs/backup/file</B> file referenced by the <B>MOUNT</B>
-instruction in the <B>CFG_HSM_device</B> file, to control how the Tape
-Coordinator handles the file.
-<PRE> #! /bin/csh -f
- set devicefile = $1
- set operation = $2
- set tries = $3
- set tapename = $4
- set tapeid = $5
-
- set exit_continue = 0
- set exit_abort = 1
- set exit_interactive = 2
-
- #--------------------------------------------
-
- if (${tries} > 1) then
- echo "Too many tries"
- exit ${exit_interactive}
- endif
-
- if (${operation} == "labeltape") then
- echo "Won't label a tape/file"
- exit ${exit_abort}
- endif
-
- if ((${operation} == "dump") |\
- (${operation} == "appenddump") |\
- (${operation} == "restore") |\
- (${operation} == "savedb") |\
- (${operation} == "restoredb")) then
-
- /bin/rm -f ${devicefile}
- /bin/ln -s /hsm/${tapename}_${tapeid} ${devicefile}
- if (${status} != 0) exit ${exit_abort}
- endif
-
- exit ${exit_continue}
-
-</PRE>
-<P>Like the example routine for a tape stacker, this routine uses the
-<TT>tries</TT> and <TT>operation</TT> parameters passed to it by the
-Backup System. The <TT>tries</TT> parameter tracks how many times the
-Tape Coordinator has attempted to access the file. A value greater than
-one indicates that the Tape Coordinator cannot access it, and the routine
-returns exit code 2 (<TT>exit_interactive</TT>), which results in a prompt
-for the operator to load a tape. The operator can use this opportunity
-to change the name of the backup data file specified in the
-<B>tapeconfig</B> file.
-<P>The primary function of this routine is to establish a link between the
-device file and the file to be dumped or restored. When the Tape
-Coordinator is executing a <B>backup dump</B>, <B>backup restore</B>,
-<B>backup savedb</B>, or <B>backup restoredb</B> operation, the
-routine invokes the UNIX <B>ln -s</B> command to create a symbolic link
-from the backup data file named in the <B>tapeconfig</B> file to the
-actual file to use (this is the recommended method). It uses the value
-of the <TT>tapename</TT> and <TT>tapeid</TT> parameters to construct the
-file name.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf085.htm#HDRBK_RESTOREDB">backup restoredb</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf017.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf019.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf018.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf020.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCLI_CSDB" HREF="auarf002.htm#ToC_17">CellServDB (client version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3912"></A>
-<A NAME="IDX3913"></A>
-<A NAME="IDX3914"></A>
-<A NAME="IDX3915"></A>
-<A NAME="IDX3916"></A>
-<A NAME="IDX3917"></A>
-<A NAME="IDX3918"></A>
-<A NAME="IDX3919"></A>
-<P>Lists the database server machines in all cells accessible from the machine
-<P><STRONG>Description</STRONG>
-<P>The client version of the <B>CellServDB</B> file lists the database
-server machines in the local cell and any foreign cell that is to be
-accessible from the local client machine. Database server machines run
-the Authentication Server, Backup Server, Protection Server, and Volume
-Location (VL) Server (the <B>kaserver</B>, <B>buserver</B>,
-<B>ptserver</B>, and <B>vlserver</B>) processes, which maintain the
-cell's administrative AFS databases.
-<P>The Cache Manager and other processes running on a client machine use the
-list of a cell's database server machines when performing several common
-functions, including:
-<UL>
-<P><LI>Fetching files. The Cache Manager contacts the VL Server to learn
-the location of the volume containing a requested file or directory.
-<P><LI>Authenticating users. Client-side authentication programs (such as
-an AFS-modified login utility or the <B>klog</B> command interpreter)
-contact the Authentication Server to obtain a server ticket, which the AFS
-server processes accept as proof that the user is authenticated.
-<P><LI>Creating protection groups. The <B>pts</B> command interpreter
-contacts the Protection Server when users create protection groups or request
-information from the Protection Database.
-</UL>
-<P>The Cache Manager reads the <B>CellServDB</B> file into kernel memory
-as it initializes, and not again until the machine next reboots. To
-enable users on the local machine to continue accessing the cell correctly,
-update the file whenever a database server machine is added to or removed from
-a cell. To update the kernel-resident list of database server machines
-without rebooting, use the <B>fs newcell</B> command.
-<P>The <B>CellServDB</B> file is in ASCII format and must reside in the
-<B>/usr/vice/etc</B> directory on each AFS client machine. Use a
-text editor to create and maintain it. Each cell's entry must have
-the following format:
-<UL>
-<P><LI>The first line begins at the left margin with the greater-than character
-(<B>></B>), followed immediately by the cell's name without an
-intervening space. Optionally, a comment can follow any number of
-spaces and a number sign (<B>#</B>), perhaps to identify the organization
-associated with the cell.
-<P><LI>Each subsequent line in the entry identifies one of the cell's
-database server machines, with the indicated information in order:
-<UL>
-<P><LI>The database server machine's IP address in dotted-decimal
-format.
-<P><LI>One or more spaces.
-<P><LI>A number sign (<B>#</B>), followed by the machine's fully
-qualified hostname without an intervening space. This number sign does
-not indicate that the hostname is a comment. It is a required
-field.
-</UL>
-</UL>
-<P>No extra blank lines or newline characters are allowed in the file, even
-after the last entry. Their presence can prevent the Cache Manager from
-reading the file into kernel memory, resulting in an error message.
-<P>The AFS Product Support group maintains a list of the database server
-machines in all cells that have registered themselves as receptive to access
-from foreign cells. When a cell's administrators change its
-database server machines, it is customary to register the change with the AFS
-Product Support group for inclusion in this file. The file conforms to
-the required <B>CellServDB</B> format, and so is a suitable basis for the
-<B>CellServDB</B> file on a client machine. Contact the AFS Product
-Support group for directions on accessing the file.
-<P>The client version of the <B>CellServDB</B> file is distinct from the
-server version, which resides in the <B>/usr/afs/etc</B> directory on each
-AFS server machine. The client version lists the database server
-machines in every AFS cell that the cell administrator wants the
-machine's users to be able to access, whereas the server version lists
-only the local cell's database server machines.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows entries for two cells in a client
-<B>CellServDB</B> file and illustrates the required format.
-<PRE> >abc.com # ABC Corporation
- 192.12.105.2 #db1.abc.com
- 192.12.105.3 #db2.abc.com
- 192.12.107.3 #db3.abc.com
- >test.abc.com # ABC Corporation Test Cell
- 192.12.108.57 #testdb1.abc.com
- 192.12.108.55 #testdb2.abc.com
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf154.htm#HDRFS_NEWCELL">fs newcell</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf018.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf020.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf019.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf021.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSV_CSDB" HREF="auarf002.htm#ToC_18">CellServDB (server version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3920"></A>
-<A NAME="IDX3921"></A>
-<A NAME="IDX3922"></A>
-<A NAME="IDX3923"></A>
-<A NAME="IDX3924"></A>
-<A NAME="IDX3925"></A>
-<A NAME="IDX3926"></A>
-<A NAME="IDX3927"></A>
-<P>Lists the local cell's database server machines
-<P><STRONG>Description</STRONG>
-<P>The server version of the <B>CellServDB</B> file lists the local
-cell's database server machines. These machines run the
-Authentication Server, Backup Server, Protection Server, and Volume Location
-(VL) Server (the <B>kaserver</B>, <B>buserver</B>,
-<B>ptserver</B>, and <B>vlserver</B>) processes, which maintain the
-cell's administrative AFS databases. The initial version of the
-file is created with the <B>bos setcellname</B> command during the
-installation of the cell's server machine, which is automatically
-recorded as the cell's first database server machine. When adding
-or removing database server machines, be sure to update this file
-appropriately. It must reside in the <B>/usr/afs/etc</B> directory
-on each AFS server machine.
-<P>The database server processes consult the <B>CellServDB</B> file to
-learn about their peers, with which they must maintain constant connections in
-order to coordinate replication of changes across the multiple copies of each
-database. The other AFS server processes consult the file to learn
-which machines to contact for information from the databases when they need
-it.
-<P>Although the <B>CellServDB</B> file is in ASCII format, do not use a
-text editor to alter it. Instead always use the appropriate commands
-from the <B>bos</B> command suite:
-<UL>
-<P><LI>The <B>bos addhost</B> command to add a machine to the file
-<P><LI>The <B>bos listhosts</B> command to display the list of machines from
-the file
-<P><LI>The <B>bos removehost</B> command to remove a machine from the file
-</UL>
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is customary to edit only the copy of the file stored on the system control
-machine. In cells that run the international version of AFS, edit the
-file on each server machine individually. For instructions on adding
-and removing database server machine, see the <I>IBM AFS Quick
-Beginnings</I> chapter on installing additional server machines.
-<P>The server version of the <B>CellServDB</B> file is distinct from the
-client version, which resides in the <B>/usr/vice/etc</B> directory on
-each AFS client machine. The server version lists only the local
-cell's database server machines, whereas the client version lists the
-database server machines in every AFS cell that the cell administrator wants
-the machine's users to be able to access.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf094.htm#HDRBOS_ADDHOST">bos addhost</A>
-<P><A HREF="auarf106.htm#HDRBOS_LISTHOSTS">bos listhosts</A>
-<P><A HREF="auarf110.htm#HDRBOS_REMOVEHOST">bos removehost</A>
-<P><A HREF="auarf116.htm#HDRBOS_SETCELLNAME">bos setcellname</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf019.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf021.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf020.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf022.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFILELOG" HREF="auarf002.htm#ToC_19">FileLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3928"></A>
-<A NAME="IDX3929"></A>
-<A NAME="IDX3930"></A>
-<P>Traces File Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>FileLog</B> file records a trace of File Server
-(<B>fileserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>FileLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the File Server starts, the server
-process creates it and writes initial start-up messages to it. If there
-is an existing file, the File Server renames it to
-<B>FileLog.old</B>, overwriting the existing
-<B>FileLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the file
-server machine and use a text editor or a file display command such as the
-UNIX <B>cat</B> command. By default, the mode bits on the
-<B>FileLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The File Server records operations only as it completes them, and cannot
-recover from failures by reviewing the file. The log contents are
-useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf020.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf022.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf021.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf023.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFORCESALVAGE" HREF="auarf002.htm#ToC_20">FORCESALVAGE</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3931"></A>
-<A NAME="IDX3932"></A>
-<A NAME="IDX3933"></A>
-<P>Forces salvage of entire partition
-<P><STRONG>Description</STRONG>
-<P>The <B>FORCESALVAGE</B> file, if present on an AFS server partition
-(that is, in a <B>/vicep</B> directory), signals that the Salvager must
-salvage the entire partition. The AFS-modified version of the
-<B>fsck</B> program creates the empty (zero-length) file when it discovers
-corruption on the partition. The Salvager removes the file when it
-completes the salvage operation.
-<P>When the File Server detects the presence of the file on a partition on
-which it is attaching volumes, it stops, detaches any volumes that are already
-attached, and exits after recording a message in the
-<B>/usr/afs/logs/FileLog</B> file. The Bos Server then invokes the
-Salvager to salvage the partition.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf021.htm#HDRFILELOG">FileLog</A>
-<P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf021.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf023.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf022.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf024.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKEYFILE" HREF="auarf002.htm#ToC_21">KeyFile</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3934"></A>
-<A NAME="IDX3935"></A>
-<A NAME="IDX3936"></A>
-<A NAME="IDX3937"></A>
-<A NAME="IDX3938"></A>
-<A NAME="IDX3939"></A>
-<A NAME="IDX3940"></A>
-<A NAME="IDX3941"></A>
-<P>Defines AFS server encryption keys
-<P><STRONG>Description</STRONG>
-<P>The <B>KeyFile</B> file defines the server encryption keys that the AFS
-server processes running on the machine use to decrypt the tickets presented
-by clients during the mutual authentication process. AFS server
-processes perform privileged actions only for clients that possess a ticket
-encrypted with one of the keys from the file. The file must reside in
-the <B>/usr/afs/etc</B> directory on every server machine. For more
-detailed information on mutual authentication and server encryption keys, see
-the <I>IBM AFS Administration Guide</I>.
-<P>Each key has a corresponding a key version number that distinguishes it
-from the other keys. The tickets that clients present are also marked
-with a key version number to tell the server process which key to use to
-decrypt it. The <B>KeyFile</B> file must always include a key with
-the same key version number and contents as the key currently listed for the
-<B>afs</B> entry in the Authentication Database.
-<P>The <B>KeyFile</B> file is in binary format, so always use the
-appropriate commands from the <B>bos</B> command suite to administer
-it:
-<UL>
-<P><LI>The <B>bos addkey</B> command to define a new key
-<P><LI>The <B>bos listkeys</B> command to display the keys
-<P><LI>The <B>bos removekey</B> command to remove a key from the file
-</UL>
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is customary to edit only the copy of the file stored on the system control
-machine. In cells that run the international version of AFS, edit the
-file on each server machine individually.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P><A HREF="auarf111.htm#HDRBOS_REMOVEKEY">bos removekey</A>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf022.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf024.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf023.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf025.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCLI_NETINFO" HREF="auarf002.htm#ToC_22">NetInfo (client version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3942"></A>
-<A NAME="IDX3943"></A>
-<A NAME="IDX3944"></A>
-<A NAME="IDX3945"></A>
-<A NAME="IDX3946"></A>
-<A NAME="IDX3947"></A>
-<P>Defines client machine interfaces to register with the File Server
-<P><STRONG>Description</STRONG>
-<P>The <B>NetInfo</B> file lists the IP addresses of one or more of the
-local machine's network interfaces. If it exists in the
-<B>/usr/vice/etc</B> directory when the Cache Manager initializes, the
-Cache Manager uses its contents as the basis for a list of local
-interfaces. Otherwise, the Cache Manager uses the list of interfaces
-configured with the operating system. It then removes from the list any
-addresses that appear in the <B>/usr/vice/etc/NetRestrict</B> file, if it
-exists. The Cache Manager records the resulting list in kernel
-memory. The first time it establishes a connection to a File Server, it
-registers the list with the File Server.
-<P>The File Server uses the addresses when it initiates a remote procedure
-call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by
-the Cache Manager). There are two common circumstances in which the
-File Server initiates RPCs: when it breaks callbacks and when it pings
-the client machine to verify that the Cache Manager is still
-accessible.
-<P>The <B>NetInfo</B> file is in ASCII format. One of the
-machine's IP addresses appears on each line, in dotted decimal
-format. The File Server initially uses the address that appears first
-in the list. The order of the remaining addresses is not
-significant: if an RPC to the first interface fails, the File Server
-simultaneously sends RPCs to all of the other interfaces in the list.
-Whichever interface replies first is the one to which the File Server then
-sends pings and RPCs to break callbacks.
-<P>To prohibit the Cache Manager absolutely from using one or more addresses,
-list them in the <B>NetRestrict</B> file. To display the addresses
-the Cache Manager is currently registering with File Servers, use the <B>fs
-getclientaddrs</B> command. To replace the current list of interfaces
-with a new one between reboots of the client machine, use the <B>fs
-setclientaddrs</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf026.htm#HDRCLI_NETRESTRICT">NetRestrict (client version)</A>
-<P><A HREF="auarf145.htm#HDRFS_GETCLIENTADDRS">fs getclientaddrs</A>
-<P><A HREF="auarf160.htm#HDRFS_SETCLIENTADDRS">fs setclientaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf023.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf025.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf024.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf026.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSV_NETINFO" HREF="auarf002.htm#ToC_23">NetInfo (server version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3948"></A>
-<A NAME="IDX3949"></A>
-<A NAME="IDX3950"></A>
-<A NAME="IDX3951"></A>
-<A NAME="IDX3952"></A>
-<P>Defines interfaces that File Server registers in VLDB and Ubik uses for
-database server machines
-<P><STRONG>Description</STRONG>
-<P>The <B>NetInfo</B> file, if present in the <B>/usr/afs/local</B>
-directory, defines the following:
-<UL>
-<P><LI>On a file server machine, the local interfaces that the File Server
-(<B>fileserver</B> process) can register in the Volume Location Database
-(VLDB) at initialization time
-<P><LI>On a database server machine, the local interfaces that the Ubik database
-synchronization library uses when communicating with the database server
-processes running on other database server machines
-</UL>
-<P>If the <B>NetInfo</B> file exists when the File Server initializes, the
-File Server uses its contents as the basis for a list of interfaces to
-register in the VLDB. Otherwise, it uses the list of network interfaces
-configured with the operating system. It then removes from the list any
-addresses that appear in the <B>/usr/vice/etc/NetRestrict</B> file, if it
-exists. The File Server records the resulting list in the
-<B>/usr/afs/local/sysid</B> file and registers the interfaces in the
-VLDB. The database server processes use a similar procedure when
-initializing, to determine which interfaces to use for communication with the
-peer processes on other database machines in the cell.
-<P>The <B>NetInfo</B> file is in ASCII format. One of the
-machine's IP addresses appears on each line, in dotted decimal
-format. The order of the addresses is not significant.
-<P>To display the File Server interface addresses registered in the VLDB, use
-the <B>vos listaddrs</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf027.htm#HDRSV_NETRESTRICT">NetRestrict (server version)</A>
-<P><A HREF="auarf049.htm#HDRSYSID">sysid</A>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf263.htm#HDRVOS_LISTADDRS">vos listaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf024.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf026.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf025.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf027.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCLI_NETRESTRICT" HREF="auarf002.htm#ToC_24">NetRestrict (client version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3953"></A>
-<A NAME="IDX3954"></A>
-<A NAME="IDX3955"></A>
-<A NAME="IDX3956"></A>
-<A NAME="IDX3957"></A>
-<A NAME="IDX3958"></A>
-<P>Defines client interfaces not to register with the File Server
-<P><STRONG>Description</STRONG>
-<P>The <B>NetRestrict</B> file, if present in a client machine's
-<B>/usr/vice/etc</B> directory, defines the IP addresses of the interfaces
-that the local Cache Manager does not register with a File Server when first
-establishing a connection to it. For an explanation of how the File
-Server uses the registered interfaces, see the reference page for the client
-version of the <B>NetInfo</B> file.
-<P>As it initializes, the Cache Manager constructs a list of interfaces to
-register, from the <B>/usr/vice/etc/NetInfo</B> file if it exists, or from
-the list of interfaces configured with the operating system otherwise.
-The Cache Manager then removes from the list any addresses that appear in the
-<B>NetRestrict</B> file, if it exists. The Cache Manager records
-the resulting list in kernel memory.
-<P>The <B>NetRestrict</B> file is in ASCII format. One IP address
-appears on each line, in dotted decimal format. The order of the
-addresses is not significant. The value <B>255</B> is a wildcard
-that represents all possible addresses in that field. For example, the
-value <B>192.12.105.255</B> indicates that the Cache
-Manager does not register any of the addresses in the
-<B>192.12.105</B> subnet.
-<P>To display the addresses the Cache Manager is currently registering with
-File Servers, use the <B>fs getclientaddrs</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf024.htm#HDRCLI_NETINFO">NetInfo (client version)</A>
-<P><A HREF="auarf145.htm#HDRFS_GETCLIENTADDRS">fs getclientaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf025.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf027.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf026.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf028.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSV_NETRESTRICT" HREF="auarf002.htm#ToC_25">NetRestrict (server version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3959"></A>
-<A NAME="IDX3960"></A>
-<A NAME="IDX3961"></A>
-<A NAME="IDX3962"></A>
-<A NAME="IDX3963"></A>
-<P>Defines interfaces that File Server does not register in VLDB and Ubik does
-not use for database server machines
-<P><STRONG>Description</STRONG>
-<P>The <B>NetRestrict</B> file, if present in the
-<B>/usr/afs/local</B> directory, defines the following:
-<UL>
-<P><LI>On a file server machine, the local interfaces that the File Server
-(<B>fileserver</B> process) does not register in the Volume Location
-Database (VLDB) at initialization time
-<P><LI>On a database server machine, the local interfaces that the Ubik
-synchronization library does not use when communicating with the database
-server processes running on other database server machines
-</UL>
-<P>As it initializes, the File Server constructs a list of interfaces to
-register, from the <B>/usr/afs/local/NetInfo</B> file if it exists, or
-from the list of interfaces configured with the operating system
-otherwise. The File Server then removes from the list any addresses
-that appear in the <B>NetRestrict</B> file, if it exists. The File
-Server records the resulting list in the <B>/usr/afs/local/sysid</B> file
-and registers the interfaces in the VLDB. The database server processes
-use a similar procedure when initializing, to determine which interfaces to
-use for communication with the peer processes on other database machines in
-the cell.
-<P>The <B>NetRestrict</B> file is in ASCII format. One IP address
-appears on each line, in dotted decimal format. The order of the
-addresses is not significant. The value <B>255</B> is a wildcard
-that represents all possible addresses in that field. For example, the
-value <B>192.12.105.255</B> indicates that the Cache
-Manager does not register any of the addresses in the
-<B>192.12.105</B> subnet.
-<P>To display the File Server interface addresses registered in the VLDB, use
-the <B>vos listaddrs</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf025.htm#HDRSV_NETINFO">NetInfo (server version)</A>
-<P><A HREF="auarf049.htm#HDRSYSID">sysid</A>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf263.htm#HDRVOS_LISTADDRS">vos listaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf026.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf028.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf027.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf029.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRNOAUTH" HREF="auarf002.htm#ToC_26">NoAuth</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3964"></A>
-<A NAME="IDX3965"></A>
-<A NAME="IDX3966"></A>
-<P>Disables authorization checking
-<P><STRONG>Description</STRONG>
-<P>The <B>NoAuth</B> file, if present in a server machine's
-<B>/usr/afs/local</B> directory, indicates to the AFS server processes
-running on the machine that it is not necessary to perform authorization
-checking. They perform any action for any user who logs into the
-machine's local file system or issues a remote command that affects the
-machine's AFS server functioning, such as commands from the AFS command
-suites. Because failure to check authorization exposes the
-machine's AFS server functionality to attack, there are normally only two
-circumstances in which the file is present:
-<UL>
-<P><LI>During installation of the machine, as instructed in the <I>IBM AFS
-Quick Beginnings</I>
-<P><LI>During correction of a server encryption key emergency, as discussed in
-the <I>IBM AFS Administration Guide</I>
-</UL>
-<P>In all other circumstances, the absence of the file means that the AFS
-server processes perform authorization checking, verifying that the issuer of
-a command has the required privilege.
-<P>Create the file in one of the following ways:
-<UL>
-<P><LI>By issuing the <B>bosserver</B> initialization command with the
-<B>-noauth</B> flag, if the Basic OverSeer (BOS) Server is not already
-running
-<P><LI>By issuing the <B>bos setauth</B> command with <B>off</B> as the
-value for the <B>-authrequired</B> argument, if the BOS Server is already
-running
-</UL>
-<P>To remove the file, issue the <B>bos setauth</B> command with
-<B>on</B> as the value for the <B>-authrequired</B> argument.
-<P>The file's contents, if any, are ignored; an empty (zero-length)
-file is effective.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf115.htm#HDRBOS_SETAUTH">bos setauth</A>
-<P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf027.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf029.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf028.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf030.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSALVAGEFS" HREF="auarf002.htm#ToC_27">SALVAGE.fs</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3967"></A>
-<A NAME="IDX3968"></A>
-<A NAME="IDX3969"></A>
-<A NAME="IDX3970"></A>
-<A NAME="IDX3971"></A>
-<P>Triggers salvaging of AFS server partitions
-<P><STRONG>Description</STRONG>
-<P>The <B>SALVAGE.fs</B> file, if present in a file server
-machine's <B>/usr/afs/local</B> directory, indicates to the Basic
-OverSeer (BOS) Server (<B>bosserver</B> process) that it must invoke the
-Salvager (<B>salvager</B> process) during recovery from a failure of the
-File Server (<B>fileserver</B> process).
-<P>The BOS Server creates the zero-length file each time it starts or restarts
-the <B>fs</B> process. When the File Server exits normally (for
-example, in response to the <B>bos shutdown</B> or <B>bos stop</B>
-command), the BOS Server removes the file. However, if the File Server
-exits unexpectedly, the file remains in the <B>/usr/afs/local</B>
-directory as a signal that the BOS Server must invoke the Salvager process to
-repair any file system inconsistencies possibly introduced during the failure,
-before restarting the File Server and Volume Server processes.
-<P>Do not create or remove this file. To invoke the Salvager process
-directly, use the <B>bos salvage</B> command or log onto the file server
-machine as the local superuser <B>root</B> and issue the
-<B>salvager</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf028.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf030.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf029.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf031.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSALVAGELOG" HREF="auarf002.htm#ToC_28">SalvageLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3972"></A>
-<A NAME="IDX3973"></A>
-<A NAME="IDX3974"></A>
-<P>Traces Salvager operations
-<P><STRONG>Description</STRONG>
-<P>The <B>SalvageLog</B> file records a trace of Salvager
-(<B>salvager</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>SalvageLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the Salvager starts, the process
-creates it and writes initial start-up messages to it. If there is an
-existing file, the Salvager renames is to <B>SalvageLog.old</B>,
-overwriting the existing <B>SalvageLog.old</B> file if it
-exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the file
-server machine and use a text editor or a file display command such as the
-UNIX <B>cat</B> command. By default, the mode bits on the
-<B>SalvageLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The Salvager records operations only as it completes them, and cannot
-recover from failures by reviewing the file. The log contents are
-useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf029.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf031.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf030.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf032.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRTE" HREF="auarf002.htm#ToC_29">TE_<I>device_name</I></A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Logs error messages from the Tape Coordinator process
-<P><STRONG>Description</STRONG>
-<P>The <B>TE_</B><VAR>device_name</VAR> file logs error messages generated
-by the Backup System Tape Coordinator (<B>butc</B> process) that controls
-the tape device or backup data file indicated by <VAR>device_name</VAR>.
-<P>As the Tape Coordinator initializes, it creates the file in ASCII format in
-the <B>/usr/afs/backup</B> directory. If there is an existing file,
-the Tape Coordinator renames it to
-<B>TE_</B><VAR>device_name</VAR><B>.old</B>, overwriting the
-existing <B>TE_</B><VAR>device_name</VAR><B>.old</B> file if it
-exists.
-<P>For a tape device, the Tape Coordinator derives the variable
-<VAR>device_name</VAR> portion of the filename from the device pathname listed
-in the local <B>/usr/afs/backup/tapeconfig</B> file, by stripping off the
-initial <B>/dev/</B> string and replacing any other slashes in the name
-with underscores. For example, the filename for a device called
-<B>/dev/rmt/4m</B> is <B>TE_rmt_4m</B>. Similarly, for a backup
-data file the Tape Coordinator strips off the initial slash (/) and replaces
-any other slashes in the name with underscores. For example, the
-filename for a backup data file called <B>/var/tmp/FILE</B> is
-<B>TE_var_tmp_FILE</B>.
-<P>The messages in the file describe the error and warning conditions the Tape
-Coordinator encounters as it operates. For instance, a message can list
-the volumes that are inaccessible during a dump operation, or warn that the
-Tape Coordinator is overwriting a tape or backup data file. The
-messages also appear in the <B>/usr/afs/backup/TL_</B><VAR>device_name</VAR>
-file, which traces most of the Tape Coordinator's actions.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf034.htm#HDRTL">TL_<I>device_name</I></A>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf030.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf032.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf031.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf033.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCLI_THISCELL" HREF="auarf002.htm#ToC_30">ThisCell (client version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3975"></A>
-<A NAME="IDX3976"></A>
-<A NAME="IDX3977"></A>
-<A NAME="IDX3978"></A>
-<A NAME="IDX3979"></A>
-<P>Defines client machine's cell membership
-<P><STRONG>Description</STRONG>
-<P>The client version of the <B>ThisCell</B> file defines the complete
-Internet domain-style name (for example, <B>abc.com</B>) of the
-cell to which the local client machine belongs. It must reside in the
-<B>/usr/vice/etc</B> directory on every AFS client machine. To
-change a client machine's cell membership, edit the file and reboot the
-machine.
-<P>The file is in ASCII format and contains a character string on a single
-line. The <I>IBM AFS Quick Beginnings</I> instructs the
-administrator to create it during the installation of each client
-machine.
-<P>The client machine's cell membership determines three defaults
-important to its functioning:
-<UL>
-<P><LI>The cell in which the machine's users authenticate by default.
-The effect is two-fold:
-<UL>
-<P><LI>The AFS-modified login utilities and the <B>klog</B> command
-interpreter contact an Authentication Server in the cell named in the
-<B>ThisCell</B> file (unless <B>-cell</B> argument to the
-<B>klog</B> command specifies an alternate cell).
-<P><LI>The command interpreters combine the cell name with the password that the
-user provides, generating an encryption key from the combination. For
-authentication to succeed, both the cell name and password must match the ones
-used to generate the user's encryption key stored in the Authentication
-Database.
-</UL>
-<P><LI>The cell the Cache Manager considers its local, or home, cell. By
-default, the Cache Manager allows programs that reside in its home cell to run
-with setuid permission, but not programs from foreign cells. For more
-details, see the <B>fs getcellstatus</B> and <B>fs setcell</B>
-reference pages.
-<P><LI>Which AFS server processes the local AFS command interpreters contact by
-default as they execute commands issued on the machine.
-</UL>
-<P>The client version of the <B>ThisCell</B> file is distinct from the
-server version, which resides in the <B>/usr/afs/etc</B> directory on each
-AFS server machine. If a server machine also runs as a client, it is
-acceptable for the server and client versions of the file on the same machine
-to name different cells. However, the behavior that results from this
-configuration can be more confusing than useful.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<P><A HREF="auarf144.htm#HDRFS_GETCELLSTATUS">fs getcellstatus</A>
-<P><A HREF="auarf159.htm#HDRFS_SETCELL">fs setcell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf031.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf033.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf032.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf034.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSV_THISCELL" HREF="auarf002.htm#ToC_31">ThisCell (server version)</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3980"></A>
-<A NAME="IDX3981"></A>
-<A NAME="IDX3982"></A>
-<A NAME="IDX3983"></A>
-<A NAME="IDX3984"></A>
-<P>Defines server machine's cell membership
-<P><STRONG>Description</STRONG>
-<P>The server version of the <B>ThisCell</B> file defines the complete
-Internet domain-style name (for example, <B>abc.com</B>) of the
-cell to which the server machine belongs. It must reside in the
-<B>/usr/afs/etc</B> directory on every AFS server machine.
-<P>The file is in ASCII format and contains a character string on a single
-line. The initial version of the file is created with the <B>bos
-setcellname</B> command during the installation of the cell's first
-file server machine, and the <I>IBM AFS Quick Beginnings</I> includes
-instructions for copying it over to additional server machine during their
-installation.
-<P>The only reason to edit the file is as part of changing the cell's
-name, which is strongly discouraged because of the large number of
-configuration changes involved. In particular, changing the cell name
-requires rebuilding the entire Authentication Database, because the
-Authentication Server combines the cell name it finds in this file with each
-user and server password and converts the combination into an encryption key
-before recording it in the Database.
-<P>The server version of the <B>ThisCell</B> file is distinct from the
-client version, which resides in the <B>/usr/vice/etc</B> directory on
-each AFS client machine. If a server machine also runs as a client, it
-is acceptable for the server and client versions of the file on the same
-machine to name different cells. However, the behavior that results
-from this configuration can be more confusing than useful.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf116.htm#HDRBOS_SETCELLNAME">bos setcellname</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf032.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf034.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf033.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf035.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRTL" HREF="auarf002.htm#ToC_32">TL_<I>device_name</I></A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Traces Tape Coordinator operations and logs errors
-<P><STRONG>Description</STRONG>
-<P>The <B>TL_</B><VAR>device_name</VAR> file logs the actions performed by
-the Backup System Tape Coordinator (<B>butc</B> process) that controls the
-tape device or backup data file indicated by <VAR>device_name</VAR>. It
-also records the same error and warning messages written to the
-<B>TE_</B><VAR>device_name</VAR> file.
-<P>As the Tape Coordinator initializes, it creates the file in ASCII format in
-the <B>/usr/afs/backup</B> directory. If there is an existing file,
-the Tape Coordinator renames it to
-<B>TL_</B><VAR>device_name</VAR><B>.old</B>, overwriting the
-existing <B>TL_</B><VAR>device_name</VAR><B>.old</B> file if it
-exists.
-<P>For a tape device, the Tape Coordinator derives the variable
-<VAR>device_name</VAR> portion of the filename from the device pathname listed
-in the local <B>/usr/afs/backup/tapeconfig</B> file, by stripping off the
-initial <B>/dev/</B> string and replacing any other slashes in the name
-with underscores. For example, the filename for a device called
-<B>/dev/rmt/4m</B> is <B>TL_rmt_4m</B>. Similarly, for a backup
-data file the Tape Coordinator strips off the initial slash (/) and replaces
-any other slashes in the name with underscores. For example, the
-filename for a backup data file called <B>/var/tmp/FILE</B> is
-<B>TL_var_tmp_FILE</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf031.htm#HDRTE">TE_<I>device_name</I></A>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf033.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf035.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf034.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf036.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSERLIST" HREF="auarf002.htm#ToC_33">UserList</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3985"></A>
-<A NAME="IDX3986"></A>
-<P>Defines privileged administrators
-<P><STRONG>Description</STRONG>
-<P>The <B>UserList</B> file lists the AFS usernames of the system
-administrators authorized to issue privileged <B>bos</B>, <B>vos</B>,
-and <B>backup</B> commands that affect the local server machine or the
-volumes housed on it. It must reside in the <B>/usr/afs/etc</B>
-directory on every server machine.
-<P>Although the <B>UserList</B> file is in ASCII format, do not use a text
-editor to alter it. Instead always use the appropriate commands from
-the <B>bos</B> command suite:
-<UL>
-<P><LI>The <B>bos adduser</B> command to add a user to the file
-<P><LI>The <B>bos listusers</B> command to display the contents of the file
-<P><LI>The <B>bos removeuser</B> command to remove a user from the file
-</UL>
-<P>Although it is theoretically possible to list different administrators in
-the <B>UserList</B> files on different server machines, doing so can cause
-unanticipated authorization failures and is not recommended. In cells
-that run the United States edition of AFS and use the Update Server to
-distribute the contents of the <B>/usr/afs/etc</B> directory, it is
-customary to edit only the copy of the file stored on the system control
-machine. In cells that run the international version of AFS, edit the
-file on each server machine individually.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf096.htm#HDRBOS_ADDUSER">bos adduser</A>
-<P><A HREF="auarf108.htm#HDRBOS_LISTUSERS">bos listusers</A>
-<P><A HREF="auarf112.htm#HDRBOS_REMOVEUSER">bos removeuser</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf034.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf036.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf035.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf037.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVN" HREF="auarf002.htm#ToC_34">V<I>n</I></A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3987"></A>
-<A NAME="IDX3988"></A>
-<A NAME="IDX3989"></A>
-<P>Houses a chunk of AFS data in the disk cache
-<P><STRONG>Description</STRONG>
-<P>A <B>V</B><VAR>n</VAR> file can store a chunk of cached AFS data on a
-client machine that is using a disk cache. As the Cache Manager
-initializes, it verifies that the local disk cache directory houses a number
-of <B>V</B><VAR>n</VAR> files equal to the largest of the following:
-<UL>
-<P><LI>100
-<P><LI>One and a half times the result of dividing the cache size by the chunk
-size (cachesize/chunksize * 1.5)
-<P><LI>The result of dividing the cache size by 10 MB (10,240)
-</UL>
-<P>The Cache Manager determines the cache size from the <B>-blocks</B>
-argument to the <B>afsd</B> command, or if the argument is not included,
-from the third field of the <B>/usr/vice/etc/cacheinfo</B> file.
-The default chunk size is 64 KB; use the <B>-chunksize</B> argument
-to the <B>afsd</B> command to override it. To override the default
-number of chunks resulting from the calculation, include the <B>-files</B>
-argument to the <B>afsd</B> command. The <B>afsd</B> reference
-page describes the restrictions on acceptable values for each of the
-arguments.
-<P>If the disk cache directory houses fewer <B>V</B><VAR>n</VAR> files than
-necessary, the Cache Manager creates new ones, assigning each a unique integer
-<VAR>n</VAR> that distinguishes it from the other files; the integers start
-with 1 and increment by one for each <B>V</B><VAR>n</VAR> file
-created. The Cache Manager removes files if there are more than
-necessary. The Cache Manager also adds and removes
-<B>V</B><VAR>n</VAR> files in response to the <B>fs setcachesize</B>
-command, which can be used to alter the cache size between reboots.
-<P>The standard disk cache directory name is <B>/usr/vice/cache</B>, but
-it is acceptable to use a directory on a partition with more available
-space. To designate a different directory, change the value in the
-second field of the <B>/usr/vice/etc/cacheinfo</B> file before issuing the
-<B>afsd</B> command, or include the <B>-cachedir</B> argument to the
-<B>afsd</B> command.
-<P><B>V</B><VAR>n</VAR> files expand and contract to accommodate the size of
-the AFS directory listing or file they temporarily house. As mentioned,
-by default each <B>V</B><VAR>n</VAR> file holds up to 64 KB (65,536 bytes)
-of a cached AFS element. AFS elements larger than 64 KB are divided
-among multiple <B>V</B><VAR>n</VAR> files. If an element is smaller
-than 64 KB, the <B>V</B><VAR>n</VAR> file expands only to the required
-size. A <B>V</B><VAR>n</VAR> file accommodates only a single element,
-so if there many small cached elements, it is possible to exhaust the
-available <B>V</B><VAR>n</VAR> files without reaching the maximum cache
-size.
-<P><STRONG>Cautions</STRONG>
-<P>Editing or removing a <B>V</B><VAR>n</VAR> file can cause a kernel
-panic. To alter cache size (and thus the number of
-<B>V</B><VAR>n</VAR> files) between reboots, use the <B>fs
-setcachesize</B> command. Alternatively, alter the value of the
-<B>-blocks</B>, <B>-files</B> or <B>-chunksize</B> arguments to
-the <B>afsd</B> command invoked in the machine's AFS initialization
-file, and reboot. To refresh the contents of one or more
-<B>V</B><VAR>n</VAR> files, use the <B>fs flush</B> or <B>fs
-flushvolume</B> command. If a <B>V</B><VAR>n</VAR> file is
-accidentally modified or deleted, rebooting the machine usually restores
-normal performance.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<P><A HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<P><A HREF="auarf158.htm#HDRFS_SETCACHESIZE">fs setcachesize</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf035.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf037.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf036.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf038.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVVOLID" HREF="auarf002.htm#ToC_35">V<I>vol_ID</I>.vol</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3990"></A>
-<A NAME="IDX3991"></A>
-<A NAME="IDX3992"></A>
-<A NAME="IDX3993"></A>
-<P>Represents an AFS volume
-<P><STRONG>Description</STRONG>
-<P>The <B>V</B><VAR>vol_ID</VAR><B>.vol</B> file is the header
-file for the AFS volume with volume ID <VAR>vol_ID</VAR>. There is one
-such file for each volume stored on an AFS server (<B>/vicep</B>)
-partition. The header file stores information that includes the
-volume's name, ID number, type (read/write, read-only, or backup), size
-and status (online, offline, or busy). To display information from the
-header file, use the <B>vos listvol</B> or <B>vos examine</B>
-command.
-<P>The header file points to, but does not contain, the actual data in the
-volume. It is not possible to access the AFS data except by mounting
-the volume in the AFS filespace and reading its contents through the Cache
-Manager.
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf036.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf038.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf037.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf039.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVLLOG" HREF="auarf002.htm#ToC_36">VLLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3994"></A>
-<A NAME="IDX3995"></A>
-<A NAME="IDX3996"></A>
-<P>Traces Volume Location Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>VLLog</B> file records a trace of Volume Location (VL) Server
-(<B>vlserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>VLLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the VL Server starts, the server
-process creates it and writes initial start-up messages to it. If there
-is an existing file, the VL Server renames it to <B>VLLog.old</B>,
-overwriting the existing <B>VLLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the server
-machine and use a text editor or a file display command such as the UNIX
-<B>cat</B> command. By default, the mode bits on the
-<B>VLLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The VL Server records operations only as it completes them, and cannot
-recover from failures by reviewing the file. The log contents are
-useful for administrative evaluation of process failures and other
-problems.
-<P>The VL Server can record messages at three levels of detail. By
-default, it records only very rudimentary messages. To increase logging
-to the first level of detail, issue the following command while logged onto
-the database server machine as the local superuser <B>root</B>.
-<PRE> # <B>kill -TSTP</B> <VAR>vlserver_pid</VAR>
-
-</PRE>
-<P>where <VAR>vlserver_pid</VAR> is the process ID of the <B>vlserver</B>
-process, as reported in the output from the standard UNIX <B>ps</B>
-command. To increase to the second and third levels of detail, repeat
-the command.
-<P>To disable logging, issue the following command.
-<PRE>
- # <B>kill -HUP</B> <VAR>vlserver_pid</VAR>
-
-</PRE>
-<P>To decrease the level of logging, first completely disable it and then
-issue the <B>kill -TSTP</B> command as many times as necessary to reach
-the desired level.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf037.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf039.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf038.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf040.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOLSERLOG" HREF="auarf002.htm#ToC_37">VolserLog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX3997"></A>
-<A NAME="IDX3998"></A>
-<A NAME="IDX3999"></A>
-<P>Traces Volume Server operations
-<P><STRONG>Description</STRONG>
-<P>The <B>VolserLog</B> file records a trace of Volume Server
-(<B>volserver</B> process) operations on the local machine and describes
-any error conditions it encounters.
-<P>If the <B>VolserLog</B> file does not already exist in the
-<B>/usr/afs/logs</B> directory when the Volume Server starts, the server
-process creates it and writes initial start-up messages to it. If there
-is an existing file, the Volume Server renames it to
-<B>VolserLog.old</B>, overwriting the existing
-<B>VolserLog.old</B> file if it exists.
-<P>The file is in ASCII format. Administrators listed in the
-<B>/usr/afs/etc/UserList</B> file can use the <B>bos getlog</B>
-command to display its contents. Alternatively, log onto the file
-server machine and use a text editor or a file display command such as the
-UNIX <B>cat</B> command. By default, the mode bits on the
-<B>VolserLog</B> file grant the required <B>r</B> (<B>read</B>)
-permission to all users.
-<P>The Volume Server records operations only as it completes them, and so
-cannot recover from failures by reviewing the file. The log contents
-are useful for administrative evaluation of process failures and other
-problems.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf038.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf040.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf039.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf041.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOLUMEITEMS" HREF="auarf002.htm#ToC_38">VolumeItems</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4000"></A>
-<A NAME="IDX4001"></A>
-<A NAME="IDX4002"></A>
-<A NAME="IDX4003"></A>
-<P>Records location mappings for volumes accessed by a Cache Manager using a
-disk cache
-<P><STRONG>Description</STRONG>
-<P>The <B>VolumeItems</B> file records the mapping between volume name and
-mount point for each volume that the Cache Manager has accessed since it
-initialized on a client machine using a disk cache. The Cache Manager
-uses the mappings to respond correctly to queries about the current working
-directory, which can come from the operating system or commands such as the
-UNIX <B>pwd</B> command.
-<P>As it initializes, the Cache Manager creates the binary-format
-<B>VolumeItems</B> file in the local disk cache directory, and it must
-always remain there. The conventional directory name is
-<B>/usr/vice/cache</B>.
-<P><STRONG>Cautions</STRONG>
-<P>Editing or removing the <B>VolumeItems</B> file can cause a kernel
-panic. To refresh the contents of the file, instead use the <B>fs
-checkvolumes</B> command. If the <B>VolumeItems</B> file is
-accidentally modified or deleted, rebooting the machine usually restores
-normal performance.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf017.htm#HDRCACHEITEMS">CacheItems</A>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf134.htm#HDRFS_CHECKVOLUMES">fs checkvolumes</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf039.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf041.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf040.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf042.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAFSZCM" HREF="auarf002.htm#ToC_39">afszcm.cat</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4004"></A>
-<A NAME="IDX4005"></A>
-<P>Error message catalog for debugging the Cache Manager
-<P><STRONG>Description</STRONG>
-<P>The <B>afszcm.cat</B> file is a message catalog for the Cache
-Manager. The <B>fstrace dump</B> command interpreter uses it in
-conjunction with the standard UNIX catalog utilities to translate Cache
-Manager operation codes into character strings as it writes traces in the
-<B>fstrace</B> trace log, which makes the log more readable.
-<P>The conventional location for the file is the <B>/usr/vice/etc/C/</B>
-directory. It can be placed in another directory if the NLSPATH and
-LANG environment variables are set appropriately.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf172.htm#HDRFSTRACE_DUMP">fstrace dump</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf040.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf042.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf041.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf043.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBDBDB" HREF="auarf002.htm#ToC_40">bdb.DB0 and bdb.DBSYS1</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4006"></A>
-<A NAME="IDX4007"></A>
-<A NAME="IDX4008"></A>
-<A NAME="IDX4009"></A>
-<A NAME="IDX4010"></A>
-<P>Contain the Backup Database and associated log
-<P><STRONG>Description</STRONG>
-<P>The <B>bdb.DB0</B> file contains the Backup Database, which
-records configuration information used by the AFS Backup System along with
-cross-indexed records of the tapes created and volumes dumped using the Backup
-System commands.
-<P>The <B>bdb.DBSYS1</B> file is a log file in which the Backup
-Server (<B>buserver</B> process) logs each database operation before
-performing it. When an operation is interrupted, the Backup Server
-replays the log to complete the operation.
-<P>Both files are in binary format and reside in the <B>/usr/afs/db</B>
-directory on each database server machine that runs the Backup Server.
-When the Backup Server starts or restarts on a given machine, it establishes a
-connection with its peers and verifies that its copy of the
-<B>bdb.DB0</B> file matches the copy on the other database server
-machines. If not, the Backup Servers use AFS's distributed
-database technology, Ubik, to distribute to all of the machines the copy of
-the database with the highest version number.
-<P>Use the commands in the <B>backup</B> suite to administer the Backup
-Database. It is advisable to create a backup copy of the
-<B>bdb.DB0</B> file on tape on a regular basis, using the UNIX
-<B>tar</B> command or another local disk backup utility.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf041.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf043.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf042.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf044.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRCACHEINFO" HREF="auarf002.htm#ToC_41">cacheinfo</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Defines configuration parameters for the Cache Manager
-<P><STRONG>Description</STRONG>
-<P>The <B>cacheinfo</B> file defines configuration parameters for the
-Cache Manager, which reads the file as it initializes.
-<P>The file contains a single line of ASCII text and must reside in the
-<B>/usr/vice/etc</B> directory. Use a text editor to create it
-during initial configuration of the client machine; the required format
-is as follows:
-<PRE> <VAR>mount_dir</VAR>:<VAR>cache_dir</VAR>:<VAR>cache_size</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>mount_dir</VAR>
-</B><DD>Names the local disk directory at which the Cache Manager mounts the AFS
-namespace. It must exist before the <B>afsd</B> program
-runs. The conventional value is <B>/afs</B>. Using any other
-value prevents traversal of pathnames that begin with <B>/afs</B> (such as
-pathnames to files in foreign cells that do use the conventional name).
-The <B>-mountdir</B> argument to the <B>afsd</B> command overrides
-this value.
-<P><DT><B><VAR>cache_dir</VAR>
-</B><DD>Names the local disk directory to use as a cache. It must exist
-before the <B>afsd</B> program runs. The standard value is
-<B>/usr/vice/cache</B>, but it is acceptable to substitute a directory on
-a partition with more available space. Although the Cache Manager
-ignores this field when configuring a memory cache, a value must always appear
-in it. The <B>-cachedir</B> argument to the <B>afsd</B> command
-overrides this value.
-<P><DT><B><VAR>cache_size</VAR>
-</B><DD>Specifies the cache size as a number of 1-kilobyte blocks. Larger
-caches generally yield better performance, but a disk cache must not exceed
-90% of the space available on the cache partition (85% for AIX systems), and a
-memory cache must use no more than 25% of available machine memory.
-<P>The <B>-blocks</B> argument to the <B>afsd</B> command overrides
-this value. To reset cache size without rebooting on a machine that
-uses disk caching, use the <B>fs setcachesize</B> command. To
-display the current size of a disk or memory cache between reboots, use the
-<B>fs getcacheparms</B> command.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>cacheinfo</B> file mounts the AFS namespace at
-<B>/afs</B>, establishes a disk cache in the <B>/usr/vice/cache</B>
-directory, and defines cache size as 50,000 1-kilobyte blocks.
-<PRE> /afs:/usr/vice/cache:50000
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf143.htm#HDRFS_GETCACHEPARMS">fs getcacheparms</A>
-<P><A HREF="auarf158.htm#HDRFS_SETCACHESIZE">fs setcachesize</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf042.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf044.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf043.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf045.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFMSLOG" HREF="auarf002.htm#ToC_42">fms.log</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Records output from the <B>fms</B> command
-<P><STRONG>Description</STRONG>
-<P>The <B>fms.log</B> file records the output generated by the
-<B>fms</B> command. The output includes two numbers that can appear
-in a tape device's entry in the <B>/usr/afs/backup/tapeconfig</B>
-file on the Tape Coordinator machine to which the tape device is
-attached:
-<UL>
-<P><LI>The capacity in bytes of the tape in the device
-<P><LI>The size in bytes of the end-of-file (EOF) marks (often referred to simply
-as <I>filemarks</I>) that the tape device writes
-</UL>
-<P>When transferring the numbers recorded in this file to the
-<B>tapeconfig</B> file, adjust them as specified on the reference page for
-the <B>tapeconfig</B> file, to improve Tape Coordinator performance during
-dump operations.
-<P>If the <B>fms.log</B> file does not already exist in the current
-working directory, the <B>fms</B> command interpreter creates it.
-In this case, the directory's mode bits must grant the <B>rwx</B>
-(<B>read</B>, <B>write</B>, and <B>execute</B>) permissions to the
-issuer of the command. If there is an existing file, the command
-interpreter overwrites it, so the file's mode bits need to grant only the
-<B>w</B> permission to the issuer of the <B>fms</B> command.
-The <B>fms</B> command interpreter also writes similar information to the
-standard output stream as it runs.
-<P>The file is in ASCII format. To display its contents, log onto the
-client machine and use a text editor or a file display command such as the
-UNIX <B>cat</B> command. By default, the mode bits on the
-<B>fms.log</B> file grant the required <B>r</B> permission only
-to the owner (which is the local superuser <B>root</B> by default).
-<P><STRONG>Output</STRONG>
-<P>The first few lines of the file provide a simple trace of the
-<B>fms</B> command interpreter's actions, specifying (for example)
-how many blocks it wrote on the tape. The final two lines in the file
-specify tape capacity and filemark size in bytes, using the following
-format:
-<PRE> Tape capacity is <VAR>tape_size</VAR> bytes
- File marks are <VAR>filemark_size</VAR> bytes
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example of the <B>fms.log</B> file specifies that
-the tape used during the execution of the <B>fms</B> command had a
-capacity of 2,136,604,672 bytes, and that the tape device writes filemarks of
-size 1,910,220 bytes.
-<PRE> fms test started
- wrote 130408 blocks
- Tape capacity is 2136604672 bytes
- File marks are 1910220 bytes
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf130.htm#HDRFMS">fms</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf043.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf045.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf044.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf046.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKASERVERDB" HREF="auarf002.htm#ToC_43">kaserver.DB0 and kaserver.DBSYS1</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4011"></A>
-<A NAME="IDX4012"></A>
-<A NAME="IDX4013"></A>
-<A NAME="IDX4014"></A>
-<A NAME="IDX4015"></A>
-<P>Contain the Authentication Database and associated log
-<P><STRONG>Description</STRONG>
-<P>The <B>kaserver.DB0</B> file contains the Authentication
-Database, which records server encryption keys and an encrypted form of all
-user passwords. The Authentication Server (<B>kaserver</B> process)
-uses the information in the database to enable secured communications between
-AFS server and client processes.
-<P>The <B>kaserver.DBSYS1</B> file is a log file in which the
-Authentication Server logs each database operation before performing
-it. When an operation is interrupted, the Authentication Server replays
-the log to complete the operation.
-<P>Both files are in binary format and reside in the <B>/usr/afs/db</B>
-directory on each of the cell's database server machines. When the
-Authentication Server starts or restarts on a given machine, it establishes a
-connection with its peers and verifies that its copy of the database matches
-the copy on the other database server machines. If not, the
-Authentication Servers call on AFS's distributed database technology,
-Ubik, to distribute to all of the machines the copy of the database with the
-highest version number.
-<P>Always use the commands in the <B>kas</B> suite to administer the
-Authentication Database. It is advisable to create an archive copy of
-the database on a regular basis, using a tool such as the UNIX <B>tar</B>
-command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf180.htm#HDRKADB_CHECK">kadb_check</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf044.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf046.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf045.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf047.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKASERVERAUXDB" HREF="auarf002.htm#ToC_44">kaserverauxdb</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4016"></A>
-<A NAME="IDX4017"></A>
-<P>Records failed authentication attempts
-<P><STRONG>Description</STRONG>
-<P>The file <B>kaserverauxdb</B> records failed authentication attempts
-for the local Authentication Server. The server creates it
-automatically in the <B>/usr/afs/local</B> directory by default; use
-the <B>-localfiles</B> argument to the <B>kaserver</B> command to
-specify an alternate directory.
-<P>The <B>kaserverauxdb</B> file is an internal database used by the
-Authentication Server to prevent access by users who have exceeded the limit
-on failed authentication attempts defined in their Authentication Database
-entry. The Authentication Server refuses further attempts to
-authenticate to an account listed in the database until either an AFS system
-administrator issues the <B>kas unlock</B> command to unlock the account,
-or the timeout period defined in the user's Authentication Database entry
-passes.
-<P>The <B>kaserverauxdb</B> file is in binary format, so its contents are
-not directly accessible. However, the output from the <B>kas
-examine</B> command reports an account's maximum number of failed
-attempts, the lockout time, and whether the account is currently
-locked.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf045.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf047.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf046.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf048.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPRDBDB" HREF="auarf002.htm#ToC_45">prdb.DB0 and prdb.DBSYS1</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4018"></A>
-<A NAME="IDX4019"></A>
-<A NAME="IDX4020"></A>
-<A NAME="IDX4021"></A>
-<A NAME="IDX4022"></A>
-<P>Contain the Protection Database and associated log
-<P><STRONG>Description</STRONG>
-<P>The <B>prdb.DB0</B> file contains the Protection Database, which
-maps AFS user, machine, and group names to their respective IDs (AFS UIDs and
-GIDs) and tracks group memberships. The Protection Server
-(<B>ptserver</B> process) uses the information in the database to help the
-File Server grant data access to authorized users.
-<P>The <B>prdb.DBSYS1</B> file is a log file in which the
-Protection Server logs each database operation before performing it.
-When an operation is interrupted, the Protection Server replays the log to
-complete the operation.
-<P>Both files are in binary format and reside in the <B>/usr/afs/db</B>
-directory on each of the cell's database server machines. When the
-Protection Server starts or restarts on a given machine, it establishes a
-connection with its peers and verifies that its copy of the database matches
-the copy on the other database server machines. If not, the Protection
-Servers call on AFS's distributed database technology, Ubik, to
-distribute to all of the machines the copy of the database with the highest
-version number.
-<P>Always use the commands in the <B>pts</B> suite to administer the
-Protection Database. It is advisable to create an archive copy of the
-database on a regular basis, using a tool such as the UNIX <B>tar</B>
-command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf209.htm#HDRPRDB_CHECK">prdb_check</A>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf046.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf048.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf047.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf049.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSALVAGELOCK" HREF="auarf002.htm#ToC_46">salvage.lock</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Prevents multiple simultaneous salvage operations on a partition
-<P><STRONG>Description</STRONG>
-<P>The <B>salvage.lock</B> file guarantees that only one Salvager
-(<B>salvager</B> process) runs at a time on a file server machine (the
-single process can fork multiple subprocesses to salvage multiple partitions
-in parallel). As the Salvager initializes, it creates the empty
-(zero-length) file in the <B>/usr/afs/local</B> directory and invokes the
-<B>flock</B> system call on it. It removes the file when it
-completes the salvage operation. Because the Salvager must lock the
-file to run, only one Salvager can run at a time.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf047.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf049.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf048.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf050.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSYSID" HREF="auarf002.htm#ToC_47">sysid</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4023"></A>
-<A NAME="IDX4024"></A>
-<A NAME="IDX4025"></A>
-<A NAME="IDX4026"></A>
-<P>Lists file server machine interface addresses registered in VLDB
-<P><STRONG>Description</STRONG>
-<P>The <B>sysid</B> file records the network interface addresses that the
-File Server (<B>fileserver</B> process) registers in the Volume Location
-Database (VLDB) for the local file server machine.
-<P>Each time the File Server restarts, it builds a list of interfaces on the
-local machine by reading the <B>/usr/afs/local/NetInfo</B> file, if it
-exists. If the file does not exist, the File Server uses the list of
-network interfaces configured with the operating system. It then
-removes from the list any addresses that appear in the
-<B>/usr/afs/local/NetRestrict</B> file, if it exists. The File
-Server records the resulting list in the binary-format <B>sysid</B> file
-and registers the interfaces in the VLDB.
-<P>When the Cache Manager requests volume location information, the Volume
-Location (VL) Server provides all of the interfaces registered for each server
-machine that houses the volume. This enables the Cache Manager to make
-use of multiple addresses when accessing AFS data stored on a multihomed file
-server machine.
-<P><STRONG>Cautions</STRONG>
-<P>The <B>sysid</B> file is unique to each file server machine, and must
-not be copied from one machine to another. If it is a common practice
-in the cell to copy the contents of the <B>/usr/afs/local</B> directory
-from an existing file server machine to a newly installed one, be sure to
-remove the <B>sysid</B> file from the new machine before starting the
-<B>fs</B> trio of processes, which includes the <B>fileserver</B>
-process.
-<P>Some versions of AFS limit how many of a file server machine's
-interface addresses that can be registered. Consult the <I>IBM AFS
-Release Notes</I>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf025.htm#HDRSV_NETINFO">NetInfo (server version)</A>
-<P><A HREF="auarf027.htm#HDRSV_NETRESTRICT">NetRestrict (server version)</A>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf048.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf050.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf049.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf051.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRTAPECONFIG" HREF="auarf002.htm#ToC_48">tapeconfig</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4027"></A>
-<A NAME="IDX4028"></A>
-<A NAME="IDX4029"></A>
-<P>Defines configuration parameters for all tape devices and backup data files
-on a Tape Coordinator machine
-<P><STRONG>Description</STRONG>
-<P>The <B>tapeconfig</B> file defines basic configuration parameters for
-all of the tape devices or backup data files available for backup operations
-on a Tape Coordinator machine. The file is in ASCII format and must
-reside in the local <B>/usr/afs/backup</B> directory. The
-instruction for each tape device or backup data file appears on its own line
-and each has the following format:
-<PRE> [<VAR>capacity</VAR> <VAR>filemark_size</VAR>] <VAR>device_name</VAR> <VAR>port_offset</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>capacity</VAR>
-</B><DD>Specifies the capacity of the tapes used with a tape device, or the amount
-of data to write into a backup data file. The Tape Coordinator refers
-to this value in two circumstances:
-<UL>
-<P><LI>When the capacity field of a tape or backup data file's label is
-empty (because the tape has never been labeled). The Tape Coordinator
-records this value on the label and uses it when determining how much data it
-can write to the tape or file during a <B>backup dump</B> or <B>backup
-savedb</B> operation. If there is already a capacity value on the
-label, the Tape Coordinator uses it instead.
-<P><LI>When the <B>-size</B> argument is omitted the first time the
-<B>backup labeltape</B> command is used on a given tape or file.
-The Tape Coordinator copies this value into the label's capacity
-field.
-</UL>
-<P>
-<P>The Tape Coordinator uses this capacity value or the one on the Backup
-System tape label to track how much space remains as it writes data to a tape
-or backup data file. The appropriate value to record for a tape depends
-on the size of the tapes usually used in the device and whether it has a
-compression mode; for suggested values, see the <I>IBM AFS
-Administration Guide</I> chapter on configuring the Backup System. If
-using a value obtained from the <B>fms</B> command, reduce it by 10% to
-15% before recording it in the file.
-<P>For a backup data file, it is best to provide a value that helps the Tape
-Coordinator avoid reaching the end-of-file (EOF) unexpectedly. Make it
-at least somewhat smaller than the amount of space available on the partition
-housing the file when the dump operation begins, and never larger than the
-maximum file size allowed by the operating system.
-<P>Specify a (positive) integer or decimal value followed by a letter than
-indicates units, with no intervening space. In a decimal number, the
-number of digits after the decimal point must not translate to fractions of
-bytes. The maximum acceptable value is 2048 GB (2 TB). The
-acceptable units letters are as follows; if the letter is omitted, the
-default is kilobytes.
-<P>
-<UL>
-<P><LI><B>k</B>or <B>K</B> for kilobytes (KB)
-<P><LI><B>m</B> or <B>M</B> for megabytes (MB)
-<P><LI><B>g</B> or <B>G</B> for gigabytes (GB)
-<P><LI><B>t</B> or <B>T</B> for terabytes (TB)
-</UL>
-<P>If this field is omitted, the Tape Coordinator uses the maximum acceptable
-value (2048 GB or 2 TB). Either leave both this field and the
-<VAR>filemark_size</VAR> field empty, or provide a value in both of them.
-<P><DT><B><VAR>filemark_size</VAR>
-</B><DD>Specifies the size of a tape device's filemarks (also called
-end-of-file or EOF marks), which is set by the device's
-manufacturer. In a dump to tape, the Tape Coordinator inserts filemarks
-at the boundary between the data from each volume, so the filemark size
-affects how much space is available for actual data.
-<P>The appropriate value to record for a tape depends on the size of the tapes
-usually used in the device and whether it has a compression mode; for
-suggested values, see the <I>IBM AFS Administration Guide</I> chapter on
-configuring the Backup System. If using a value obtained from the
-<B>fms</B> command, increase it by 10% to 15% before recording it in the
-file.
-<P>For backup data files, record a value of <B>0</B> (zero). The
-Tape Coordinator actually ignores this field for backup data files, because it
-does not use filemarks when writing to a file.
-<P>Use the same notation as for the <VAR>capacity</VAR> field, but note that the
-default units is bytes rather than kilobytes. The maximum acceptable
-value is 2048 GB.
-<P>If this field is empty, the Tape Coordinator uses the value <B>0</B>
-(zero). Either leave both this field and the <VAR>capacity</VAR> field
-empty, or provide a value in both of them.
-<P><DT><B><VAR>device_name</VAR>
-</B><DD>Specifies the complete pathname of the tape device or backup data
-file. The format of tape device names depends on the operating system,
-but on UNIX systems device names generally begin with the string
-<B>/dev/</B>. For a backup data file, this field defines the
-complete pathname; for a discussion of suggested naming conventions see
-the description of the <B>FILE</B> instruction in <A HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>.
-<P><DT><B><VAR>port_offset</VAR>
-</B><DD>Specifies the port offset number associated with this combination of Tape
-Coordinator and tape device or backup data file.
-<P>Acceptable values are the integers <B>0</B> through <B>58510</B>
-(the Backup System can track a maximum of 58,511 port offset numbers).
-Each value must be unique among the cell's Tape Coordinators, but any
-number of them can be associated with a single machine. Port offset
-numbers need not be assigned sequentially, and can appear in any order in the
-<B>tapeconfig</B> file. Assign port offset <B>0</B> to the Tape
-Coordinator for the tape device or backup data file used most often for backup
-operations; doing so will allow the operator to omit the
-<B>-portoffset</B> argument from the largest possible number of
-<B>backup</B> commands.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>Creating the file requires UNIX <B>w</B> (<B>write</B>) and
-<B>x</B> (<B>execute</B>) permissions on the
-<B>/usr/afs/backup</B> directory. Editing the file requires UNIX
-<B>w</B> (<B>write</B>) permission on the file.
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>tapeconfig</B> file configures three tape
-devices and a backup data file. The first device has device name
-<B>/dev/rmt/0h</B>, and is assigned port offset <B>0</B> because it
-will be the most frequently used device for all backup operations in the
-cell. Its default tape capacity is 2 GB and filemark size is 1
-MB. The <B>/dev/rmt/3h</B> drive has half the capacity but a much
-smaller filemark size; its port offset is <B>3</B>. The third
-device listed, <B>/dev/rmt/4h</B>, has the same capacity and filemark size
-as the first device and is assigned port offset <B>2</B>. Port
-offset <B>4</B> is assigned to the backup data file <B>/dev/FILE</B>,
-which is actually a symbolic link to the actual file located elsewhere on the
-local disk. The Tape Coordinator writes up to 1.5 GB into the
-file; as recommended, the filemark size is set to zero.
-<PRE> 2G 1M /dev/rmt/0h 0
- 1g 4k /dev/rmt/3h 3
- 2G 1m /dev/rmt/4h 2
- 1.5G 0 /dev/FILE 4
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P><A HREF="auarf130.htm#HDRFMS">fms</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf049.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf051.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf050.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf052.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVLDBDB" HREF="auarf002.htm#ToC_49">vldb.DB0 and vldb.DBSYS1</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4030"></A>
-<A NAME="IDX4031"></A>
-<A NAME="IDX4032"></A>
-<A NAME="IDX4033"></A>
-<A NAME="IDX4034"></A>
-<A NAME="IDX4035"></A>
-<P>Contain the Volume Location Database and associated log
-<P><STRONG>Description</STRONG>
-<P>The file <B>vldb.DB0</B> contains the Volume Location Database
-(VLDB), which tracks the location of all AFS volumes stored on file server
-machines in the cell. The Volume Location (VL) Server
-(<B>vlserver</B> process) provides information from the database to Cache
-Managers when they need to access AFS data.
-<P>The file <B>vldb.DBSYS1</B> is a log file in which the VL Server
-logs each database operation before performing it. When an operation is
-interrupted, the VL Server replays the log to complete the operation.
-<P>Both files are in binary format and reside in the <B>/usr/afs/db</B>
-directory on each of the cell's database server machines. When the
-VL Server starts or restarts on a given machine, it establishes a connection
-with its peers and verifies that its copy of the database matches the copy on
-the other database server machines. If not, the VL Servers call on
-AFS's distributed database technology, Ubik, to distribute to all of the
-machines the copy of the database with the highest version number.
-<P>Always use the commands in the <B>vos</B> suite to administer the
-VLDB. It is advisable to create an archive copy of the database on a
-regular basis, using a tool such as the UNIX <B>tar</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf248.htm#HDRVLDB_CHECK">vldb_check</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf050.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf052.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf051.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf053.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAFSMONCONFIG" HREF="auarf002.htm#ToC_50">afsmonitor Configuration File</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4036"></A>
-<A NAME="IDX4037"></A>
-<P>Provides instructions for the <B>afsmonitor</B> command
-<P><STRONG>Description</STRONG>
-<P>The <B>afsmonitor</B> configuration file determines which machines the
-<B>afsmonitor</B> command probes for File Server or Cache Manager
-statistics and which statistics it gathers. Use the <B>-config</B>
-argument to the <B>afsmonitor</B> command to identify the configuration
-file to use.
-<P>The instructions that can appear in the configuration file are as
-follows:
-<DL>
-<P><DT><B><TT>cm <VAR>host_name</VAR></TT>
-</B><DD>Names a client machine for which to display Cache Manager
-statistics. The order of <B>cm</B> lines in the file determines the
-order in which client machines appear from top to bottom on the <TT>System
-Overview</TT> and <TT>Cache Managers</TT> output screens.
-<P><DT><B><TT>fs <VAR>host_name</VAR></TT>
-</B><DD>Names a file server machine for which to display File Server
-statistics. The order of <B>fs</B> lines in the file determines the
-order in which file server machines appear from top to bottom on the
-<TT>System Overview</TT> and <TT>File Servers</TT> output screens.
-<P><DT><B><TT>thresh fs | cm <VAR>field_name</VAR> <VAR>thresh_val</VAR>
-[<VAR>cmd_to_run</VAR>] [<VAR>arg</VAR><SUB>1</SUB>] . . .
-[<VAR>arg</VAR><SUB>n</SUB>]</TT>
-</B><DD>Assigns the threshold value <VAR>thresh_val</VAR> to the statistic
-<VAR>field_name</VAR>, for either a File Server statistic (<B>fs</B>) or a
-Cache Manager statistic (<B>cm</B>). The optional
-<VAR>cmd_to_execute</VAR> field names a binary or script to execute each time
-the value of the statistic changes from being below <VAR>thresh_val</VAR> to
-being at or above <VAR>thresh_val</VAR>. A change between two values that
-both exceed <VAR>thresh_val</VAR> does not retrigger the binary or
-script. The optional <VAR>arg</VAR><SUB>1</SUB> through
-<VAR>arg</VAR><SUB>n</SUB> fields are additional values that the
-<B>afsmonitor</B> program passes as arguments to the
-<VAR>cmd_to_execute</VAR> command. If any of them include one or more
-spaces, enclose the entire field in double quotes.
-<p>The <b>afsmonitor</b> program passes the following parameters to the
-<var>cmd_to_execute</var>:
-<p><dt><b><var>host_name</var> fs|cm <var>field_name</var>
-<var>threshold_val</var>
-<var>actual_val</var> [<<var>arg</var><sub>1</sub>>]
-. . . [<<var>arg</var><sub>n</sub>>]</b>
-<P>The parameters <B>fs</B>, <B>cm</B>, <VAR>field_name</VAR>,
-<VAR>threshold_val</VAR>, and <VAR>arg</VAR><SUB>1</SUB> through
-<VAR>arg</VAR><SUB>n</SUB> correspond to the values with the same name on the
-<B>thresh</B> line. The <VAR>host_name</VAR> parameter identifies the
-file server or client machine where the statistic has crossed the threshold,
-and the <VAR>actual_val</VAR> parameter is the actual value of
-<VAR>field_name</VAR> that exceeds the threshold value.
-<P>Use the <B>thresh</B> line to set either a global threshold, which
-applies to all file server machines listed on <B>fs</B> lines or client
-machines listed on <B>cm</B> lines in the configuration file, or a
-machine-specific threshold, which applies to only one file server or client
-machine.
-<UL>
-<P><LI>To set a global threshold, place the <B>thresh</B> line before any of
-the <B>fs</B> or <B>cm</B> lines in the file.
-<P><LI>To set a machine-specific threshold, place the <B>thresh</B> line
-below the corresponding <B>fs</B> or <B>cm</B> line, and above any
-other <B>fs</B> or <B>cm</B> lines. A machine-specific
-threshold value always overrides the corresponding global threshold, if
-set. Do not place a <B>thresh fs</B> line directly after a
-<B>cm</B> line or a <B>thresh cm</B> line directly after a
-<B>fs</B> line.
-</UL>
-<P><DT><B><TT>show fs | cm <VAR>field/group/section</VAR></TT>
-</B><DD>Specifies which individual statistic, group of statistics, or section of
-statistics to display on the <TT>File Servers</TT> screen (<B>fs</B>) or
-<TT>Cache Managers</TT> screen (<B>cm</B>) and the order in which to
-display them. The appendix of <B>afsmonitor</B> statistics in the
-<I>IBM AFS Administration Guide</I> specifies the group and section to
-which each statistic belongs. Include as many <B>show</B> lines as
-necessary to customize the screen display as desired, and place them anywhere
-in the file. The top-to-bottom order of the <B>show</B> lines in
-the configuration file determines the left-to-right order in which the
-statistics appear on the corresponding screen.
-<P>If there are no <B>show</B> lines in the configuration file, then the
-screens display all statistics for both Cache Managers and File
-Servers. Similarly, if there are no <B>show fs</B> lines, the
-<TT>File Servers</TT> screen displays all file server statistics, and if
-there are no <B>show cm</B> lines, the <TT>Cache Managers</TT> screen
-displays all client statistics.
-<P><DT><B># <VAR>comments</VAR>
-</B><DD>Precedes a line of text that the <B>afsmonitor</B> program ignores
-because of the initial number (<B>#</B>) sign, which must appear in the
-very first column of the line.
-</DL>
-<P>For a list of the values that can appear in the
-<VAR>field/group/section</VAR> field of a <B>show</B> instruction, see the
-<B>afsmonitor</B> statistics appendix to the <I>IBM AFS Administration
-Guide</I>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf059.htm#HDRAFSMONITOR">afsmonitor</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf051.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf053.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf052.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf054.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPACKAGECONFIG" HREF="auarf002.htm#ToC_51">package Configuration File</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4038"></A>
-<A NAME="IDX4039"></A>
-<A NAME="IDX4040"></A>
-<P>Provides instructions for the <B>package</B> command
-<P><STRONG>Description</STRONG>
-<P>The <B>package</B> configuration file defines the file system elements
-that the <B>package</B> command creates or alters on the local disk of an
-AFS client machine it is configuring. Use the <B>-config</B> or
-<B>-fullconfig</B> argument to the <B>package</B> command to identify
-the configuration file to use.
-<P><B>Summary of Configuration File Instructions</B>
-<P>The configuration file can include one or more instances of each of the
-following instructions, each on its own line. A more detailed
-description of each instruction's syntax follows this list.
-<DL>
-<P><DT><B>B
-</B><DD>Defines a block special device, such as a disk, which deals with input in
-units of multi-byte command blocks
-<P><DT><B>C
-</B><DD>Defines a character special device, such as a terminal or tty, which deals
-with input in single character units
-<P><DT><B>D
-</B><DD>Creates a directory
-<P><DT><B>F
-</B><DD>Creates or alters a file to match the contents of a specified source file
-<P><DT><B>L
-</B><DD>Creates a symbolic link
-<P><DT><B>S
-</B><DD>Defines a socket, which is a communications device for UDP and TCP/IP
-connections
-<P><DT><B>%define
-</B><DD>Defines a variable or declares a string as defined
-<P><DT><B>%ifdef
-</B><DD>Specifies an action to perform if a certain string is declared or defined
-<P><DT><B>%ifndef
-</B><DD>Specifies an action to perform if a certain string is not declared or
-defined
-<P><DT><B>%include
-</B><DD>Includes a library file
-<P><DT><B>%undef
-</B><DD>Declares a string not to be defined, or a variable no longer to have a
-value
-</DL>
-<P><B>The B and C Instructions for Defining Block and Character Special
-Devices</B>
-<A NAME="IDX4041"></A>
-<A NAME="IDX4042"></A>
-<A NAME="IDX4043"></A>
-<A NAME="IDX4044"></A>
-<A NAME="IDX4045"></A>
-<A NAME="IDX4046"></A>
-<A NAME="IDX4047"></A>
-<A NAME="IDX4048"></A>
-<A NAME="IDX4049"></A>
-<A NAME="IDX4050"></A>
-<A NAME="IDX4051"></A>
-<A NAME="IDX4052"></A>
-<A NAME="IDX4053"></A>
-<A NAME="IDX4054"></A>
-<A NAME="IDX4055"></A>
-<P>The <B>B</B> instruction in a <B>package</B> configuration file
-defines a block special device, such as a disk, that deals with input in units
-of multi-byte command blocks. The <B>C</B> instruction defines a
-character special device, such as a terminal or tty, that deals with input in
-single character units. They share a common syntax:
-<PRE> {<B>B </B>| <B>C</B>} <VAR>device_name</VAR> <VAR>major_device</VAR> <VAR>minor_device</VAR> <VAR>owner</VAR> <VAR>group</VAR> <VAR>mode_bits</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>B
-</B><DD>Indicates the definition of a block special device. It must be a
-capital letter.
-<P><DT><B>C
-</B><DD>Indicates the definition of character special device. It must be a
-capital letter.
-<P><DT><B><VAR>device_name</VAR>
-</B><DD>Names the special device to define. To learn the name format
-appropriate to the machine's system type, consult the hardware or
-operating system documentation.
-<P><DT><B><VAR>major_device</VAR>
-</B><DD>Specifies the device's major device number in decimal format.
-To learn the correct value for the machine's system type, consult the
-hardware or operating system documentation.
-<P><DT><B><VAR>minor_device</VAR>
-</B><DD>Specifies the device's minor device number in one of hexadecimal,
-octal, or decimal format. Precede a hexadecimal number with the string
-<B>0x</B> (zero and the letter <B>x</B>) or an octal number with a
-<B>0</B> (zero). A number without either prefix is interpreted as a
-decimal. To learn the correct value for the machine's system type,
-consult the hardware or operating system documentation.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the device's owner in the output from the UNIX <B>ls -l</B>
-command.
-<P><DT><B><VAR>group</VAR>
-</B><DD>Specifies the group name or UNIX group ID (GID) of the group to be
-designated the device's group in the output from the UNIX <B>ls
--lg</B> command.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Defines the device's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-</DL>
-<P><B>The D Instruction for Creating a Directory</B>
-<A NAME="IDX4056"></A>
-<A NAME="IDX4057"></A>
-<A NAME="IDX4058"></A>
-<A NAME="IDX4059"></A>
-<A NAME="IDX4060"></A>
-<A NAME="IDX4061"></A>
-<A NAME="IDX4062"></A>
-<P>The <B>D</B> instruction in a <B>package</B> configuration file
-creates a directory on the local disk. If a symbolic link, file, or
-other element on the local disk has the same name, it is replaced with a
-directory. If the directory already exists, its owner, group, and mode
-bits are changed if necessary to conform with the instruction. The
-instruction has the following syntax:
-<PRE> <B>D</B>[<VAR>update_code</VAR>] <VAR>directory</VAR> <VAR>owner</VAR> <VAR>group</VAR> <VAR>mode_bits</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>D
-</B><DD>Indicates the creation of a directory. It must be a capital
-letter.
-<P><DT><B><VAR>update_code</VAR>
-</B><DD>Modulates the directory creation instruction. It is optional and
-follows the letter <B>D</B> directly, without an intervening space.
-Choose one of the two acceptable values:
-<DL>
-<P><DT><B>X
-</B><DD>Indicates that the directory is a <B>lost+found</B> directory (used by
-the <B>fsck</B> program).
-<P><DT><B>R
-</B><DD>Removes any subdirectory (along its contents) or file that exists in the
-existing directory on the local disk but for which an instruction does not
-appear in the configuration file.
-</DL>
-<P><DT><B><VAR>directory</VAR>
-</B><DD>Specifies the full pathname of the directory to create.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the directory's owner in the output from the UNIX <B>ls -ld</B>
-command.
-<P><DT><B><VAR>group</VAR>
-</B><DD>Specifies the name or UNIX group ID (GID) of the group to be designated
-the directory's group in the output from the UNIX <B>ls -lgd</B>
-command.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Defines the directory's UNIX mode bits. Acceptable values are
-the standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>drwxr-xr-x</B>, and <B>644</B> to <B>drw-r--r--</B>.
-</DL>
-<P><B>The F Instruction for Creating or Updating a File</B>
-<A NAME="IDX4063"></A>
-<A NAME="IDX4064"></A>
-<A NAME="IDX4065"></A>
-<A NAME="IDX4066"></A>
-<A NAME="IDX4067"></A>
-<A NAME="IDX4068"></A>
-<A NAME="IDX4069"></A>
-<P>The <B>F</B> instruction in a <B>package</B> configuration file
-creates or updates a file on the local disk by copying in the contents of the
-indicated source file, which can reside in AFS or on the local disk. If
-the <B>package</B> command interpreter cannot access the source file, it
-exits without executing any instruction in the configuration file.
-<P>If a file with the same name already exists on disk, the <B>package</B>
-command overwrites it with the contents of the source file, unless the
-<B>I</B> update code is used to prevent that. To add a
-<B>.old</B> extension to the current version of the file, include
-the <B>O</B> update code. To have the machine reboot automatically
-after the <B>package</B> program completes, include the <B>Q</B>
-update code.
-<P>If a symbolic link, directory, or other element on the local disk has the
-same name, it is replaced with the file (a directory's contents are first
-removed as necessary).
-<P>The instruction has the following syntax:
-<PRE> <B>F</B>[<VAR>update_code</VAR>] <VAR>file</VAR> <VAR>source_file</VAR> [<VAR>owner group mode_bits</VAR>]
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>F
-</B><DD>Indicates the creation or update of a file. It must be a capital
-letter.
-<P><DT><B><VAR>update_code</VAR>
-</B><DD>Modulates the file creation instruction. It is optional and follows
-the letter <B>F</B> directly, without an intervening space. Choose
-one or more of the four acceptable values, and list them in any order:
-<DL>
-<P><DT><B>A
-</B><DD>Indicates that the pathname in the <VAR>source_file</VAR> field is the
-complete pathname of the source file, including the filename. If this
-argument is omitted, the <B>package</B> command appends the pathname in
-the <VAR> file</VAR> field to the pathname in the <VAR>source_file</VAR> field to
-derive the source file's full name. This code allows the source
-and target filenames to differ.
-<P><DT><B>I
-</B><DD>Preserves the existing file called <VAR>file</VAR>, rather than overwriting
-it.
-<P><DT><B>O
-</B><DD>Saves the existing version of the file by appending a
-<B>.old</B> extension to it.
-<P><DT><B>Q
-</B><DD>Causes the <B>package</B> command to exit with status code
-<B>4</B> if it overwrites the file. If the standard
-<B>package</B>-related changes have been made to the machine's AFS
-initialization file, then status code <B>4</B> causes the machine to
-reboot automatically. Use this code when the machine must reboot if
-updates to the file are to have any effect (for example, if the operating
-system file--<B>/vmunix</B> or equivalent--has changed).
-</DL>
-<P><DT><B><VAR>file</VAR>
-</B><DD>Specifies the complete pathname on the local disk of the file to create or
-update, including the filename as the final element.
-<P><DT><B><VAR>source_file</VAR>
-</B><DD>Specifies the pathname (local or AFS) of the file to copy to the local
-disk.
-<P>If the <B>A</B> update code is included, specify the source file's
-complete pathname. Otherwise, the <B>package</B> command derives
-the source file's full name by appending the <VAR>file</VAR> pathname to
-this pathname. For example, if the <B>A</B> update code is not
-included and the file <B>/afs/abc.com/rs_aix42/bin/grep</B> is the
-source file for the <B>/bin/grep</B> binary, the proper value in this
-field is <B>/afs/abc.com/rs_aix42</B>.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the file's owner in the output from the UNIX <B>ls -l</B>
-command.
-<P>To copy the source file's owner to the target file, leave this field
-empty. In this case, the <VAR>group</VAR> and <VAR>mode_bits</VAR> fields
-must also be empty.
-<P><DT><B><VAR>group</VAR>
-</B><DD>Specifies the name or UNIX group ID (GID) of the group to be designated
-the file's group in the output from the UNIX <B>ls -lg</B>
-command.
-<P>To copy the source file's group to the target file, leave this field
-empty. In this case, the <VAR> owner</VAR> and <VAR>mode_bits</VAR> fields
-must also be empty.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Defines the file's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-<P>To copy the source file's mode bits to the target file, leave this
-field empty. In this case, the <VAR>owner</VAR> and <VAR>group</VAR> fields
-must also be empty.
-</DL>
-<P><B>The L Instruction for Creating a Symbolic Link</B>
-<A NAME="IDX4070"></A>
-<A NAME="IDX4071"></A>
-<A NAME="IDX4072"></A>
-<A NAME="IDX4073"></A>
-<A NAME="IDX4074"></A>
-<A NAME="IDX4075"></A>
-<A NAME="IDX4076"></A>
-<P>The <B>L</B> instruction in a <B>package</B> configuration file
-creates a symbolic link on the local disk to a directory or file that exists
-either in AFS or elsewhere on the local disk. As with the standard UNIX
-<B>ln -s</B> command, the link is created even if the actual file or
-directory does not exist.
-<P>If a file or directory on the local disk already has the same name, the
-<B>package</B> command replaces it with a symbolic link.
-<P>The instruction has the following syntax:
-<PRE> <B>L</B>[<VAR>update_code</VAR>] <VAR>link</VAR> <VAR>actual_path</VAR> [<VAR>owner group mode_bits</VAR>]
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>L
-</B><DD>Indicates the creation of a symbolic link. It must be a capital
-letter.
-<P><DT><B><VAR>update_code</VAR>
-</B><DD>Modulates the link creation instruction. It is optional and follows
-the letter <B>L</B> directly, without an intervening space. Choose
-one or both of the acceptable values, and list them in any order:
-<DL>
-<P><DT><B>A
-</B><DD>Indicates that the pathname in the <VAR>actual_path</VAR> field is the
-complete pathname of the actual directory or file (including the filename for
-a file). If this argument is omitted, the <B>package</B> command
-appends the value in the <VAR>link</VAR> field to the pathname in the
-<VAR>actual_path</VAR> field to derive the actual directory or file's full
-name. This code allows the name of the symbolic link and actual
-directory or file to differ.
-<P><DT><B>I
-</B><DD>Preserves the existing symbolic link called <VAR>link</VAR>, rather than
-overwriting it.
-</DL>
-<P><DT><B><VAR>link</VAR>
-</B><DD>Specifies the complete local disk pathname of the symbolic link to
-create.
-<P><DT><B><VAR>actual_path</VAR>
-</B><DD>Specifies the pathname (local or AFS) of the directory or file to which
-the link refers. If the <B>A</B> update code is included, specify
-the directory or file's complete pathname. Otherwise, the
-<B>package</B> command derives the actual directory or file's full
-name by appending the value in the <VAR>link</VAR> field to this
-pathname. For example, if the <B>A</B> update code is not included
-and <B>/etc/ftpd</B> is a symbolic link to the file
-<B>/afs/abc.com/sun4x_56/etc/ftpd</B>, the proper value in this
-field is <B>/afs/abc.com/sun4x_56</B>.
-<P>The <B>package</B> command interpreter correctly handles pathnames that
-begin with the <B>./</B> (period, slash) or
-<B>../</B> (two periods, slash) notation, interpreting them
-relative to the current working directory from which the <B>package</B>
-command is invoked.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the symbolic link's owner in the output from the UNIX <B>ls -l</B>
-command.
-<P>To designate the issuer of the <B>package</B> command (usually, the
-local superuser <B>root</B>) as the symbolic link's owner, leave this
-field empty. In this case, the <VAR>group</VAR> and <VAR>mode_bits</VAR>
-fields must also be empty.
-<P><DT><B><VAR>group</VAR>
-</B><DD>Specifies the name or UNIX group ID (GID) of the group to be designated
-the link's group in the output from the UNIX <B>ls -lg</B>
-command.
-<P>To have the symbolic link's group match the default group associated
-with the <B>package</B> command's issuer, leave this field
-empty. The issuer is usually the local superuser <B>root</B> and
-the default group is designated in the issuer's entry in the local
-<B>/etc/passwd</B> file or equivalent. If this field is left empty,
-the <VAR>owner</VAR> and <VAR>mode_bits</VAR> fields must also be empty.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Defines the symbolic link's UNIX mode bits. Acceptable values
-are the standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-<P>Leaving this field empty sets the symbolic link's mode bits to
-<B>777</B> (<B>rwxrwxrwx</B>). In this case, the <VAR>owner</VAR>
-and <VAR>group</VAR> fields must also be empty.
-</DL>
-<P><B>The S Instruction for Creating a Socket</B>
-<A NAME="IDX4077"></A>
-<A NAME="IDX4078"></A>
-<A NAME="IDX4079"></A>
-<A NAME="IDX4080"></A>
-<A NAME="IDX4081"></A>
-<A NAME="IDX4082"></A>
-<A NAME="IDX4083"></A>
-<P>The <B>S</B> instruction in a <B>package</B> configuration file
-creates a socket (a communications device for UDP or TCP/IP connections) on
-the local disk. The instruction has the following syntax:
-<PRE> <B>S</B> <VAR>socket</VAR> [<VAR>owner group mode_bits</VAR>]
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>S
-</B><DD>Indicates the creation of a socket. It must be a capital
-letter.
-<P><DT><B><VAR>socket</VAR>
-</B><DD>Names the socket. The proper format depends on the local
-machine's operating system.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the socket's owner in the output from the UNIX <B>ls -l</B>
-command.
-<P>To designate the issuer of the <B>package</B> command (usually, the
-local superuser <B>root</B>) as the socket's owner, leave this field
-empty. In this case, the <VAR>group</VAR> and <VAR>mode_bits</VAR> fields
-must also be empty.
-<P><DT><B><VAR>group</VAR>
-</B><DD>Specifies the name or UNIX group ID (GID) of the group to be designated
-the socket's group in the output from the UNIX <B>ls -lg</B>
-command.
-<P>To have the symbolic link's group match the default group associated
-with the <B>package</B> command's issuer, leave this field
-empty. The issuer is usually the local superuser <B>root</B> and
-the default group is designated in the issuer's entry in the local
-<B>/etc/passwd</B> file or equivalent. If this field is left empty,
-the <VAR>owner</VAR> and <VAR>mode_bits</VAR> fields must also be empty.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Defines the socket's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-<P>Leaving this field empty sets the symbolic link's mode bits to
-<B>777</B> (<B>rwxrwxrwx</B>), modulated by the cell's
-umask. In this case, the <VAR>owner</VAR> and <VAR>group</VAR> fields must
-also be empty.
-</DL>
-<P><B>The %define or %undef Instructions Declaring or Undeclaring a
-Definition</B>
-<A NAME="IDX4084"></A>
-<A NAME="IDX4085"></A>
-<A NAME="IDX4086"></A>
-<A NAME="IDX4087"></A>
-<A NAME="IDX4088"></A>
-<A NAME="IDX4089"></A>
-<P>The <B>%define</B> instruction in a <B>package</B> configuration
-file declares or defines a variable, depending on its number of
-arguments:
-<UL>
-<P><LI>If followed by a single argument, it declares that argument to be
-defined. The argument is then available as a controller when mentioned
-in <B>%ifdef</B> and <B>%ifndef</B> statements, which evaluate to
-<B>true</B> and <B>false</B> respectively.
-<P><LI>If followed by two arguments, it defines the second argument as the value
-of the first. When the first argument appears later in this prototype
-or other prototype or library files as a variable--surrounded by curly
-braces and preceded by a dollar sign, as in the example
-<TT>${variable}</TT>--the <B>package</B> command interpreter
-substitutes the second argument for it.
-</UL>
-<P>The <B>%undef</B> statement negates the effect of a previous
-<B>%define</B> statement, declaring its argument to be defined no longer,
-or to have a value no longer if it is a variable.
-<P>The syntax for the two types of instruction are as follows:
-<PRE> %define <VAR>declaration</VAR>
- %define <VAR>variable</VAR> <VAR>value</VAR>
- %undef <VAR>declaration</VAR>
- %undef <VAR>variable</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>%define
-</B><DD>Indicates a definition statement.
-<P><DT><B>%undef
-</B><DD>Indicates a statement that negates a definition.
-<P><DT><B><VAR>declaration</VAR>
-</B><DD>Names the string being declared by a <B>%define</B> statement, or
-negated by an <B>%undef</B> statement.
-<P><DT><B><VAR>variable</VAR>
-</B><DD>Specifies the name of the variable that a <B>%define</B> statement is
-defining, or an <B>%undef</B> statement is negating.
-<P><DT><B><VAR>value</VAR>
-</B><DD>Specifies the value to substitute for the string in the <VAR>variable</VAR>
-field when it appears in the appropriate format (surrounded by curly braces
-and preceded by a dollar sign, as in the example <TT>${variable}</TT>), in
-this or other prototype and library files. It can include one or more
-words.
-</DL>
-<P><B>The %ifdef and %ifndef Instructions for Specifying a Conditional
-Action to Perform</B>
-<A NAME="IDX4090"></A>
-<A NAME="IDX4091"></A>
-<A NAME="IDX4092"></A>
-<A NAME="IDX4093"></A>
-<A NAME="IDX4094"></A>
-<A NAME="IDX4095"></A>
-<P>The <B>%ifdef</B> instruction in a <B>package</B> configuration
-file specifies one or more actions to perform if the indicated string has been
-declared by a single-argument <B>%define</B> statement, or is a variable
-for which a value has been defined by a two-argument <B>%define</B>
-statement.
-<P>Similarly, the <B>%ifndef</B> instruction specifies one or more actions
-to perform if the indicated string has not been declared or is a variable
-without a value, either because no <B>%define</B> statement has defined it
-or an <B>%undef</B> statement has undefined it.
-<P>In both cases, the optional <B>%else</B> statement specifies one or
-more alternate actions to perform if the first statement evaluates to
-<B>false</B>. (For an <B>%ifdef</B> statement, the
-<B>%else</B> statement is executed if the indicated string has never been
-declared or is a variable without a value, or if an <B>%undef</B>
-statement has undefined either one; for an <B>%ifndef</B> statement,
-it is executed if the string has been declared or is a variable with a
-value.)
-<P>It is possible to nest any number of <B>%ifdef</B> and
-<B>%ifndef</B> statements.
-<P>The two types of statement share a common syntax:
-<PRE> %ifdef | ifndef <VAR>declaration</VAR>
- <VAR>action</VAR><SUP>+</SUP>
- [%else [<VAR>declaration</VAR>]
- <VAR>alternate_action</VAR><SUP>+</SUP>]
- %endif <VAR>declaration</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>ifdef
-</B><DD>Indicates that the statement evaluates as <B>true</B> if the string in
-the <VAR>declaration</VAR> field is declared or is a variable with a defined
-value.
-<P><DT><B>ifndef
-</B><DD>Indicates that the statement evaluates as <B>true</B> if the string in
-the <VAR>declaration</VAR> field is not declared or is a variable without a
-defined value.
-<P><DT><B><VAR>declaration</VAR>
-</B><DD>Specifies the string that must be declared or the variable name that must
-have a defined value for an <B>%ifdef</B> statement to evaluate as
-<B>true</B>, which results in the specified action being performed.
-For an <B>%ifndef</B> statement, the string must not be declared or the
-variable must have no defined value for the statement to evaluate as
-<B>true</B>. The first and third occurrences of
-<VAR>declaration</VAR> (the latter following the string <B>%endif</B>) are
-required. The second occurrence (following the string <B>%else</B>)
-is optional, serving only to clarify to which <B>%ifdef</B> or
-<B>%ifndef</B> statement the <B>%else</B> statement belongs.
-<P><DT><B><VAR>action</VAR>
-</B><DD>Specifies each action to perform if the <B>%ifdef</B> or
-<B>%ifndef</B> statement evaluates as <B>true</B>. Each action
-must appear on a separate line. Acceptable types of actions are other
-statements beginning with a percent sign and definition instructions.
-<P><DT><B><VAR>alternate_action</VAR>
-</B><DD>Specifies each action to perform if the <B>%ifdef</B> or
-<B>%ifndef</B> statement evaluates to <B>false</B>. Each action
-must appear on a separate line. Acceptable types of actions are other
-statements beginning with a percent sign and definition instructions.
-</DL>
-<P><B>The %include Instruction for Including a Library File</B>
-<A NAME="IDX4096"></A>
-<A NAME="IDX4097"></A>
-<A NAME="IDX4098"></A>
-<P>The <B>%include</B> instruction in a <B>package</B> configuration
-file includes the contents of the indicated library file in a configuration
-file that results from the compilation of the prototype file in which the
-<B>%include</B> instruction appears. It has the following
-syntax:
-<PRE> %include <VAR>pathname</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>%include
-</B><DD>Indicates a library file include statement.
-<P><DT><B><VAR>pathname</VAR>
-</B><DD>Specifies the complete pathname of the library file to include. It
-can be in AFS or on the local disk, and can include one or more
-variables.
-</DL>
-<P><STRONG>Cautions</STRONG>
-<P>The configuration file must be completely correct. If there are any
-syntax errors or incorrect values, the <B>package</B> command interpreter
-exits without executing any instruction.
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>B</B> and <B>C</B> instructions define a
-disk <B>/dev/hd0a</B> with major and minor device numbers <B>1</B> and
-<B>0</B> and mode bits of <B>-rw-r--r--</B>, and a tty
-<B>/dev/ttyp5</B> with major and minor device numbers <B>6</B> and
-<B>5</B> and mode bits of <B>-rw-rw-rw</B>. In both cases, the
-owner is <B>root</B> and the owning group <B>wheel</B>.
-<PRE> B /dev/hd0a 1 0 root wheel 644
- C /dev/ttyp5 6 5 root wheel 666
-
-</PRE>
-<P>The following example <B>D</B> instruction creates the local
-<B>/usr</B> directory with owner <B>root</B> and group
-<B>wheel</B> and mode bits of <B>drwxr-xr-x</B>. The
-<B>R</B> update code removes any files and subdirectories that reside in
-the <B>/usr</B> directory (if it already exists) but do not appear in the
-configuration file.
-<PRE> DR /usr root wheel 755
-
-</PRE>
-<P>The following example <B>F</B> instruction, appropriate for a machine
-running AIX 4.2 in the ABC Corporation cell, creates or updates the
-local disk file <B>/bin/grep</B>, using
-<B>/afs/abc.com/rs_aix42/bin/grep</B> as the source.
-<PRE> F /bin/grep /afs/abc.com/rs_aix42 root wheel 755
-
-</PRE>
-<P>The next example <B>F</B> instruction creates the
-<B>/usr/vice/etc/ThisCell</B> file and specifies an absolute pathname for
-the source file, as indicated by the <B>A</B> update code. The
-<B>Q</B> code makes the <B>package</B> command return status code 4 as
-it exits, prompting a reboot of the machine if the standard
-<B>package</B>-related changes have been made to the machine's AFS
-initialization file. No values are provided for the owner, group and
-mode bits, so the file inherits them from the source file.
-<PRE> FAQ /usr/vice/etc/ThisCell /afs/abc.com/common/etc/ThisCell
-
-</PRE>
-<P>The following example <B>L</B> instruction, appropriate for a machine
-running AIX 4.2 in the ABC Corporation cell, creates a symbolic link
-from <B>/etc/ftpd</B> on the local disk to the file
-<B>/afs/abc.com/rs_aix42/etc/ftpd</B>.
-<PRE> L /etc/ftpd /afs/abc.com/rs_aix42 root wheel 644
-
-</PRE>
-<P>The following example <B>S</B> instruction defines the socket
-<B>/dev/printer</B>.
-<PRE>
- S /dev/printer root wheel 777
-
-</PRE>
-<P>The following example <B>%define</B> instruction defines the value for
-the variable <TT>${diskmode}</TT>. This variable is used elsewhere in
-the template to fill the <VAR>owner_name</VAR>, <VAR>group_name</VAR>, and
-<VAR>mode_bits</VAR> fields in a <B>D</B>, <B>F</B>, or <B>L</B>
-instruction.
-<PRE> %define diskmode root wheel 644
-
-</PRE>
-<P>The following example <B>%undef</B> instruction declares the string
-<B>afsd</B> not to be defined.
-<PRE> %undef afsd
-
-</PRE>
-<P>The following example <B>%ifdef</B> instruction specifies that if the
-string <TT>rs_aix42</TT> is currently declared, then when the prototype file
-containing the instruction is compiled the three indicated library files are
-included. There is no alternate action defined. There must be
-<B>%define</B> statements earlier in the prototype file to declare
-<B>rs_aix42</B> and to assign a value to the <TT>${wsadmin}</TT>
-variable.
-<PRE> %ifdef rs_aix42
- %include ${wsadmin}/lib/rs_aix42.readonly
- %include ${wsadmin}/lib/rs_aix42.generic
- %include ${wsadmin}/lib/rs_aix42.generic.dev
- %endif rs_aix42
-
-</PRE>
-<P>The following example <B>%ifndef</B> instruction, appropriate for the
-State University cell, defines <TT>stateu.edu</TT> as the value of
-the <TT>${cell}</TT> variable if it does not already have a value.
-<PRE> %ifndef cell
- %define cell stateu.edu
- %endif cell
-
-</PRE>
-<P>The following example <B>%include</B> instruction includes the library
-file <B>base.generic</B> from the <B>lib</B> subdirectory of
-the directory in which <B>package</B>-related files reside. The
-<TT>${wsadmin}</TT> variable resolves to an actual pathname (such as
-<B>/afs/abc.com/wsadmin</B>) during compilation.
-<PRE> %include ${wsadmin}/lib/base.generic
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf052.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf054.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf053.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf055.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSSBULKINPUT" HREF="auarf002.htm#ToC_52">uss Bulk Input File</A></H2>
-<A NAME="IDX4099"></A>
-<A NAME="IDX4100"></A>
-<A NAME="IDX4101"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Provides instructions for the <B>uss bulk</B> command
-<P><STRONG>Description</STRONG>
-<P>The <B>uss</B> bulk input file lists instructions for the
-<B>uss</B> command interpreter to execute when running the <B>uss
-bulk</B> command. If the file includes <B>add</B> instructions
-that reference a <B>uss</B> template file, then the template file must
-also exist.
-<P><B>Summary of Bulk Input File Instructions</B>
-<P>The bulk input file can include the following instructions, each on its own
-line. A more detailed description of each instruction's syntax
-follows this list.
-<DL>
-<P><DT><B>add
-</B><DD>Creates a user account. Equivalent to the <B>uss add</B>
-command.
-<P><DT><B>delete
-</B><DD>Deletes a user account. Equivalent to the <B>uss delete</B>
-command.
-<P><DT><B>delvolume
-</B><DD>Removes the volume and VLDB entry for each account referenced by a
-<B>delete</B> instruction that follows this instruction in the bulk input
-file.
-<P><DT><B>exec
-</B><DD>Executes a command.
-<P><DT><B>savevolume
-</B><DD>Preserves the volume and VLDB entry for each account referenced by a
-<B>delete</B> instruction that follows this instruction in the bulk input
-file.
-</DL>
-<P><B>The add Instruction for Creating an Account</B>
-<A NAME="IDX4102"></A>
-<A NAME="IDX4103"></A>
-<P>The <B>add</B> instruction creates a user account. Each instance
-in the bulk input file is equivalent in effect to a <B>uss add</B> command
-issued on the command line. The order of the instruction's fields
-matches the order of arguments to the <B>uss add</B> command, although
-some arguments do not have a corresponding field. Like the <B>uss
-add</B> command's arguments, many of the fields correspond to (provide
-a value for) a variable in the <B>uss</B> template file, as indicated in
-the following description of each field.
-<P>The instruction's syntax is as follows. It appears on multiple
-lines here only for the sake of legibility--each <B>add</B>
-instruction must appear on a single line in the bulk input file.
-<PRE> add <VAR>username</VAR>[:<VAR>full_name</VAR>][:<VAR>initial_password</VAR>][:<VAR>password_expires</VAR>]
- [:<VAR>file_server</VAR>][:<VAR>partition</VAR>][:<VAR>mount_point</VAR>][:<VAR>uid</VAR>][:<VAR>var1</VAR>][:<VAR>var2</VAR>]
- [:<VAR>var3</VAR>][:<VAR>var4</VAR>][:<VAR>var5</VAR>][:<VAR>var6</VAR>][:<VAR>var7</VAR>][:<VAR>var8</VAR>][:<VAR>var9</VAR>][:]
-
-</PRE>
-<P>To omit a value for a field (presumably because it is optional or the
-template specifies a constant value for it), type nothing between the two
-colons that surround it. After the last argument provided, end the line
-with either a colon and carriage return, or a carriage return alone.
-<P>The meaning of, and acceptable values for, each field are as
-follows.
-<DL>
-<P><DT><B><VAR>username</VAR>
-</B><DD>Names the user's Authentication Database and Protection Database
-entries. It can include up to eight alphanumeric characters, but not
-the <B>:</B> (colon), <B>.</B> (period), or <B>@</B>
-(at-sign) characters. Because it becomes the username (the name under
-which a user logs in), it is best not to include shell metacharacters and to
-obey the restrictions that many operating systems impose on usernames
-(usually, to contain no more than eight lowercase letters).
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-user</B>. Corresponding variable in the template file:
-$USER.
-<P><DT><B><VAR>full_name</VAR>
-</B><DD>Specifies the user's full name. Do not surround it with double
-quotes (""), even if it contains spaces. If not provided, it defaults
-to the username in the <VAR>username</VAR> field.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-realname</B>. Corresponding variable in the template
-file: $NAME. Many operating systems include a field for the full
-name in a user's entry in the local password file (<B>/etc/passwd</B>
-or equivalent), and this variable can be used to pass a value to be used in
-that field.
-<P><DT><B><VAR>initial_password</VAR>
-</B><DD>Specifies the user's initial password. Although the AFS
-commands that handle passwords accept strings of virtually unlimited length,
-it is best to use a password of eight characters or less, which is the maximum
-length that many applications and utilities accept. If not provided,
-this argument defaults to the string <B>changeme</B>.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-pass</B>. Corresponding variable in the template file:
-none.
-<P><DT><B><VAR>password_expires</VAR>
-</B><DD>Sets the number of days after a user's password is changed that it
-remains valid. Provide an integer from the range <B>1</B> through
-<B>254</B> to specify the number of days until expiration, or the value
-<B>0</B> to indicate that the password never expires (the default).
-<P>When the password becomes invalid (expires), the user is unable to
-authenticate, but has 30 more days in which to issue the <B>kpasswd</B>
-command to change the password (after that, only an administrator can change
-it).
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-pwexpires</B>. Corresponding variable in the template
-file: $PWEXPIRES.
-<P><DT><B><VAR>file_server</VAR>
-</B><DD>Names the file server machine on which to create the new user's
-volume. It is best to provide a fully-qualified hostname (for example,
-<B>fs1.abc.com</B>), but an abbreviated form is acceptable
-provided that the cell's naming service is available to resolve it at the
-time the volume is created.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-server</B>. Corresponding variable in the template file:
-$SERVER.
-<P><DT><B><VAR>partition</VAR>
-</B><DD>Specifies the partition on which to create the user's volume; it
-must reside on the file server machine named in the <VAR>file_server</VAR>
-field. Identify the partition by its complete name (for example,
-<B>/vicepa</B>, or use one of the following abbreviations:
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-partition</B>. Corresponding variable in template:
-$PART.
-<P><DT><B><VAR>mount_point</VAR>
-</B><DD>Specifies the complete pathname for the user's home directory.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-mount</B>.
-<P>Corresponding variable in template: $MTPT, but in the template
-file's <B>V</B> instruction only. Occurrences of the $MTPT
-variable in template instructions that follow the <B>V</B> instruction
-take their value from the <B>V</B> instruction's <VAR>mount_point</VAR>
-field. Thus the value of this command line argument becomes the value
-for the $MTPT variable in instructions that follow the <B>V</B>
-instruction only if the string $MTPT appears alone in the <B>V</B>
-instruction's <VAR>mount_point</VAR> field.
-<P><DT><B><VAR>uid</VAR>
-</B><DD>Specifies a positive integer other than <B>0</B> (zero) to assign as
-the user's AFS UID. If this argument is omitted, the Protection
-Server assigns an AFS UID that is one greater than the current value of the
-<TT>max</TT> <TT>user</TT> <TT>id</TT> counter (use the <B>pts
-listmax</B> command to display the counter). If including this
-argument, first use the <B>pts examine</B> command to verify that no
-existing account already has the desired AFS UID; if one does, the
-account-creation process terminates with an error.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-uid</B>. Corresponding variable in template: $UID.
-<P><DT><B><VAR>var1</VAR> through <VAR>var9</VAR>
-</B><DD>Specifies values for each of the number variables $1 through $9 that can
-appear in the template file. The number variables allow the
-administrator to provide values for variables other than the set defined by
-the <B>uss</B> command suite.
-<P>Corresponding argument to the <B>uss add</B> command:
-<B>-var</B>. Corresponding variables in template: $1 through
-$9.
-<P>If providing a value in any of the fields, then in every field that
-precedes it either provide an actual value or indicate an empty field by
-putting nothing between two colons. It is acceptable, but not
-necessary, to indicate empty fields by putting colons after the last field
-that contains an actual value.
-</DL>
-<P><B>The delete Instruction for Deleting an Account</B>
-<A NAME="IDX4104"></A>
-<A NAME="IDX4105"></A>
-<P>The <B>delete</B> instruction deletes a user account from the
-system. Each instance in the bulk input file is equivalent in effect to
-a <B>uss delete</B> command issued on the command line. The order
-of the instruction's fields matches the order of arguments to the
-<B>uss delete</B> command:
-<PRE> delete <VAR>username</VAR>:<VAR>mount_point_path</VAR>[:{ savevolume | delvolume }][:]
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>username</VAR>
-</B><DD>Names the entry to delete from the Protection and Authentication
-Databases.
-<P><DT><B><VAR>mount_point_path</VAR>
-</B><DD>Specifies the complete pathname to the user's home directory, which
-is deleted from the filespace. By default, the volume mounted there is
-also deleted from the file server machine where it resides, as is its record
-from the Volume Location Database (VLDB). To prevent deletion, include
-the <B>savevolume</B> string in the instruction's third field, or
-precede this <B>delete</B> instruction with a <B>savevolume</B>
-instruction. Partial pathnames are interpreted relative to the current
-working directory.
-<P><DT><B>savevolume
-</B><DD>Retains the volume on its file server machine, and the corresponding entry
-in the VLDB. Provide this value or <B>delvolume</B> in the third
-field, or omit both values to treat the volume according to the prevailing
-default, which is set by a preceding <B>savevolume</B> or
-<B>delvolume</B> instruction in the bulk input file.
-<P><DT><B>delvolume
-</B><DD>Removes the volume from its file server machine, and the corresponding
-entry from the VLDB. Provide this value or <B>savevolume</B> in the
-third field, or omit both values to treat the volume according to the
-prevailing default, which is set by a preceding <B>savevolume</B> or
-<B>delvolume</B> instruction in the bulk input file.
-</DL>
-<P>After the last argument provided, end the line with either a colon and
-carriage return or a carriage return alone.
-<P><B>The exec Instruction for Executing a Command</B>
-<P>The <B>exec</B> instruction executes the specified command, which can
-be a UNIX shell script or command, a program, or an AFS command. The
-<B>uss</B> command interpreter must have the necessary privileges in AFS
-and the local file system; it assumes the AFS and local identities of the
-issuer of the <B>uss bulk</B> command.
-<P>The instruction's syntax is as follows:
-<PRE> exec <VAR>command</VAR>
-
-</PRE>
-<P><B>The delvolume and savevolume Instructions for Setting the Default
-Treatment of Volumes</B>
-<A NAME="IDX4106"></A>
-<A NAME="IDX4107"></A>
-<A NAME="IDX4108"></A>
-<A NAME="IDX4109"></A>
-<P>The <B>savevolume</B> and <B>delvolume</B> instructions determine
-the default treatment of volumes referenced by the <B>delete</B>
-instructions that follow them in the bulk input file. Their syntax is
-as follows:
-<PRE> savevolume
- delvolume
-
-</PRE>
-<P>The <B>savevolume</B> instruction prevents the removal of the volume
-and VLDB entry for all <B>delete</B> instruction that follow it in the
-bulk input file, and the <B>delvolume</B> instruction removes the volume
-and VLDB entry for all subsequent <B>delete</B> instructions.
-Either setting persists until its opposite appears in the file, or until the
-end of the bulk file.
-<P>If neither line appears in the bulk input file, the default is to remove
-the volume and the VLDB entry; <B>delete</B> instructions that appear
-before the first <B>savevolume</B> instruction are also subject to this
-default. If a <B>delete</B> instruction's third field
-specifies either <B>savevolume</B> or <B>delvolume</B>, that setting
-overrides the default.
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>add</B> instruction creates an
-authentication-only account. The user's initial password is
-<B>changeme</B> (the default).
-<PRE> add anderson
-
-</PRE>
-<P>The following example <B>add</B> instructions refer to the indicated
-<B>V</B> instruction in a template file (which must appear on a single
-line in the template file).
-<PRE> add smith:John Smith:::fs1:a:::::marketing
- add jones:Pat Jones:::fs3:c:::::finance
- V user.$USER $SERVER.abc.com /vicep$PART 2000 \
- /afs/abc.com/usr/$3/$USER $UID $USER all
-
-</PRE>
-<P>The first <B>add</B> instruction creates an account called
-<B>smith</B> in the Protection and Authentication Databases, with an
-initial password <B>changeme</B> and a value for $UID provided by the
-Protection Server. The volume <B>user.smith</B> resides on
-partition <B>/vicepa</B> of file server machine
-<B>fs1.abc.com</B> and is mounted at
-<B>/afs/abc.com/usr/marketing/smith</B>. He owns his home
-directory and has all access permissions on its root directory's access
-control list (ACL). The account for <B>jones</B> is similar, except
-that the volume resides on partition <B>/vicepc</B> of file server machine
-<B>fs3.abc.com</B> and is mounted at
-<B>/afs/abc.com/usr/finance/jones</B>.
-<P>Notice that the fields corresponding to the volume mount point, UID, $1
-variable, and $2 variable are empty (between <TT>a</TT> and
-<TT>marketing</TT> on the first example line), because their corresponding
-variables do not appear in the template file. The initial password
-field is also empty.
-<P>The following <B>add</B> instructions are equivalent in effect to the
-preceding example, but explicitly indicate empty fields for all of the number
-variables that don't have a value:
-<PRE> add smith:John Smith:::fs1:a:::::marketing::::::
- add jones:Pat Jones:::fs3:c:::::finance::::::
-
-</PRE>
-<P>The following example shows a complete bulk file containing a set of
-<B>delete</B> instructions combined with a <B>savevolume</B>
-instruction. Because the <B>delete</B> instruction for users
-<B>smith</B>, <B>pat</B>, and <B>rogers</B> appear before the
-<B>savevolume</B> instruction and the third field is blank in each, the
-corresponding home volumes are removed. The volume for user
-<B>terry</B> is retained because the default established by the
-<B>savevolume</B> instruction applies to it, but user
-<B>johnson</B>'s volume is removed because the third field of her
-<B>delete</B> instruction overrides the current default.
-<PRE> delete smith:/afs/abc.com/usr/smith
- delete pat:/afs/abc.com/usr/pat
- delete rogers:/afs/abc.com/usr/rogers
- savevolume
- delete terry:/afs/abc.com/usr/terry
- delete johnson:/afs/abc.com/usr/johnson:delvolume
-
-</PRE>
-<P>The following example <B>exec</B> instruction appears between sets of
-<B>add</B> and <B>delete</B> instructions in a bulk input file.
-A message appears in the command shell where the <B>uss bulk</B> command
-is issued, to indicate when the additions are finished and the deletions
-beginning.
-<PRE> exec echo "Additions completed; beginning deletions..."
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-<P><A HREF="auarf243.htm#HDRUSS_ADD">uss add</A>
-<P><A HREF="auarf245.htm#HDRUSS_BULK">uss bulk</A>
-<P><A HREF="auarf246.htm#HDRUSS_DELETE">uss delete</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf053.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf055.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf054.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf056.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSSFILE" HREF="auarf002.htm#ToC_53">uss Template File</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4110"></A>
-<A NAME="IDX4111"></A>
-<A NAME="IDX4112"></A>
-<P>Provides instructions for the <B>uss add</B> command
-<P><STRONG>Description</STRONG>
-<P>The <B>uss</B> template file defines the components of an AFS user
-account that the <B>uss add</B> command (or <B>add</B> instruction in
-a <B>uss</B> bulk input file) creates. Use the <B>-template</B>
-argument to the <B>uss add</B> or <B>uss bulk</B> command to identify
-the template file.
-<P><B>Summary of Template File Instructions</B>
-<P>The template file can include the following instructions, each on its own
-line. A more detailed description of each instruction's syntax
-follows this list.
-<DL>
-<P><DT><B>A
-</B><DD>Imposes restrictions on user passwords and authentication attempts
-<P><DT><B>D
-</B><DD>Creates a directory
-<P><DT><B>E
-</B><DD>Creates a single-line file
-<P><DT><B>F
-</B><DD>Creates a file by copying a prototype
-<P><DT><B>G
-</B><DD>Defines a directory that is one of a set of parent directories into which
-the <B>uss</B> command interpreter evenly distributes newly created home
-directories
-<P><DT><B>L
-</B><DD>Creates a hard link
-<P><DT><B>S
-</B><DD>Creates a symbolic link
-<P><DT><B>V
-</B><DD>Creates a volume, mounts it in the file space and sets the ACL on the
-mount point
-<P><DT><B>X
-</B><DD>Executes a command
-</DL>
-<P>If the template file is empty (zero-length), the <B>uss add</B> command
-or <B>add</B> instruction in a bulk input file only creates an entry in
-the Protection and Authentication Databases, naming them according to the name
-specified with the <B>uss add</B> command's <B>-user</B>
-argument, or in the bulk input file <B>add</B> instruction's
-<VAR>username</VAR> field.
-<P><B>The A Instruction for Setting the Default Treatment of Volumes</B>
-<A NAME="IDX4113"></A>
-<A NAME="IDX4114"></A>
-<A NAME="IDX4115"></A>
-<A NAME="IDX4116"></A>
-<A NAME="IDX4117"></A>
-<A NAME="IDX4118"></A>
-<A NAME="IDX4119"></A>
-<P>The <B>A</B> instruction in a <B>uss</B> template file enhances
-cell security by imposing the following restrictions on users' password
-choice and authentication attempts. For further information on these
-limits, see the <I>IBM AFS Administration Guide</I> and the <B>kas
-setfields</B> reference page.
-<UL>
-<P><LI>Limiting the user's password lifetime. When the lifetime
-expires, the user can no longer authenticate using that password, and must
-change it.
-<P><LI>Prohibiting the reuse of the user's 20 most recently used
-passwords.
-<P><LI>Limiting the number of consecutive times that a user can provide an
-incorrect password during authentication, and for how long the Authentication
-Server refuses further authentication attempts after the limit is exceeded
-(referred to as an <I>account lockout</I>). For regular user
-accounts in most cells, the recommended limit is nine and lockout time is 25
-minutes.
-</UL>
-<P>The instruction has the following syntax:
-<PRE> <B>A</B> <VAR>username</VAR> <VAR>password_lifetime</VAR> <VAR>password_reuse</VAR> <VAR>failures</VAR> <VAR>locktime</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>A
-</B><DD>Indicates a security-enhancing instruction. It must be a capital
-letter.
-<P><DT><B><VAR>username</VAR>
-</B><DD>Names the Authentication Database entry on which to impose security
-restrictions. Specify the value <B>$USER</B> to read in the
-username from the <B>uss add</B> command's <B>-user</B> argument,
-or from the <VAR>username</VAR> field of an <B>add</B> instruction in a bulk
-input file.
-<P><DT><B><VAR>password_lifetime</VAR>
-</B><DD>Sets the number of days after the user's password is changed that it
-remains valid. When the password becomes invalid (expires), the user is
-unable to authenticate, but has 30 more days in which to issue the
-<B>kpasswd</B> command to change the password (after that, only an
-administrator can change it).
-<P>Specify an integer from the range <B>1</B> through <B>254</B> to
-specify the number of days until expiration, the value <B>0</B> to
-indicate that the password never expires, or the value <B>$PWEXPIRES</B>
-to read in the number of days from the <B>uss add</B> or <B>uss
-bulk</B> command's <B>-pwexpires</B> argument. If the
-<B>A</B> instruction does not appear in the template file, the default is
-for the user's password never to expire.
-<P><DT><B><VAR>password_reuse</VAR>
-</B><DD>Determines whether or not the user can change his or her password (using
-the <B>kpasswd</B> or <B>kas setpassword</B> command) to one that is
-similar to any of the last twenty passwords. The acceptable values are
-<B>reuse</B> to allow reuse and <B>noreuse</B> to prohibit it.
-If the <B>A</B> instruction does not appear in the template file, the
-default is to allow password reuse.
-<P><DT><B><VAR>failures</VAR>
-</B><DD>Sets the number of consecutive times the user can provide an incorrect
-password during authentication (using the <B>klog</B> command or a login
-utility that grants AFS tokens). When the user exceeds the limit, the
-Authentication Server rejects further authentication attempts for the amount
-of time specified in the <VAR>locktime</VAR> field.
-<P>Specify an integer from the range <B>1</B> through <B>254</B> to
-specify the number of failures permitted, or the value <B>0</B> to
-indicate that there is no limit to the number of unsuccessful attempts.
-If the <B>A</B> instruction does not appear in the template file, the
-default is to allow an unlimited number of failures.
-<P><DT><B><VAR>locktime</VAR>
-</B><DD>Specifies how long the Authentication Server refuses authentication
-attempts from a user who has exceeded the failure limit set in the
-<VAR>failures</VAR> field.
-<P>Specify a number of hours and minutes (<VAR>hh:mm</VAR>) or minutes
-only (<VAR>mm</VAR>), from the range <B>01</B> (one minute) through
-<B>36:00</B> (36 hours). The Authentication Server
-automatically reduces any larger value to <B>36:00</B> and also
-rounds up any non-zero value to the next higher multiple of 8.5
-minutes. A value of <B>0</B> (zero) sets an infinite lockout
-time; an administrator must always issue the <B>kas unlock</B>
-command to unlock the account.
-</DL>
-<P><B>The D Instruction for Creating a Directory</B>
-<A NAME="IDX4120"></A>
-<A NAME="IDX4121"></A>
-<A NAME="IDX4122"></A>
-<A NAME="IDX4123"></A>
-<A NAME="IDX4124"></A>
-<A NAME="IDX4125"></A>
-<A NAME="IDX4126"></A>
-<A NAME="IDX4127"></A>
-<A NAME="IDX4128"></A>
-<A NAME="IDX4129"></A>
-<A NAME="IDX4130"></A>
-<P>The <B>D</B> instruction in a <B>uss</B> template file creates a
-directory. Its intended use is to create a subdirectory in the user
-home directory created by the <B>V</B> instruction in the template
-file.
-<P>Any number of <B>D</B> instructions can appear in the template
-file. If any variables in the instruction take their values from the
-<B>V</B> instruction (notably, the $MTPT variable), the instruction must
-follow the <B>V</B> instruction in the file.
-<P>Although it is possible to use the <B>D</B> instruction to create a
-directory on the local disk of the machine where the <B>uss</B> command is
-issued, it is not recommended. The preferred method for automated
-creation of directories on a local disk is the <B>package</B>
-program. Two complications arise if the <VAR>pathname</VAR> field refers
-to a local disk directory:
-<UL>
-<P><LI>The <B>uss</B> command prints a warning message because it cannot
-associate an access control list (ACL) with a local disk directory. It
-creates the directory nonetheless, and some syntactically correct value must
-appear in the instruction's <VAR>ACL</VAR> field.
-<P><LI>To designate any user other than the issuer as the new directory's
-owner, the issuer must log onto the machine as the local superuser
-<B>root</B>. For local disk directories, only the local superuser
-<B>root</B> is allowed to issue the UNIX <B>chown</B> command that the
-<B>uss</B> command interpreter invokes to change the owner from the
-default value (the directory's creator, which in this case is the issuer
-of the <B>uss</B> command). The issuer must then also use the
-<B>-admin</B> argument to the <B>uss add</B> or <B>uss bulk</B>
-command to authenticate as a privileged AFS administrator, which is required
-for creating the Authentication Database and Protection Database entries that
-the <B>uss</B> command interpreter always creates for a new
-account.
-</UL>
-<P>The instruction has the following syntax:
-<PRE> <B>D</B> <VAR>pathname</VAR> <VAR>mode_bits</VAR> <VAR>owner</VAR> <VAR>ACL</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>D
-</B><DD>Indicates a directory creation instruction. It must be a capital
-letter.
-<P><DT><B><VAR>pathname</VAR>
-</B><DD>Specifies the directory's full pathname. It can include
-variables.
-<P>Specify the read/write path to the directory, to avoid the failure that
-results from attempting to create a new directory in a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-reference page for the <B>fs mkmount</B> command.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Sets the directory's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>. The
-first (owner) <B>x</B> bit must be turned on to enable access to a
-directory.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the directory's owner in the output from the UNIX <B>ls -ld</B>
-command. If the directory resides in AFS, place the $UID variable in
-this field. If the directory resides on the local disk, this field must
-be the username or UID of the <B>uss</B> command's issuer, unless the
-issuer is logged in as the local superuser <B>root</B>.
-<P><DT><B><VAR>ACL</VAR>
-</B><DD>Sets the ACL on the new directory. It must appear even if the new
-directory resides on the local disk rather than in AFS, but is ignored in that
-case. Provide one or more paired values, each pair consisting of an AFS
-username or group name and the desired permissions, in that order.
-Separate the two parts of the pair, and each pair, with a space. The
-<B>fs setacl</B> reference page describes the available
-permissions.
-<P>For an AFS directory, grant all permissions to the directory's owner
-at least. Usually that is the new user, in which case the appropriate
-value is <B>$USER all</B>.
-<P>It is not possible to grant any permissions to the issuer of the
-<B>uss</B> command. As the last step in account creation, the
-<B>uss</B> command interpreter automatically deletes that person from any
-ACLs set during the creation process.
-</DL>
-<P><B>The E Instruction for Creating a Single-line File</B>
-<A NAME="IDX4131"></A>
-<A NAME="IDX4132"></A>
-<A NAME="IDX4133"></A>
-<A NAME="IDX4134"></A>
-<A NAME="IDX4135"></A>
-<A NAME="IDX4136"></A>
-<P>The <B>E</B> instruction in a <B>uss</B> template file creates a
-file by echoing a specified character string into it. Its intended use
-is to create files in the user home directory created by the <B>V</B>
-instruction in the template file, or in a subdirectory created by a
-<B>D</B> instruction.
-<P>Any number of <B>E</B> instructions can appear in the template
-file. If the file resides in a directory created by a <B>D</B>
-instruction, the <B>E</B> instruction must follow the <B>D</B>
-instruction in the file.
-<P>The <B>E</B> and <B>F</B> instructions have complementary
-advantages. The character string echoed into the file by an
-<B>E</B> instruction can be customized for each user, because it can
-include the standard variables for which the <B>uss</B> command
-interpreter substitutes the values specified by arguments to the <B>uss
-add</B> command or fields in a bulk input file <B>add</B>
-instruction. In contrast, a file created using the <B>F</B>
-instruction cannot include variables and so has the same content for all
-users. However, a file created by an <B>E</B> instruction can be a
-single line only, because no carriage returns (newline characters) are allowed
-in the character string.
-<P>Although it is possible to use the <B>E</B> instruction to create a
-file on the local disk of the machine where the <B>uss</B> command is
-issued, it is not recommended. The preferred method for automated
-creation of files on a local disk is the <B>package</B> program.
-The main complication is that designating any user other than the issuer as
-the new file's owner requires logging onto the machine as the local
-superuser <B>root</B>. For local disk files, only the local
-superuser <B>root</B> is allowed to issue the UNIX <B>chown</B>
-command that the <B>uss</B> command interpreter invokes to change the
-owner from the default value (the file's creator, which in this case is
-the issuer of the <B>uss</B> command). The issuer must then also
-use the <B>-admin</B> argument to the <B>uss add</B> or <B>uss
-bulk</B> command to authenticate as a privileged AFS administrator, which is
-required for creating the Authentication Database and Protection Database
-entries that the <B>uss</B> command interpreter always creates for a new
-account.
-<P>The instruction has the following syntax:
-<PRE> <B>E</B> <VAR>pathname</VAR> <VAR>mode_bits</VAR> <VAR>owner</VAR> "<VAR>contents</VAR>"
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>E
-</B><DD>Indicates a file creation instruction. It must be a capital
-letter.
-<P><DT><B><VAR>pathname</VAR>
-</B><DD>Specifies the file's full pathname. It can include
-variables.
-<P>Specify the read/write path to the file, to avoid the failure that results
-from attempting to create a new file in a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-reference page for the <B>fs mkmount</B> command.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Sets the file's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the file's owner in the output from the UNIX <B>ls -l</B>
-command. If the file resides in AFS, place the $UID variable in this
-field. If the file resides on the local disk, specify the username or
-UID of the <B>uss</B> command's issuer; otherwise, the account
-creation operation halts immediately.
-<P><DT><B><VAR>contents</VAR>
-</B><DD>Specifies the one-line character string to write into the new file.
-Surround it with double quotes if it contains one or more spaces. It
-cannot contain the newline character, but can contain any of the standard
-variables, which the command interpreter resolves as it creates the
-file.
-</DL>
-<P><A NAME="SPTWQ6"></A><B>The F Instruction for Creating a File
-from a Prototype</B>
-<A NAME="IDX4137"></A>
-<A NAME="IDX4138"></A>
-<A NAME="IDX4139"></A>
-<A NAME="IDX4140"></A>
-<A NAME="IDX4141"></A>
-<A NAME="IDX4142"></A>
-<P>The <B>F</B> instruction in a <B>uss</B> template file creates a
-file by copying the contents of an existing file (the <I>prototype</I>)
-into it. Its intended use is to create files in the user home directory
-created by the <B>V</B> instruction in the template file, or in a
-subdirectory created by a <B>D</B> instruction.
-<P>Any number of <B>F</B> instructions can appear in the template
-file. If the file resides in a directory created by a <B>D</B>
-instruction, the <B>F</B> instruction must follow the <B>D</B>
-instruction in the file.
-<P>The <B>E</B> and <B>F</B> instructions have complementary
-advantages. A file created using the <B>F</B> instruction has the
-same content for all users, whereas a file created by an <B>E</B>
-instruction can be customized for each user if it includes variables.
-However, a file created by an <B>E</B> instruction can be a single line
-only, whereas the prototype file copied by an <B>F</B> instruction can be
-any length.
-<P>Although it is possible to use the <B>F</B> instruction to create a
-file on the local disk of the machine where the <B>uss</B> command is
-issued, it is not recommended. The preferred method for automated
-creation of files on a local disk is the <B>package</B> program.
-The main complication is that designating any user other than the issuer as
-the new file's owner requires logging onto the machine as the local
-superuser <B>root</B>. For local disk files, only the local
-superuser <B>root</B> is allowed to issue the UNIX <B>chown</B>
-command that the <B>uss</B> command interpreter invokes to change the
-owner from the default value (the file's creator, which in this case is
-the issuer of the <B>uss</B> command). The issuer must then also
-use the <B>-admin</B> argument to the <B>uss add</B> or <B>uss
-bulk</B> command to authenticate as a privileged AFS administrator, which is
-required for creating the Authentication Database and Protection Database
-entries that the <B>uss</B> command interpreter always creates for a new
-account.
-<P>The instruction has the following syntax:
-<PRE> <B>F</B> <VAR>pathname</VAR> <VAR>mode_bits</VAR> <VAR>owner</VAR> <VAR>prototype_file</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>F
-</B><DD>Indicates a file creation instruction. It must be a capital
-letter.
-<P><DT><B><VAR>pathname</VAR>
-</B><DD>Specifies the full pathname of the file to create, including the
-filename. It can include variables.
-<P>Specify the read/write path to the file, to avoid the failure that results
-from attempting to create a new file in a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-reference page for the <B>fs mkmount</B> command.
-<P><DT><B><VAR>mode_bits</VAR>
-</B><DD>Sets the file's UNIX mode bits. Acceptable values are the
-standard three- or four-digit numbers corresponding to combinations of
-permissions. Examples: <B>755</B> corresponds to
-<B>rwxr-xr-x</B>, and <B>644</B> to <B>rw-r--r--</B>.
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the file's owner in the output from the UNIX <B>ls -l</B>
-command. If the file resides in AFS, place the $UID variable in this
-field. If the file resides on the local disk, specify the username or
-UID of the <B>uss</B> command's issuer; otherwise, the account
-creation operation halts immediately.
-<P><DT><B><VAR>prototype_file</VAR>
-</B><DD>Names the AFS or local disk directory that houses the prototype file to
-copy. The prototype file's name must match the final element in
-the <VAR>pathname</VAR> field.
-</DL>
-<P><A NAME="SPTWQ7"></A><B>The G Instruction for Facilitating Even
-Distribution of Home Directories</B>
-<A NAME="IDX4143"></A>
-<A NAME="IDX4144"></A>
-<A NAME="IDX4145"></A>
-<A NAME="IDX4146"></A>
-<A NAME="IDX4147"></A>
-<A NAME="IDX4148"></A>
-<P>The <B>G</B> instruction in a <B>uss</B> template file creates a
-directory as one of the set of directories from which the <B>uss</B>
-command interpreter selects when choosing a new user home directory's
-parent directory. More specifically, when the $AUTO variable appears in
-the <VAR>mount_point</VAR> field of a <B>V</B> instruction, the command
-interpreter substitutes for it the directory defined by a <B>G</B>
-instruction that currently has the fewest entries.
-<P>The instruction's intended use is to distribute user accounts evenly
-among several directories, rather than using directories that reflect
-divisions such as departmental affiliation. Distributing home
-directories in this fashion is useful mainly in very large cells where storing
-all user home directories under a single parent directory potentially slows
-directory lookup, or where a workplace-based division results in unevenly
-sized directories such that some users consistently experience slower
-directory lookup than others. See the chapter on <B>uss</B> in the
-<I>IBM AFS Administration Guide</I> for more information.
-<P>Any number of <B>G</B> instructions can appear in the template
-file. If the <B>V</B> instruction includes the $AUTO variable, it
-must appear after all of the <B>G</B> instructions in the file.
-<P>The instruction has the following syntax:
-<PRE> <B>G</B> <VAR>directory</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>G
-</B><DD>Indicates an instruction that creates a directory to be considered as a
-value for the $AUTO variable. It must be a capital letter.
-<P><DT><B><VAR>directory</VAR>
-</B><DD>Specifies the directory's name as either a complete pathname or only
-the directory name. The choice determines the appropriate format for
-the <VAR>mount_point</VAR> field of a <B>V</B> instruction, as discussed in
-the following example.
-<P>Specify the read/write path to the directory, to avoid the failure that
-results from attempting to create a new mount point in a read-only volume when
-the $AUTO variable is used in a <B>V</B> instruction's
-<VAR>mount_point</VAR> field. By convention, the read/write path is
-indicated by placing a period before the cell name at the pathname's
-second level (for example, <B>/afs/.abc.com</B>). For
-further discussion of the concept of read/write and read-only paths through
-the filespace, see the reference page for the <B>fs mkmount</B>
-command.
-</DL>
-<P><B>The L and S Instructions for Creating a Link</B>
-<A NAME="IDX4149"></A>
-<A NAME="IDX4150"></A>
-<A NAME="IDX4151"></A>
-<A NAME="IDX4152"></A>
-<A NAME="IDX4153"></A>
-<A NAME="IDX4154"></A>
-<A NAME="IDX4155"></A>
-<A NAME="IDX4156"></A>
-<A NAME="IDX4157"></A>
-<A NAME="IDX4158"></A>
-<A NAME="IDX4159"></A>
-<A NAME="IDX4160"></A>
-<A NAME="IDX4161"></A>
-<P>The <B>L</B> instruction in a <B>uss</B> template file creates a
-hard link between two files, as achieved by the standard UNIX <B>ln</B>
-command. The <B>S</B> instruction creates a symbolic link between
-two files, as achieved by the standard UNIX <B>ln -s</B> command. A
-full explanation of links is beyond the scope of this document, but the basic
-effect is to create a second name for an existing file, enabling access via
-either name. Creating a link does not create a second copy of the
-file.
-<P>AFS allows hard links only if the linked files reside in the same
-directory, because it becomes difficult to determine which access control list
-(ACL) applies to the file if the two copies reside in directories with
-different ACLs. AFS allows symbolic links between two files that reside
-in different directories, or even different volumes. The File Server
-uses the ACL associated with the actual file rather than the link.
-<P>Any number of <B>L</B> and <B>S</B> instructions can appear in the
-template file. If the existing file or link is to reside in a directory
-created by a <B>D</B> instruction, or if the existing file was created by
-an <B>E</B> or <B>F</B> instruction, the <B>L</B> or <B>S</B>
-instruction must follow the <B>D</B>, <B>E</B>, or <B>F</B>
-instruction.
-<P>The instructions share the following syntax:
-<PRE> <B>L</B> <VAR>existing_file</VAR> <VAR>link</VAR>
- <B>S</B> <VAR>existing_file</VAR> <VAR>link</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>L
-</B><DD>Indicates a hard link creation instruction. It must be a capital
-letter.
-<P><DT><B>S
-</B><DD>Indicates a symbolic link creation instruction. It must be a
-capital letter.
-<P><DT><B><VAR>existing_file</VAR>
-</B><DD>Specifies the complete pathname of the existing file.
-<P><DT><B><VAR>link</VAR>
-</B><DD>Specifies the complete pathname of the second name for the file.
-<P>Specify the read/write path to the link, to avoid the failure that results
-from attempting to create a new link in a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-reference page for the <B>fs mkmount</B> command.
-</DL>
-<P><A NAME="SPTWQ8"></A><B>The V Instruction for Creating and
-Mounting a Volume</B>
-<A NAME="IDX4162"></A>
-<A NAME="IDX4163"></A>
-<A NAME="IDX4164"></A>
-<A NAME="IDX4165"></A>
-<A NAME="IDX4166"></A>
-<A NAME="IDX4167"></A>
-<A NAME="IDX4168"></A>
-<A NAME="IDX4169"></A>
-<A NAME="IDX4170"></A>
-<A NAME="IDX4171"></A>
-<A NAME="IDX4172"></A>
-<A NAME="IDX4173"></A>
-<A NAME="IDX4174"></A>
-<A NAME="IDX4175"></A>
-<A NAME="IDX4176"></A>
-<A NAME="IDX4177"></A>
-<A NAME="IDX4178"></A>
-<A NAME="IDX4179"></A>
-<A NAME="IDX4180"></A>
-<P>The <B>V</B> instruction in a <B>uss</B> template file creates a
-volume on a specified file server machine and partition and creates an entry
-for it in the Volume Location Database (VLDB). It mounts the volume at
-a location in the AFS file space that becomes the user's home directory,
-then designates the directory's owner and sets its access control list
-(ACL).
-<P>Only one <B>V</B> instruction can appear in the template file, and one
-must appear if the template file contains any instructions at all (is not
-empty). All other instructions are optional, except that the template
-must include <B>G</B> instructions if the $AUTO variable appears in
-it. (The <B>V</B> instruction is not necessarily the first line in
-the template. If the template includes the $AUTO variable, then the
-<B>G</B> instructions which provide values for the variable must precede
-it in the file.)
-<P>The instruction has the following syntax:
-<PRE> <B>V</B> <VAR>volume_name</VAR> <VAR>server</VAR> <VAR>partition</VAR> <VAR>quota</VAR> <VAR>mount_point</VAR> <VAR>owner</VAR> <VAR>ACL</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>V
-</B><DD>Indicates a volume creation instruction. It must be a capital
-letter.
-<P><DT><B><VAR>volume_name</VAR>
-</B><DD>Specifies the volume's name. To follow the convention for AFS
-user volume names, specify the value <B>user.$USER</B>.
-Provide a value for the $USER variable via the <B>uss add</B>
-command's <B>-user</B> argument or the <VAR>username</VAR> field in the
-bulk input file <B>add</B> instruction.
-<P><DT><B><VAR>server</VAR>
-</B><DD>Names the file server machine on which to create the new user's
-volume. It is best to provide the fully-qualified hostname (for
-example, <B>fs1.abc.com</B>), but an abbreviated form is
-acceptable provided that the cell's naming service is available to
-resolve it at the time the volume is created. To read in the value from
-the <B>uss add</B> command's <B>-server</B> argument, specify the
-value <B>$SERVER</B>.
-<P><DT><B><VAR>partition</VAR>
-</B><DD>Specifies the partition on which to create the user's volume; it
-must be on the file server machine named in the <VAR>server</VAR> field.
-Identify the partition by its complete name (for example, <B>/vicepa</B>)
-or use or use one of the following abbreviations.
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P>To read in the value from the <B>uss add</B> command's
-<B>-partition</B> argument, specify the value <B>$PART</B>.
-<P><DT><B><VAR>quota</VAR>
-</B><DD>Sets the maximum number of kilobyte blocks the volume can occupy on the
-file server machine's disk. Specify an integer constant if all
-volumes have the same quota (<B>1024</B> equals a megabyte), or use one of
-the number variables ($1 through $9) to assign different values to different
-volumes.
-<P><DT><B><VAR>mount_point</VAR>
-</B><DD>Creates a mount point for the volume, which serves as the volume's
-root directory. Include the $USER variable as part of the pathname to
-follow the convention that user home directory names include the
-username.
-<P>Specify the read/write path to the mount point, to avoid the failure that
-results from attempting to create a new mount point in a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). If the $AUTO variable appears
-in this field, the directories named by each <B>G</B> instruction possibly
-already indicate the read/write path. For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-reference page for the <B>fs mkmount</B> command..
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">If used, the $MTPT variable in this field takes its value from the <B>uss
-add</B> command's <B>-mount</B> argument or from the
-<VAR>mount_point</VAR> field of an <B>add</B> instruction in the bulk input
-file. However, subsequent uses of the $MTPT variable (usually in
-following <B>D</B>, <B>E</B>, or <B>F</B> instructions) take as
-their value the complete contents of this field.
-</TD></TR></TABLE>
-<P><DT><B><VAR>owner</VAR>
-</B><DD>Specifies the username or UNIX user ID (UID) of the user to be designated
-the mount point's owner in the output from the UNIX <B>ls -ld</B>
-command. To follow the convention for home directory ownership, place
-the value <B>$UID</B> in this field.
-<P><DT><B><VAR>ACL</VAR>
-</B><DD>Sets the ACL on the new directory. Provide one or more paired
-values, each pair consisting of an AFS username or group name and the desired
-permissions, in that order. Separate the two parts of the pair, and
-each pair, with a space. The <B>fs setacl</B> reference page
-describes the available permissions.
-<P>Grant all permissions to the new user at least. The appropriate
-value is <B>$USER all</B>.
-<P>AFS automatically grants the <B>system:administrators</B> group
-all permissions as well. It is not possible to grant any permissions to
-the issuer of the <B>uss</B> command. As the last step in account
-creation, the <B>uss</B> command interpreter automatically deletes that
-user from any ACLs set during the creation process.
-</DL>
-<P><A NAME="SPTWQ9"></A><B>The X Instruction for Running a
-Command</B>
-<A NAME="IDX4181"></A>
-<A NAME="IDX4182"></A>
-<A NAME="IDX4183"></A>
-<P>The <B>X</B> instruction in a <B>uss</B> template file runs the
-indicated command, which can be a standard UNIX or AFS command. It can
-include any variables from the template file, which the <B>uss</B> command
-interpreter resolves before passing the command on to the appropriate other
-command interpreter. It must be a single line only, however (cannot
-contain carriage returns or newline characters).
-<P>Any number of <B>X</B> instructions can appear in the template
-file. If an instruction manipulates an element created by another
-instruction, it must follow that instruction in the file.
-<P>The instruction has the following syntax:
-<PRE> <B>X "</B><VAR>command</VAR><B>"</B>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B>X
-</B><DD>Indicates a command execution instruction. It must be a capital
-letter.
-<P><DT><B><VAR>command</VAR>
-</B><DD>Specifies the command to run. Surround it with double quotes as
-shown if it contains one or more spaces. It can contain any variables
-from the template file, but not newline characters.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>A</B> instruction sets a password lifetime of
-254 days, prohibits password reuse, limits the number of consecutive failed
-authentication attempts to nine and sets the corresponding locktime to
-25:30 minutes (which is a multiple of 8.5 minutes). The
-username is read in from the <B>-user</B> argument to the <B>uss
-add</B> command or from the <I>username</I> field in each <B>add</B>
-instruction in a bulk input file.
-<PRE> A $USER 254 noreuse 9 25:30
-
-</PRE>
-<P>The following example <B>D</B> instruction creates a directory called
-<I>public</I> in a new user's home directory, designates the user as
-the directory's owner, and grants him or her all ACL permissions.
-<PRE> D $MTPT/public 0755 $UID $USER all
-
-</PRE>
-<P>The following example <B>E</B> instruction creates a file in the
-current working directory called
-<VAR>username</VAR>.<B>etcp</B>. The contents are an entry
-suitable for incorporating into the cell's global
-<B>/etc/password</B> file.
-<PRE> E $USER.etcp 0644 root "$USER:X:$UID:10:$NAME:$MTPT:/bin/csh"
-
-</PRE>
-<P>The following example <B>F</B> instruction, appropriate for the ABC
-Corporation cell, copies a prototype <B>.login</B> file into the
-user's home directory.
-<PRE> F $MTPT/.login 0644 $UID /afs/abc.com/common/uss/skel/.login
-
-</PRE>
-<P>In the following example, the State University cell's administrators
-have decided to distribute user home directories evenly into three
-directories. They define three <B>G</B> instructions:
-<PRE> G usr1
- G usr2
- G usr3
-
-</PRE>
-<P>and then put the following value in the <I>mount_point</I> field of the
-<B>V</B> instruction:
-<PRE> /afs/stateu.edu/$AUTO/$USER
-
-</PRE>
-<P>Alternatively, if they include the entire directory pathname in the
-<B>G</B> instruction:
-<PRE> G /afs/stateu.edu/usr1
- G /afs/stateu.edu/usr2
- G /afs/stateu.edu/usr3
-
-</PRE>
-<P>then the <I>mount_point</I> field of the <B>V</B> instruction
-specifies only the following:
-<PRE> $AUTO/$USER
-
-</PRE>
-<P>The following example <B>L</B> instruction creates a hard link between
-the files <B>mail</B> and <B>mbox</B> in the user's home
-directory.
-<PRE> L $MTPT/mbox $MTPT/mail
-
-</PRE>
-<P>The following example <B>S</B> instruction, appropriate for the ABC
-Corporation cell, links the file <B>Mail/outgoing</B> in the user's
-home directory to the file
-<B>/afs/abc.com/common/mail/outgoing</B>.
-<PRE> S /afs/abc.com/common/mail/outgoing $MTPT/Mail/outgoing
-
-</PRE>
-<P>The following example <B>V</B> instruction creates a volume called
-<B>user.</B><VAR>username</VAR> on the <B>/vicepa</B> partition
-of the specified file server machine, assigning it a quota of 3000 kilobyte
-blocks. The mount point is under <B>/afs/abc.com/usr</B> and
-matches the username (the value of the $USER variable). The user owns
-the home directory and has all access rights to it. The instruction
-appears on two lines only for legibility; it must appear on a single line
-in the template file.
-<PRE> V user.$USER $SERVER.abc.com /vicepa 3000 \
- /afs/abc.com/usr/$USER $UID $USER all
-
-</PRE>
-<P>The following example <B>X</B> instruction mounts the backup version of
-the user's volume at the <B>OldFiles</B> subdirectory.
-<PRE> X "fs mkm /afs/abc.com/usr/$USER/OldFiles user.$USER.backup"
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf243.htm#HDRUSS_ADD">uss add</A>
-<P><A HREF="auarf245.htm#HDRUSS_BULK">uss bulk</A>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf054.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf056.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf055.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf057.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<HR><H1><A NAME="Header_54" HREF="auarf002.htm#ToC_54">AFS System Commands</A></H1>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf055.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf057.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf056.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf058.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAFSINTRO" HREF="auarf002.htm#ToC_55">afs_intro</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to AFS commands
-<P><STRONG>Description</STRONG>
-<P>AFS provides many commands that enable users and system administrators to
-use and customize its features. Many of the commands belong to the
-following categories, called <I>command suites</I>.
-<DL>
-<P><DT><B>backup
-</B><DD>Interface for configuring and operating the AFS Backup System
-<P><DT><B>bos
-</B><DD>Interface to the Basic Overseer (BOS) Server for administering server
-processes and configuration files
-<P><DT><B>fs
-</B><DD>Interface for administering access control lists (ACLs), the Cache
-Manager, and other miscellaneous file system functions
-<P><DT><B>fstrace
-</B><DD>Interface for tracing Cache Manager operations when debugging problems
-<P><DT><B>kas
-</B><DD>Interface to the Authentication Server for administering security and
-authentication information
-<P><DT><B>pts
-</B><DD>Interface to the Protection Server for administering AFS ID and group
-membership information
-<P><DT><B>uss
-</B><DD>Interface for automated administration of user accounts
-<P><DT><B>vos
-</B><DD>Interface to the Volume Server and Volume Location (VL) Server for
-administering volumes
-</DL>
-<P>In addition, there are several commands that do not belong to
-suites.
-<P><H5><A NAME="HDRWQ10">AFS Command Syntax</A></H5>
-<P>AFS commands that belong to suites have the following
-structure:
-<PRE> <B>command_suite operation_code</B> <B>-switch</B> <<VAR>value</VAR>><SUP>[+]</SUP> [<B>-flag</B>]
-
-</PRE>
-<P><H6><A NAME="Header_57">Command Names</A></H6>
-<P>Together, the <B>command_suite</B> and <B>operation_code</B>
-make up the <I>command name</I>.
-<P>The <B>command_suite</B> specifies the group of related commands to
-which the command belongs, and indicates which command interpreter and server
-process perform the command. AFS has several command suites, including
-<B>bos</B>, <B>fs</B>, <B>kas</B>, <B>package</B>,
-<B>pts</B>, <B>scout</B>, <B>uss</B> and <B>vos</B>.
-Some of these suites have an interactive mode in which the issuer omits the
-<B>command_suite</B> portion of the command name.
-<P>The <B>operation_code</B> tells the command interpreter and server
-process which action to perform. Most command suites include several
-operation codes. The <I>IBM AFS Administration Reference</I>
-describes each operation code in detail, and the <I>IBM AFS Administration
-Guide</I> describes how to use them in the context of performing
-administrative tasks.
-<P>Several AFS commands do not belong to a suite and so their names do not
-have a <B>command_suite</B> portion. Their structure is otherwise
-similar to the commands in the suites.
-<P><H6><A NAME="Header_58">Options</A></H6>
-<P>The term <I>option</I> refers to both arguments and flags, which
-are described in the following sections.
-<P><H6><A NAME="Header_59">Arguments</A></H6>
-<P>One or more arguments can follow the command name. Arguments
-specify the entities on which to act while performing the command (for
-example, which server machine, server process, or file). To minimize
-the potential for error, provide a command's arguments in the order
-prescribed in its syntax definition.
-<P>Each argument has two parts, which appear in the indicated order:
-<UL>
-<P><LI>The <I>switch</I> specifies the argument's type and is preceded
-by a hyphen ( <B>-</B> ). For instance, the switch
-<B>-server</B> usually indicates that the argument names a server
-machine. Switches can often be omitted, subject to the rules outlined
-in <A HREF="#HDRNOSWITCH">Conditions for Omitting Switches</A>.
-<P><LI>The <I>value</I> names a particular entity of the type specified by
-the preceding switch. For example, the proper value for a
-<B>-server</B> switch is a server machine name like
-<B>fs3.abc.com</B>. Unlike switches (which have a
-required form), values vary depending on what the issuer wants to
-accomplish. Values appear surrounded by angle brackets (<B><
-></B>) in command descriptions and the online help to show that they are
-user-supplied variable information.
-</UL>
-<P>Some arguments accept multiple values, as indicated by trailing plus sign (
-<B>+</B> ) in the command descriptions and online help. How many of
-a command's arguments take multiple values, and their ordering with
-respect to other arguments, determine when it is acceptable to omit
-switches. See <A HREF="#HDRNOSWITCH">Conditions for Omitting Switches</A>.
-<P>Some commands have optional as well as required arguments; the command
-descriptions and online help show optional arguments in square brackets ([
-]).
-<P><H6><A NAME="Header_60">Flags</A></H6>
-<P>Some commands have one or more flags, which specify the manner in which
-the command interpreter and server process perform the command, or what kind
-of output it produces. Flags are preceded by hyphens like switches, but
-they take no values. Although the command descriptions and online help
-generally list a command's flags after its arguments, there is no
-prescribed order for flags. They can appear anywhere on the command
-line following the operation code, except in between the parts of an
-argument. Flags are always optional.
-<P><H6><A NAME="HDRCOMMAND-EX">An Example Command</A></H6>
-<P>The following example illustrates the different parts
-of a command that belongs to an AFS command suite.
-<PRE> % <B>bos getdate -server fs1.abc.com -file ptserver kaserver </B>
-
-</PRE>
-<P>where
-<UL>
-<P><LI><B>bos</B> is the command suite. The BOS Server executes most
-of the commands in this suite.
-<P><LI><B>getdate</B> is the operation code. It tells the BOS Server
-on the specified server machine (in this case
-<B>fs1.abc.com</B>) to report the modification dates of
-binary files in the local <B>/usr/afs/bin</B> directory.
-<P><LI><B>-server fs1.abc.com</B> is one argument, with
-<B>-server</B> as the switch and <B>fs1.abc.com</B> as
-the value. This argument specifies the server machine on which BOS
-Server is to collect and report binary dates.
-<P><LI><B>-file ptserver kaserver</B> is an argument that takes multiple
-values. The switch is <B>-file</B> and the values are
-<B>ptserver</B> and <B>kaserver</B>. This argument tells the
-BOS Server to report the modification dates on the files
-<B>/usr/afs/bin/kaserver</B> and <B>/usr/afs/bin/ptserver</B>.
-</UL>
-<P><H6><A NAME="HDRWQ11">Rules for Entering AFS Commands</A></H6>
-<P>Enter each AFS command on a single line (press
-<B><Return></B> only at the end of the command). Some commands
-in this document appear broken across multiple lines, but that is for
-legibility only.
-<P>Use a space to separate each element on a command line from its
-neighbors. Spaces rather than commas also separate multiple values of
-an argument.
-<P>In many cases, the issuer of a command can reduce the amount of typing
-necessary by using one or both of the following methods:
-<UL>
-<P><LI>Omitting switches
-<P><LI>Using accepted abbreviations for operation codes, switches (if they are
-included at all), and some types of values
-</UL>
-<P>The following sections explain the conditions for omitting or shortening
-parts of the command line. It is always acceptable to type a command in
-full, with all of its switches and no abbreviations.
-<P><I><B><A NAME="HDRNOSWITCH">Conditions for Omitting Switches</A>: </B></I>
-It is always acceptable to type the switch part of an
-argument, but in many cases it is not necessary. Specifically, switches
-can be omitted if the following conditions are met.
-<UL>
-<P><LI>All of the command's required arguments appear in the order
-prescribed by the syntax statement
-<P><LI>No switch is provided for any argument
-<P><LI>There is only one value for each argument (but note the important
-exception discussed in the following paragraph)
-</UL>
-<P>Omitting switches is possible only because there is a prescribed order for
-each command's arguments. When the issuer does not include
-switches, the command interpreter relies instead on the order of
-arguments; it assumes that the first element after the operation code is
-the command's first argument, the next element is the command's
-second argument, and so on. The important exception is when a
-command's final required argument accepts multiple values. In this
-case, the command interpreter assumes that the issuer has correctly provided
-one value for each argument up through the final one, so any additional values
-at the end belong to the final argument.
-<P>The following list describes the rules for omitting switches from the
-opposite perspective: an argument's switch must be provided when
-any of the following conditions apply.
-<UL>
-<P><LI>The command's arguments do not appear in the prescribed order
-<P><LI>An optional argument is omitted but a subsequent optional argument is
-provided
-<P><LI>A switch is provided for a preceding argument
-<P><LI>More than one value is supplied for a preceding argument (which must take
-multiple values, of course); without a switch on the current argument,
-the command interpreter assumes that the current argument is another value for
-the preceding argument
-</UL>
-<P><I><B><A NAME="Header_64">An Example of Omitting Switches</A>: </B></I>
-Consider again the example command from <A HREF="#HDRCOMMAND-EX">An Example Command</A>.
-<PRE> % <B> bos getdate -server fs1.abc.com -file ptserver kaserver</B>
-
-</PRE>
-<P>This command has two required arguments: the server machine name
-(identified by the <B>-server</B> switch) and binary file name (identified
-by the <B>-file</B> switch). The second argument accepts multiple
-values. By complying with all three conditions, the issuer can omit the
-switches:
-<PRE> % <B>bos getdate fs1.abc.com ptserver kaserver</B>
-
-</PRE>
-<P>Because there are no switches, the <B>bos</B> command interpreter
-relies on the order of arguments. It assumes that the first element
-following the operation code, <B>fs1.abc.com</B>, is the
-server machine name, and that the next argument, <B>ptserver</B>, is a
-binary file name. Then, because the command's second (and last)
-argument accepts multiple values, the command interpreter correctly interprets
-<B>kaserver</B> as an additional value for it.
-<P>On the other hand, the following is not acceptable because it violates the
-first two conditions in <A HREF="#HDRNOSWITCH">Conditions for Omitting Switches</A>: even though there is only one value per argument, the
-arguments do not appear in the prescribed order, and a switch is provided for
-one argument but not the other.
-<PRE> % <B>bos getdate ptserver -server fs1.abc.com</B>
-
-</PRE>
-<P><H6><A NAME="HDRWQ12">Rules for Using Abbreviations and Aliases</A></H6>
-<P>This section explains how to abbreviate operation codes,
-option names, server machine names, partition names, and cell names. It
-is not possible to abbreviate other types of values.
-<P><I><B><A NAME="Header_66">Abbreviating Operation Codes</A>: </B></I>
-It is acceptable to abbreviate an operation code to the shortest form
-that still distinguishes it from the other operation codes in its
-suite.
-<P>For example, it is acceptable to shorten <B>bos install</B> to <B>bos
-i</B> because there are no other operation codes in the <B>bos</B>
-command suite that begin with the letter <B>i</B>. In contrast,
-there are several <B>bos</B> operation codes that start with the letter
-<B>s</B>, so the abbreviations must be longer to remain unambiguous:
-<DL>
-<DD><P><B>bos sa</B> for <B>bos salvage</B>
-<DD><P><B>bos seta</B> for <B>bos setauth</B>
-<DD><P><B>bos setc</B> for <B>bos setcellname</B>
-<DD><P><B>bos setr</B> for <B>bos setrestart</B>
-<DD><P><B>bos sh</B> for <B>bos shutdown</B>
-<DD><P><B>bos start</B> for <B>bos start</B>
-<DD><P><B>bos startu</B> for <B>bos startup</B>
-<DD><P><B>bos stat</B> for <B>bos status</B>
-<DD><P><B>bos sto</B> for <B>bos stop</B>
-</DL>
-<P>In addition to abbreviations, some operation codes have an
-<I>alias</I>, a short form that is not derived by abbreviating the
-operation code to its shortest unambiguous form. For example, the alias
-for the <B>fs setacl</B> command is <B>fs sa</B>, whereas the shortest
-unambiguous abbreviation is <B>fs seta</B>.
-<P>There are two usual reasons an operation code has an alias:
-<UL>
-<P><LI>Because the command is frequently issued, it is convenient to have a form
-shorter than the one derived by abbreviating. The <B>fs setacl</B>
-command is an example.
-<P><LI>Because the command's name has changed, but users of previous
-versions of AFS know the former name. For example, <B>bos
-listhosts</B> has the alias <B>bos getcell</B>, its former name.
-It is acceptable to abbreviate aliases to their shortest unambiguous form (for
-example, <B>bos getcell</B> to <B>bos getc</B>).
-</UL>
-<P>Even if an operation code has an alias, it is still acceptable to use the
-shortest unambiguous form. Thus, the <B>fs setacl</B> command has
-three acceptable forms: <B>fs setacl</B> (the full form), <B>fs
-seta</B> (the shortest abbreviation), and <B>fs sa</B> (the
-alias).
-<P><I><B><A NAME="Header_67">Abbreviating Switches and Flags</A>: </B></I>
-It is acceptable to shorten a switch or flag to the shortest form that
-distinguishes it from the other switches and flags for its operation
-code. It is often possible to omit switches entirely, subject to the
-conditions listed in <A HREF="#HDRNOSWITCH">Conditions for Omitting Switches</A>.
-<P><I><B><A NAME="HDRFMSABBREV">Abbreviating Server Machine Names</A>: </B></I>
-AFS server machines must have fully-qualified
-Internet-style host names (for example, <B>fs1.abc.com</B>),
-but it is not always necessary to type the full name on the command
-line. AFS commands accept unambiguous shortened forms, but depend on
-the cell's name service (such as the Domain Name Service) or a local host
-table to resolve a shortened name to the fully-qualified equivalent when the
-command is issued.
-<P>Most commands also accept the dotted decimal form of the machine's IP
-address as an identifier.
-<P><I><B><A NAME="HDRPARTABBREV">Abbreviating Partition Names</A>: </B></I>
-Partitions that house AFS volumes must have names of
-the form <B>/vicep</B><VAR>x</VAR> or <B>/vicep</B><VAR>xx</VAR>, where
-the variable final portion is one or two lowercase letters. By
-convention, the first server partition created on a file server machine is
-called <B>/vicepa</B>, the second <B>/vicepb</B>, and so on.
-The <I>IBM AFS Quick Beginnings</I> explains how to configure and name a
-file server machine's partitions in preparation for storing AFS volumes
-on them.
-<P>When issuing AFS commands, you can abbreviate a partition name using any of
-the following forms:
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P><I><B><A NAME="HDRCELLABBREV">Abbreviating Cell Names</A>: </B></I>
-A cell's full name usually matches its Internet
-domain name (such as <B>stateu.edu</B> for the State University or
-<B>abc.com</B> for ABC Corporation). Some AFS commands
-accept unambiguous shortened forms, usually with respect to the local
-<B>/usr/vice/etc/CellServDB file</B> but sometimes depending on the
-ability of the local name service to resolve the corresponding domain
-name.
-<P><H6><A NAME="HDRWQ13">Displaying Online Help for AFS Commands</A></H6>
-<P>To display online help for AFS commands that belong to
-suites, use the <B>help</B> and <B>apropos</B> operation codes.
-A <B>-help</B> flag is also available on every almost every AFS
-command.
-<P>The online help entry for a command consists of two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes what it does
-<P><LI>If the command has aliases, they appear on the next line
-<P><LI>The final line, which begins with the string <TT>Usage:</TT>,
-lists the command's options in the prescribed order; online help
-entries use the same typographical symbols (brackets and so on) as this
-documentation.
-</UL>
-<P>If no operation code is specified, the <B>help</B> operation code
-displays the first line (short description) for every operation code in the
-suite:
-<PRE>
- % <VAR>command_suite</VAR> <B>help</B>
-
-</PRE>
-<P>If the issuer specifies one or more operation codes, the <B>help</B>
-operation code displays each command's complete online entry (short
-description, alias if any, and syntax):
-<PRE>
- % <VAR>command_suite</VAR> <B>help</B> <VAR>operation_code</VAR><SUP>+</SUP>
-
-</PRE>
-<P>The <B>-help</B> flag displays a command's syntax but not the
-short description or alias:
-<PRE> % <VAR>command_name</VAR> <B>-help</B>
-
-</PRE>
-<P>The <B>apropos</B> operation code displays the short description of any
-command in a suite whose operation code or short description includes the
-specified keyword:
-<PRE> % <VAR>command_suite</VAR> <B>apropos</B> <VAR>"<help string>"</VAR>
-
-</PRE>
-<P>The following example command displays the complete online help entry for
-the <B>fs setacl</B> command:
-<PRE>
- % <B>fs help setacl </B>
- fs setacl: set access control list
- aliases: sa
- Usage: fs setacl -dir <directory>+ -acl <access list entries>+
- [-clear] [-negative] [-id] [-if] [-help]
-
-</PRE>
-<P>To see only the syntax statement, use the <B>-help</B> flag:
-<PRE> % <B>fs setacl -help</B>
- Usage: fs setacl -dir <directory>+ -acl <access list entries>+
- [-clear] [-negative] [-id] [-if] [-help]
-
-</PRE>
-<P>In the following example, a user wants to display the quota for her home
-volume. She knows that the relevant command belongs to the
-<B>fs</B> suite, but cannot remember the operation code. She uses
-<B>quota</B> as the keyword:
-<PRE>
- % <B>fs apropos quota</B>
- listquota: list volume quota
- quota: show volume quota usage
- setquota: set volume quota
-
-</PRE>
-<P>The following illustrates the error message that results if no command name
-or short description contains the keyword:
-<PRE>
- % <B>fs apropos "list quota"</B>
- Sorry, no commands found
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>Many AFS commands require one or more types of administrative
-privilege. See the reference page for each command.
-<P><STRONG>Related Information</STRONG>
-<DL>
-<DD><P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<DD><P><A HREF="auarf059.htm#HDRAFSMONITOR">afsmonitor</A>
-<DD><P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<DD><P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<DD><P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<DD><P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<DD><P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<DD><P><A HREF="auarf127.htm#HDRDLOG">dlog</A>
-<DD><P><A HREF="auarf128.htm#HDRDPASS">dpass</A>
-<DD><P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<DD><P><A HREF="auarf130.htm#HDRFMS">fms</A>
-<DD><P><A HREF="auarf131.htm#HDRFS_INTRO">fs</A>
-<DD><P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<DD><P><A HREF="auarf178.htm#HDRFTPD">ftpd (AFS version)</A>
-<DD><P><A HREF="auarf179.htm#HDRINETD">inetd (AFS version)</A>
-<DD><P><A HREF="auarf180.htm#HDRKADB_CHECK">kadb_check</A>
-<DD><P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<DD><P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<DD><P><A HREF="auarf199.htm#HDRKDB">kdb</A>
-<DD><P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<DD><P><A HREF="auarf201.htm#HDRKNFS">knfs</A>
-<DD><P><A HREF="auarf202.htm#HDRKPASSWD">kpasswd</A>
-<DD><P><A HREF="auarf203.htm#HDRKPWVALID">kpwvalid</A>
-<DD><P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<DD><P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<DD><P><A HREF="auarf207.htm#HDRPACKAGE_TEST">package_test</A>
-<DD><P><A HREF="auarf208.htm#HDRPAGSH">pagsh</A>
-<DD><P><A HREF="auarf209.htm#HDRPRDB_CHECK">prdb_check</A>
-<DD><P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<DD><P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<DD><P><A HREF="auarf228.htm#HDRRCP">rcp (AFS version)</A>
-<DD><P><A HREF="auarf229.htm#HDRRSH">rsh (AFS version)</A>
-<DD><P><A HREF="auarf230.htm#HDRRUNNTP">runntp</A>
-<DD><P><A HREF="auarf231.htm#HDRRXDEBUG">rxdebug</A>
-<DD><P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<DD><P><A HREF="auarf233.htm#HDRSCOUT">scout</A>
-<DD><P><A HREF="auarf234.htm#HDRSYS">sys</A>
-<DD><P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<DD><P><A HREF="auarf236.htm#HDRTRANSLATE_ET">translate_et</A>
-<DD><P><A HREF="auarf238.htm#HDRUNLOG">unlog</A>
-<DD><P><A HREF="auarf239.htm#HDRUP">up</A>
-<DD><P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<DD><P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<DD><P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<DD><P><A HREF="auarf248.htm#HDRVLDB_CHECK">vldb_check</A>
-<DD><P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<DD><P><A HREF="auarf250.htm#HDRVOLINFO">volinfo</A>
-<DD><P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<DD><P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<DD><P><A HREF="auarf281.htm#HDRXFS_SIZE_CHECK">xfs_size_check</A>
-<DD><P><A HREF="auarf282.htm#HDRXSTAT_CM_TEST">xstat_cm_test</A>
-<DD><P><A HREF="auarf283.htm#HDRXSTAT_FS_TEST">xstat_fs_test</A>
-</DL>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf056.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf058.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf057.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf059.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAFSD" HREF="auarf002.htm#ToC_72">afsd</A></H2>
-<A NAME="IDX4184"></A>
-<A NAME="IDX4185"></A>
-<A NAME="IDX4186"></A>
-<A NAME="IDX4187"></A>
-<A NAME="IDX4188"></A>
-<A NAME="IDX4189"></A>
-<A NAME="IDX4190"></A>
-<A NAME="IDX4191"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Cache Manager and starts related daemons.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>afsd</B> [-<B>blocks</B> <<VAR>1024 byte blocks in cache</VAR>>]
- [<B>-files</B> <<VAR>files in cache</VAR>>]
- [<B>-rootvol</B> <<VAR>name of AFS root volume</VAR>>]
- [<B>-stat</B> <<VAR>number of stat entries</VAR>>]
- [<B>-memcache</B>] [<B>-cachedir</B> <<VAR>cache directory</VAR>>]
- [<B>-mountdir</B> <<VAR>mount location</VAR>>]
- [<B>-daemons</B> <<VAR>number of daemons to use</VAR>>]
- [<B>-nosettime</B>] [<B>-verbose</B>] [<B>-rmtsys</B>] [<B>-debug</B>]
- [<B>-chunksize</B> <<VAR>log(2) of chunk size</VAR>>]
- [<B>-dcache</B> <<VAR>number of dcache entries</VAR>>]
- [<B>-volumes</B> <<VAR>number of volume entries</VAR>>]
- [<B>-biods</B> <<VAR>number of bkg I/O daemons (aix vm)</VAR>>]
- [<B>-prealloc</B> <<VAR>number of 'small' preallocated blocks</VAR>>]
- [<B>-confdir</B> <<VAR>configuration directory</VAR>>]
- [<B>-logfile</B> <<VAR>Place to keep the CM log</VAR>>]
- [<B>-waitclose</B>] [<B>-shutdown</B>] [<B>-enable_peer_stats</B>]
- [<B>-enable_process_stats</B>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>afsd</B> command initializes the Cache Manager on an AFS client
-machine by transferring AFS-related configuration information into kernel
-memory and starting several daemons. More specifically, the
-<B>afsd</B> command performs the following actions:
-<UL>
-<P><LI>Sets a field in kernel memory that defines the machine's cell
-membership. Some Cache Manager-internal operations and system calls
-consult this field to learn which cell to execute in. (The AFS command
-interpreters refer to the <B>/usr/vice/etc/ThisCell</B> file
-instead.) This information is transferred into the kernel from the
-<B>/usr/vice/etc/ThisCell</B> file and cannot be changed until the
-<B>afsd</B> program runs again.
-<P><LI>Places in kernel memory the names and Internet addresses of the database
-server machines in the local cell and (optionally) foreign cells. The
-appearance of a cell's database server machines in this list enables the
-Cache Manager to contact them and to access files in the cell. Omission
-of a cell from this list, or incorrect information about its database server
-machines, prevents the Cache Manager from accessing files in it.
-<P>The list of database server machines is transferred into the kernel from
-the <B>/usr/vice/etc/CellServDB</B> file. After initialization, use
-the <B>fs newcell</B> command to change the kernel-resident list without
-having to reboot.
-<P><LI>Mounts the root of the AFS filespace on a directory on the machine's
-local disk, according to either the first field in the
-<B>/usr/vice/etc/cacheinfo</B> file (the default) or the <B>afsd</B>
-command's <B>-mountdir</B> argument. The conventional value is
-<B>/afs</B>.
-<P><LI>Determines which volume to mount at the root of the AFS file tree.
-The default is the volume <B>root.afs</B>; use the
-<B>-rootvol</B> argument to override it. Although the base
-(read/write) form of the volume name is the appropriate value, the Cache
-Manager has a bias for accessing the read-only version of the volume (by
-convention, <B>root.afs.readonly</B>) if it is
-available.
-<P><LI>Configures the cache on disk (the default) or in machine memory if the
-<B>-memcache</B> argument is provided. In the latter case, the
-<B>afsd</B> program allocates space in machine memory for caching, and the
-Cache Manager uses no disk space for caching even if the machine has a
-disk.
-<P><LI>Defines the name of the local disk directory devoted to caching, when the
-<B>-memcache</B> argument is not used. If necessary, the
-<B>afsd</B> program creates the directory (its parent directory must
-already exist). It does not remove the directory that formerly served
-this function, if one exists.
-<P>The second field in the <B>/usr/vice/etc/cacheinfo</B> file is the
-source for this name, and the standard value is the <B>/usr/vice/cache</B>
-directory. Use the <B>-cachedir</B> argument to override the value
-in the <B>cacheinfo</B> file.
-<P><LI>Sets the size of the cache. The default source for the value is the
-third field in the <B>/usr/vice/etc/cacheinfo</B> file, which specifies a
-number of kilobytes.
-<P>For a memory cache, the following arguments to the <B>afsd</B> command
-override the value in the <B>cacheinfo</B> file:
-<UL>
-<P><LI>The <B>-blocks</B> argument, to specify a different number of kilobyte
-blocks.
-<P><LI>The <B>-dcache</B> and <B>-chunksize</B> arguments together, to
-set both the number of dcache entries and the chunk size (see below for
-definition of these parameters). In this case, the <B>afsd</B>
-program derives cache size by multiplying the two values. Using this
-combination is not recommended, as it requires the issuer to perform the
-calculation beforehand to determine the resulting cache size.
-<P><LI>The <B>-dcache</B> argument by itself. In this case, the
-<B>afsd</B> program derives cache size by multiplying the value specified
-by the <B>-dcache</B> argument by the default memory cache chunk size of
-eight kilobytes. Using this argument is not recommended, as it requires
-the issuer to perform the calculation beforehand to determine the resulting
-cache size.
-</UL>
-<P>For satisfactory memory cache performance, the specified value must leave
-enough memory free to accommodate all other processes and commands that can
-run on the machine. If the value exceeds the amount of memory
-available, the <B>afsd</B> program exits without initializing the Cache
-Manager and produces the following message on the standard output
-stream:
-<PRE> afsd: memCache allocation failure at <VAR>number</VAR> KB
-
-</PRE>
-<P>where <VAR>number</VAR> is how many kilobytes were allocated just before the
-failure.
-<P>For a disk cache, use the <B>-blocks</B> argument to the
-<B>afsd</B> command to override the value in the <B>cacheinfo</B>
-file. The value specified in either way sets an absolute upper limit on
-cache size; values provided for other arguments (such as
-<B>-dcache</B> and <B>-chunksize</B>) never result in a larger
-cache. The <B>afsd</B> program rejects any setting larger than 95%
-of the partition size, and exits after generating an error message on the
-standard output stream, because the cache implementation itself requires a
-small amount of disk space and overfilling the partition can cause the client
-machine to panic.
-<P>To change the size of a disk cache after initialization without rebooting,
-use the <B>fs setcachesize</B> command; the setting persists until
-the <B>afsd</B> command runs again or the <B>fs setcachesize</B>
-command is reissued. The <B>fs setcachesize</B> command does not
-work for memory caches.
-<P><LI>Sets the size of each cache <VAR>chunk</VAR>, and by implication the amount
-of data that the Cache Manager requests at a time from the File Server (how
-much data per fetch RPC, since AFS uses partial file transfer).
-<P>For a disk cache, a chunk is a <B>V</B><VAR>n</VAR> file and this
-parameter sets the maximum size to which each one can expand; the default
-is 64 KB. For a memory cache, each chunk is a collection of contiguous
-memory blocks; the default is size is 8 KB.
-<P>To override the default chunk size for either type of cache, use the
-<B>-chunksize</B> argument to provide an integer to be used as an exponent
-of two; see the <B>Options</B> section for details. For a
-memory cache, if total cache size divided by chunk size leaves a remainder,
-the <B>afsd</B> program rounds down the number of dcache entries,
-resulting in a slightly smaller cache.
-<P><LI>Sets the number of chunks in the cache. For a memory cache, the
-number of chunks is equal to the cache size divided by the chunk size.
-For a disk cache, the number of chunks (<B>V</B><VAR>n</VAR> files) is set
-to the largest of the following unless the <B>-files</B> argument is used
-to set the value explicitly:
-<UL>
-<P><LI>100
-<P><LI>1.5 times the result of dividing cache size by chunk size
-(<VAR>cachesize</VAR>/<VAR>chunksize</VAR> * 1.5)
-<P><LI>The result of dividing cachesize by 10 KB (<VAR>cachesize</VAR>/10240)
-</UL>
-<P><LI>Sets the number of <VAR>dcache entries</VAR> allocated in machine memory for
-storing information about the chunks in the cache.
-<P>For a disk cache, the <B>/usr/vice/cache/CacheItems</B> file contains
-one entry for each <B>V</B><VAR>n</VAR> file. By default, one half
-the number of these entries (but not more that 2,000) are duplicated as dcache
-entries in machine memory for quicker access.
-<P>For a memory cache, there is no <B>CacheItems</B> file so all
-information about cache chunks must be in memory as dcache entries.
-Thus, there is no default number of dcache entries for a memory cache;
-instead, the <B>afsd</B> program derives it by dividing the cache size by
-the chunk size.
-<P>To set the number of dcache entries, use the <B>-dcache</B>
-argument; the specified value can exceed the default limit of
-2,000. Using this argument is not recommended for either type of
-cache. Increasing the number of dcache entries for a disk cache
-sometimes improves performance (because more entries are retrieved from memory
-rather than from disk), but only marginally. Using this argument for a
-memory cache requires the issuer to calculate the cache size by multiplying
-this value by the chunk size.
-<P><LI>Sets the number of <VAR>stat</VAR> entries available in machine memory for
-caching status information about cached AFS files. The default is
-300; use the <B>-stat</B> argument to override the default.
-<P><LI>Randomly selects a file server machine in the local cell as the source for
-the correct time. Every five minutes thereafter, the local clock is
-adjusted (if necessary) to match the file server machine's clock.
-<P>Use the <B>-nosettime</B> flag to prevent the <B>afsd</B> command
-from selecting a time standard. This is recommended only on file server
-machines that are also acting as clients. File server machines maintain
-the correct time using the Network Time Protocol Daemon instead.
-</UL>
-<P>In addition to setting cache configuration parameters, the <B>afsd</B>
-program starts the following daemons. (On most system types, these
-daemons appear as nameless entries in the output of the UNIX <B>ps</B>
-command.)
-<UL>
-<P><LI>One <I>callback</I> daemon, which handles callbacks. It also
-responds to the File Server's periodic probes, which check that the
-client machine is still alive.
-<P><LI>One <I>maintenance</I> daemon, which performs the following
-tasks:
-<UL>
-<P><LI>Garbage collects obsolete data (for example, expired tokens) from kernel
-memory
-<P><LI>Synchronizes files
-<P><LI>Refreshes information from read-only volumes once per hour
-<P><LI>Does delayed writes for NFS clients if the machine is running the NFS/AFS
-Translator
-</UL>
-<P><LI>One <I>cache-truncation</I> daemon, which flushes the cache when free
-space is required, by writing cached data and status information to the File
-Server.
-<P><LI>One <I>server connection</I> daemon, which sends a probe to the File
-Server every few minutes to check that it is still accessible. It also
-synchronizes the machine's clock with the clock on a randomly-chosen file
-server machine, unless the <B>-nosettime</B> flag is used. There is
-always one server connection daemon.
-<P><LI>One or more <I>background</I> daemons that improve performance by
-pre-fetching files and performing background (delayed) writes of saved data
-into AFS.
-<P>The default number of background daemons is two, enough to service at least
-five simultaneous users of the machine. To increase the number, use the
-<B>-daemons</B> argument. A value greater than six is not generally
-necessary.
-<P><LI>On some system types, one <I>Rx listener</I> daemon, which listens for
-incoming RPCs.
-<P><LI>On some system types, one <I>Rx event</I> daemon, which reviews the Rx
-system's queue of tasks and performs them as appropriate. Most
-items in the queue are retransmissions of failed packets.
-<P><LI>On machines that run AIX with virtual memory (VM) integration, one or more
-<I>VM</I> daemons (sometimes called <I>I/O</I> daemons, which transfer
-data between disk and machine memory. The number of them depends on the
-setting of the <B>-biods</B> and <B>-daemons</B> arguments:
-<UL>
-<P><LI>If the <B>-biods</B> argument is used, it sets the number of VM
-daemons.
-<P><LI>If only the <B>-daemons</B> argument is used, the number of VM daemons
-is twice the number of background daemons.
-<P><LI>If neither argument is used, there are five VM daemons.
-</UL>
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>Do not use the <B>-shutdown</B> parameter. It does not shutdown
-the Cache Manager effectively. Instead, halt Cache Manager activity by
-using the standard UNIX <B>umount</B> command to unmount the AFS root
-directory (by convention, <B>/afs</B>). The machine must then be
-rebooted to reinitialize the Cache Manager.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-blocks
-</B><DD>Specifies the number of kilobyte blocks to be made available for caching
-in the machine's cache directory (for a disk cache) or memory (for a
-memory cache), overriding the default defined in the third field of the
-<B>/usr/vice/etc/cacheinfo</B> file. For a disk cache, the value
-cannot exceed 95% of the space available in the cache partition. If
-using a memory cache, do not combine this argument with the <B>-dcache</B>
-argument, since doing so can possibly result in a chunk size that is not an
-exponent of 2.
-<P><DT><B>-files
-</B><DD>Specifies the number of <B>V</B><VAR>n</VAR> files to create in the
-cache directory for a disk cache, overriding the default that is calculated as
-described in the <B>Description</B> section. Each
-<B>V</B><VAR>n</VAR> file accommodates a chunk of data, and can grow to a
-maximum size of 64 KB by default. Do not combine this argument with the
-<B>-memcache</B> argument.
-<P><DT><B>-rootvol
-</B><DD>Names the read/write volume corresponding to the root directory for the
-AFS file tree (which is usually the <B>/afs</B> directory). This
-value overrides the default of the <B>root.afs</B> volume.
-<P><DT><B>-stat
-</B><DD>Specifies the number of entries to allocate in the machine's memory
-for recording status information about the AFS files in the cache. This
-value overrides the default of 300.
-<P><DT><B>-memcache
-</B><DD>Initializes a memory cache rather than a disk cache. Do not combine
-this flag with the <B>-files</B> argument.
-<P><DT><B>-cachedir
-</B><DD>Names the local disk directory to be used as the cache. This value
-overrides the default defined in the second field of the
-<B>/usr/vice/etc/cacheinfo</B> file.
-<P><DT><B>-mountdir
-</B><DD>Names the local disk directory on which to mount the root of the AFS
-filespace. This value overrides the default defined in the first field
-of the <B>/usr/vice/etc/cacheinfo</B> file. If a value other than
-the <B>/afs</B> directory is used, the machine cannot access the filespace
-of cells that do use that value.
-<P><DT><B>-daemons
-</B><DD>Specifies the number of background daemons to run on the machine.
-These daemons improve efficiency by doing prefetching and background writing
-of saved data. This value overrides the default of 2, which is adequate
-for a machine serving up to five users. Values greater than
-<B>6</B> are not generally more effective than <B>6</B>.
-<P><B>Note:</B> On AIX machines with integrated virtual memory (VM),
-the number of VM daemons is set to twice the value of this argument, if it is
-provided and the <B>-biods</B> argument is not. If both arguments
-are omitted, there are five VM daemons.
-<P><DT><B>-nosettime
-</B><DD>Prevents the Cache Manager from synchronizing its clock with the clock on
-a server machine selected at random, by checking the time on the server
-machine every five minutes. Use this flag only on a machine that is
-already using another time synchronization protocol (for example, a server
-machine that is running the <B>runntp</B> process).
-<P><DT><B>-verbose
-</B><DD>Generates a detailed trace of the <B>afsd</B> program's actions
-on the standard output stream.
-<P><DT><B>-rmtsys
-</B><DD>Initializes an additional daemon to execute AFS-specific system calls on
-behalf of NFS client machines. Use this flag only if the machine is an
-NFS/AFS translator machine serving users of NFS client machines who execute
-AFS commands.
-<A NAME="IDX4192"></A>
-<P><DT><B>-debug
-</B><DD>Generates a highly detailed trace of the <B>afsd</B> program's
-actions on the standard output stream. The information is useful mostly
-for debugging purposes.
-<P><DT><B>-chunksize
-</B><DD>Sets the size of each cache chunk. The integer provided, which must
-be from the range <B>0</B> to <B>30</B>, is used as an exponent on the
-number 2. It overrides the default of 16 for a disk cache
-(2<SUP>16</SUP> is 64 KB) and 13 for a memory cache (2<SUP>13</SUP> is 8
-KB). A value of <B>0</B> or less, or greater than <B>30</B>,
-sets chunk size to the appropriate default. Values less than
-<B>10</B> (which sets chunk size to a 1 KB) are not recommended.
-Combining this argument with the <B>-dcache</B> argument is not
-recommended because it requires that the issuer calculate the cache size that
-results.
-<P><DT><B>-dcache
-</B><DD>Sets the number of dcache entries in memory, which are used to store
-information about cache chunks. For a disk cache, this overrides the
-default, which is 50% of the number of <B>V</B><VAR>n</VAR> files (cache
-chunks). For a memory cache, this argument effectively sets the number
-of cache chunks, but its use is not recommended, because it requires the
-issuer to calculate the resulting total cache size (derived by multiplying
-this value by the chunk size). Do not combine this argument with the
-<B>-blocks</B> argument, since doing so can possibly result in a chunk
-size that is not an exponent of 2.
-<P><DT><B>-volumes
-</B><DD>Specifies the number of memory structures to allocate for storing volume
-location information. The default value is 50.
-<P><DT><B>-biods
-</B><DD>Sets the number of VM daemons dedicated to performing I/O operations on a
-machine running a version of AIX with virtual memory (VM) integration.
-If both this argument and the <B>-daemons</B> argument are omitted, the
-default is five. If this argument is omitted but the
-<B>-daemons</B> argument is provided, the number of VM daemons is set to
-twice the value of the <B>-daemons</B> argument.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">Provide this argument only on a machine that runs AIX with VM
-integration.
-</TD></TR></TABLE>
-<P><DT><B>-prealloc
-</B><DD>Specifies the number of pieces of memory to preallocate for the Cache
-Manager's internal use. The default initial value is 400, but the
-Cache Manager dynamically allocates more memory as it needs it.
-<P><DT><B>-confdir
-</B><DD>Names a directory other than the <B>/usr/vice/etc</B> directory from
-which to fetch the <B>cacheinfo</B>, <B>ThisCell</B>, and
-<B>CellServDB</B> configuration files.
-<P><DT><B>-logfile
-</B><DD>Is obsolete and has no real effect. It specifies an alternate file
-in which to record a type of trace that the Cache Manager no longer
-generates; the default value is <B>/usr/vice/etc/AFSLog</B>.
-<P><DT><B>-waitclose
-</B><DD>Has no effect on the operation of the Cache Manager. The behavior
-it affected in previous versions of the Cache Manager, to perform synchronous
-writes to the File Server, is now the default behavior. To perform
-asynchronous writes in certain cases, use the <B>fs storebehind</B>
-command.
-<P><DT><B>-shutdown
-</B><DD>Shuts down the Cache Manager, but not in the most effective possible
-way. Do not use this flag.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The <B>afsd</B> command is normally included in the machine's AFS
-initialization file, rather than typed at the command shell prompt. For
-most disk caches, the appropriate form is
-<PRE> /usr/vice/etc/afsd
-
-</PRE>
-<P>The following command is appropriate when enabling a machine to act as an
-NFS/AFS Translator machine serving more than five users.
-<PRE> /usr/vice/etc/afsd -daemons 4 -rmtsys
-
-</PRE>
-<P>The following command initializes a memory cache and sets chunk size to 16
-KB (2<SUP>14</SUP>).
-<PRE> /usr/vice/etc/afsd -memcache -chunksize 14
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf017.htm#HDRCACHEITEMS">CacheItems</A>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf036.htm#HDRVN">V<I>n</I></A>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<A NAME="IDX4193"></A>
-<A NAME="IDX4194"></A>
-<A NAME="IDX4195"></A>
-<A NAME="IDX4196"></A>
-<A NAME="IDX4197"></A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf057.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf059.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf058.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf060.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRAFSMONITOR" HREF="auarf002.htm#ToC_73">afsmonitor</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Monitors File Servers and Cache Managers
-<P><STRONG>Description</STRONG>
-<PRE><B>afsmonitor</B> [<B>initcmd</B>] [<B>-config</B> <<VAR>configuration file</VAR>>]
- [<B>-frequency</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-output</B> <<VAR>storage file name</VAR>>] [<B>-detailed</B>]
- [<B>-debug</B> <<VAR>turn debugging output on to the named file</VAR>>]
- [<B>-fshosts</B> <<VAR>list of file servers to monitor</VAR>><SUP>+</SUP>]
- [<B>-cmhosts</B> <<VAR>list of cache managers to monitor</VAR>><SUP>+</SUP>]
- [<B>-buffers</B> <<VAR>number of buffer slots</VAR>>] [<B>-help</B>]
-
-<B>afsmonitor</B> [<B>i</B>] [<B>-co</B> <<VAR>configuration file</VAR>>]
- [<B>-fr</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-o</B> <<VAR>storage file name</VAR>>] [<B>-det</B>]
- [<B>-deb</B> <<VAR>turn debugging output on to the named file</VAR>>]
- [<B>-fs</B> <<VAR>list of file servers to monitor</VAR>><SUP>+</SUP>]
- [<B>-cm</B> <<VAR>list of cache managers to monitor</VAR>><SUP>+</SUP>]
- [<B>-b</B> <<VAR>number of buffer slots</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>afsmonitor</B> command initializes a program that gathers and
-displays statistics about specified File Server and Cache Manager
-operations. It allows the issuer to monitor, from a single location, a
-wide range of File Server and Cache Manager operations on any number of
-machines in both local and foreign cells.
-<P>There are 271 available File Server statistics and 571 available Cache
-Manager statistics, listed in the appendix about <B>afsmonitor</B>
-statistics in the <I>IBM AFS Administration Guide</I>. By default,
-the command displays all of the relevant statistics for the file server
-machines named by the <B>-fshosts</B> argument and the client machines
-named by the <B>-cmhosts</B> argument. To limit the display to only
-the statistics of interest, list them in the configuration file specified by
-the <B>-config</B> argument. In addition, use the configuration
-file for the following purposes:
-<UL>
-<P><LI>To set threshold values for any monitored statistic. When the value
-of a statistic exceeds the threshold, the <B>afsmonitor</B> command
-displays it in reverse video. There are no default threshold
-values.
-<P><LI>To invoke a program or script automatically when a statistic exceeds its
-threshold. The AFS distribution does not include any such
-scripts.
-<P><LI>To list the file server and client machines to monitor, instead of using
-the <B>-fshosts</B> and <B>-cmhosts</B> arguments.
-</UL>
-<P>For a description of the configuration file, see the <B>afsmonitor
-Configuration File</B> reference page
-<P><STRONG>Cautions</STRONG>
-<P>The following software must be accessible to a machine where the
-<B>afsmonitor</B> program is running:
-<UL>
-<P><LI>The AFS <B>xstat</B> libraries, which the <B>afsmonitor</B>
-program uses to gather data
-<P><LI>The <B>curses</B> graphics package, which most UNIX distributions
-provide as a standard utility
-</UL>
-<A NAME="IDX4198"></A>
-<A NAME="IDX4199"></A>
-<P>The <B>afsmonitor</B> screens format successfully both on so-called
-dumb terminals and in windowing systems that emulate terminals. For the
-output to looks its best, the display environment needs to support reverse
-video and cursor addressing. Set the TERM environment variable to the
-correct terminal type, or to a value that has characteristics similar to the
-actual terminal type. The display window or terminal must be at least
-80 columns wide and 12 lines long.
-<A NAME="IDX4200"></A>
-<A NAME="IDX4201"></A>
-<A NAME="IDX4202"></A>
-<P>The <B>afsmonitor</B> program must run in the foreground, and in its
-own separate, dedicated window or terminal. The window or terminal is
-unavailable for any other activity as long as the <B>afsmonitor</B>
-program is running. Any number of instances of the
-<B>afsmonitor</B> program can run on a single machine, as long as each
-instance runs in its own dedicated window or terminal. Note that it can
-take up to three minutes to start an additional instance.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-config
-</B><DD>Names the configuration file which lists the machines to monitor,
-statistics to display, and threshold values, if any. A partial pathname
-is interpreted relative to the current working directory. Provide this
-argument if not providing the <B>-fshosts</B> argument,
-<B>-cmhosts</B> argument, or neither. For instructions on creating
-this file, see the preceding <B>Description</B> section, and the section
-on the <B>afsmonitor</B> program in the <I>IBM AFS Administration
-Guide</I>.
-<P><DT><B>-frequency
-</B><DD>Specifies in seconds how often the <B>afsmonitor</B> program probes
-the File Servers and Cache Managers. Valid values range from
-<B>1</B> to <B>86400</B> (which is 24 hours); the default value
-is <B>60</B>. This frequency applies to both File Servers and Cache
-Managers, but the <B>afsmonitor</B> program initiates the two types of
-probes, and processes their results, separately. The actual interval
-between probes to a host is the probe frequency plus the time required for all
-hosts to respond.
-<P><DT><B>-output
-</B><DD>Names the file to which the <B>afsmonitor</B> program writes all of
-the statistics that it collects. By default, no output file is
-created. See the section on the <B>afsmonitor</B> command in the
-<I>IBM AFS Administration Guide</I> for information on this file.
-<P><DT><B>-detailed
-</B><DD>Formats the information in the output file named by <B>-output</B>
-argument in a maximally readable format. Provide the <B>-output</B>
-argument along with this one.
-<P><DT><B>-fshosts
-</B><DD>Names one or more machines from which to gather File Server
-statistics. For each machine, provide either a fully qualified host
-name, or an unambiguous abbreviation (the ability to resolve an abbreviation
-depends on the state of the cell's name service at the time the command
-is issued). This argument can be combined with the <B>-cmhosts</B>
-argument, but not with the <B>-config</B> argument.
-<P><DT><B>-cmhosts
-</B><DD>Names one or more machines from which to gather Cache Manager
-statistics. For each machine, provide either a fully qualified host
-name, or an unambiguous abbreviation (the ability to resolve an abbreviation
-depends on the state of the cell's name service at the time the command
-is issued). This argument can be combined with the <B>-fshosts</B>
-argument, but not with the <B>-config</B> argument.
-<P><DT><B>-buffers
-</B><DD>Is nonoperational and provided to accommodate potential future
-enhancements to the program.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The <B>afsmonitor</B> program displays its data on three screens:
-<UL>
-<P><LI><TT>System Overview</TT>: This screen appears automatically when
-the <B>afsmonitor</B> program initializes. It summarizes separately
-for File Servers and Cache Managers the number of machines being monitored and
-how many of them have <I>alerts</I> (statistics that have exceeded their
-thresholds). It then lists the hostname and number of alerts for each
-machine being monitored, indicating if appropriate that a process failed to
-respond to the last probe.
-<P><LI><TT>File Server</TT>: This screen displays File Server statistics
-for each file server machine being monitored. It highlights statistics
-that have exceeded their thresholds, and identifies machines that failed to
-respond to the last probe.
-<P><LI><TT>Cache Managers</TT>: This screen displays Cache Manager
-statistics for each client machine being monitored. It highlights
-statistics that have exceeded their thresholds, and identifies machines that
-failed to respond to the last probe.
-</UL>
-<P>Fields at the corners of every screen display the following
-information:
-<UL>
-<P><LI>In the top left corner, the program name and version number.
-<P><LI>In the top right corner, the screen name, current and total page numbers,
-and current and total column numbers. The page number (for example,
-<TT>p. 1 of 3</TT>) indicates the index of the current page and the
-total number of (vertical) pages over which data is displayed. The
-column number (for example, <TT>c. 1 of 235</TT>) indicates the index
-of the current leftmost column and the total number of columns in which data
-appears. (The symbol <TT>>>></TT> indicates that there is additional
-data to the right; the symbol <TT><<<</TT> indicates that
-there is additional data to the left.)
-<P><LI>In the bottom left corner, a list of the available commands. Enter
-the first letter in the command name to run that command. Only the
-currently possible options appear; for example, if there is only one page
-of data, the <TT>next</TT> and <TT>prev</TT> commands, which scroll the
-screen up and down respectively, do not appear. For descriptions of the
-commands, see the following section about navigating the display
-screens.
-<P><LI>In the bottom right corner, the <TT>probes</TT> field reports how many
-times the program has probed File Servers (<TT>fs</TT>), Cache Managers
-(<TT>cm</TT>), or both. The counts for File Servers and Cache
-Managers can differ. The <TT>freq</TT> field reports how often the
-program sends probes.
-</UL>
-<P><B>Navigating the afsmonitor Display Screens</B>
-<P>As noted, the lower left hand corner of every display screen displays the
-names of the commands currently available for moving to alternate screens,
-which can either be a different type or display more statistics or machines of
-the current type. To execute a command, press the lowercase version of
-the first letter in its name. Some commands also have an uppercase
-version that has a somewhat different effect, as indicated in the following
-list.
-<DL>
-<P><DT><B><TT>cm</TT>
-</B><DD>Switches to the <TT>Cache Managers</TT> screen. Available only on
-the <TT>System Overview</TT> and <TT>File Servers</TT> screens.
-<P><DT><B><TT>fs</TT>
-</B><DD>Switches to the <TT>File Servers</TT> screen. Available only on
-the <TT>System Overview</TT> and the <TT>Cache Managers</TT>
-screens.
-<P><DT><B><TT>left</TT>
-</B><DD>Scrolls horizontally to the left, to access the data columns situated to
-the left of the current set. Available when the <TT><<<</TT>
-symbol appears at the top left of the screen. Press uppercase
-<B>L</B> to scroll horizontally all the way to the left (to display the
-first set of data columns).
-<P><DT><B><TT>next</TT>
-</B><DD>Scrolls down vertically to the next page of machine names.
-Available when there are two or more pages of machines and the final page is
-not currently displayed. Press uppercase <B>N</B> to scroll to the
-final page.
-<P><DT><B><TT>oview</TT>
-</B><DD>Switches to the <TT>System Overview</TT> screen. Available only
-on the <TT>Cache Managers</TT> and <TT>File Servers</TT> screens.
-<P><DT><B><TT>prev</TT>
-</B><DD>Scrolls up vertically to the previous page of machine names.
-Available when there are two or more pages of machines and the first page is
-not currently displayed. Press uppercase <B>N</B> to scroll to the
-first page.
-<P><DT><B><TT>right</TT>
-</B><DD>Scrolls horizontally to the right, to access the data columns situated to
-the right of the current set. This command is available when the
-<TT>>>></TT> symbol appears at the upper right of the screen. Press
-uppercase <B>R</B> to scroll horizontally all the way to the right (to
-display the final set of data columns).
-</DL>
-<P><B>The System Overview Screen</B>
-<P>The <TT>System Overview</TT> screen appears automatically as the
-<B>afsmonitor</B> program initializes. This screen displays the
-status of as many File Server and Cache Manager processes as can fit in the
-current window; scroll down to access additional information.
-<P>The information on this screen is split into File Server information on the
-left and Cache Manager information on the right. The header for each
-grouping reports two pieces of information:
-<UL>
-<P><LI>The number of machines on which the program is monitoring the indicated
-process
-<P><LI>The number of alerts and the number of machines affected by them (an
-<I>alert</I>means that a statistic has exceeded its threshold or a process
-failed to respond to the last probe)
-</UL>
-<P>A list of the machines being monitored follows. If there are any
-alerts on a machine, the number of them appears in square brackets to the left
-of the hostname. If a process failed to respond to the last probe, the
-letters <TT>PF</TT> (probe failure) appear in square brackets to the left of
-the hostname.
-<P><B>The File Servers Screen</B>
-<P>The <TT>File Servers</TT> screen displays the values collected at the
-most recent probe for File Server statistics.
-<P>A summary line at the top of the screen (just below the standard program
-version and screen title blocks) specifies the number of monitored File
-Servers, the number of alerts, and the number of machines affected by the
-alerts.
-<P>The first column always displays the hostnames of the machines running the
-monitored File Servers.
-<P>To the right of the hostname column appear as many columns of statistics as
-can fit within the current width of the display screen or window; each
-column requires space for 10 characters. The name of the statistic
-appears at the top of each column. If the File Server on a machine did
-not respond to the most recent probe, a pair of dashes (<TT>--</TT>) appears
-in each column. If a value exceeds its configured threshold, it is
-highlighted in reverse video. If a value is too large to fit into the
-allotted column width, it overflows into the next row in the same
-column.
-<P><B>The Cache Managers Screen</B>
-<P>The <TT>Cache Managers</TT> screen displays the values collected at the
-most recent probe for Cache Manager statistics.
-<P>A summary line at the top of the screen (just below the standard program
-version and screen title blocks) specifies the number of monitored Cache
-Managers, the number of alerts, and the number of machines affected by the
-alerts.
-<P>The first column always displays the hostnames of the machines running the
-monitored Cache Managers.
-<P>To the right of the hostname column appear as many columns of statistics as
-can fit within the current width of the display screen or window; each
-column requires space for 10 characters. The name of the statistic
-appears at the top of each column. If the Cache Manager on a machine
-did not respond to the most recent probe, a pair of dashes (<TT>--</TT>)
-appears in each column. If a value exceeds its configured threshold, it
-is highlighted in reverse video. If a value is too large to fit into
-the allotted column width, it overflows into the next row in the same
-column.
-<P><B>Writing to an Output File</B>
-<P>Include the <B>-output</B> argument to name the file into which the
-<B>afsmonitor</B> program writes all of the statistics it collects.
-The output file can be useful for tracking performance over long periods of
-time, and enables the administrator to apply post-processing techniques that
-reveal system trends. The AFS distribution does not include any
-post-processing programs.
-<P>The output file is in ASCII format and records the same information as the
-<TT>File Server</TT> and <TT>Cache Manager</TT> display screens.
-Each line in the file uses the following format to record the time at which
-the <B>afsmonitor</B> program gathered the indicated statistic from the
-Cache Manager (<TT>CM</TT>) or File Server (<TT>FS</TT>) running on the
-machine called <VAR>host_name</VAR>. If a probe failed, the error code
-<TT>-1</TT> appears in the <VAR>statistic</VAR> field.
-<PRE> <VAR>time</VAR> <VAR>host_name</VAR> CM|FS <VAR>statistic</VAR>
-
-</PRE>
-<P>If the administrator usually reviews the output file manually, rather than
-using it as input to an automated analysis program or script, including the
-<B>-detail</B> flag formats the data in a more easily readable
-form.
-<P><STRONG>Examples</STRONG>
-<P>For examples of commands, display screens, and configuration files, see the
-section about the <B>afsmonitor</B> program in the <I>IBM AFS
-Administration Guide</I>.
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf052.htm#HDRAFSMONCONFIG">afsmonitor Configuration File</A>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf233.htm#HDRSCOUT">scout</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf058.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf060.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf059.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf061.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_INTRO" HREF="auarf002.htm#ToC_74">backup</A></H2>
-<A NAME="IDX4203"></A>
-<A NAME="IDX4204"></A>
-<A NAME="IDX4205"></A>
-<A NAME="IDX4206"></A>
-<A NAME="IDX4207"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>backup</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>backup</B> command suite are the administrative
-interface to the AFS Backup System. There are several categories of
-commands in the suite:
-<UL>
-<P><LI>Commands to copy data from AFS volumes to tape or a backup data file, and
-to restore it to the file system: <B>backup diskrestore</B>,
-<B>backup dump</B>, <B>backup volrestore</B>, and <B>backup
-volsetrestore</B>
-<P><LI>Commands to administer the records in the Backup Database:
-<B>backup adddump</B>, <B>backup addhost</B>, <B>backup
-addvolentry</B>, <B>backup addvolset</B>, <B>backup deldump</B>,
-<B>backup deletedump</B>, <B>backup delhost</B>, <B>backup
-delvolentry</B>, <B>backup delvolset</B>, <B>backup dumpinfo</B>,
-<B>backup listdumps</B>, <B>backup listhosts</B>, <B>backup
-listvolsets</B>, <B>backup scantape</B>, <B>backup setexp</B>, and
-<B>backup volinfo</B>
-<P><LI>Commands to write and read tape labels: <B>backup labeltape</B>
-and <B>backup readlabel</B>
-<P><LI>Commands to list and change the status of backup operations and the
-machines performing them: <B>(backup) jobs</B>, <B>(backup)
-kill</B>, and <B>backup status</B>
-<P><LI>Commands to enter and leave interactive mode: <B>backup
-(interactive)</B> and <B>(backup) quit</B>
-<P><LI>Commands to check for and repair corruption in the Backup Database:
-<B>backup dbverify</B>, <B>backup restoredb</B>, and <B>backup
-savedb</B>
-<P><LI>Commands to obtain help: <B>backup apropos</B> and <B>backup
-help</B>
-</UL>
-<P>The <B>backup</B> command interpreter interacts with two other
-processes:
-<A NAME="IDX4208"></A>
-<A NAME="IDX4209"></A>
-<UL>
-<P><LI>The Backup Server (<B>buserver</B>) process. It maintains the
-Backup Database, which stores most of the administrative information used by
-the Backup System. In the standard configuration, the Backup Server
-runs on each database server machine in the cell, and uses AFS's
-distributed database technology, Ubik, to synchronize its copy of the database
-with the copies on the other database server machines.
-<P><LI>The Backup Tape Coordinator (<B>butc</B>) process. A separate
-instance of the process controls each tape device or backup data file used to
-dump or restore data. The Tape Coordinator runs on a Tape Coordinator
-machine, which is an AFS server or client machine that has one or more tape
-devices attached, or has sufficient disk space to accommodate one or more
-backup data files on its local disk.
-<P>Each Tape Coordinator must be registered in the Backup Database and in the
-<B>/usr/afs/backup/tapeconfig</B> configuration file on the Tape
-Coordinator machine's local disk, and information in the two places must
-be consistent for proper Backup System performance. The optional
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> for each Tape Coordinator
-records information used to automate its operation.
-</UL>
-<P>In addition to the standard command line interface, the <B>backup</B>
-command suite provides an <I>interactive</I> interface, which has several
-useful features described on the <B>backup (interactive)</B> reference
-page. Three of the commands in the suite are available only in
-interactive mode: <B>(backup) jobs</B>, <B>(backup) kill</B>,
-and <B>(backup) quit</B>.
-<P><STRONG>Options</STRONG>
-<P>The following options are available on many commands in the
-<B>backup</B> suite. The reference page for each command also lists
-them, but they are described here in greater detail.
-<A NAME="IDX4210"></A>
-<A NAME="IDX4211"></A>
-<A NAME="IDX4212"></A>
-<DL>
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P>
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell.
-<P>The <B>-cell</B> argument is not available on commands issued in
-interactive mode. The cell defined when the <B>backup</B> command
-interpreter enters interactive mode applies to all commands issued during the
-interactive session.
-<A NAME="IDX4213"></A>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>
-<A NAME="IDX4214"></A>
--localauth
-</B><DD>Constructs a server ticket using the server encryption key with the
-highest key version number in the local <B>/usr/afs/etc/KeyFile</B>
-file. The <B>backup</B> command interpreter presents the ticket,
-which never expires, to the Backup Server, Volume Server and Volume Location
-(VL) Server during mutual authentication.
-<P>Use this flag only when issuing a command on a server machine; client
-machines do not usually have a <B>/usr/afs/etc/KeyFile</B> file.
-The issuer of a command that includes this flag must be logged on to the
-server machine as the local superuser <B>root</B>. The flag is
-useful for commands invoked by an unattended application program, such as a
-process controlled by the UNIX <B>cron</B> utility or by a cron entry in
-the machine's <B>/usr/afs/local/BosConfig</B> file. It is also
-useful if an administrator is unable to authenticate to AFS but is logged in
-as the local superuser <B>root</B>.
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell.
-<P>The <B>-localauth</B> argument is not available on commands issued in
-interactive mode. The local identity and AFS tokens with which the
-<B>backup</B> command interpreter enters interactive mode apply to all
-commands issued during the interactive session.
-<P><DT><B>
-<A NAME="IDX4215"></A>
--portoffset <<VAR>TC port offset</VAR>>
-</B><DD>Specifies the port offset number of the Tape Coordinator that is to
-execute the <B>backup</B> command. The port offset number uniquely
-identifies a pairing of a Tape Coordinator (<B>butc</B>) process and tape
-device or backup data file.
-<P>The <B>backup</B> command interpreter and Tape Coordinator process
-communicate via a UDP socket, or port. Before issuing a
-<B>backup</B> command that involves reading or writing a tape, the backup
-operator must start a <B>butc</B> process that controls the appropriate
-tape device and listens for requests sent to its port number. If a
-Backup System machine has multiple tape devices attached, they can perform
-backup operations simultaneously because each device has its own associated
-<B>butc</B> process and port offset number.
-<P>The Backup System associates a tape capacity and file mark size with each
-port offset (as defined in the <B>tapeconfig</B> file). For a
-compressing tape device, the capacity and file mark values differ for
-compression and non-compression modes, so the two modes have distinct port
-offset numbers.
-<P>The Backup Database can store up to 58,511 port offsets, so the legal
-values for this argument are the integers <B>0</B> through
-<B>58510</B>. If the issuer omits the argument, it defaults to
-<B>0</B>. (The limit of 58,511 port offsets results from the fact
-that UDP socket numbers are identified by a 16-bit integer, and the lowest
-socket number used by the Backup System is 7025. The largest number
-that a 16-bit integer can represent is 65,535. Subtracting 7,025 yields
-58,510. The addition of port offset 0 (zero) increases the maximum to
-58,511.)
-<P>Although it is possible to define up to 58,511 port offset numbers for a
-cell, it is not possible to run 58,511 tape devices simultaneously, due to the
-following limits:
-<UL>
-<P><LI>The maximum number of dump or restore operations that can run
-simultaneously is 64.
-<P><LI>The maximum number of tape devices that can work together on a restore
-operation is 128 (that is the maximum number of values that can be provided
-for the <B>-portoffset</B> argument to the <B>backup diskrestore</B>,
-<B>backup volrestore</B>, or <B>backup volsetrestore</B>
-command).
-</UL>
-<P>
-<P>The Backup System does not reserve UDP sockets. If another
-application is already using the Tape Coordinator's socket when it tries
-to start, the <B>butc</B> process fails and the following error message
-appears at the shell prompt:
-<PRE> bind: Address already in use
- rxi_GetUDPSocket: bind failed
-
-</PRE>
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<A NAME="IDX4216"></A>
-<A NAME="IDX4217"></A>
-<P>To issue any <B>backup</B> command that accesses the Backup Database
-only, the issuer must be listed in the <B>/usr/afs/etc/UserList</B> file
-on every machine where the Backup Server is running. To issue any
-<B>backup</B> command that accesses volume data, the issuer must appear in
-the <B>UserList</B> file on every Backup Server machine, every Volume
-Location (VL) Server machine, and every file server machine that houses
-affected volumes. By convention, a common <B>UserList</B> file is
-distributed to all database server and file server machines in the
-cell. See the chapter on privileged users in the <I>IBM AFS
-Administration Guide</I> for more information on this type of
-privilege.
-<P>If the <B>-localauth</B> flag is included, the user must instead be
-logged on as the local superuser <B>root</B> on the server machine where
-the <B>backup</B> command is issued.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<P><A HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf066.htm#HDRBK_DBVERIFY">backup dbverify</A>
-<P><A HREF="auarf067.htm#HDRBK_DELDUMP">backup deldump</A>
-<P><A HREF="auarf068.htm#HDRBK_DELETEDUMP">backup deletedump</A>
-<P><A HREF="auarf069.htm#HDRBK_DELHOST">backup delhost</A>
-<P><A HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<P><A HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf074.htm#HDRBK_DUMPINFO">backup dumpinfo</A>
-<P><A HREF="auarf075.htm#HDRBK_HELP">backup help</A>
-<P><A HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<P><A HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<P><A HREF="auarf078.htm#HDRBK_KILL">backup kill</A>
-<P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
-<P><A HREF="auarf080.htm#HDRBK_LISTDUMPS">backup listdumps</A>
-<P><A HREF="auarf081.htm#HDRBK_LISTHOSTS">backup listhosts</A>
-<P><A HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<P><A HREF="auarf083.htm#HDRBK_QUIT">backup quit</A>
-<P><A HREF="auarf084.htm#HDRBK_READLABEL">backup readlabel</A>
-<P><A HREF="auarf085.htm#HDRBK_RESTOREDB">backup restoredb</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P><A HREF="auarf087.htm#HDRBK_SCANTAPE">backup scantape</A>
-<P><A HREF="auarf088.htm#HDRBK_SETEXP">backup setexp</A>
-<P><A HREF="auarf089.htm#HDRBK_STATUS">backup status</A>
-<P><A HREF="auarf090.htm#HDRBK_VOLINFO">backup volinfo</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf059.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf061.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf060.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf062.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_ADDDUMP" HREF="auarf002.htm#ToC_75">backup adddump</A></H2>
-<A NAME="IDX4218"></A>
-<A NAME="IDX4219"></A>
-<A NAME="IDX4220"></A>
-<A NAME="IDX4221"></A>
-<A NAME="IDX4222"></A>
-<A NAME="IDX4223"></A>
-<A NAME="IDX4224"></A>
-<A NAME="IDX4225"></A>
-<A NAME="IDX4226"></A>
-<A NAME="IDX4227"></A>
-<A NAME="IDX4228"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Defines a dump level in the dump hierarchy
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup adddump -dump</B> <<VAR>dump level name</VAR>><SUP>+</SUP> [<B>-expires</B> <<VAR>expiration date</VAR>><SUP>+</SUP>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup addd -d</B> <<VAR>dump level name</VAR>><SUP>+</SUP> [<B>-e</B> <<VAR>expiration date</VAR>><SUP>+</SUP>] [<B>-l</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup adddump</B> command creates one or more dump levels in
-the dump hierarchy stored in the Backup Database, and optionally assigns an
-expiration date to each one. All of the dump levels in the Backup
-Database collectively constitute the dump hierarchy.
-<P>Use the <B>-expires</B> argument to associate an expiration date with
-each dump level. When the Backup System subsequently creates a dump at
-the dump level, it uses the specified value to derive the dump's
-expiration date, which it records on the label of the tape (or backup data
-file). The Backup System refuses to overwrite a tape until after the
-latest expiration date of any dump that the tape contains, unless the
-<B>backup labeltape</B> command is used to relabel the tape. If a
-dump level does not have an expiration date, the Backup System treats dumps
-created at the level as expired as soon as it creates them.
-<P>(Note that the Backup System does not automatically remove a dump's
-record from the Backup Database when the dump reaches its expiration date, but
-only if the tape that contains the dump is recycled or relabeled. To
-remove expired and other obsolete dump records, use the <B>backup
-deletedump</B> command.)
-<P>Define either an absolute or relative expiration date:
-<UL>
-<P><LI>An absolute expiration date defines the month/day/year (and, optionally,
-hour and minutes) at which a dump expires. If the expiration date
-predates the dump creation time, the Backup System immediately treats the dump
-as expired.
-<P><LI>A relative date defines the number of years, months, or days (or a
-combination of the three) after the dump's creation that it
-expires. When the Backup System creates a dump at the dump level, it
-calculates an actual expiration date by adding the relative date to the start
-time of the dump operation.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dump
-</B><DD>Names each dump level to add to the dump hierarchy. Precede full
-dump level names with a slash (for example, <B>/full</B>). Indicate
-an incremental dump level by preceding it with an ordered list of the dump
-levels directly above it in the hierarchy (its parent dump levels); use
-the slash as a separator. The parent dump levels must already
-exist. For example, the dump levels <B>/full</B> and
-<B>/full/incremental1</B> must exist when the incremental dump level
-<B>/full/incremental1/incremental2</B> is created.
-<P>Dump level names can have any number of levels, but cannot exceed 256
-characters in length, including the slashes. The maximum length for any
-single level (the text between slashes) is 28 characters, not including the
-preceding slash.
-<P>All alphanumeric characters are allowed in dump level names. Do not
-use the period (<B>.</B>), however, because it is the separator
-between the volume set name and dump level name in the dump name assigned
-automatically by the <B>backup dump</B> command. It is best not to
-include other metacharacters either; if using them, enclose them in
-double quotes (<B>" "</B>) when issuing the <B>backup adddump</B>
-command outside interactive mode.
-<P><DT><B>-expires
-</B><DD>Defines the absolute or relative expiration date to associate with each
-dump level named by the <B>-dump</B> argument. Absolute expiration
-dates have the following format:
-<P>
-<PRE> [<B>at</B>] {<B>NEVER</B> | <VAR>mm</VAR><B>/</B><VAR>dd</VAR><B>/</B><VAR>yyyy</VAR> [<VAR>hh</VAR><B>:</B><VAR>MM</VAR>] }
-
-</PRE>
-<P>where the optional word <B>at</B> is followed either by the string
-<B>NEVER</B>, which indicates that dumps created at the dump level never
-expire, or by a date value with a required portion (<VAR>mm</VAR> for month,
-<VAR>dd</VAR> for day, and <VAR>yyyy</VAR> for year) and an optional portion
-(<VAR>hh</VAR> for hours and <VAR>MM</VAR> for minutes).
-<P>Omit the <VAR>hh</VAR>:<VAR>MM</VAR> portion to use the default of
-midnight (00:00 hours), or provide a value in 24-hour format (for
-example, <B>20:30</B> is 8:30 p.m.).
-Valid values for the year range from <B>1970</B> to <B>2037</B>;
-higher values are not valid because the latest possible date in the standard
-UNIX representation is in February 2038. The command interpreter
-automatically reduces later dates to the maximum value.
-<P>Relative expiration dates have the following format:
-<PRE> [<B>in</B>] [<VAR>years</VAR><B>y</B>] [<VAR>months</VAR><B>m</B>] [<VAR>days</VAR><B>d</B>]
-
-</PRE>
-<P>
-<P>where the optional word <B>in</B> is followed by at least one of a
-number of years (maximum <B>9999</B>) followed by the letter <B>y</B>,
-a number of months (maximum <B>12</B>) followed by the letter
-<B>m</B>, or a number of days (maximum <B>31</B>) followed by the
-letter <B>d</B>. If providing more than one of the three, list them
-in the indicated order. If the date that results from adding the
-relative expiration value to a dump's creation time is later than the
-latest possible date in the UNIX time representation, the Backup System
-automatically reduces it to that date.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition to be
-associated with each dump level specified by the <B>-dump</B>
-argument.
-</TD></TR></TABLE>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command defines a full dump called <B>/1999</B> with a
-relative expiration date of one year:
-<PRE> % <B>backup adddump -dump /1999 -expires in 1y</B>
-
-</PRE>
-<P>The following command defines an incremental dump called
-<B>/sunday1/monday</B>1 with a relative expiration date of 13 days:
-<PRE> % <B>backup adddump -dump /sunday1/monday1 -expires in 13d</B>
-
-</PRE>
-<P>The following command defines two dump incremental dump levels,
-<B>/Monthly/Week1</B> and <B>/Monthly/Week2</B>. Their parent,
-the full dump level <B>/Monthly</B>, must already exist. The
-expiration date for both levels is 12:00 a.m. on 1 January
-2000.
-<PRE> % <B>backup adddump -dump /Monthly/Week1 /Monthly/Week2 -expires at 01/01/2000</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf067.htm#HDRBK_DELDUMP">backup deldump</A>
-<P><A HREF="auarf068.htm#HDRBK_DELETEDUMP">backup deletedump</A>
-<P><A HREF="auarf080.htm#HDRBK_LISTDUMPS">backup listdumps</A>
-<P><A HREF="auarf088.htm#HDRBK_SETEXP">backup setexp</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf060.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf062.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf061.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf063.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_ADDHOST" HREF="auarf002.htm#ToC_76">backup addhost</A></H2>
-<A NAME="IDX4229"></A>
-<A NAME="IDX4230"></A>
-<A NAME="IDX4231"></A>
-<A NAME="IDX4232"></A>
-<A NAME="IDX4233"></A>
-<A NAME="IDX4234"></A>
-<A NAME="IDX4235"></A>
-<A NAME="IDX4236"></A>
-<A NAME="IDX4237"></A>
-<A NAME="IDX4238"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a Tape Coordinator entry to the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup addhost -tapehost</B> <<VAR>tape machine name</VAR>> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup addh -t</B> <<VAR>tape machine name</VAR>> [<B>-p</B> <<VAR>TC port offset</VAR>>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup addhost</B> command creates a Tape Coordinator entry in
-the Backup Database. The entry records
-<UL>
-<P><LI>The host name of the Tape Coordinator machine where the Tape Coordinator
-(<B>butc</B>) process runs, as specified with the <B>-tapehost</B>
-argument.
-<P><LI>The Tape Coordinator's port offset number, as specified with the
-<B>-portoffset</B> argument. An entry for the port offset must also
-appear in the <B>/usr/afs/backup/tapeconfig</B> file on the Tape
-Coordinator machine, where it is mapped to a UNIX device name (for a tape
-device) or pathname (for a backup data file).
-</UL>
-<P>Each Tape Coordinator must have its own port offset number, and the command
-fails if a Backup Database entry already exists for the requested port offset
-number. To display existing Tape Coordinator entries, use the
-<B>backup listhosts</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-tapehost
-</B><DD>Specifies the fully-qualified hostname of the machine for which to create
-a Tape Coordinator entry in the Backup Database. The machine must have
-an entry in either the cell's naming service (such as the Domain Name
-Service) or the host file (<B>/etc/hosts</B> or equivalent) on the machine
-where the command is issued.
-<P><DT><B>-portoffset
-</B><DD>Specifies the Tape Coordinator's port offset number. Provide
-an integer from the range <B>0</B> through <B>58510</B>, or omit this
-argument to use the default value of <B>0</B> (zero). The value
-must match the port offset number recorded for the same combination of Tape
-Coordinator and tape device or file in the
-<B>/usr/afs/backup/tapeconfig</B> file on the Tape Coordinator machine
-named by the <B>-tapehost</B> argument.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command creates an entry in the Backup Database that assigns
-port offset number 4 to a Tape Coordinator running on the machine
-<B>backup1.abc.com</B>:
-<PRE> % <B>backup addhost -tapehost backup1.abc.com -portoffset 4</B>
-
-</PRE>
-<P>The following command creates a Backup Database entry that assigns port
-offset number 0 to a Tape Coordinator on the machine
-<B>backup3.abc.com</B>:
-<PRE> % <B>backup addhost backup3.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf069.htm#HDRBK_DELHOST">backup delhost</A>
-<P><A HREF="auarf081.htm#HDRBK_LISTHOSTS">backup listhosts</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf061.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf063.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf062.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf064.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_ADDVOLENTRY" HREF="auarf002.htm#ToC_77">backup addvolentry</A></H2>
-<A NAME="IDX4239"></A>
-<A NAME="IDX4240"></A>
-<A NAME="IDX4241"></A>
-<A NAME="IDX4242"></A>
-<A NAME="IDX4243"></A>
-<A NAME="IDX4244"></A>
-<A NAME="IDX4245"></A>
-<A NAME="IDX4246"></A>
-<A NAME="IDX4247"></A>
-<A NAME="IDX4248"></A>
-<A NAME="IDX4249"></A>
-<A NAME="IDX4250"></A>
-<A NAME="IDX4251"></A>
-<A NAME="IDX4252"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Defines a volume entry in a volume set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup addvolentry -name</B> <<VAR>volume set name</VAR>> <B>-server</B> <<VAR>machine name</VAR>>
- <B>-partition</B> <<VAR>partition name</VAR>>
- <B>-volumes</B> <<VAR>volume name (regular expression)</VAR>>
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup addvole -n</B> <<VAR>volume set name</VAR>> <B>-s</B> <<VAR>machine name</VAR>> <B>-p</B> <<VAR>partition name</VAR>>
- <B>-v</B> <<VAR>volume name (regular expression)</VAR>>
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup addvolentry</B> command adds a volume entry definition to
-the existing volume set named by the <B>-name</B> argument. A
-volume entry definition can match one or more volumes, depending on the
-combination of the <B>-server</B>, <B>-partition</B>, and
-<B>-volumes</B> arguments.
-<P>For the <B>-server</B> and <B>-partition</B> arguments, provide
-either
-<UL>
-<P><LI>The name of one machine or partition
-<P><LI>The metacharacter expression <B>.*</B> (period and asterisk),
-which matches every machine name or partition name in the Volume Location
-Database (VLDB).
-</UL>
-<P>For the <B>-volumes</B> argument, specify a combination of alphanumeric
-characters and one or more metacharacters to wildcard part or all of the
-volume name. The <B>Options</B> section lists the acceptable
-metacharacters.
-<P><STRONG>Cautions</STRONG>
-<P>It is best to issue this command in interactive mode. If issuing it
-at the shell prompt, enclose any strings containing metacharacters in double
-quotes, or escape the metacharacters with other delimiters, to prevent the
-shell from interpreting them. Adding volume entries to a temporary
-volume set is possible only within the interactive session in which the volume
-set was created.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the volume set to which to add this volume entry definition.
-The volume set must already exist (use the <B>backup addvolset</B> command
-to create it).
-<P><DT><B>-server
-</B><DD>Defines the set of one or more file server machines that house the volumes
-in the volume entry. Provide either one fully-qualified hostname (such
-as <B>fs1.abc.com</B>) or the metacharacter expression
-<B>.*</B> (period and asterisk), which matches all machine names in
-the VLDB.
-<P><DT><B>-partition
-</B><DD>Defines the set of one or more partitions that house the volumes in the
-volume entry. Provide either one complete partition name (such as
-<B>/vicepa</B>) or the metacharacter expression <B>.*</B>
-(period and asterisk), which matches all partition names.
-<P><DT><B>-volumes
-</B><DD>Defines the set of one or more volumes included in the volume
-entry. Specify the volumes by name, by using any combination of regular
-alphanumeric characters and one or more of the following metacharacter
-expressions:
-<A NAME="IDX4253"></A>
-<A NAME="IDX4254"></A>
-<DL>
-<P><DT><B>.
-</B><DD>The period matches any single character.
-<P><DT><B>*
-</B><DD>The asterisk matches zero or more instances of the preceding
-character. Combine it with any other alphanumeric character or
-metacharacter.
-<P><DT><B>[ ]
-</B><DD>Square brackets around a list of characters match a single instance of any
-of the characters, but no other characters; for example, <B>[abc]</B>
-matches a single <B>a</B> or <B>b</B> or <B>c</B>, but not
-<B>d</B> or <B>A</B>. This expression can be combined with the
-asterisk.
-<P><DT><B>^
-</B><DD>The caret, when used as the first character in a square-bracketed set,
-designates a match with any single character <I>except</I> the characters
-that follow it; for example, <B>[^a]</B> matches any single character
-except lowercase <B>a</B>. This expression can be combined with the
-asterisk.
-<P><DT><B>\
-</B><DD>A backslash preceding any of the metacharacters in this list makes it
-match its literal value only. For example, the expression
-<B>\.</B> (backslash and period) matches a single period,
-<B>\*</B> a single asterisk, and <B>\\</B> a single backslash.
-Such expressions can be combined with the asterisk (for example,
-<B>\.*</B> matches any number of periods).
-</DL>
-<P>
-<P>Perhaps the most common metacharacter expression is the period followed by
-an asterisk (<B>.*</B>). This expression matches any string
-of any length, because the period matches any character and the asterisk means
-any number of that character. As mentioned, it is the only acceptable
-metacharacter expression for the <B>-server</B> and <B>-partition</B>
-arguments. In a volume definition it can stand alone (in which case it
-matches every volume listed in the VLDB), or can combine with regular
-characters. The following example matches any volume name that begins
-with the string <B>user</B> and ends with <B>backup</B>:
-<PRE> <B>user.*backup</B>
-
-</PRE>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command adds a volume entry to the volume set called
-<B>sys</B>. The entry matches all volumes on any machine or
-partition whose names begin with the string <B>sun4x_56</B> followed by a
-period:
-<PRE> backup> <B>addvolentry sys .* .* sun4x_56\..*</B>
-
-</PRE>
-<P>The following command adds a volume entry to the volume set called
-<B>fs2</B>, to match all volumes on the <B>/vicepb</B> partition of
-file server machine <B>fs2.abc.com</B>. Because it is
-issued at the shell prompt, double quotes surround the metacharacters in the
-<B>-volumes</B> argument. (The command is shown here on two lines
-only for legibility reasons.)
-<PRE> % <B>backup addvolentry -name fs2 -server fs2.abc.com \
- -partition /vicepb -volumes ".*"</B>
-
-</PRE>
-<P>The chapter in the <I>IBM AFS Administration Guide</I> about
-configuring the AFS Backup System presents additional examples as well as
-advice on grouping volumes.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<P><A HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<P><A HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf062.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf064.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf063.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf065.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_ADDVOLSET" HREF="auarf002.htm#ToC_78">backup addvolset</A></H2>
-<A NAME="IDX4255"></A>
-<A NAME="IDX4256"></A>
-<A NAME="IDX4257"></A>
-<A NAME="IDX4258"></A>
-<A NAME="IDX4259"></A>
-<A NAME="IDX4260"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a new (empty) volume set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup addvolset -name</B> <<VAR>volume set name</VAR>> [<B>-temporary</B>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup addvols -n</B> <<VAR>volume set name</VAR>> [<B>-t</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup addvolset</B> command creates a new volume set, by
-default adding it to the Backup Database. It is best that the volume
-set's name indicate the volume set's contents; for example,
-define the volume entries in the <B>user</B> volume set to match all user
-volumes. The volume set name must be unique within the Backup Database
-of the local cell.
-<P>After issuing this command, issue the <B>backup addvolentry</B> command
-to define the volume entries in the volume set.
-<P>Sometimes it is convenient to create volume sets without recording them
-permanently in the Backup Database, for example when using the <B>backup
-volsetrestore</B> command to restore a group of volumes that were not
-necessarily backed up together. To create a <I>temporary</I> volume
-set, include the <B>-temporary</B> flag. A temporary volume set
-exists only during the lifetime of the current interactive session, so the
-flag is effective only when used during an interactive session (opened by
-issuing the <B>backup interactive</B> command). If it is included
-when the command is issued at the regular command shell prompt, the command
-appears to succeed, but the volume set is not created. As noted, a
-temporary volume set ceases to exist when the current interactive session
-ends, or use the <B>backup delvolset</B> command to delete it before
-that.
-<P>One advantage of temporary volume sets is that the <B>backup
-addvolset</B> command, and any <B>backup addvolentry</B> commands
-subsequently used to add volume entries to it, complete more quickly than for
-regular volume sets, because no records are created in the Backup
-Database.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the new volume set. The name can include up to 31 of any
-character other than the period. Avoid other metacharacters as
-well.
-<P><DT><B>-temporary
-</B><DD>Creates a volume set that exists only within the context of the current
-interactive session. It is not added to the Backup Database.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command creates a volume set called <B>sys</B>:
-<PRE> % <B>backup addvolset sys</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<P><A HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<P><A HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf063.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf065.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf064.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf066.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_APROPOS" HREF="auarf002.htm#ToC_79">backup apropos</A></H2>
-<A NAME="IDX4261"></A>
-<A NAME="IDX4262"></A>
-<A NAME="IDX4263"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>backup ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup apropos</B> command displays the first line of the online
-help entry for any <B>backup</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>backup help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes
-(<B>" "</B>) or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>backup</B> command where the string specified with the
-<B>-topic</B> argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following example lists all <B>backup</B> commands that include the
-word <B>tape</B> in their names or short descriptions:
-<PRE> % <B>backup apropos tape</B>
- labeltape: label a tape
- readlabel: read the label on tape
- scantape: dump information recovery from tape
- status: get tape coordinator status
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf075.htm#HDRBK_HELP">backup help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf064.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf066.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf065.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf067.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DBVERIFY" HREF="auarf002.htm#ToC_80">backup dbverify</A></H2>
-<A NAME="IDX4264"></A>
-<A NAME="IDX4265"></A>
-<A NAME="IDX4266"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Checks the integrity of the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup dbverify</B> [<B>-detail</B>] [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup db</B> [<B>-d</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup dbverify</B> command checks the integrity of the Backup
-Database. The command's output indicates whether the Backup
-Database is damaged (data is corrupted) or not. If the Backup Database
-is undamaged, it is safe to continue using it. If it is corrupted,
-discontinue any backup operations until it is repaired.
-<P><STRONG>Cautions</STRONG>
-<P>While this command runs, no other backup operation can access the Backup
-Database; the other commands do not run until this command
-completes. Avoid issuing this command when other backup operations are
-likely to run. The <B>backup savedb</B> command repairs some types
-of corruption.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-detail
-</B><DD>Reports the number of orphaned blocks found, any inconsistencies, and the
-name of the server machine running the Backup Server that is checking its copy
-of the database.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command displays one of the following two messages:
-<DL>
-<P><DT><B><TT>Database OK</TT>
-</B><DD>The database is undamaged and can be used.
-<P><DT><B><TT>Database not OK</TT>
-</B><DD>The database is damaged. You can use the <B>backup savedb</B>
-command to repair many kinds of corruption as it creates a backup copy.
-For more detailed instructions, see the <I>IBM AFS Administration
-Guide</I> chapter about performing backup operations.
-</DL>
-<P>The <B>-detail</B> flag provides additional information:
-<UL>
-<P><LI>The number of <I>orphan blocks</I> found. These are ranges of
-memory that the Backup Server preallocated in the database but cannot
-use. Orphan blocks do not interfere with database access, but do waste
-disk space. To free the unusable space, dump the database to tape by
-using the <B>backup savedb</B> command, and then restore it by using the
-<B>backup restoredb</B> command.
-<P><LI>Any inconsistencies in the database, such as invalid hostnames for Tape
-Coordinator machines.
-<P><LI>The name of the database server machine on which the Backup Database was
-checked, designated as the <TT>Database checker</TT>. For a detailed
-trace of the verification operation, see the
-<B>/usr/afs/logs/BackupLog</B> file on the indicated machine. You
-can use the <B>bos getlog</B> command to display it.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command confirms that the Backup Database is undamaged:
-<PRE> % <B>backup dbverify</B>
- Database OK
-
-</PRE>
-<P>The following command confirms that the Backup Database is undamaged and
-that it has no orphan blocks or invalid Tape Coordinator entries. The
-Backup Server running on the machine <B>db1.abc.com</B>
-checked its copy of the Database.
-<PRE> % <B>backup dbverify -detail</B>
- Database OK
- Orphan blocks 0
- Database checker was db1.abc.com
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf014.htm#HDRBACKUPLOG">BackupLog</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf085.htm#HDRBK_RESTOREDB">backup restoredb</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf065.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf067.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf066.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf068.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DELDUMP" HREF="auarf002.htm#ToC_81">backup deldump</A></H2>
-<A NAME="IDX4267"></A>
-<A NAME="IDX4268"></A>
-<A NAME="IDX4269"></A>
-<A NAME="IDX4270"></A>
-<A NAME="IDX4271"></A>
-<A NAME="IDX4272"></A>
-<A NAME="IDX4273"></A>
-<A NAME="IDX4274"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a dump level from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup deldump -dump</B> <<VAR>dump level name</VAR>> [<B>-localauth</B>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup deld -d</B> <<VAR>dump level name</VAR>> [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup deldump</B> command deletes the indicated dump level and
-all of its child dump levels from the dump hierarchy in the Backup
-Database. Use the <B>backup listdumps</B> command to display the
-dump hierarchy.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dump
-</B><DD>Specifies the complete pathname of the dump level to delete.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command deletes the dump level <B>/sunday1/monday1</B>
-from the dump hierarchy, along with any of its child dump levels.
-<PRE> % <B>backup deldump /sunday1/monday1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<P><A HREF="auarf080.htm#HDRBK_LISTDUMPS">backup listdumps</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf066.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf068.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf067.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf069.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DELETEDUMP" HREF="auarf002.htm#ToC_82">backup deletedump</A></H2>
-<A NAME="IDX4275"></A>
-<A NAME="IDX4276"></A>
-<A NAME="IDX4277"></A>
-<A NAME="IDX4278"></A>
-<A NAME="IDX4279"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes one or more dump records from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup deletedump</B> [<B>-dumpid</B> <<VAR>dump id</VAR>><SUP>+</SUP>] [<B>-from</B> <<VAR>date time</VAR>><SUP>+</SUP>] [<B>-to</B> <<VAR>date time</VAR>><SUP>+</SUP>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup dele</B> [<B>-d</B> <<VAR>dump id</VAR>><SUP>+</SUP>] [<B>-f</B> <<VAR>date time</VAR>><SUP>+</SUP>] [<B>-t</B> <<VAR>date time</VAR>><SUP>+</SUP>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup deletedump</B> command deletes one or more dump records
-from the Backup Database. Either use the <B>-dumpid</B> argument to
-specify the dump ID number of one or more dumps, or use the <B>-from</B>
-and <B>-to</B> arguments to delete the records for all regular dumps
-created during the time period bracketed by the specified values.
-<P>Use this command to remove dump records that are incorrect (possibly
-because a dump operation was interrupted or failed), or that correspond to
-dumps that are expired or otherwise no longer needed.
-<P><STRONG>Cautions</STRONG>
-<P>The only way to remove the dump record for an appended dump is to remove
-the record for its initial dump, and doing so removes the records for all of
-the initial dump's associated appended dumps.
-<P>The only way to remove the record for a Backup Database dump (created with
-the <B>backup savedb</B> command) is to specify its dump ID number with
-the <B>-dumpid</B> argument. Using the <B>-from</B> and
-<B>-to</B> arguments never removes database dump records.
-<P>Removing records of a dump makes it impossible to restore data from the
-corresponding tapes or from any dump that refers to the deleted dump as its
-parent, directly or indirectly. That is, restore operations must begin
-with the full dump and continue with each incremental dump in order. If
-the records for a specific dump are removed, it is not possible to restore
-data from later incremental dumps unless the deleted records are restored by
-running the <B>backup scantape</B> command with the <B>-dbadd</B>
-flag.
-<P>If a dump set contains any dumps that were created outside the time range
-specified by the <B>-from</B> and <B>-to</B> arguments, the command
-does not delete any of the records associated with the dump set, even if some
-of them represent dumps created during the time range.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dumpid
-</B><DD>Specifies the dump ID of each dump record to delete. The
-corresponding dumps must be initial dumps; it is not possible to delete
-appended dump records directly, but only by deleting the record of their
-associated initial dump. Using this argument is the only way to delete
-records of Backup Database dumps (created with the <B>backup savedb</B>
-command).
-<P>Provide either this argument or the <B>-to</B> (and optionally
-<B>-from</B>) argument.
-<P><DT><B>-from
-</B><DD>Specifies the beginning of a range of dates; the record for any dump
-created during the indicated period of time is deleted.
-<P>Omit this argument to indicate the default of midnight (00:00 hours)
-on 1 January 1970 (UNIX time zero), or provide a date value in the format
-<VAR>mm/dd/yyyy</VAR> [<VAR>hh:MM</VAR>]. The month (<VAR>mm</VAR>),
-day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>) are required. The hour and
-minutes (<VAR>hh</VAR>:<VAR>MM</VAR>) are optional, but if provided must be
-in 24-hour format (for example, the value <B>14:36</B> represents
-2:36 p.m.). If omitted, the time defaults to
-midnight (00:00 hours).
-<P>The <B>-to</B> argument must be provided along with this one.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition.
-</TD></TR></TABLE>
-<P><DT><B>-to
-</B><DD>Specifies the end of a range of dates; the record of any dump created
-during the range is deleted from the Backup Database.
-<P>Provide either the value <B>NOW</B> to indicate the current date and
-time, or a date value in the same format as for the <B>-from</B>
-argument. Valid values for the year (<VAR>yyyy</VAR>) range from
-<B>1970</B> to <B>2037</B>; higher values are not valid because
-the latest possible date in the standard UNIX representation is in February
-2038. The command interpreter automatically reduces any later date to
-the maximum value.
-<P>If the time portion (<VAR>hh:MM</VAR>) is omitted, it defaults to 59
-seconds after midnight (00:00:59 hours). Similarly, the
-<B>backup</B> command interpreter automatically adds 59 seconds to any
-time value provided. In both cases, adding 59 seconds compensates for
-how the Backup Database and <B>backup dumpinfo</B> command represent dump
-creation times in hours and minutes only. For example, the Database
-records a creation timestamp of <TT>20:55</TT> for any dump operation
-that begins between 20:55:00 and 20:55:59.
-Automatically adding 59 seconds to a time thus includes the records for all
-dumps created during that minute.
-<P>Provide either this argument, or the <B>-dumpid</B> argument.
-This argument is required if the <B>-from</B> argument is provided.
-<P><B>Caution:</B> Specifying the value <B>NOW</B> for this
-argument when the <B>-from</B> argument is omitted deletes all dump
-records from the Backup Database (except for Backup Database dump records
-created with the <B>backup savedb</B> command).
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition.
-</TD></TR></TABLE>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>At the conclusion of processing, the output lists the dump IDs of all dump
-records deleted in the following format:
-<PRE> The following dumps were deleted:
- <VAR>dump ID 1</VAR>
- <VAR>dump ID 2</VAR>
- <VAR>etc.</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command deletes the dump record with dump ID 653777462, and
-for any appended dumps associated with it:
-<PRE> % <B>backup deletedump -dumpid 653777462</B>
- The following dumps were deleted:
- 653777462
-
-</PRE>
-<P>The following command deletes the Backup Database record of all dumps
-created between midnight on 1 January 1997 and 23:59:59 hours on
-31 December 1997:
-<PRE> % <B>backup deletedump -from 01/01/1997 -to 12/31/1997</B>
- The following dumps were deleted:
- 598324045
- 598346873
- ...
- ...
- 653777523
- 653779648
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf074.htm#HDRBK_DUMPINFO">backup dumpinfo</A>
-<P><A HREF="auarf087.htm#HDRBK_SCANTAPE">backup scantape</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf067.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf069.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf068.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf070.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DELHOST" HREF="auarf002.htm#ToC_83">backup delhost</A></H2>
-<A NAME="IDX4280"></A>
-<A NAME="IDX4281"></A>
-<A NAME="IDX4282"></A>
-<A NAME="IDX4283"></A>
-<A NAME="IDX4284"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a Tape Coordinator entry from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup delhost -tapehost</B> <<VAR>tape machine name</VAR>> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup delh -t</B> <<VAR>tape machine name</VAR>> [<B>-p</B> <<VAR>TC port offset</VAR>>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup delhost</B> command deletes the indicated Tape
-Coordinator entry from the Backup Database. It is then impossible to
-submit backup operations to that Tape Coordinator, even if it is still
-running. To keep configuration information consistent, also remove the
-corresponding entry from the <B>/usr/afs/backup/tapeconfig</B> file on the
-Tape Coordinator machine.
-<P>To list the Tape Coordinator machines and port offsets defined in the
-Backup Database, issue the <B>backup listhosts</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-tapehost
-</B><DD>Specifies the hostname of the machine housing the Tape Coordinator to
-delete.
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator to delete.
-If omitted, it defaults to <B>0</B>. If provided, it is an integer
-between <B>0</B> (zero) and <B>58510</B>, and must match the port
-offset number assigned to the same combination of Tape Coordinator and tape
-device or file in the <B>/usr/afs/backup/tapeconfig</B> file on the Tape
-Coordinator machine indicated by the <B>-tapehost</B> argument.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command deletes the Backup Database entry for the Tape
-Coordinator with port offset 2 on the Tape Coordinator machine
-<B>backup3.abc.com</B>:
-<PRE> % <B>backup delhost -tapehost backup3.abc.com -portoffset 2</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<P><A HREF="auarf081.htm#HDRBK_LISTHOSTS">backup listhosts</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf068.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf070.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf069.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf071.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DELVOLENTRY" HREF="auarf002.htm#ToC_84">backup delvolentry</A></H2>
-<A NAME="IDX4285"></A>
-<A NAME="IDX4286"></A>
-<A NAME="IDX4287"></A>
-<A NAME="IDX4288"></A>
-<A NAME="IDX4289"></A>
-<A NAME="IDX4290"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a volume entry from a volume set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup delvolentry -name</B> <<VAR>volume set name</VAR>> <B>-entry</B> <<VAR>volume set index</VAR>>
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup delvole -n</B> <<VAR>volume set name</VAR>> <B>-e</B> <<VAR>volume set index</VAR>>
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup delvolentry</B> command deletes the indicated volume
-entry from the volume set specified with the <B>-name</B> argument.
-Use the <B>-entry</B> argument to identify the volume entry by its index
-number. To display the index numbers, use the <B>backup
-listvolsets</B> command.
-<P>If there are any remaining volume entries with index numbers higher than
-the deleted entry, their indexes are automatically decremented to eliminate
-any gaps in the indexing sequence.
-<P><STRONG>Cautions</STRONG>
-<P>Deleting volume entries from a temporary volume set is possible only within
-the interactive session in which the volume set was created.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the volume set from which to delete a volume entry.
-<P><DT><B>-entry
-</B><DD>Specifies the index number of the volume entry to delete. Use the
-<B>backup listvolsets</B> command to display the index numbers for a
-volume set's volume entries.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command deletes the fourth volume entry from the volume set
-called <B>sys</B>:
-<PRE> % <B>backup delvolentry -name sys -entry 4</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<P><A HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf069.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf071.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf070.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf072.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DELVOLSET" HREF="auarf002.htm#ToC_85">backup delvolset</A></H2>
-<A NAME="IDX4291"></A>
-<A NAME="IDX4292"></A>
-<A NAME="IDX4293"></A>
-<A NAME="IDX4294"></A>
-<A NAME="IDX4295"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes one or more volume sets from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup delvolset -name</B> <<VAR>volume set name</VAR>><SUP>+</SUP>
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup delvols -n</B> <<VAR>volume set name</VAR>><SUP>+</SUP> [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup delvolset</B> command deletes each volume set named by
-the <B>-name</B> argument, and the volume entries each contains, from the
-Backup Database. The <B>backup listvolsets</B> command lists the
-volume sets (and their volume entries) currently defined in the Backup
-Database.
-<P><STRONG>Cautions</STRONG>
-<P>Deleting a temporary volume set is possible only within the interactive
-session in which it was created. Exiting the interactive session also
-destroys the temporary volume set automatically.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names each volume set to delete.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command deletes the volume set called <B>user</B> and all
-volume entries in it:
-<PRE> % <B>backup delvolset user</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<P><A HREF="auarf082.htm#HDRBK_LISTVOLSETS">backup listvolsets</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf070.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf072.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf071.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf073.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DISKRESTORE" HREF="auarf002.htm#ToC_86">backup diskrestore</A></H2>
-<A NAME="IDX4296"></A>
-<A NAME="IDX4297"></A>
-<A NAME="IDX4298"></A>
-<A NAME="IDX4299"></A>
-<A NAME="IDX4300"></A>
-<A NAME="IDX4301"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restores the entire contents of a partition
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup diskrestore -server</B> <<VAR>machine to restore</VAR>>
- <B>-partition</B> <<VAR>partition to restore</VAR>>
- [<B>-portoffset</B> <<VAR>TC port offset</VAR>><SUP>+</SUP>]
- [-<B>newserver</B> <<VAR>destination machine</VAR>>]
- [<B>-newpartition</B> <<VAR>destination partition</VAR>>]
- [<B>-extension</B> <<VAR>new volume name extension</VAR>>]
- [<B>-n</B>] [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup di -s</B> <<VAR>machine to restore</VAR>> <B>-pa</B> <<VAR>partition to restore</VAR>>
- [<B>-po</B> <<VAR>TC port offset</VAR>><SUP>+</SUP>] [<B>-news</B> <<VAR>destination machine</VAR>>]
- [<B>-newp</B> <<VAR>destination partition</VAR>>] [<B>-e</B> <<VAR>new volume name extension</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup diskrestore</B> command restores all of the volumes for
-which the Volume Location Database (VLDB) lists a read/write site on the
-partition specified with the <B>-server</B> and <B>-partition</B>
-arguments. It is useful if a disk or machine failure corrupts or
-destroys the data on an entire partition. (To restore any read-only or
-backup volumes that resided on the partition, use the <B>vos release</B>
-and <B>vos backup</B> commands, respectively, after restoring the
-read/write version.)
-<P>If restoring only selected volumes to a single site, it is usually more
-efficient to use the <B>backup volrestore</B> command. To restore
-multiple volumes to many different sites, use the <B>backup
-volsetrestore</B> command.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file on the Tape
-Coordinator machine associated with the specified port offset, then the Backup
-System restores data from the backup data file listed for that port offset in
-the Tape Coordinator's <B>/usr/afs/backup/tapeconfig</B> file,
-instead of from tape. For the sake of clarity, the following text
-refers to tapes only, but the Backup System handles backup data files in much
-the same way.)
-<P>The Backup System determines whether the read/write or backup version of
-each volume was dumped more recently, and restores the dumps of that version,
-starting with the most recent full dump. It resets the creation
-timestamp of each restored volume to the date and time at which it begins
-restoring the volume (the creation timestamp appears in the
-<TT>Creation</TT> field of the output from the <B>vos examine</B> and
-<B>vos listvol</B> commands).
-<P>If all of the full and incremental dumps of all relevant volumes were not
-written on compatible tape devices, use the <B>-portoffset</B> argument to
-list multiple port offset numbers in the order in which the tapes are needed
-(first list the port offset for the full dump, second the port offset for the
-level 1 incremental dump, and so on). This implies that the full dumps
-of all relevant volumes must have been written to a type of tape that the
-first Tape Coordinator can read, the level 1 incremental dumps to a type of
-tape the second Tape Coordinator can read, and so on. If dumps are on
-multiple incompatible tape types, use the <B>backup volrestore</B> command
-to restore individual volumes, or the <B>backup volsetrestore</B> command
-after defining groups of volumes that were dumped to compatible tape
-types. For further discussion, see the <I>IBM AFS Administration
-Guide</I>.
-<P>By default, the Backup System restores the contents of the specified
-partition to that same partition. To restore the contents to an
-alternate site, combine the following options as indicated. The Backup
-System removes each volume from the original site, if it still exists, and
-records the change of site in the VLDB.
-<UL>
-<P><LI>To restore to a different partition on the same file server machine,
-provide the <B>-newpartition</B> argument.
-<P><LI>To restore to the partition with the same name on a different file server
-machine, provide the <B>-newserver</B> argument.
-<P><LI>To restore to a completely different site, combine the
-<B>-newserver</B> and <B>-newpartition</B> arguments.
-</UL>
-<P>By default, the Backup System overwrites the contents of existing volumes
-with the restored data. To create a new volume to house the restored
-data instead, use the <B>-extension</B> argument. The Backup System
-creates the new volume at the site designated by the <B>-newserver</B> and
-<B>-newpartition</B> arguments if they are used or the <B>-server</B>
-and <B>-partition</B> arguments otherwise. It derives the volume
-name by adding the extension to the read/write base name listed in the VLDB,
-and creates a new VLDB entry. The command does not affect the existing
-volume in any way. However, if a volume with the specified extension
-also already exists, the command overwrites it.
-<P>To print out a list of the tapes containing the needed dumps, without
-actually performing the restore operation, include the <B>-n</B> flag
-along with the other options to be used on the actual command.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape it needs by invoking the <B>MOUNT</B> instruction in the
-local <B>CFG_</B><VAR>device_name</VAR> file, or by prompting the backup
-operator to insert the tape if there is no <B>MOUNT</B>
-instruction. However, if the <B>AUTOQUERY NO</B> instruction
-appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of
-the <B>butc</B> command included the <B>-noautoquery</B> flag, the
-Tape Coordinator instead expects the tape to be in the device already.
-If it is not, or is the wrong tape, the Tape Coordinator invokes the
-<B>MOUNT</B> instruction or prompts the operator. It also invokes
-the <B>MOUNT</B> instruction or prompts for any additional tapes needed to
-complete the restore operation; the backup operator must arrange to
-provide them.
-<P><STRONG>Cautions</STRONG>
-<P>If issuing this command to recover data after a disk crash or other damage,
-be sure not to issue the <B>vos syncserv</B> command first. Doing
-so destroys the VLDB record of the volumes that resided on the
-partition.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Names the file server machine that the VLDB lists as the site of the
-volumes that need to be restored.
-<P><DT><B>-partition
-</B><DD>Names the partition that the VLDB lists as the site of the volumes that
-need to be restored.
-<P><DT><B>-portoffset
-</B><DD>Specifies one or more port offset numbers (up to a maximum of 128), each
-corresponding to a Tape Coordinator to use in the operation. If there
-is more than one value, the Backup System uses the first one when restoring
-the full dump of each volume, the second one when restoring the level 1
-incremental dump of each volume, and so on. It uses the final value in
-the list when restoring dumps at the corresponding depth in the dump hierarchy
-and at all lower levels.
-<P>Provide this argument unless the default value of 0 (zero) is appropriate
-for all dumps. If <B>0</B> is just one of the values in the list,
-provide it explicitly in the appropriate order.
-<P><DT><B>-newserver
-</B><DD>Names an alternate file server machine to which to restore the
-volumes. If this argument is omitted, the volumes are restored to the
-file server machine named by the <B>-server</B> argument.
-<P><DT><B>-newpartition
-</B><DD>Names an alternate partition to which to restore the data. If this
-argument is omitted, the volumes are restored to the partition named by the
-<B>-partition</B> argument.
-<P><DT><B>-extension
-</B><DD>Creates a new volume for each volume being restored, to house the restored
-data. The Backup System derives the new volume's name by appending
-the specified string to the read/write base name listed in the VLDB, and
-creates a new VLDB volume entry. The Backup System preserves the
-contents of the volumes on the partition, if any still exist. Any
-string other than <B>.readonly</B> or <B>.backup</B> is
-acceptable, but the combination of the base name and extension cannot exceed
-22 characters in length. To use a period to separate the extension from
-the name, specify it as the first character of the string (as in
-<B>.rst</B>, for example).
-<P><DT><B>-n
-</B><DD>Displays a list of the tapes necessary to perform the requested restore,
-without actually performing the operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If a tape error occurs during the restore operation, the Tape Coordinator
-displays the following messages:
-<PRE> Restore operation on volume <VAR>name</VAR> failed due to tape error
- Do you want to continue (y/n)?
-
-</PRE>
-<P>where <VAR>name</VAR> is the name of the volume that was being restored when
-the tape error occurred. Enter the value <B>y</B> to continue the
-operation without restoring the indicated volume or the value <B>n</B> to
-terminate the operation. In the latter case, the operator can then
-attempt to determine the cause of the tape error.
-<P>If the issuer includes the <B>-n</B> flag with the command, the
-following string appears at the head of the list of the tapes necessary to
-perform the restore operation:
-<PRE> Tapes needed:
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command restores the volumes for which the VLDB lists a
-read/write site on the <B>/vicepd</B> partition of the machine
-<B>fs5.abc.com</B>. The Tape Coordinator associated
-with port offset 3 performs the operation.
-<PRE> % <B>backup diskrestore -server fs5.abc.com -partition /vicepd -portoffset 3</B>
-
-</PRE>
-<P>The following command restores the volumes for which the VLDB lists a
-read/write site on the <B>/vicepb</B> partition of the machine
-<B>fs1.abc.com</B> to a new site: the
-<B>/vicepa</B> partition on the machine
-<B>fs3.abc.com</B>. The Tape Coordinator associated
-with port offset 0 performs the operation. (The command appears here on
-two lines only for legibility.)
-<PRE> % <B>backup diskrestore -server fs1.abc.com -partition /vicepb</B> \
- <B>-newserver fs3.abc.com -newpartition /vicepa</B>
-
-</PRE>
-<P>The following command lists the tapes required to restore the volumes for
-which the VLDB lists a read/write site on the <B>/vicepm</B> partition of
-the machine <B>fs4.abc.com</B>:
-<PRE> % <B>backup diskrestore -server fs4.abc.com -partition /vicepm -n</B>
- Tapes needed:
- user.sunday1.1
- user.sunday1.2
- user.monday1.1
- user.tuesday1.1
- user.wednesday1.1
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server or Volume Location (VL) Server is
-running, and on every file server machine that houses an affected
-volume. If the <B>-localauth</B> flag is included, the issuer must
-instead be logged on to a server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf071.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf073.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf072.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf074.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DUMP" HREF="auarf002.htm#ToC_87">backup dump</A></H2>
-<A NAME="IDX4302"></A>
-<A NAME="IDX4303"></A>
-<A NAME="IDX4304"></A>
-<A NAME="IDX4305"></A>
-<A NAME="IDX4306"></A>
-<A NAME="IDX4307"></A>
-<A NAME="IDX4308"></A>
-<A NAME="IDX4309"></A>
-<A NAME="IDX4310"></A>
-<A NAME="IDX4311"></A>
-<A NAME="IDX4312"></A>
-<A NAME="IDX4313"></A>
-<A NAME="IDX4314"></A>
-<A NAME="IDX4315"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a dump (dumps a volume set at a particular dump level)
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup dump</B> [<B>-volumeset</B> <<VAR>volume set name</VAR>>] [<B>-dump</B> <<VAR>dump level name</VAR>>]
- [<B>-portoffset</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
- [<B>-append</B>] [<B>-n</B>] [<B>-file</B> <<VAR>load file</VAR>>]
- [<B>-localauth</B>] [-<B>cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup dump</B> [<B>-v</B> <<VAR>volume set name</VAR>>] [<B>-d</B> <<VAR>dump level name</VAR>>]
- [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-at</B> <<VAR>Date/time to start dump</VAR>><SUP>+</SUP>]
- [<B>-ap</B>] [<B>-n</B>] [<B>-f</B> <<VAR>load file</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup dump</B> command either dumps the volume set specified by
-the <B>-volumeset</B> argument at the dump level specified by the
-<B>-dump</B> argument and creates a Backup Database dump record about it,
-or executes the dump instructions listed in the file named by the
-<B>-file</B> argument. The Tape Coordinator indicated by the
-<B>-portoffset</B> argument (or on each command in the file) executes the
-operation.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file on the Tape
-Coordinator machine associated with the specified port offset, then the Backup
-System dumps data to the backup data file listed for that port offset in the
-Tape Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather
-than to tape. For the sake of clarity, the following text refers to
-tapes only, but the Backup System handles backup data files in much the same
-way.)
-<P>The term <I>dumping</I> refers to copying a collection of data to tape
-or a backup data file, and the resulting collection is termed a
-<I>dump</I>. The set of tapes that contain one or more dumps is
-called a <I>dump set</I>. The first dump in a dump set is its
-<I>initial dump</I>, and any dumps subsequently added to the dump set (by
-use of the <B>-append</B> argument) are <I>appended dumps</I>.
-Creating appended dumps is optional, and appended dumps can be of different
-volume sets, and at different dump levels, than the initial dump.
-<P>A <I>full dump</I>, created at a full dump level in the dump hierarchy,
-contains all of the data that existed at the time of the dump in the volumes
-belonging to the volume set. An <I>incremental dump</I>, created at
-an incremental dump level, contains only data that has changed since the
-volume set was dumped at the incremental level's <I>parent dump
-level</I> (the dump level immediately above the incremental level in the
-hierarchy), which can be a full or incremental level. More
-specifically, an incremental dump includes only the files and directories that
-have modification timestamps later than the <I>clone date</I> of the
-volume included at the parent dump level. For backup and read-only
-volumes, the clone date is the time at which the volume was cloned from its
-read/write source before being included in the parent dump; for
-read/write volumes, it represents the time at which the volume was locked for
-inclusion in the parent dump. The clone date appears in the <VAR>clone
-date</VAR> field of the output from the <B>backup volinfo</B>
-command. As an example, an incremental dump at the
-<B>/full/week1/thursday</B> level includes only files and directories that
-have changed since the volume set was dumped at the <B>/full/week1</B>
-level.
-<P><B>Initiating different types of dump operations</B>
-<P>To initiate a dump operation that is to start as soon as the relevant Tape
-Coordinator is available, provide only the <B>-volumeset</B>,
-<B>-dump</B>, <B>-portoffset</B>, and optionally <B>-append</B>
-options. To schedule a single <B>backup dump</B> command to execute
-in the future, also include the <B>-at</B> argument to specify the start
-time.
-<P>To append a dump to an existing dump set, include the <B>-append</B>
-flag. The Backup System imposes the following conditions on appended
-dumps:
-<UL>
-<P><LI>If writing to tape, the Tape Coordinator checks that it is the final one
-in a dump set for which there are complete and valid tape and dump records in
-the Backup Database. If not, it rejects the tape and requests an
-acceptable one. The operator can use the <B>-dbadd</B> argument to
-the <B>backup scantape</B> command to insert the necessary records into
-the database.
-<P><LI>The most recent dump on the tape or in the backup data file must have
-completed successfully.
-<P><LI>The dump set must begin with an initial dump that is recorded in the
-Backup Database. If there are no dumps on the tape, then the Backup
-System treats the dump operation as an initial dump and imposes the relevant
-requirements (for example, checks the AFS tape name if appropriate).
-</UL>
-<P>To schedule multiple dump operations, list the operations in the file named
-by the <B>-file</B> argument. Optionally include the <B>-at</B>
-argument to specify when the <B>backup</B> command interpreter reads the
-file; otherwise it reads it immediately. Do not combine the
-<B>-file</B> argument with the command's first three arguments or the
-<B>-append</B> or <B>-n</B> flags. The commands in the file can
-include any of the <B>backup dump</B> command's arguments, including
-the <B>-at</B> argument to schedule them to run even later in the
-future.
-<P>To generate a list of the volumes included in a dump, without actually
-dumping them, combine the <B>-n</B> flag with the options to be used on
-the actual command.
-<P><B>How the Backup System executes a dump operation</B>
-<P>Before beginning a dump operation, the Backup System verifies that there is
-a Backup Database entry for the volume set, dump level, and port
-offset. If the command is correctly formed and issued in interactive
-mode, it is assigned a job number and added to the jobs list. List jobs
-in interactive mode by using the <B>(backup) jobs</B> command;
-terminate them with the <B>(backup) kill</B> command.
-<P>After obtaining the list of volumes to dump from the Volume Location (VL)
-Server, the Backup System sorts the list by site (server and
-partition). It groups volumes from the same site together in the dump
-to minimize the number of times the operator must change tapes during restore
-operations.
-<P>The dependence of an incremental dump on its parent means that a valid
-parent dump must already exist for the Backup System to create its child
-incremental dump. If the Backup System does not find a record of a dump
-created at the immediate parent dump level, it looks in the Backup Database
-for a dump created at one level higher in the hierarchy, and so on, up to the
-full dump level if necessary. It creates an incremental dump at the
-level one below the lowest valid parent dump set that it finds. If it
-fails to find even a full dump, it dumps the volume set at the full dump
-level.
-<P>If the Backup System is unable to access a volume during a dump operation,
-it skips the volume and dumps the remaining volumes from the volume
-set. Possible reasons a volume is inaccessible include server machine
-or process outages, or that the volume was moved between the time the Volume
-Location (VL) Server generated the list of sites for the volume in the volume
-set and the time the Backup System actually attempts to dump the data in
-it. After the first dumping pass, the Backup System attempts to dump
-each volume it skipped. If it still cannot dump a volume and the
-<B>ASK NO</B> instruction does not appear in the
-<B>CFG_</B><VAR>device_name</VAR> file, it queries the operator as to
-whether it needs to attempt to dump the volume again, omit the volume from the
-dump, or halt the dump operation altogether. When prompted, the
-operator can attempt to solve whatever problem prevented the Backup System
-from accessing the volumes. If the <B>ASK NO</B> instruction
-appears in the <B>CFG_</B><VAR>device_name</VAR> file, the Backup System
-omits the volume from the dump.
-<P>Before scheduling a dump operation, the Backup System verifies that the
-date specified by the <B>-at</B> argument is in the future, and checks the
-validity of the volume set, dump level and port offset as for a regular dump
-operation. It checks the validity of the parameters again just before
-actually running the scheduled operation.
-<P>Before writing an initial dump to a tape that does not have a permanent
-name on the label, the Backup System checks that the AFS tape name on the
-label is acceptable. If desired, disable name checking by including the
-<B>NAME_CHECK NO</B> instruction in the
-<B>CFG_</B><VAR>device_name</VAR> file.
-<P>If AFS tape name checking is enabled, the Backup System accepts the
-following three types of values for the AFS tape name. If the name on
-the label does not conform, the Backup System obtains a tape with an
-acceptable label by invoking the <B>MOUNT</B> instruction in the
-<B>CFG_</B><VAR>device_name</VAR> file or prompting the operator.
-<OL TYPE=1>
-<P><LI>A name of the form
-<VAR>volume_set_name.dump_level_name.tape_index</VAR>, where
-<VAR>volume_set_name</VAR> matches the value of the <B>-volumeset</B>
-argument, <VAR>dump_level_name</VAR> matches the last element in the pathname
-value of the <B>-dump</B> argument, and <VAR>tape_index</VAR> reflects the
-tape's place in a multitape dump set. As an example, the first
-tape in a dump set for which the initial dump is of volume set <B>user</B>
-at the dump level <B>/sunday2/monday</B> has AFS tape name
-<B>user.monday.1</B>. If the label records this type
-of AFS tape name, the Backup System retains the AFS tape name and writes the
-dump to the tape.
-<P><LI>The string <TT><NULL></TT>, which usually indicates that a backup
-operator has used the <B>backup labeltape</B> command to write a label on
-the tape, but did not include the <B>-name</B> argument to assign an AFS
-tape name. Presumably, the operator did include the <B>-pname</B>
-argument to assign a permanent name. If the label records a
-<TT><NULL></TT> value, the Backup System constructs and records on the
-label the appropriate AFS tape name, and writes the dump on the tape.
-<P><LI>No value at all, because the tape has never been labeled or used in the
-Backup System. As when the AFS tape name is <TT><NULL></TT>, the
-Backup System constructs and records on the label the appropriate AFS tape
-name, and writes the dump on the tape.
-</OL>
-<P>To determine how much data it can write to a tape, the Tape Coordinator
-reads the capacity recorded on the tape's label (placed there by
-including the <B>-size</B> argument to the <B>backup labeltape</B>
-command). If the label's capacity field is empty, the Tape
-Coordinator uses the capacity recorded for the specified port offset in the
-local <B>tapeconfig</B> file. If the capacity field in the
-<B>tapeconfig</B> file is also empty, the Tape Coordinator uses the
-maximum capacity of 2 TB.
-<P>During a dump operation, the Tape Coordinator tracks how much data it has
-written and stops shortly before it reaches what it believes is the
-tape's capacity. If it is in the middle of writing the data for a
-volume when it reaches that point, it writes a special marker that indicates
-an interrupted volume and continues writing the volume on the next
-tape. It can split a volume this way during both an initial and an
-appended dump, and the fact that the volume resides on multiple tapes is
-automatically recorded in the Backup Database.
-<P>If the tape is actually larger than the expected capacity, then the Tape
-Coordinator simply does not use the excess tape. If the tape is smaller
-than the expected capacity, the Tape Coordinator can reach the end-of-tape
-(EOT) unexpectedly while it is writing data. If the Tape Coordinator is
-in the middle of the writing data from a volume, it obtains a new tape and
-rewrites the entire contents of the interrupted volume to it. The data
-from the volume that was written to the previous tape remains there, but is
-never used.
-<P>The Backup System allows recycling of tapes (writing a new dump set over an
-old dump set that is no longer needed), but imposes the following
-conditions:
-<UL>
-<P><LI>All dumps in the old dump set must be expired. The Backup System
-always checks expiration dates, even when name checking is disabled.
-<P><LI>If the tape to be recycled does not have a permanent name and name
-checking is enabled, then the AFS tape name derived from the new initial
-dump's volume set name and dump level name must match the AFS tape name
-already recorded on the label.
-<P><LI>The tape cannot already have data on it that belongs to the dump currently
-being performed, because that implies that the operator or automated tape
-device has not removed the previous tape from the drive, or has mistakenly
-reinserted it. The Tape Coordinator generates the following message and
-attempts to obtain another tape:
-<PRE> Can't overwrite tape containing the dump in progress
-
-</PRE>
-<P><LI>The tape cannot contain data from a parent dump of the current
-(incremental) dump, because overwriting a parent dump makes it impossible to
-restore data from the current dump. The Tape Coordinator generates the
-following message and attempts to obtain another tape:
-<PRE> Can't overwrite the parent dump <VAR>parent_name</VAR> (<VAR>parent_dump_ID</VAR>)
-
-</PRE>
-</UL>
-<P>To recycle a tape before all dumps on it have expired or if the AFS tape
-name is wrong, use the <B>backup labeltape</B> command to overwrite the
-tape's label and remove all associated tape and dump records from the
-Backup Database.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape by invoking the <B>MOUNT</B> instruction in the
-<B>CFG_</B><VAR>device_name</VAR> file, or by prompting the backup operator
-to insert the tape if there is no <B>MOUNT</B> instruction.
-However, if the <B>AUTOQUERY NO</B> instruction appears in the
-<B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of the
-<B>butc</B> command included the <B>-noautoquery</B> flag, the Tape
-Coordinator instead expects the tape to be in the device already. If it
-is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
-prompts the operator. It also invokes the <B>MOUNT</B> instruction
-or prompts for any additional tapes needed to complete the dump
-operation; the issuer must arrange to provide them.
-<P><STRONG>Cautions</STRONG>
-<P>If a dump operation is interrupted or fails for any reason, data from all
-volumes written to tape before the interrupt are valid can be used in a
-restore operation. The Backup Database includes an entry for the failed
-dump and for each volume that was successfully dumped. See the <I>IBM
-AFS Administration Guide</I> for information on dealing with interrupted
-dumps.
-<P>If dumping to tape rather than a backup data file, it is best to use only
-compatible tape devices (ones that can read the same type of tape).
-Using compatible devices greatly simplifies restore operations. The
-<B>-portoffset</B> argument to the <B>backup diskrestore</B> and
-<B>backup volsetrestore</B> commands accepts multiple port offset numbers,
-but the Backup System uses the first listed port offset when restoring all
-full dumps, the second port offset when restoring all level 1 dumps, and so
-on. At the very least, use compatible tape devices to perform dumps at
-each level. If compatible tape devices are not used, the <B>backup
-volrestore</B> command must be used to restore one volume at a time.
-<P>Valid (unexpired) administrative tokens must be available to the
-<B>backup</B> command interpreter both when it reads the file named by the
-<B>-file</B> argument and when it runs each operation listed in the
-file. Presumably, the issuer is scheduling dumps for times when no
-human operator is present, and so must arrange for valid tokens to be
-available on the local machine. One option is to issue all commands (or
-run all scripts) on file server machines and use the <B>-localauth</B>
-flag on the <B>backup</B> and <B>vos</B> commands. To protect
-against improper access to the machine or the tokens, the machine must be
-physically secure (perhaps even more protected than a Tape Coordinator machine
-monitored by a human operator during operation). Also, if an unattended
-dump requires multiple tapes, the operator must properly configure a tape
-stacker or jukebox and the device configuration file.
-<P>When the command is issued in regular (non-interactive) mode, the command
-shell prompt does not return until the dump operation completes. To
-avoid having to open additional connections, issue the command in interactive
-mode, especially when including the <B>-at</B> argument to schedule dump
-operations.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-volumeset
-</B><DD>Names the volume set to dump. The <B>-dump</B> argument must be
-provided along with this one; do not combine them with the
-<B>-file</B> argument. If using a temporary volume set, the
-<B>vos dump</B> command must be issued within the interactive session in
-which the <B>backup addvolset</B> command was issued with the
-<B>-temporary</B> flag.
-<P><DT><B>-dump
-</B><DD>Specifies the complete pathname of the dump level at which to dump the
-volume set. The <B>-volumeset</B> argument must be provided along
-with this one; do not combine them with the <B>-file</B>
-argument.
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the
-tapes for this operation. It must be provided unless the default value
-of 0 (zero) is appropriate; do not combine it with the <B>-file</B>
-argument.
-<P><DT><B><B>-at</B>
-</B><DD>Specifies the date and time in the future at which to run the command, or
-to read the file named by the <B>-file</B> argument. Provide a
-value in the format <VAR>mm/dd/yyyy</VAR> [<VAR>hh:MM</VAR>], where the
-month (<VAR>mm</VAR>), day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>) are
-required. Valid values for the year range from <B>1970</B> to
-<B>2037</B>; higher values are not valid because the latest possible
-date in the standard UNIX representation is in February 2038. The
-Backup System automatically reduces any later date to the maximum
-value.
-<P>The hour and minutes (<VAR>hh:MM</VAR>) are optional, but if provided
-must be in 24-hour format (for example, the value <B>14:36</B>
-represents 2:36 p.m.). If omitted, the time
-defaults to midnight (00:00 hours).
-<P>As an example, the value <B>04/23/1999 20:20</B> schedules the
-command for 8:20 p.m. on 23 April 1999.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition.
-</TD></TR></TABLE>
-<P><DT><B>-append
-</B><DD>Appends the dump onto the end of a tape that already contains data from
-another dump. However, if the tape is not in fact part of an existing
-dump set, the Backup System creates a new dump set using the parameters of
-this dump. If the tape is not the last tape in the dump set, the Tape
-Coordinator prompts for insertion of the appropriate tape. Do not
-combine this argument with the <B>-file</B> argument.
-<P><DT><B>-n
-</B><DD>Displays the names of volumes to be included in the indicated dump,
-without actually performing the dump operation. Do not combine this
-argument with the <B>-file</B> argument.
-<P><DT><B>-file
-</B><DD>Specifies the local disk or AFS pathname of a file containing
-<B>backup</B> commands. The Backup System reads the file
-immediately, or at the time specified by the <B>-at</B> argument if it is
-provided. A partial pathname is interpreted relative to the current
-working directory.
-<P>Place each <B>backup dump</B> command on its own line in the indicated
-file, using the same syntax as for the command line, but without the word
-<B>backup</B> at the start of the line. Each command must include a
-value for the <B>-volumeset</B> and <B>-dump</B> arguments, and for
-the <B>-portoffset</B> argument unless the default value of 0 is
-appropriate. Commands in the file can also include any of the
-<B>backup dump</B> command's optional options. In the
-following example file, the first command runs as soon as the Backup System
-reads the file, whereas the other commands are themselves scheduled; the
-specified date and time must be later than the date and time at which the
-Backup System reads the file.
-<PRE> dump user /sunday1/wednesday -port 1
- dump sun4x_56 /sunday1/friday -port 2 -at 04/08/1999
- dump sun4x_55 /sunday1/friday -port 2 -at 04/08/1999 02:00 -append
-
-</PRE>
-<P>
-<P>Do not combine this argument with the <B>-volumeset</B>,
-<B>-dump</B>, <B>-portoffset</B>, <B>-append</B>, or <B>-n</B>
-options.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command interpreter first generates a list of the volumes to be
-included in the dump by matching the entries in the volume set against the
-volumes listed in the Volume Location Database (VLDB). It prints the
-list following the header:
-<PRE> Preparing to dump the following volumes:
-
-</PRE>
-<P>The following message then indicates that the command interpreter has
-passed the dump request to the appropriate Tape Coordinator for
-processing:
-<PRE> Starting dump.
-
-</PRE>
-<P>If the issuer includes the <B>-n</B> flag, the output is of the
-following form:
-<PRE> Starting dump of volume set '<VAR>volume set</VAR>' (dump set '<VAR>dump level</VAR>')
- Total number of volumes : <VAR>number dumped</VAR>
- Would have dumped the following volumes:
- <VAR>list_of_volumes</VAR>
-
-</PRE>
-<P>where <VAR>list_of_volumes</VAR> identifies each volume by name and volume ID
-number.
-<P>If the Tape Coordinator is unable to access a volume, it prints an error
-message in its window and records the error in its log and error files.
-<P><STRONG>Examples</STRONG>
-<P>The following command dumps the volumes in the volume set called
-<B>user</B> at the dump level <B>/full/sunday2/monday</B>. The
-issuer places the necessary tapes in the device with port offset 5.
-<PRE> % <B>backup dump -volumeset user -dump /full/sunday2/monday -portoffset 5</B>
- Preparing to dump the following volumes:
- user.jones.backup 387623900
- user.pat.backup 486219245
- user.smith.backup 597315841
- . .
- . .
- Starting dump.
-
-</PRE>
-<P>The following command displays the list of volumes to be dumped when the
-user dumps the <B>sys_sun</B> volume set at the <B>/full</B> dump
-level.
-<PRE> % <B>backup dump -volumeset sys_sun -dump /full -n</B>
- Starting dump of volume set 'sys_sun' (dump set '/full')
- Total number of volumes: 24
- Would have dumped the following volumes:
- sun4x_56 124857238
- sun4x_56.bin 124857241
- . .
- . .
- sun4x_55 124857997
- . .
- . .
-
-</PRE>
-<P>The following command schedules a dump of the volumes in the volume set
-<B>user</B> at the dump level <B>/sunday2/monday1</B> for 11:00
-p.m. on 14 June 1999. The appropriate Tape Coordinator
-has port offset 0 (zero), so that argument is omitted.
-<PRE> % <B>backup dump -volumeset user -dump /sunday2/monday1 -at 06/14/1999 23:00</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server or Volume Location (VL) Server is
-running, and on every file server machine that houses an affected
-volume. If the <B>-localauth</B> flag is included, the issuer must
-instead be logged on to a server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf072.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf074.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf073.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf075.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_DUMPINFO" HREF="auarf002.htm#ToC_88">backup dumpinfo</A></H2>
-<A NAME="IDX4316"></A>
-<A NAME="IDX4317"></A>
-<A NAME="IDX4318"></A>
-<A NAME="IDX4319"></A>
-<A NAME="IDX4320"></A>
-<A NAME="IDX4321"></A>
-<A NAME="IDX4322"></A>
-<A NAME="IDX4323"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays a dump record from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup dumpinfo</B> [<B>-ndumps</B> <<VAR>no. of dumps</VAR>>] [<B>-id</B> <<VAR>dump id</VAR>>]
- [<B>-verbose</B>] [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B> ]
-
-<B>backup dumpi</B> [<B>-n</B> <<VAR>no. of dumps</VAR>>] [<B>-i</B> <<VAR>dump id</VAR>>]
- [<B>-v</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup dumpinfo</B> command formats and displays the Backup
-Database record for the specified dumps. To specify how many of the
-most recent dumps to display, starting with the newest one and going back in
-time, use the <B>-ndumps</B> argument. To display more detailed
-information about a single dump, use the <B>-id</B> argument. To
-display the records for the 10 most recent dumps, omit both the
-<B>-ndumps</B> and <B>-id</B> arguments.
-<P>The <B>-verbose</B> flag produces very detailed information that is
-useful mostly for debugging purposes. It can be combined only with the
-<B>-id</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-ndumps
-</B><DD>Displays the Backup Database record for each of the specified number of
-dumps that were most recently performed. If the database contains fewer
-dumps than are requested, the output includes the records for all existing
-dumps. Do not combine this argument with the <B>-id</B> or
-<B>-verbose</B> options; omit all options to display the records for
-the last 10 dumps.
-<P><DT><B>-id
-</B><DD>Specifies the dump ID number of a single dump for which to display the
-Backup Database record. Precede the <VAR>dump id</VAR> value with the
-<B>-id</B> switch; otherwise, the command interpreter interprets it
-as the value of the <B>-ndumps</B> argument. Combine this argument
-with the <B>-verbose</B> flag, but not with the <B>-ndumps</B>
-argument; omit all options to display the records for the last 10
-dumps.
-<P><DT><B>-verbose
-</B><DD>Provides more detailed information about the dump specified with the
-<B>-id</B> argument, which must be provided along with it. Do not
-combine this flag with the <B>-ndumps</B> argument.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the <B>-ndumps</B> argument is provided, the output presents the
-following information in table form, with a separate line for each dump:
-<DL>
-<P><DT><B><TT>dumpid</TT>
-</B><DD>The dump ID number.
-<P><DT><B><TT>parentid</TT>
-</B><DD>The dump ID number of the dump's parent dump. A value of
-<TT>0</TT> (zero) identifies a full dump.
-<P><DT><B><TT>lv</TT>
-</B><DD>The depth in the dump hierarchy of the dump level used to create the
-dump. A value of <TT>0</TT> (zero) identifies a full dump, in which
-case the value in the <TT>parentid</TT> field is also <TT>0</TT>. A
-value of <TT>1</TT> or greater indicates an incremental dump made at the
-corresponding level in the dump hierarchy.
-<P><DT><B><TT>created</TT>
-</B><DD>The date and time at which the Backup System started the dump operation
-that created the dump.
-<P><DT><B><TT>nt</TT>
-</B><DD>The number of tapes that contain the data in the dump. A value of
-<TT>0</TT> (zero) indicates that the dump operation was terminated or
-failed. Use the <B>backup deletedump</B> command to remove such
-entries.
-<P><DT><B><TT>nvols</TT>
-</B><DD>The number of volumes from which the dump includes data. If a
-volume spans tapes, it is counted twice. A value of <TT>0</TT> (zero)
-indicates that the dump operation was terminated or failed; the value in
-the <TT>nt</TT> field is also <TT>0</TT> in this case.
-<P><DT><B><TT>dump name</TT>
-</B><DD>The dump name in the form
-<PRE> <VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR> (<VAR>initial_dump_ID</VAR>)
-
-</PRE>
-<P>
-<P>where <VAR>volume_set_name</VAR> is the name of the volume set, and
-<VAR>dump_level_name</VAR> is the last element in the dump level pathname at
-which the volume set was dumped.
-<P>The <VAR>initial_dump_ID</VAR>, if displayed, is the dump ID of the initial
-dump in the dump set to which this dump belongs. If there is no value
-in parentheses, the dump is the initial dump in a dump set that has no
-appended dumps.
-</DL>
-<P>If the <B>-id</B> argument is provided alone, the first line of output
-begins with the string <TT>Dump</TT> and reports information for the entire
-dump in the following fields:
-<DL>
-<P><DT><B><TT>id</TT>
-</B><DD>The dump ID number.
-<P><DT><B><TT>level</TT>
-</B><DD>The depth in the dump hierarchy of the dump level used to create the
-dump. A value of <TT>0</TT> (zero) identifies a full dump. A
-value of <TT>1</TT> (one) or greater indicates an incremental dump made at
-the specified level in the dump hierarchy.
-<P><DT><B><TT>volumes</TT>
-</B><DD>The number of volumes for which the dump includes data.
-<P><DT><B><TT>created</TT>
-</B><DD>The date and time at which the dump operation began.
-</DL>
-<P>If an XBSA server was the backup medium for the dump (rather than a tape
-device or backup data file), the following line appears next:
-<PRE> Backup Service: <VAR>XBSA_program</VAR>: Server: <VAR>hostname</VAR>
-</PRE>
-<P>where <VAR>XBSA_program</VAR> is the name of the XBSA-compliant program and
-<VAR>hostname</VAR> is the name of the machine on which the program runs.
-<P>Next the output includes an entry for each tape that houses volume data
-from the dump. Following the string <TT>Tape</TT>, the first two
-lines of each entry report information about that tape in the following
-fields:
-<DL>
-<P><DT><B><TT>name</TT>
-</B><DD>The tape's permanent name if it has one, or its AFS tape name
-otherwise, and its tape ID number in parentheses.
-<P><DT><B><TT>nVolumes</TT>
-</B><DD>The number of volumes for which this tape includes dump data.
-<P><DT><B><TT>created</TT>
-</B><DD>The date and time at which the Tape Coordinator began writing data to this
-tape.
-</DL>
-<P>Following another blank line, the tape-specific information concludes with
-a table that includes a line for each volume dump on the tape. The
-information appears in columns with the following headings:
-<DL>
-<P><DT><B><TT>Pos</TT>
-</B><DD>The relative position of each volume in this tape or file. On a
-tape, the counter begins at position 2 (the tape label occupies position 1),
-and increments by one for each volume. For volumes in a backup data
-file, the position numbers start with 1 and do not usually increment only by
-one, because each is the ordinal of the 16 KB offset in the file at which the
-volume's data begins. The difference between the position numbers
-therefore indicates how many 16 KB blocks each volume's data
-occupies. For example, if the second volume is at position 5 and the
-third volume in the list is at position 9, that means that the dump of the
-second volume occupies 64 KB (four 16-KB blocks) of space in the file.
-<P><DT><B><TT>Clone time</TT>
-</B><DD>For a backup or read-only volume, the time at which it was cloned from its
-read/write source. For a Read/Write volume, it is the same as the dump
-creation date reported on the first line of the output.
-<P><DT><B><TT>Nbytes</TT>
-</B><DD>The number of bytes of data in the dump of the volume.
-<P><DT><B><TT>Volume</TT>
-</B><DD>The volume name, complete with <TT>.backup</TT> or
-<TT>.readonly</TT> extension if appropriate.
-</DL>
-<P>If both the <B>-id</B> and <B>-verbose</B> options are provided,
-the output is divided into several sections:
-<UL>
-<P><LI>The first section, headed by the underlined string <TT>Dump</TT>,
-includes information about the entire dump. The fields labeled
-<TT>id</TT>, <TT>level</TT>, <TT>created</TT>, and <TT>nVolumes</TT>
-report the same values (though in a different order) as appear on the first
-line of output when the <B>-id</B> argument is provided by itself.
-Other fields of potential interest to the backup operator are:
-<DL>
-<P><DT><B><TT>Group id</TT>
-</B><DD>The dump's <I>group ID number</I>, which is recorded in the
-dump's Backup Database record if the <B>GROUPID</B> instruction
-appears in the Tape Coordinator's <B>
-/usr/afs/backup/CFG_</B><VAR>tcid</VAR> file when the dump is created.
-<P><DT><B><TT>maxTapes</TT>
-</B><DD>The number of tapes that contain the dump set to which this dump
-belongs.
-<P><DT><B><TT>Start Tape Seq</TT>
-</B><DD>The ordinal of the tape on which this dump begins in the set of tapes that
-contain the dump set.
-</DL>
-<P><LI>For each tape that contains data from this dump, there follows a section
-headed by the underlined string <TT>Tape</TT>. The fields labeled
-<TT>name</TT>, <TT>written</TT>, and <TT>nVolumes</TT> report the same
-values (though in a different order) as appear on the second and third lines
-of output when the <B>-id</B> argument is provided by itself. Other
-fields of potential interest to the backup operator are:
-<DL>
-<P><DT><B><TT>expires</TT>
-</B><DD>The date and time when this tape can be recycled, because all dumps it
-contains have expired.
-<P><DT><B><TT>nMBytes Data</TT> and <TT>nBytes Data</TT>
-</B><DD>Summed together, these fields represent the total amount of dumped data
-actually from volumes (as opposed to labels, filemarks, and other
-markers).
-<P><DT><B><TT>KBytes Tape Used</TT>
-</B><DD>The number of kilobytes of tape (or disk space, for a backup data file)
-used to store the dump data. It is generally larger than the sum of the
-values in the <TT>nMBytes Data</TT> and <TT>nBytes Data</TT> fields,
-because it includes the space required for the label, file marks and other
-markers, and because the Backup System writes data at 16 KB offsets, even if
-the data in a given block doesn't fill the entire 16 KB.
-</DL>
-<P><LI>For each volume on a given tape, there follows a section headed by the
-underlined string <TT>Volume</TT>. The fields labeled
-<TT>name</TT>, <TT>position</TT>, <TT>clone</TT>, and <TT>nBytes</TT>
-report the same values (though in a different order) as appear in the table
-that lists the volumes in each tape when the <B>-id</B> argument is
-provided by itself. Other fields of potential interest to the backup
-operator are:
-<DL>
-<P><DT><B><TT>id</TT>
-</B><DD>The volume ID.
-<P><DT><B><TT>tape</TT>
-</B><DD>The name of the tape containing this volume data.
-</DL>
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays information about the last five dumps:
-<PRE> % <B>backup dumpinfo -ndumps 5</B>
- dumpid parentid lv created nt nvols dump name
- 924424000 0 0 04/18/1999 04:26 1 22 usr.sun (924424000)
- 924685000 924424000 1 04/21/1999 04:56 1 62 usr.wed (924424000)
- 924773000 924424000 1 04/22/1999 05:23 1 46 usr.thu (924424000)
- 924860000 924424000 1 04/23/1999 05:33 1 58 usr.fri (924424000)
- 925033000 0 0 04/25/1999 05:36 2 73 sys.week
-
-</PRE>
-<P>The following example displays a more detailed record for a single
-dump.
-<PRE> % <B>backup dumpinfo -id 922097346</B>
- Dump: id 922097346, level 0, volumes 1, created Mon Mar 22 05:09:06 1999
- Tape: name monday.user.backup (922097346)
- nVolumes 1, created 03/22/1999 05:09
- Pos Clone time Nbytes Volume
- 1 03/22/1999 04:43 27787914 user.pat.backup
-
-</PRE>
-<P>The following example displays even more detailed information about the
-dump displayed in the previous example (dump ID 922097346). This
-example includes only one exemplar of each type of section (<TT>Dump</TT>,
-<TT>Tape</TT>, and <TT>Volume</TT>):
-<PRE> % <B>backup dumpinfo -id 922097346 -verbose</B>
- Dump
- ----
- id = 922097346
- Initial id = 0
- Appended id = 922099568
- parent = 0
- level = 0
- flags = 0x0
- volumeSet = user
- dump path = /monday1
- name = user.monday1
- created = Mon Mar 22 05:09:06 1999
- nVolumes = 1
- id = 0
- tapeServer =
- format= user.monday1.%d
- maxTapes = 1
- Start Tape Seq = 1
- name = pat
- instance =
- cell =
- Tape
- ----
- tape name = monday.user.backup
- AFS tape name = user.monday1.1
- flags = 0x20
- written = Mon Mar 22 05:09:06 1999
- expires = NEVER
- kBytes Tape Used = 121
- nMBytes Data = 0
- nBytes Data = 19092
- nFiles = 0
- nVolumes = 1
- seq = 1
- tapeid = 0
- useCount = 1
- dump = 922097346
- Volume
- ------
- name = user.pat.backup
- flags = 0x18
- id = 536871640
- server =
- partition = 0
- nFrags = 1
- position = 2
- clone = Mon Mar 22 04:43:06 1999
- startByte = 0
- nBytes = 19092
- seq = 0
- dump = 922097346
- tape = user.monday1.1
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf068.htm#HDRBK_DELETEDUMP">backup deletedump</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf073.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf075.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf074.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf076.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_HELP" HREF="auarf002.htm#ToC_89">backup help</A></H2>
-<A NAME="IDX4324"></A>
-<A NAME="IDX4325"></A>
-<A NAME="IDX4326"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>backup</B> commands or lists
-functional descriptions of all <B>backup</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>backup h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [-<B>h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup help</B> command displays the complete online help entry
-(short description and syntax statement) for each operation code specified by
-the <B>-topic</B> argument. If the <B>-topic</B> argument is
-omitted, the output includes the first line (name and short description) of
-the online help entry for every <B>backup</B> command.
-<P>To list every <B>backup</B> command whose name or short description
-includes a specified keyword, use the <B>backup apropos</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>backup</B> part of the command name, providing
-only the operation code (for example, specify <B>dump</B>, not <B>backup
-dump</B>). If this argument is omitted, the output briefly describes
-every <B>backup</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>backup</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the online help entry for the <B>backup
-dump</B> command:
-<PRE> % <B>backup help dump</B>
- backup dump: start dump
- Usage: backup dump -volumeset <volume set name> -dump <dump level name>
- [-portoffset <TC port offset>] [-at <Date/time to start dump>+]
- [-append] [-n] [-file <load file>] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf065.htm#HDRBK_APROPOS">backup apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf074.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf076.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf075.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf077.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_INTERACTIVE" HREF="auarf002.htm#ToC_90">backup interactive</A></H2>
-<A NAME="IDX4327"></A>
-<A NAME="IDX4328"></A>
-<A NAME="IDX4329"></A>
-<A NAME="IDX4330"></A>
-<A NAME="IDX4331"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Enters interactive mode
-<P><STRONG>Synopsis</STRONG>
-<P>
-<PRE><B>backup</B> [<B>interactive</B>] [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup</B> [<B>i</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup interactive</B> initiates an interactive session for
-issuing <B>backup</B> commands. As indicated in the syntax
-statement, the operation code (<B>interactive</B>) is optional.
-<P>Several features of interactive mode distinguish it from regular
-mode:
-<UL>
-<P><LI>In interactive mode, the <TT>backup></TT> prompt replaces the system
-(shell) prompt. The operator enters only a command's operation
-code (omitting the command suite name, <B>backup</B>).
-<P><LI>If the <B>-localauth</B> flag or the <B>-cell</B> argument is
-included on the <B>backup (interactive)</B> command, the settings apply to
-all commands issued during that interactive session. The issuer does
-not need to type them on every command. Another consequence is that the
-flag and argument do not appear in the syntax statement generated by the
-<B>help</B> subcommand or <B>-help</B> flag on an individual command
-issued at the <TT>backup></TT> prompt.
-<P><LI>The <B>(backup) jobs</B> and <B>(backup) kill</B> commands are
-available only in interactive mode. It is not possible to track and
-terminate backup operations as cleanly in non-interactive mode.
-<P><LI>It is not necessary to enclose strings that include metacharacters in
-double quotes or other delimiters.
-<P><LI>The <B>backup</B> command interpreter establishes a connection to the
-Backup Server, Volume Server and Volume Location (VL) Server processes as it
-enters interactive mode, and uses the same connection for all commands during
-the session. Execution time can therefore be faster than in
-non-interactive mode, in which the command interpreter must establish a new
-connection for each command.
-</UL>
-<P>To exit an interactive session, issue the <B>(backup) quit</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows how the <B>-localauth</B> flag and
-<B>-cell</B> argument do not appear when the <B>help dump</B>
-subcommand is issued in interactive mode.
-<PRE> % <B>backup</B>
- backup> <B>help dump</B>
- dump: start dump
- Usage: dump [-volumeset <volume set name>] [-dump <dump level name>]
- [-portoffset <TC port offset>] [-at <Date/time to start dump>+]
- [-append ] [-n ] [-file <load file>] [-help ]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None. However, <B>backup</B> commands that require privilege in
-regular mode still require it in interactive mode.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<P><A HREF="auarf078.htm#HDRBK_KILL">backup kill</A>
-<P><A HREF="auarf083.htm#HDRBK_QUIT">backup quit</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf075.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf077.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf076.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf078.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_JOBS" HREF="auarf002.htm#ToC_91">backup jobs</A></H2>
-<A NAME="IDX4332"></A>
-<A NAME="IDX4333"></A>
-<A NAME="IDX4334"></A>
-<A NAME="IDX4335"></A>
-<A NAME="IDX4336"></A>
-<A NAME="IDX4337"></A>
-<A NAME="IDX4338"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Lists pending and running operations in interactive mode
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>jobs</B> [<B>-help</B>]
-
-<B>j</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>(backup) jobs</B> command lists the job ID number and status of
-each <B>backup</B> operation running or pending in the current interactive
-session.
-<P>This command can be issued in interactive mode only. If the issuer
-of the <B>backup (interactive)</B> command included the
-<B>-localauth</B> flag, the <B>-cell</B> argument, or both, those
-settings apply to this command also.
-<P>To terminate operations that appear in the output, issue the <B>(backup)
-kill</B> command and identify the operation to cancel with the job ID number
-from this command's output.
-<P>To check the status of a Tape Coordinator, rather than of a certain
-operation, use the <B>backup status</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output always includes the expiration date and time of the tokens that
-the <B>backup</B> command interpreter is using during the current
-interactive session, in the following format:
-<PRE> <VAR>date</VAR> <VAR>time</VAR>: TOKEN EXPIRATION
-</PRE>
-<P>If the execution date and time specified for a scheduled dump operation is
-later than <I>date time</I>, then its individual line (as described in the
-following paragraphs) appears below this line to indicate that the current
-tokens will not be available to it.
-<P>If the issuer of the <B>backup</B> command included the
-<B>-localauth</B> flag when entering interactive mode, the line instead
-reads as follows:
-<PRE> : TOKEN NEVER EXPIRES
-</PRE>
-<P>The entry for a scheduled dump operation has the following format:
-<PRE> Job <VAR>job_ID</VAR>: <VAR>timestamp</VAR>: dump <VAR>volume_set</VAR> <VAR>dump_level</VAR>
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>job_ID</VAR>
-</B><DD>Is a job identification number assigned by the Backup System.
-<P><DT><B><VAR>timestamp</VAR>
-</B><DD>Indicates the date and time the dump operation is to begin, in the format
-<I>month</I>/<I>date</I>/<I>year</I>
-<I>hours</I>:<I>minutes</I> (in 24-hour format)
-<P><DT><B><VAR>volume_set</VAR>
-</B><DD>Indicates the volume set to dump.
-<P><DT><B><VAR>dump_level</VAR>
-</B><DD>Indicates the dump level at which to perform the dump operation.
-</DL>
-<P>The line for a pending or running operation of any other type has the
-following format:
-<PRE> Job <VAR>job_ID</VAR>: <VAR>operation</VAR> <VAR>status</VAR>
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>job_ID</VAR>
-</B><DD>Is a job identification number assigned by the Backup System.
-<P><DT><B><VAR>operation</VAR>
-</B><DD>Identifies the operation the Tape Coordinator is performing, which is
-initiated by the indicated command:
-<DL>
-<P><DT><B><TT>Dump</TT> <TT>(</TT><VAR>dump name</VAR><TT>)</TT>
-</B><DD>Initiated by the <B>backup dump</B> command. The <VAR>dump
-name</VAR> has the following format:
-<P><VAR>volume_set_name</VAR><B>.</B><VAR>dump_level_name</VAR>
-<P><DT><B><TT>Restore</TT>
-</B><DD>Initiated by the <B>backup diskrestore</B>, <B>backup
-volrestore</B>, or <B>backup volsetrestore</B> command.
-<P><DT><B><TT>Labeltape</TT> <TT>(</TT><VAR>tape_label</VAR><TT>)</TT>
-</B><DD>Initiated by the <B>backup labeltape</B> command. The
-<VAR>tape_label</VAR> is the name specified by the <B>backup labeltape</B>
-command's <B>-name</B> or <B>-pname</B> argument.
-<P><DT><B><TT>Scantape</TT>
-</B><DD>Initiated by the <B>backup scantape</B> command.
-<P><DT><B><TT>SaveDb</TT>
-</B><DD>Initiated by the <B>backup savedb</B> command.
-<P><DT><B><TT>RestoreDb</TT>
-</B><DD>Initiated by the <B>backup restoredb</B> command.
-</DL>
-<P><DT><B><VAR>status</VAR>
-</B><DD>Indicates the job's current status in one of the following
-messages. If no message appears, the job is either still pending or has
-finished.
-<DL>
-<P><DT><B><VAR>number</VAR> <TT>Kbytes, volume</TT> <VAR>volume_name</VAR>
-</B><DD>For a running dump operation, indicates the number of kilobytes copied to
-tape or a backup data file so far, and the volume currently being
-dumped.
-<P><DT><B><VAR>number</VAR> <TT>Kbytes, restore.volume</TT>
-</B><DD>For a running restore operation, indicates the number of kilobytes copied
-into AFS from a tape or a backup data file so far.
-<P><DT><B><TT>[abort requested]</TT>
-</B><DD>The <B>(backup) kill</B> command was issued, but the termination
-signal has yet to reach the Tape Coordinator.
-<P><DT><B><TT>[abort sent]</TT>
-</B><DD>The operation is canceled by the <B>(backup) kill</B> command.
-Once the Backup System removes an operation from the queue or stops it from
-running, it no longer appears at all in the output from the command.
-<P><DT><B><TT>[butc contact lost]</TT>
-</B><DD>The <B>backup</B> command interpreter cannot reach the Tape
-Coordinator. The message can mean either that the Tape Coordinator
-handling the operation was terminated or failed while the operation was
-running, or that the connection to the Tape Coordinator timed out.
-<P><DT><B><TT>[done]</TT>
-</B><DD>The Tape Coordinator has finished the operation.
-<P><DT><B><TT>[drive wait]</TT>
-</B><DD>The operation is waiting for the specified tape drive to become
-free.
-<P><DT><B><TT>[operator wait]</TT>
-</B><DD>The Tape Coordinator is waiting for the backup operator to insert a tape
-in the drive.
-</DL>
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows that two restore operations and one dump
-operation are running (presumably on different Tape Coordinators) and that the
-<B>backup</B> command interpreter's tokens expire on 22 April 1999 at
-10:45 am:
-<PRE> backup> <B>jobs</B>
- Job 1: Restore, 1306 Kbytes, restore.volume
- Job 2: Dump (user.sunday1), 34 Kbytes, volume user.pat.backup
- Job 3: Restore, 2498 Kbytes, restore.volume
- 04/22/1999 10:45: TOKEN EXPIRATION
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None. However, queuing any operation requires privilege, and it is
-possible to issue this command only within the interactive session in which
-the jobs are queued.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<P><A HREF="auarf078.htm#HDRBK_KILL">backup kill</A>
-<P><A HREF="auarf083.htm#HDRBK_QUIT">backup quit</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf076.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf078.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf077.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf079.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_KILL" HREF="auarf002.htm#ToC_92">backup kill</A></H2>
-<A NAME="IDX4339"></A>
-<A NAME="IDX4340"></A>
-<A NAME="IDX4341"></A>
-<A NAME="IDX4342"></A>
-<A NAME="IDX4343"></A>
-<A NAME="IDX4344"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Terminates a pending or running operation
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kill -id</B> <<VAR>job ID or dump set name</VAR>> [<B>-help</B>]
-
-<B>k -i</B> <<VAR>job ID or dump set name</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>(backup) kill</B> command dequeues a Backup System operation
-that is pending, or terminates an operation that is running, in the current
-interactive session. It is available only in interactive mode.
-If the issuer of the <B>backup (interactive)</B> command included the
-<B>-localauth</B> flag, the <B>-cell</B> argument, or both, then those
-settings apply to this command also.
-<P>To terminate a dump operation, specify either the dump name
-(<VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>) or its job ID
-number, which appears in the output from the <B>(backup) jobs</B>
-command. To terminate any other type of operation, provide the job ID
-number.
-<P>The effect of terminating an operation depends on the type and current
-state of the operation:
-<UL>
-<P><LI>If an operation is still pending, the Tape Coordinator removes it from the
-queue with no other lasting effects.
-<P><LI>If the Tape Coordinator is unable to process the termination signal before
-an operation completes, it simply confirms the operation's
-completion. The operator must take the action necessary to undo the
-effects of the incorrect operation.
-<P><LI>If a tape labeling operation is running, the effect depends on when the
-Tape Coordinator receives the termination signal. The labeling
-operation is atomic, so it either completes or does not begin at all.
-Use the <B>backup readlabel</B> command to determine if the labeling
-operation completed, and reissue the <B>backup labeltape</B> command to
-overwrite the incorrect label if necessary.
-<P><LI>If a tape scanning operation is running, it terminates with no other
-effects unless the <B>-dbadd</B> flag was included on the
-<B>backup</B> command. In that case, the Backup System possibly has
-already written new Backup Database records to represent dumps on the scanned
-tape. If planning to restart the scanning operation, first locate and
-remove the records created during the terminated operation: a repeated
-<B>backup scantape</B> operation exits automatically when it finds that a
-record that it needs to create already exists.
-<P><LI>If a dump operation is running, all of the volumes written to the tape or
-backup data file before the termination signal is received are complete and
-usable. If the operation is restarted, the Backup System performs all
-the dumps again from scratch, and assigns a new dump ID number. If
-writing the new dumps to the same tape or file, the operator must relabel it
-first if the interrupted dump is not expired. If writing the new dump
-to a different tape or file, the operator can remove the dump record
-associated with the interrupted dump to free up space in the database.
-<P><LI>If a restore operation is running, completely restored volumes are online
-and usable. However, it is unlikely that many volumes are completely
-restored, given that complete restoration usually requires data from multiple
-tapes. If the termination signal comes before the Backup System has
-accessed all of the necessary tapes, each volume is only partially written and
-is never brought online. It is best to restart the restore operation
-from scratch to avoid possible inconsistencies. See also the
-<B>Cautions</B> section.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>It is best not to issue the <B>(backup) kill</B> command against
-restore operations. If the termination signal interrupts a restore
-operation as the Backup System is overwriting an existing volume, it is
-possible to lose the volume entirely (that is, to lose both the contents of
-the volume as it was before the restore and any data that was restored before
-the termination signal arrived). The data being restored still exists
-on the tape, but some data can be lost permanently.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Identifies the backup operation to terminate. Provide one of two
-types of values:
-<UL>
-<P><LI>The operation's job ID number, as displayed in the output of the
-<B>(backup) jobs</B> command.
-<P><LI>For a dump operation, either the job ID number or a dump name of the form
-<VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>, where
-<VAR>volume_set_name</VAR> is the name of the volume set being dumped and
-<VAR>dump_level_name</VAR> is the last element in the dump level pathname at
-which the volume set is being dumped. The dump name appears in the
-output of the <B>(backup) jobs</B> command along with the job ID
-number.
-</UL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command terminates the operation with job ID 5:
-<PRE> backup> <B>kill 5</B>
-
-</PRE>
-<P>The following command terminates the dump operation called
-<B>user.sunday1</B>:
-<PRE> backup> <B>kill user.sunday1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the privilege required to initiate the operation being
-cancelled. Because this command can be issued only within the
-interactive session during which the operation was initiated, the required
-privilege is essentially guaranteed.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<P><A HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf077.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf079.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf078.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf080.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_LABELTAPE" HREF="auarf002.htm#ToC_93">backup labeltape</A></H2>
-<A NAME="IDX4345"></A>
-<A NAME="IDX4346"></A>
-<A NAME="IDX4347"></A>
-<A NAME="IDX4348"></A>
-<A NAME="IDX4349"></A>
-<A NAME="IDX4350"></A>
-<A NAME="IDX4351"></A>
-<A NAME="IDX4352"></A>
-<A NAME="IDX4353"></A>
-<A NAME="IDX4354"></A>
-<A NAME="IDX4355"></A>
-<A NAME="IDX4356"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates the magnetic label on a tape
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup labeltape</B> [<B>-name</B> <<VAR>AFS tape name, defaults to NULL</VAR>>]
- [<B>-size</B> <<VAR>tape size in Kbytes, defaults to size in tapeconfig</VAR>>]
- [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-pname</B> <<VAR>permanent tape name</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup la</B> [<B>-n</B> <<VAR>AFS tape name, defaults to NULL</VAR>>]
- [<B>-s</B> <<VAR>tape size in Kbytes, defaults to size in tapeconfig</VAR>>]
- [<B>-po</B> <<VAR>TC port offset</VAR>>] [<B>-pn</B> <<VAR>permanent tape name</VAR>>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup labeltape</B> command creates a magnetic label, readable
-by the Backup System, at the beginning of a tape. The label records the
-tape's name (either a <I>permanent name</I>, or an <I>AFS tape
-name</I> that reflects the tape's contents in a prescribed format) and
-its capacity.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file on the Tape
-Coordinator machine associated with the specified port offset, then the
-<B>backup</B> command writes label information to the first 16 KB block in
-the backup data file listed for that port offset in the Tape
-Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather than at
-the beginning of a tape. For the sake of clarity, the following text
-refers to tapes only, but the Backup System handles backup data files in much
-the same way.)
-<P>Relabeling a tape that already contains AFS backup data effectively makes
-the data unusable, because the command removes the Backup Database record of
-the complete dump set of which the tape is a part. Use this command to
-enable recycling of a tape that contains unexpired dumps that are not actually
-still needed.
-<P>To write a permanent name on the label, include the <B>-pname</B>
-argument to specify a string of up to 32 characters. The permanent name
-persists until the <B>-pname</B> argument is again included on the
-<B>backup labeltape</B> command, regardless of the tape's contents
-and of how often the tape is otherwise relabeled or recycled. Include
-this argument or the <B>-name</B> argument, but not both. If this
-argument is included, the AFS tape name is set to <TT><NULL></TT>.
-The permanent name is set to <TT><NULL></TT> if this argument is omitted
-and no permanent name already exists.
-<P>The issuer must ensure that a permanent name is unique among the tapes used
-for AFS backup in the cell, because the <B>backup</B> command interpreter
-does not verify that another tape does not already have the same permanent
-name. When a tape has a permanent name, the Backup System uses it
-instead of the AFS tape name in most prompts and when referring to the tape in
-output from <B>backup</B> commands. The permanent name appears in
-the <TT>tape</TT> <TT>name</TT> field of the output from the <B>backup
-readlabel</B> command.
-<P>To write an AFS tape name on the label, provide a value for the
-<B>-name</B> argument in the required format described in the
-<B>Options</B> section. Include the <B>-name</B> argument or
-the <B>-pname</B> argument, but not both. If this argument is
-omitted, the AFS tape name is set to <TT><NULL></TT>, but the Backup
-System automatically assigns the appropriate name when the tape is used in a
-future <B>backup dump</B> or <B>backup savedb</B> operation.
-The AFS tape name appears in the <TT>AFS</TT> <TT>tape</TT>
-<TT>name</TT> field of the output from the <B>backup readlabel</B> and
-<B>backup scantape</B> commands.
-<P>The <B>backup</B> command interpreter does not accept the
-<B>-name</B> argument if the tape already has a permanent name. To
-erase a tape's permanent name, provide a null value to the
-<B>-pname</B> argument by issuing the following command:
-<PRE> % <B>backup labeltape -pname ""</B>
-
-</PRE>
-<P>To record the tape's capacity on the label, specify a number of
-kilobytes as the <B>-size</B> argument. If the argument is omitted
-the first time a tape is labeled, the Backup System records the default tape
-capacity recorded for the specified port offset in the
-<B>/usr/afs/backup/tapeconfig</B> file on the Tape Coordinator
-machine. Subsequently, the value in the size field persists until the
-<B>-size</B> argument is again included on the <B>backup labeltape</B>
-command.
-<P>To determine how much data can be written to a tape during a <B>backup
-dump</B> or <B>backup savedb</B> operation, the Tape Coordinator reads
-the capacity recorded on the tape's label (or uses the value associated
-with its port offset in the <B>/usr/afs/backup/tapeconfig</B> file, if the
-tape was never labeled). For further description, see the <B>backup
-dump</B> reference page.
-<P>The Tape Coordinator's default response to this command is to access
-the tape by invoking the <B>MOUNT</B> instruction in the local
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by prompting the
-backup operator to insert the tape if there is no <B>MOUNT</B>
-instruction. However, if the <B>AUTOQUERY NO</B> instruction
-appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of
-the <B>butc</B> command included the <B>-noautoquery</B> flag, the
-Tape Coordinator instead expects the tape to be in the device already.
-If it is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
-prompts the operator.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies the AFS tape name to record on the label. Include this
-argument or the <B>-pname</B> argument, but not both. If this
-argument is omitted, the AFS tape name is set to <TT><NULL></TT>.
-If this argument is provided, it must have the following format:
-<PRE> <VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>.<VAR>tape_index</VAR>
-
-</PRE>
-<P>for the tape to be acceptable for use in a future <B>backup dump</B>
-operation. The <VAR>volume_set_name</VAR> must match the volume set name
-of the initial dump to be written to the tape, <VAR>dump_level_name</VAR> must
-match the last element of the dump level pathname at which the volume set will
-be dumped, and <VAR>tape_index</VAR> indicates the order of the tape in the dump
-set (indexing begins with <B>1</B>). To disable this type of name
-checking, include the <B>NAME_CHECK NO</B> instruction in the
-<B>CFG_</B><VAR>device_name</VAR> file.
-<P>For the tape to be acceptable for use in a future <B>backup savedb</B>
-operation, the value specified for the <B>-name</B> argument must have the
-following format:
-<PRE> <B>Ubik_db_dump.</B><VAR>tape_index</VAR>
-
-</PRE>
-<P>where <VAR>tape_index</VAR> indicates the order of the tape in the set of
-tapes that house the Backup Database dump; indexing begins with 1
-(one).
-<P><DT><B>-size
-</B><DD>Specifies the tape capacity to record on the label. Provide an
-integer value followed by a letter that indicates units, with no intervening
-space. A unit value of <B>k</B> or <B>K</B> indicates
-kilobytes, <B>m</B> or <B>M</B> indicates megabytes, and <B>g</B>
-or <B>G</B> indicates gigabytes. If the units letter is omitted,
-the default is kilobytes.
-<P>If this argument is omitted the first time a tape is labeled, the Backup
-System records the capacity that is associated with the specified port offset
-in the <B>/usr/afs/backup/tapeconfig</B> file on the Tape Coordinator
-machine. The value recorded the first time then persists until the
-<B>-size</B> argument is provided on a future issuance of the
-command.
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the tape
-for this operation.
-<P><DT><B>-pname
-</B><DD>Specifies the permanent name to record on the label. It can be up
-to 32 characters in length, and include any alphanumeric characters.
-Avoid metacharacters that have a special meaning to the shell, to avoid having
-to mark them as literal in commands issued at the shell prompt.
-<P>Include this argument or the <B>-name</B> argument, but not
-both. If this argument is provided, the AFS tape name is set to
-<TT><NULL></TT>. If this argument is omitted, any existing
-permanent name is retained.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command records the AFS tape name
-<B>user.monthly.1</B> on the label of the tape in the device
-with port offset 3:
-<PRE> % <B>backup labeltape -name user.monthly.1 -portoffset 3</B>
-
-</PRE>
-<P>The following three commands are equivalent in effect: they all
-record a capacity of 2 GB on the label of the tape in the device with port
-offset 4. They set the AFS tape name to <TT><NULL></TT> and leave
-the permanent name unchanged.
-<PRE> % <B>backup labeltape -size 2g -portoffset 4</B>
- % <B>backup labeltape -size 2048M -portoffset 4</B>
- % <B>backup labeltape -size 2097152 -portoffset 4</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf084.htm#HDRBK_READLABEL">backup readlabel</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf078.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf080.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf079.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf081.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_LISTDUMPS" HREF="auarf002.htm#ToC_94">backup listdumps</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4357"></A>
-<A NAME="IDX4358"></A>
-<A NAME="IDX4359"></A>
-<A NAME="IDX4360"></A>
-<A NAME="IDX4361"></A>
-<A NAME="IDX4362"></A>
-<A NAME="IDX4363"></A>
-<A NAME="IDX4364"></A>
-<P>Displays the dump hierarchy from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup listdumps</B> [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup listd</B> [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup listdumps</B> command displays the dump hierarchy from
-the Backup Database.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays the complete dump hierarchy and indicates the
-relationship between full and incremental dump levels. Full dump levels
-appear at the left margin. The hierarchy can include more than one full
-dump level; each one defines a subhierarchy of dump levels that can be
-used for dumping different volume sets.
-<P>Incremental dump levels appear below and indented to the right of their
-parent dump levels, which can be either full or incremental. Since
-multiple incremental dump levels can share the same parent, an incremental
-dump level is not always directly below its parent; the amount of
-indentation indicates the parent/child relationship.
-<P>If a dump level has an associated expiration date, it appears along with
-the level name. Absolute expiration dates appear in the format
-<PRE> <VAR>dump_level</VAR> expires at <VAR>day month date time year</VAR>
-
-</PRE>
-<P>and relative expiration dates in the format
-<PRE> <VAR>dump_level</VAR> expires in {<VAR>years</VAR>y | <VAR>months</VAR>m | <VAR>days</VAR>d}
-
-</PRE>
-<P>to indicate the number of years, months, days, or combination of the three
-after creation a dump expires when created at this level.
-<P><STRONG>Examples</STRONG>
-<P>The following example depicts six dump hierarchies. The expiration
-date for all incremental dump levels is 13 days so that the corresponding
-tapes can be recycled two weeks after their creation. The expiration
-dates for all full dump levels is 27 days so that the corresponding tapes can
-be recycled four weeks after their creation.
-<PRE> % <B>backup listdumps</B>
- /week1 expires in 27d
- /tuesday expires in 13d
- /thursday expires in 13d
- /sunday expires in 13d
- /tuesday expires in 13d
- /thursday expires in 13d
- /week3 expires in 27d
- /tuesday expires in 13d
- /thursday expires in 13d
- /sunday expires in 13d
- /tuesday expires in 13d
- /thursday expires in 13d
- /sunday1 expires in 27d
- /monday1 expires in 13d
- /tuesday1 expires in 13d
- /wednesday1 expires in 13d
- /thursday1 expires in 13d
- /friday1 expires in 13d
- /sunday2 expires in 27d
- /monday2 expires in 13d
- /tuesday2 expires in 13d
- /wednesday2 expires in 13d
- /thursday2 expires in 13d
- /friday2 expires in 13d
- /sunday3 expires in 27d
- /monday1 expires in 13d
- /tuesday1 expires in 13d
- /wednesday1 expires in 13d
- /thursday1 expires in 13d
- /friday1 expires in 13d
- /sunday4 expires in 27d
- /monday2 expires in 13d
- /tuesday2 expires in 13d
- /wednesday2 expires in 13d
- /thursday2 expires in 13d
- /friday2 expires in 13d
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<P><A HREF="auarf067.htm#HDRBK_DELDUMP">backup deldump</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf079.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf081.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf080.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf082.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_LISTHOSTS" HREF="auarf002.htm#ToC_95">backup listhosts</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX4365"></A>
-<A NAME="IDX4366"></A>
-<A NAME="IDX4367"></A>
-<A NAME="IDX4368"></A>
-<A NAME="IDX4369"></A>
-<A NAME="IDX4370"></A>
-<A NAME="IDX4371"></A>
-<A NAME="IDX4372"></A>
-<A NAME="IDX4373"></A>
-<P>Lists Tape Coordinator machines registered in the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup listhosts</B> [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup listh</B> [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup listhosts</B> command displays the Backup Database record
-of the port offset numbers defined for Tape Coordinator machines. A
-Tape Coordinator must have an entry in the list to be available for backup
-operations.
-<P>The existence of an entry does not necessarily indicate that the Tape
-Coordinator process (<B>butc</B>) is currently running at that port
-offset. To check, issue the <B>backup status</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>After a <TT>Tape</TT> <TT>hosts:</TT> header, the output reports
-two things about each Tape Coordinator currently defined in the Backup
-Database:
-<UL>
-<P><LI>The hostname of the machine housing the Tape Coordinator. The
-format of this name depends on the hostname format used when the <B>backup
-addhost</B> command was issued.
-<P><LI>The Tape Coordinator's port offset number.
-</UL>
-<P>The Tape Coordinators appear in the order in which they were added to the
-Backup Database.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the result of the command in the ABC
-Corporation cell:
-<PRE> % <B>backup listhosts</B>
- Tape hosts:
- Host backup1.abc.com, port offset 0
- Host backup1.abc.com, port offset 1
- Host backup3.abc.com, port offset 4
- Host backup2.abc.com, port offset 3
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<P><A HREF="auarf069.htm#HDRBK_DELHOST">backup delhost</A>
-<P><A HREF="auarf089.htm#HDRBK_STATUS">backup status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf080.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf082.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf081.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf083.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_LISTVOLSETS" HREF="auarf002.htm#ToC_96">backup listvolsets</A></H2>
-<A NAME="IDX4374"></A>
-<A NAME="IDX4375"></A>
-<A NAME="IDX4376"></A>
-<A NAME="IDX4377"></A>
-<A NAME="IDX4378"></A>
-<A NAME="IDX4379"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Lists volume set entries from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup listvolsets</B> [<B>-name</B> <<VAR>volume set name</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup listv</B> [<B>-n</B> <<VAR>volume set name</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup listvolsets</B> command displays the Backup Database
-records for either
-<UL>
-<P><LI>All volume sets and their volume entries, if the <B>-name</B> argument
-is omitted
-<P><LI>The volume set specified by the <B>-name</B> argument, along with its
-volume entries
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the volume set to display. If this argument is omitted, the
-output lists all volume sets defined in the Backup Database.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The entry for each volume set begins with the <TT>Volume set</TT> header
-and the volume set's name. A temporary volume set's name is
-followed by the string <TT> (temporary)</TT>. Each volume entry
-follows on a separate line, indicating the entry's index number and the
-server, partition, and volume names it matches. The output uses the
-metacharacter notation described on the <B>backup addvolentry</B>
-reference page. Use the index number to identify volume entries when
-deleting them with the <B>backup delvolentry</B> command.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the volume entries in the three volume sets
-currently defined in the Backup Database:
-<PRE> % <B>backup listvolsets</B>
- Volume set user:
- Entry 1: server .*, partition .*, volumes: user.*\.backup
- Volume set sun
- Entry 1: server .*, partition .*, volumes: sun4x_55\..*
- Entry 2: server .*, partition .*, volumes: sun4x_56\..*
- Volume set rs
- Entry 1: server .*, partition .*, volumes: rs_aix42\..*
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf070.htm#HDRBK_DELVOLENTRY">backup delvolentry</A>
-<P><A HREF="auarf071.htm#HDRBK_DELVOLSET">backup delvolset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf081.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf083.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf082.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf084.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_QUIT" HREF="auarf002.htm#ToC_97">backup quit</A></H2>
-<A NAME="IDX4380"></A>
-<A NAME="IDX4381"></A>
-<A NAME="IDX4382"></A>
-<A NAME="IDX4383"></A>
-<A NAME="IDX4384"></A>
-<A NAME="IDX4385"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Leaves interactive mode
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>quit</B> [<B>-help</B>]
-
-<B>q</B> [<B>-h</B>]
-
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>(backup) quit</B> command exits interactive mode, returning the
-issuer to the regular shell prompt at which the <B>backup</B> or
-<B>backup interactive</B> command was issued to enter interactive
-mode. The command has no effect when issued outside interactive
-mode. Issuing the <<B>Ctrl-d</B>> command also exits interactive
-mode.
-<P><STRONG>Cautions</STRONG>
-<P>To exit interactive mode, all jobs must be completed. Use the
-<B>(backup) jobs</B> command to list any jobs currently pending or
-executing, and the <B>(backup) kill</B> command to terminate them as
-necessary.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command exits interactive mode:
-<PRE> backup> <B>quit</B>
- %
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf076.htm#HDRBK_INTERACTIVE">backup interactive</A>
-<P><A HREF="auarf077.htm#HDRBK_JOBS">backup jobs</A>
-<P><A HREF="auarf078.htm#HDRBK_KILL">backup kill</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf082.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf084.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf083.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf085.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_READLABEL" HREF="auarf002.htm#ToC_98">backup readlabel</A></H2>
-<A NAME="IDX4386"></A>
-<A NAME="IDX4387"></A>
-<A NAME="IDX4388"></A>
-<A NAME="IDX4389"></A>
-<A NAME="IDX4390"></A>
-<A NAME="IDX4391"></A>
-<A NAME="IDX4392"></A>
-<A NAME="IDX4393"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reads and displays a tape's label
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup readlabel</B> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup rea</B> [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup readlabel</B> command displays information from the
-magnetic tape label of a tape. The information includes the tape's
-name (either a <I>permanent name</I>, or an <I>AFS tape name</I> that
-reflects the tape's contents in a prescribed format) and its
-capacity.
-<P>If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup readlabel</B> command reads the
-label information from the first 16 KB block in the backup data file listed
-for that port offset in the Tape Coordinator's
-<B>/usr/afs/backup/tapeconfig</B> file, rather than from the beginning of
-a tape.
-<P>The Tape Coordinator's default response to this command is to access
-the tape by invoking the <B>MOUNT</B> instruction in the local
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by prompting the
-backup operator to insert the tape if there is no <B>MOUNT</B>
-instruction. However, if the <B>AUTOQUERY NO</B> instruction
-appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of
-the <B>butc</B> command included the <B>-noautoquery</B> flag, the
-Tape Coordinator instead expects the tape to be in the device already.
-If it is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
-prompts the operator.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the
-tapes for this operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>Output from this command appears in both the shell window where the command
-is issued, and in the Tape Coordinator window.
-<P>If the tape is unlabeled or if the specified tape device is empty, the
-output reads
-<PRE> Failed to read tape label.
-
-</PRE>
-<P>Otherwise, the output in the shell window has the following format:
-<PRE> Tape read was labelled: <VAR>tape name</VAR> (<VAR>dump id</VAR>)
- size: <VAR>size</VAR> Kbytes
-
-</PRE>
-<P>where <VAR>tape name</VAR> is the permanent name if the tape has one, or the
-AFS tape name otherwise. The <VAR>dump ID</VAR> is dump ID of the initial
-dump on the tape, and <VAR>size</VAR> is the recorded capacity of the tape in
-kilobytes.
-<P>The output in the Tape Coordinator windows is bounded by an underlined
-<TT>Tape</TT> <TT>label</TT> header at the top, and the following string
-at the bottom:
-<PRE> -- End of tape label --
-
-</PRE>
-<P>In between are lines reporting the following information:
-<DL>
-<P><DT><B><TT>tape name</TT>
-</B><DD>The permanent name assigned by using the <B>-pname</B> argument of the
-<B>backup labeltape</B> command. This name remains on the tape
-until that argument is used again, no matter how many times the tape is
-recycled or otherwise relabeled. If the tape does not have a permanent
-name, the value <TT><NULL></TT> appears in this field.
-<P><DT><B><TT>AFS tape name</TT>
-</B><DD>A tape name in one of the following prescribed formats. The Backup
-System automatically writes the appropriate AFS tape name to the label as part
-of a <B>backup dump</B> or <B>backup savedb</B> operation, or the
-operator can assign it with the <B>-name</B> argument to the <B>backup
-labeltape</B> command.
-<UL>
-<P><LI><VAR>volume_set_name</VAR><B>.</B><VAR>dump_level_name</VAR><B>.</B><VAR>tape_index</VAR>,
-if the tape contains volume data. The <VAR>volume_set_name</VAR> is the
-name of the volume set that was dumped to create the initial dump in the dump
-set of to which this tape belongs; <VAR>dump_level_name</VAR> is the last
-pathname element of the dump level at which the initial dump was backed
-up; and <VAR>tape_index</VAR> is the numerical position of the tape in the
-dump set.
-<P><LI><TT>Ubik.db.dump.</TT><VAR>tape_index</VAR> if the
-tape contains a dump of the Backup Database, created with the <B>backup
-savedb</B> command. The <VAR>tape_index</VAR> is the ordinal of the
-tape in the dump set.
-<P><LI><TT><NULL></TT> if the tape has no AFS tape name. This is
-normally the case if the <B>-name</B> argument was not included the last
-time the <B>backup labeltape</B> command was used on this tape, and no
-data has been written to it since.
-</UL>
-<P><DT><B><TT>creationTime</TT>
-</B><DD>The date and time at which the Backup System started performing the dump
-operation that created the initial dump.
-<P><DT><B><TT>cell</TT>
-</B><DD>The cell in which the dump set was created. This is the cell whose
-Backup Database contains a record of the dump set.
-<P><DT><B><TT>size</TT>
-</B><DD>The tape's capacity (in kilobytes) as recorded on the label, rather
-than the amount of data on the tape. The value is assigned by the
-<B>-size</B> argument to the <B>backup labeltape</B> command or
-derived from the <B>/usr/afs/backup/tapeconfig</B> file on the Tape
-Coordinator machine, not from a measurement of the tape.
-<P><DT><B><TT>dump path</TT>
-</B><DD>The dump level of the initial dump in the dump set
-<P><DT><B><TT>dump id</TT>
-</B><DD>The dump ID number of the initial dump in the dump set, as recorded in the
-Backup Database
-<P><DT><B><TT>useCount</TT>
-</B><DD>The number of times a dump has been written to the tape, or it has been
-relabeled
-</DL>
-<P>The message <TT>ReadLabel: Finished</TT> indicates the completion
-of the output.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the tape with permanent name
-<B>oct.guest.dump</B> and capacity 2 MB, expressed in
-kilobyte units (2097152 equals 2 times 1024<SUP>2</SUP>).
-<PRE> % <B>backup readlabel -portoffset 6</B>
- Tape read was labelled: oct.guest.dump (907215000)
- size: 2097152 Kbytes
-
-</PRE>
-<P>The output in the Tape Coordinator window reads:
-<PRE> Tape label
- ----------
- tape name = oct.guest.dump
- AFS tape name = guests.monthly.3
- creationTime = Thu Oct 1 00:10:00 1998
- cell = abc.com
- size = 2097152 Kbytes
- dump path = /monthly
- dump id = 907215000
- useCount = 5
- ---- End of tape label ----
-
-</PRE>
-<P>The following example is for a tape that does not have a permanent
-tape.
-<PRE> % backup readlabel -portoffset 6
- Tape read was labelled: guests.monthly.2 (909899900)
- size: 2097152 Kbytes
-
-</PRE>
-<P>The output in the Tape Coordinator window reads:
-<PRE> Tape label
- ----------
- tape name = <NULL>
- AFS tape name = guests.monthly.2
- creationTime = Sun Nov 1 00:58:20 1998
- cell = abc.com
- size = 2097152 Kbytes
- dump path = /monthly
- dump id = 909899900
- useCount = 1
- ---- End of tape label ----
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf079.htm#HDRBK_LABELTAPE">backup labeltape</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf083.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf085.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf084.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf086.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_RESTOREDB" HREF="auarf002.htm#ToC_99">backup restoredb</A></H2>
-<A NAME="IDX4394"></A>
-<A NAME="IDX4395"></A>
-<A NAME="IDX4396"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restores a saved copy of the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup restoredb</B> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup res</B> [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup restoredb</B> command restores to the Backup Server
-machine's local disk a version of the Backup Database previously written
-to tape by using the <B>backup savedb</B> command.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup restoredb</B> command restores
-data from the backup data file listed for that port offset in the Tape
-Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, instead of from
-tape. For the sake of clarity, the following text refers to tapes only,
-but the Backup System handles backup data files in much the same way.)
-<P>The most common reason to run this command is to replace a corrupted or
-otherwise damaged Backup Database; use the <B>backup dbverify</B>
-command to determine the database's status. The command can also
-be used to restore records that were removed from the database when the
-<B>-archive</B> argument was included on a previous <B>backup
-savedb</B> command.
-<P>The command completely overwrites the existing Backup Database records for
-volume sets, Tape Coordinators, and the dump hierarchy with the corresponding
-information from the saved version. It does not overwrite existing dump
-records, but instead interleaves the records from the copy being
-restored. If both the existing database (on the Backup Server
-machine's disk) and the copy being restored include a record about the
-same dump, the Backup System retains the one in the existing database.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape it needs by invoking the <B>MOUNT</B> instruction in the
-local <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by
-prompting the backup operator to insert the tape if there is no
-<B>MOUNT</B> instruction. However, if the <B>AUTOQUERY NO</B>
-instruction appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the
-issuer of the <B>butc</B> command included the <B>-noautoquery</B>
-flag, the Tape Coordinator instead expects the tape to be in the device
-already. If it is not, or is the wrong tape, the Tape Coordinator
-invokes the <B>MOUNT</B> instruction or prompts the operator. It
-also invokes the <B>MOUNT</B> instruction or prompts for any additional
-tapes needed to complete the restore operation; the backup operator must
-arrange to provide them.
-<P><STRONG>Cautions</STRONG>
-<P>If the database is corrupted, do not attempt to restore a saved database on
-top of it. Instead, use the instructions for repairing a corrupted
-database in the <I>IBM AFS Administration Guide</I> chapter about
-performing backup operations.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the
-tapes for this operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the Backup Database being restored from the
-Tape Coordinator with port offset 0:
-<PRE> % <B>backup restoredb</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf066.htm#HDRBK_DBVERIFY">backup dbverify</A>
-<P><A HREF="auarf086.htm#HDRBK_SAVEDB">backup savedb</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf084.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf086.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf085.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf087.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_SAVEDB" HREF="auarf002.htm#ToC_100">backup savedb</A></H2>
-<A NAME="IDX4397"></A>
-<A NAME="IDX4398"></A>
-<A NAME="IDX4399"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a saved copy of the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup savedb</B> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>] [<B>-archive</B> <<VAR>date time</VAR>><SUP>+</SUP>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup sa</B> [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-a</B> <<VAR>date time</VAR>><SUP>+</SUP>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup savedb</B> command creates a backup copy of the entire
-Backup Database and writes it to the tape in the device controlled by the Tape
-Coordinator indicated with the <B>-portoffset</B> argument. If the
-database is damaged (as reported by the <B>backup dbverify</B> command),
-this command repairs as much of the corruption as possible as it creates the
-saved copy. The Backup Server creates a dump record for the saved
-database in the Backup Database (but in the disk version of the database only,
-not in the version written to tape).
-<P>If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup savedb</B> command dumps the
-database copy to the backup data file listed for that port offset in the Tape
-Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, instead of to
-tape. For the sake of clarity, the following text refers to tapes only,
-but the Backup System handles backup data files in much the same way.
-<P>If the <B>-archive</B> flag is provided, after writing the saved copy
-of the database the Backup System truncates the copy of the database on disk
-by deleting volume dump records with timestamps prior to the specified date
-and time (it does not delete the dump records created by previous <B>backup
-savedb</B> commands, however).
-<P>If the tape to which the database copy is written has an AFS tape name, it
-must be <B>Ubik_db_dump.1</B> or <TT><NULL></TT>. Any
-permanent name is acceptable.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape by invoking the <B>MOUNT</B> instruction in the local
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by prompting the
-backup operator to insert the tape if there is no <B>MOUNT</B>
-instruction. However, if the <B>AUTOQUERY NO</B> instruction
-appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of
-the <B>butc</B> command included the <B>-noautoquery</B> flag, the
-Tape Coordinator instead expects the tape to be in the device already.
-If it is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
-prompts the operator. It also invokes the <B>MOUNT</B> instruction
-or prompts for any additional tapes needed to complete the operation; the
-backup operator must arrange to provide them.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the
-tapes for this operation.
-<P><DT><B>-archive
-</B><DD>Specifies a date and time; volume dump records with earlier
-timestamps are deleted from the disk copy of the Backup Database after the
-Backup System dumps the database (a dump's timestamp appears in the
-<TT>created</TT> field of the output from the <B>backup dumpinfo</B>
-command). However, if a dump set contains any dump created after the
-specified date, none of the dump records associated with the dump set are
-deleted. Dump records for previous dumps of the database (created with
-the <B>backup savedb</B> command) are never deleted; use the
-<B>backup deletedump</B> command to remove them.
-<P>Provide one of two values:
-<UL>
-<P><LI>The string <B>NOW</B> to indicate the current date and time, in which
-case the Backup System deletes all dump records except those for dumps of the
-Backup Database itself.
-<P><LI>A date value in the format <VAR>mm/dd/yyyy</VAR>
-[<VAR>hh:MM</VAR>]. The month (<VAR>mm</VAR>), day (<VAR>dd</VAR>), and
-year (<VAR>yyyy</VAR>) are required, and valid values for the year range from
-<B>1970</B> to <B>2037</B>; higher values are not valid because
-the latest possible date in the standard UNIX representation is in February
-2038. The Backup System automatically reduces any later date to the
-maximum value.
-<P>The hour and minutes (<VAR>hh</VAR>:<VAR>MM</VAR>) are optional, but if
-provided must be in 24-hour format (for example, the value
-<B>14:36</B> represents 2:36 p.m.). If
-omitted, the time defaults to 59 seconds after midnight (00:00:59
-hours). Similarly, the <B>backup</B> command interpreter
-automatically adds 59 seconds to any time value provided. In both
-cases, adding 59 seconds compensates for how the Backup Database and
-<B>backup dumpinfo</B> command represent dump creation times in hours and
-minutes only. That is, the Database records a creation timestamp of
-<TT>20:55</TT> for any dump created between 20:55:00 and
-20:55:59. Automatically adding 59 seconds to a time thus
-includes the records for all dumps created during that minute.
-</UL>
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition.
-</TD></TR></TABLE>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example writes a copy of the Backup Database to the tape
-device controlled by the Tape Coordinator with port offset 1:
-<PRE> % <B>backup savedb -portoffset 1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf066.htm#HDRBK_DBVERIFY">backup dbverify</A>
-<P><A HREF="auarf085.htm#HDRBK_RESTOREDB">backup restoredb</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf085.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf087.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf086.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf088.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_SCANTAPE" HREF="auarf002.htm#ToC_101">backup scantape</A></H2>
-<A NAME="IDX4400"></A>
-<A NAME="IDX4401"></A>
-<A NAME="IDX4402"></A>
-<A NAME="IDX4403"></A>
-<A NAME="IDX4404"></A>
-<A NAME="IDX4405"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Extracts dump information from a tape
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup scantape</B> [<B>-dbadd</B>] [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup sc</B> [<B>-d</B>] [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup scantape</B> command extracts information from the dump
-labels and volume headers on the tape in the device controlled by the Tape
-Coordinator indicated by the <B>-portoffset</B> argument. The Tape
-Coordinator displays the information for each volume in its window as soon as
-it extracts it (rather than waiting until it has scanned the entire
-tape).
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup scantape</B> command extracts
-dump information from the backup data file named in that port offset's
-entry in the <B>/usr/afs/backup/tapeconfig</B> file on the Tape
-Coordinator machine, rather than from a tape. For the sake of clarity,
-the following text refers to tapes only, but the Backup System handles backup
-data files in much the same way.)
-<P>If the <B>-dbadd</B> flag is provided, the <B>backup scantape</B>
-command creates new dump and volume records in the Backup Database for the
-scanned information. However, if it finds that a record already exists
-in the database for the same dump, it terminates the scanning
-operation.
-<P>The scanning operation works only on tapes containing volume data.
-The command fails with an error message if the tape contains a copy of the
-Backup Database (was created with the <B>backup savedb</B> command, or has
-the AFS tape name <B>Ubik_db_dump.1</B>).
-<P>The Tape Coordinator's default response to this command is to access
-the tape by invoking the <B>MOUNT</B> instruction in the
-<B>CFG_</B><VAR>device_name</VAR> file, or by prompting the backup operator
-to insert the tape if there is no <B>MOUNT</B> instruction.
-However, if the <B>AUTOQUERY NO</B> instruction appears in the
-<B>CFG_</B><VAR>device_name</VAR> file, or if the issuer of the
-<B>butc</B> command included the <B>-noautoquery</B> flag, the Tape
-Coordinator instead expects the tape to be in the device already. If it
-is not, the Tape Coordinator invokes the <B>MOUNT</B> instruction or
-prompts the operator.
-<P>To terminate a tape scanning operation in interactive mode, issue the
-<B>(backup) kill</B> command. In noninteractive mode, the only
-choice is to use a termination signal such as <<B>Ctrl-c</B>> to halt
-the Tape Coordinator completely.
-<P><STRONG>Cautions</STRONG>
-<P>A scanning operation does not have to begin with the first tape in a dump
-set, but the Backup System can process tapes only in sequential order after
-the initial tape provided. The Tape Coordinator automatically requests
-any subsequent tapes by invoking the <B>MOUNT</B> instruction in the local
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by prompting the
-operator if there is no <B>MOUNT</B> instruction.
-<P>The Tape Coordinator's success in scanning a tape that is corrupted or
-damaged depends on the extent of the damage and what type of data is
-corrupted. It can almost always scan the tape successfully up to the
-point of damage. If the damage is minor, the Tape Coordinator can
-usually skip over it and scan the rest of the tape, but more major damage can
-prevent further scanning. Because a scanning operation can start on any
-tape in a dump set, damage on one tape does not prevent scanning of the others
-in the dump set. However, it is possible to scan either the tapes that
-precede the damaged one or the ones that follow it, but not both.
-<P>If a tape is relabeled with the <B>backup labeltape</B> command, it is
-not possible to recover data from it for the purposes of rebuilding the Backup
-Database.
-<P>If the <B>-dbadd</B> flag is included on the command, it is best not to
-terminate the tape scanning operation before it completes (for example, by
-issuing the <B>(backup) kill</B> command in interactive mode). The
-Backup System writes a new record in the Backup Database for each dump as soon
-as it scans the relevant information on the tape, and so it possibly has
-already written new records. If the operator wants to rerun the
-scanning operation, he or she must locate and remove the records created
-during the terminated operation: the second operation exits
-automatically if it finds that a record that it needs to create already
-exists.
-<P>If the <B>-dbadd</B> flag is included and the first tape provided is
-not the first tape in the dump set, the following restrictions apply:
-<UL>
-<P><LI>If the first data on the tape is a continuation of a volume that begins on
-the previous (unscanned) tape in the dump set, the Backup System does not add
-a record for that volume to the Backup Database.
-<P><LI>The Backup System must read the marker that indicates the start of an
-appended dump to add database records for the volumes in it. If the
-first volume on the tape belongs to an appended dump, but is not immediately
-preceded by the appended-dump marker, the Backup System does not create a
-Backup Database record for it or any subsequent volumes that belong to that
-appended dump.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dbadd
-</B><DD>Adds the information extracted from the tape to the Backup Database (but
-only if the database does not already contain an entry with the same dump ID
-number).
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator handling the
-tapes for this operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>For every dump on a tape, the <B>backup scantape</B> command displays
-in the Tape Coordinator window the dump label and the volume header of each
-volume in the dump. If a dump spans more than one tape, the dump label
-does not repeat at the beginning of subsequent tapes.
-<P>A dump label contains the following fields, which are the same as in the
-output from the <B>backup readlabel</B> command:
-<DL>
-<P><DT><B><TT>tape name</TT><TT></TT>
-</B><DD>The permanent name assigned by using the <B>-pname</B> argument of the
-<B>backup labeltape</B> command. This name remains on the tape
-until that argument is used again, no matter how many times the tape is
-recycled or otherwise relabeled. If the tape does not have a permanent
-name, the value <TT><NULL></TT> appears in this field.
-<P><DT><B><TT>AFS tape name</TT>
-</B><DD>A tape name in one of the following prescribed formats. The Backup
-System automatically writes the appropriate AFS tape name to the label as part
-of a <B>backup dump</B> operation, or the operator can assign it with the
-<B>-name</B> argument to the <B>backup labeltape</B> command.
-<UL>
-<P><LI><VAR>volume_set_name</VAR>.<VAR>dump_level_name</VAR>.<VAR>tape
-_index</VAR>, if the tape contains volume data. The
-<VAR>volume_set_name</VAR> is the name of the volume set that was dumped to
-create the initial dump in the dump set of which this tape is a part;
-<VAR>dump_level_name</VAR> is the last pathname element of the dump level at
-which the initial dump was backed up; and <VAR>tape_index</VAR> is the
-numerical position of the tape in the dump set.
-<P><LI><TT><NULL></TT> if the tape has no AFS tape name. This is
-normally the case if the <B>-name</B> argument was not included the last
-time the <B>backup labeltape</B> command was used on this tape, and no
-data has been written to it since.
-</UL>
-<P><DT><B><TT>creationTime</TT>
-</B><DD>The date and time at which the Backup System started performing the dump
-operation that created the initial dump.
-<P><DT><B><TT>cell</TT>
-</B><DD>The cell in which the dump set was created. This is the cell whose
-Backup Database contains a record of the dump set.
-<P><DT><B><TT>size</TT>
-</B><DD>The tape's capacity (in kilobytes) as recorded on the label, rather
-than the amount of data on the tape. The value is assigned by the
-<B>-size</B> argument to the <B>backup labeltape</B> command or
-derived from the <B>/usr/afs/backup/tapeconfig</B> file on the Tape
-Coordinator machine, not from a measurement of the tape.
-<P><DT><B><TT>dump</TT> <TT>path</TT>
-</B><DD>The dump level of the initial dump in the dump set.
-<P><DT><B><TT>dump</TT> <TT>id</TT>
-</B><DD>The dump ID number of the initial dump in the dump set, as recorded in the
-Backup Database.
-<P><DT><B><TT>useCount</TT>
-</B><DD>The number of times a dump has been written to the tape, or it has been
-relabeled.
-</DL>
-<P>The volume header contains the following fields:
-<DL>
-<P><DT><B><TT>volume</TT> <TT>name</TT>
-</B><DD>The volume name, complete with a <TT>.backup</TT> or
-<TT>.readonly</TT> extension, if appropriate.
-<P><DT><B><TT>volume</TT> <TT>ID</TT>
-</B><DD>The volume's volume ID.
-<P><DT><B><TT>dumpSetName</TT>
-</B><DD>The dump to which the volume belongs. The dump name is of the form
-<VAR>volume_set_name</VAR><B>.</B><VAR>dump_level_name</VAR> and
-matches the name displayed in the dump label.
-<P><DT><B><TT>dumpID</TT>
-</B><DD>The dump ID of the dump named in the <TT>dumpSetName</TT> field.
-<P><DT><B><TT>level</TT>
-</B><DD>The depth in the dump hierarchy of the dump level used in creating the
-dump. A value of <TT>0</TT> indicates a full dump. A value of
-<TT>1</TT> or greater indicates an incremental dump made at the indicated
-depth in the hierarchy. The value reported is for the entire dump, not
-necessarily for the volume itself; for example, it is possible for a dump
-performed at an incremental level to include a full dump of an individual
-volume if the volume was omitted from previous dumps.
-<P><DT><B><TT>parentID</TT>
-</B><DD>The dump ID number of <TT>dumpSetName</TT>'s parent dump. It
-is <TT>0</TT> if the value in the <TT>level</TT> field is
-<TT>0</TT>.
-<P><DT><B><TT>endTime</TT>
-</B><DD>Is always <TT>0</TT>; it is reserved for internal use.
-<P><DT><B><TT>cloneDate</TT>
-</B><DD>The date and time at which the volume was created. For a backup or
-read-only volume, this represents the time at which it was cloned from its
-read/write source. For a read/write volume, it indicates the time at
-which the Backup System locked the volume for purposes of including it in the
-dump named in the <TT>dumpSetName</TT> field.
-</DL>
-<P>The message <TT>Scantape: Finished</TT> indicates the completion of
-the output.
-<P>In normal circumstances, the Backup System writes a marker to indicate that
-a volume is the last one on a tape, or that the volume continues on the next
-tape. However, if a backup operation terminated abnormally (for
-example, because the operator terminated the Tape Coordinator by issuing the
-<<B>Ctrl-c</B>> command during the operation), then there is no such
-marker. Some very early versions of the Backup System also did not
-write these markers. If a tape does not conclude with one of the
-expected markers, the Tape Coordinator cannot determine if there is a
-subsequent tape in the dump set and so generates the following message in its
-window:
-<PRE> Are there more tapes? (y/n)
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the first two volumes on a tape
-in the device with port offset 0:
-<PRE> % <B>backup scantape</B>
- Dump label
- ----------
- tape name = monthly_guest
- AFS tape name = guests.monthly.3
- creationTime = Mon Feb 1 04:06:40 1999
- cell = abc.com
- size = 2150000 Kbytes
- dump path = /monthly
- dump id = 917860000
- useCount = 44
- -- End of dump label --
- -- volume --
- volume name: user.guest10.backup
- volume ID 1937573829
- dumpSetName: guests.monthly
- dumpID 917860000
- level 0
- parentID 0
- endTime 0
- clonedate Mon Feb 1 03:03:23 1999
- -- volume --
- volume name: user.guest11.backup
- volume ID 1938519386
- dumpSetName: guests.monthly
- dumpID 917860000
- level 0
- parentID 0
- endTime 0
- clonedate Mon Feb 1 03:05:15 1999
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf074.htm#HDRBK_DUMPINFO">backup dumpinfo</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf086.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf088.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf087.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf089.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_SETEXP" HREF="auarf002.htm#ToC_102">backup setexp</A></H2>
-<A NAME="IDX4406"></A>
-<A NAME="IDX4407"></A>
-<A NAME="IDX4408"></A>
-<A NAME="IDX4409"></A>
-<A NAME="IDX4410"></A>
-<A NAME="IDX4411"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the expiration date for existing dump levels.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup setexp -dump</B> <<VAR>dump level name</VAR>><SUP>+</SUP> [<B>-expires</B> <<VAR>expiration date</VAR>><SUP>+</SUP>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup se -d</B> <<VAR>dump level name</VAR>><SUP>+</SUP> [<B>-e</B> <<VAR>expiration date</VAR>><SUP>+</SUP>]
- [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup setexp</B> command sets or changes the expiration date
-associated with each specified dump level, which must already exist in the
-dump hierarchy.
-<P>Use the <B>-expires</B> argument to associate an expiration date with
-each dump level. When the Backup System subsequently creates a dump at
-the dump level, it uses the specified value to derive the dump's
-expiration date, which it records on the label of the tape (or backup data
-file). The Backup System refuses to overwrite a tape until after the
-latest expiration date of any dump that the tape contains, unless the
-<B>backup labeltape</B> command is used to relabel the tape. If a
-dump level does not have an expiration date, the Backup System treats dumps
-created at the level as expired as soon as it creates them.
-<P>(Note that the Backup System does not automatically remove a dump's
-record from the Backup Database when the dump reaches its expiration date, but
-only if the tape that contains the dump is recycled or relabeled. To
-remove expired and other obsolete dump records, use the <B>backup
-deletedump</B> command.)
-<P>Define either an absolute or relative expiration date:
-<UL>
-<P><LI>An absolute expiration date defines the month/day/year (and, optionally,
-hour and minutes) at which a dump expires. If the expiration date
-predates the dump creation time, the Backup System immediately treats the dump
-as expired.
-<P><LI>A relative date defines the number of years, months, or days (or a
-combination of the three) after the dump's creation that it
-expires. When the Backup System creates a dump at the dump level, it
-calculates an actual expiration date by adding the relative date to the start
-time of the dump operation.
-</UL>
-<P>If the command is used to change an existing expiration date associated
-with a dump level, the new date applies only to dumps created after the
-change. Existing dumps retain the expiration date assigned at the time
-they were created.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dump
-</B><DD>Specifies the full pathname of each dump level to assign the expiration
-date specified by the <B>-expires</B> argument.
-<P><DT><B>-expires
-</B><DD>Defines the absolute or relative expiration date to associate with each
-dump level named by the <B>-dump</B> argument. Absolute expiration
-dates have the following format:
-<P>
-<PRE> [<B>at</B>] {<B>NEVER</B> | <VAR>mm</VAR><B>/</B><VAR>dd</VAR><B>/</B><VAR>yyyy</VAR> [<VAR>hh</VAR><B>:</B><VAR>MM</VAR>] }
-
-</PRE>
-<P>where the optional word <B>at</B> is followed either by the string
-<B>NEVER</B>, which indicates that dumps created at the dump level never
-expire, or by a date value with a required portion (<VAR>mm</VAR> for month,
-<VAR>dd</VAR> for day, and <VAR>yyyy</VAR> for year) and an optional portion
-(<VAR>hh</VAR> for hours and <VAR>MM</VAR> for minutes).
-<P>Omit the <VAR>hh</VAR>:<VAR>MM</VAR> portion to use the default of
-midnight (00:00 hours), or provide a value in 24-hour format (for
-example, <B>20:30</B> is 8:30 p.m.).
-Valid values for the year range from <B>1970</B> to <B>2037</B>;
-higher values are not valid because the latest possible date in the standard
-UNIX representation is in February 2038. The command interpreter
-automatically reduces later dates to the maximum value.
-<P>Relative expiration dates have the following format:
-<PRE> [<B>in</B>] [<VAR>years</VAR><B>y</B>] [<VAR>months</VAR><B>m</B>] [<VAR>days</VAR><B>d</B>]
-
-</PRE>
-<P>
-<P>where the optional word <B>in</B> is followed by at least one of a
-number of years (maximum <B>9999</B>) followed by the letter <B>y</B>,
-a number of months (maximum <B>12</B>) followed by the letter
-<B>m</B>, or a number of days (maximum <B>31</B>) followed by the
-letter <B>d</B>. If providing more than one of the three, list them
-in the indicated order. If the date that results from adding the
-relative expiration value to a dump's creation time is later than the
-latest possible date in the UNIX time representation, the Backup System
-automatically reduces it to that date.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition to be
-associated with each dump level specified by the <B>-dump</B>
-argument.
-</TD></TR></TABLE>
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example associates an absolute expiration date of 10:00
-p.m. on 31 December 1999 with the dump level
-<B>/1998/december</B>:
-<PRE> % <B>backup setexp -dump /1998/december -expires at 12/31/1999 22:00</B>
-
-</PRE>
-<P>The following example associates a relative expiration date of 7 days with
-the two dump levels <B>/monthly/week1</B> and
-<B>/monthly/week2</B>:
-<PRE> % <B>backup setexp -dump /monthly/week1 /monthly/week -expires 7d</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf061.htm#HDRBK_ADDDUMP">backup adddump</A>
-<P><A HREF="auarf067.htm#HDRBK_DELDUMP">backup deldump</A>
-<P><A HREF="auarf080.htm#HDRBK_LISTDUMPS">backup listdumps</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf087.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf089.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf088.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf090.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_STATUS" HREF="auarf002.htm#ToC_103">backup status</A></H2>
-<A NAME="IDX4412"></A>
-<A NAME="IDX4413"></A>
-<A NAME="IDX4414"></A>
-<A NAME="IDX4415"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports a Tape Coordinator's status
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup status</B> [<B>-portoffset</B> <<VAR>TC port offset</VAR>>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup st</B> [<B>-p</B> <<VAR>TC port offset</VAR>>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup status</B> command displays which operation, if any, the
-indicated Tape Coordinator is currently executing.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-portoffset
-</B><DD>Specifies the port offset number of the Tape Coordinator for which to
-report the status.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The following message indicates that the Tape Coordinator is not currently
-performing an operation:
-<PRE> Tape coordinator is idle
-</PRE>
-<P>Otherwise, the output includes a message of the following format for each
-running or pending operation:
-<PRE> Task <VAR>task_ID</VAR>: <VAR>operation</VAR>: <VAR>status</VAR>
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>task_ID</VAR>
-</B><DD>Is a task identification number assigned by the Tape Coordinator.
-It begins with the Tape Coordinator's port offset number.
-<P><DT><B><VAR>operation</VAR>
-</B><DD>Identifies the operation the Tape Coordinator is performing, which is
-initiated by the indicated command:
-<UL>
-<P><LI><TT>Dump</TT> (the <B>backup dump</B> command)
-<P><LI><TT>Restore</TT> (the <B>backup diskrestore</B>, <B>backup
-volrestore</B>, or <B>backup volsetrestore</B> commands)
-<P><LI><TT>Labeltape</TT> (the <B>backup labeltape</B> command)
-<P><LI><TT>Scantape</TT> (the <B>backup scantape</B> command)
-<P><LI><TT>SaveDb</TT> (the <B>backup savedb</B> command)
-<P><LI><TT>RestoreDb</TT> (the <B>backup restoredb</B> command)
-</UL>
-<P><DT><B><VAR>status</VAR>
-</B><DD>Indicates the job's current status in one of the following
-messages.
-<DL>
-<P><DT><B><VAR>number</VAR> <TT>Kbytes transferred, volume</TT> <VAR>volume_name</VAR>
-</B><DD>For a running dump operation, indicates the number of kilobytes copied to
-tape or a backup data file so far, and the volume currently being
-dumped.
-<P><DT><B><VAR>number</VAR> <TT>Kbytes, restore.volume</TT>
-</B><DD>For a running restore operation, indicates the number of kilobytes copied
-into AFS from a tape or a backup data file so far.
-<P><DT><B><TT>[abort requested]</TT>
-</B><DD>The <B>(backup) kill</B> command was issued, but the termination
-signal has yet to reach the Tape Coordinator.
-<P><DT><B><TT>[abort sent]</TT>
-</B><DD>The operation is canceled by the <B>(backup) kill</B> command.
-Once the Backup System removes an operation from the queue or stops it from
-running, it no longer appears at all in the output from the command.
-<P><DT><B><TT>[butc contact lost]</TT>
-</B><DD>The <B>backup</B> command interpreter cannot reach the Tape
-Coordinator. The message can mean either that the Tape Coordinator
-handling the operation was terminated or failed while the operation was
-running, or that the connection to the Tape Coordinator timed out.
-<P><DT><B><TT>[done]</TT>
-</B><DD>The Tape Coordinator has finished the operation.
-<P><DT><B><TT>[drive wait]</TT>
-</B><DD>The operation is waiting for the specified tape drive to become
-free.
-<P><DT><B><TT>[operator wait]</TT>
-</B><DD>The Tape Coordinator is waiting for the backup operator to insert a tape
-in the drive.
-</DL>
-</DL>
-<P>If the Tape Coordinator is communicating with an XBSA server (a third-party
-backup utility that implements the Open Group's Backup Service API
-[XBSA]), the following message appears last in the output:
-<PRE> <VAR>XBSA_program</VAR> Tape coordinator
-</PRE>
-<P>where <VAR>XBSA_program</VAR> is the name of the XBSA-compliant
-program.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows that the Tape Coordinator with port offset 4
-has so far dumped about 1.5 MB of data for the current dump operation,
-and is currently dumping the volume named
-<B>user.pat.backup</B>:
-<PRE> % <B>backup status -portoffset 4</B>
- Task 4001: Dump: 1520 Kbytes transferred, volume user.pat.backup
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server is running, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf088.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf090.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf089.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf091.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_VOLINFO" HREF="auarf002.htm#ToC_104">backup volinfo</A></H2>
-<A NAME="IDX4416"></A>
-<A NAME="IDX4417"></A>
-<A NAME="IDX4418"></A>
-<A NAME="IDX4419"></A>
-<A NAME="IDX4420"></A>
-<A NAME="IDX4421"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays a volume's dump history from the Backup Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup volinfo -volume</B> <<VAR>volume name</VAR>>
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup voli -v</B> <<VAR>volume name</VAR>> [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup volinfo</B> command displays a dump history of the
-specified volume, reporting information such as the date on which the volume
-was dumped and the tapes that contain it. Include the
-<B>.backup</B> extension on the volume name if the backup version
-of the volume was dumped.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-volume
-</B><DD>Names the volume for which to display the dump history. Include
-the<TT> .backup</TT> or <TT>.readonly</TT> extension if the
-backup or read-only version of the volume was dumped.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes a line for each Backup Database dump record that
-mentions the specified volume, order from most to least recent. The
-output for each record appears in a table with six columns:
-<DL>
-<P><DT><B><TT>dumpID</TT>
-</B><DD>The dump ID of the dump that includes the volume.
-<P><DT><B><TT>lvl</TT>
-</B><DD>The depth in the dump hierarchy of the dump level at which the volume was
-dumped. A value of <TT>0</TT> indicates a full dump. A value
-of <TT>1</TT> or greater indicates an incremental dump made at the specified
-depth in the dump hierarchy.
-<P><DT><B><TT>parentid</TT>
-</B><DD>The dump ID of the dump's parent dump. A value of <TT>0</TT>
-indicates a full dump, which has no parent; in this case, the value in
-the <TT>lvl</TT> column is also <TT>0</TT>.
-<P><DT><B><TT>creation date</TT>
-</B><DD>The date and time at which the Backup System started the dump operation
-that created the dump.
-<P><DT><B><TT>clone date</TT>
-</B><DD>For a backup or read-only volume, the time at which it was cloned from its
-read/write source. For a read/write volume, the same as the value in
-the <TT>creation date</TT> field.
-<P><DT><B><TT>tape name</TT>
-</B><DD>The name of the tape containing the dump: either the permanent tape
-name, or an AFS tape name in the format
-<I>volume_set_name</I>.<I>dump_level_name</I>.<I>tape_index</I>
-where <I>volume_set_name</I> is the name of the volume set associated with
-the initial dump in the dump set of which this tape is a part;
-<I>dump_level_name</I> is the name of the dump level at which the initial
-dump was backed up; <I>tape_index</I> is the ordinal of the tape in
-the dump set. Either type of name can be followed by a dump ID in
-parentheses; if it appears, it is the dump ID of the initial dump in the
-dump set to which this appended dump belongs.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows part of the dump history of the Backup volume
-<B>user.smith.backup</B>:
-<PRE> % <B>backup volinfo -volume user.smith.backup</B>
- DumpID lvl parentID creation date clone date tape name
- 924600000 1 924427600 04/20/1999 05:20 04/20/1999 05:01 user_incr_2 (924514392)
- 924514392 1 924427600 04/19/1999 05:33 04/19/1999 05:08 user_incr_2
- 924427600 0 0 04/18/1999 05:26 04/18/1999 04:58 user_full_6
- . . . . . . . .
- . . . . . . . .
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf074.htm#HDRBK_DUMPINFO">backup dumpinfo</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf089.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf091.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf090.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf092.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_VOLRESTORE" HREF="auarf002.htm#ToC_105">backup volrestore</A></H2>
-<A NAME="IDX4422"></A>
-<A NAME="IDX4423"></A>
-<A NAME="IDX4424"></A>
-<A NAME="IDX4425"></A>
-<A NAME="IDX4426"></A>
-<A NAME="IDX4427"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restores one or more volumes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup volrestore -server</B> <<VAR>destination machine</VAR>>
- <B>-partition</B> <<VAR>destination partition</VAR>>
- <B>-volume</B> <<VAR>volume(s) to restore</VAR>><SUP>+</SUP>
- [<B>-extension</B> <<VAR>new volume name extension</VAR>>]
- [<B>-date</B> <<VAR>date from which to restore</VAR>><SUP>+</SUP>]
- [<B>-portoffset</B> <<VAR>TC port offsets</VAR>><SUP>+</SUP>] [<B>-n</B>]
- [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup volr -s</B> <<VAR>destination machine</VAR>> <B>-pa</B> <<VAR>destination partition</VAR>>
- <B>-v</B> <<VAR>volume(s) to restore</VAR>><SUP>+</SUP> [<B>-e</B> <<VAR>new volume name extension</VAR>>]
- [<B>-d</B> <<VAR>date from which to restore</VAR>><SUP>+</SUP>] [-<B>po</B> <<VAR>TC port offsets</VAR>><SUP>+</SUP>]
- [<B>-n</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup volrestore</B> command restores the contents of one or
-more volumes to the site indicated by the <B>-server</B> and
-<B>-partition</B> arguments. Use the command either to overwrite
-the contents of existing volumes with the restored data or to create new
-volumes while retaining the existing ones. The specified site does not
-have to be the current site for the volumes.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup volrestore</B> command restores
-data from the backup data file listed for that port offset in the Tape
-Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, rather than
-from tape. For the sake of clarity, the following text refers to tapes
-only, but the Backup System handles backup data files in much the same
-way.)
-<P>The command's arguments can be combined as indicated:
-<UL>
-<P><LI>To preserve a volume's current contents and also create a new volume
-to house the restored version, use the <B>-extension</B> argument.
-The Backup System creates the new volume on the server and partition named by
-the <B>-server</B> and <B>-partition</B> arguments, assigns it the
-same name as the current volume with the addition of the specified extension,
-and creates a new Volume Location Database (VLDB) entry for it.
-Creating a new volume enables the administrator to compare the two
-versions.
-<P><LI>To overwrite a volume's existing contents with the restored version,
-omit the <B>-extension</B> argument, and specify the site as
-indicated:
-<UL>
-<P><LI>To retain the current site, specify it with the <B>-server</B> and
-<B>-partition</B> arguments.
-<P><LI>To move the volume to a different site while overwriting it, specify the
-new site with the <B>-server</B> argument, <B>-partition</B> argument,
-or both. The Backup System creates a new volume at that site, removes
-the existing volume, and updates the site information in the volume's
-VLDB entry. The backup version of the volume is not removed
-automatically from the original site, if it exists. Use the <B>vos
-remove</B> command to remove it and the <B>vos backup</B> command to
-create a backup version at the new site.
-</UL>
-<P><LI>To restore a volume that no longer exists in the file system, specify its
-name with the <B>-volume</B> argument and use the <B>-server</B> and
-<B>-partition</B> arguments to place it at the desired site. The
-Backup System creates a new volume and new VLDB entry.
-</UL>
-<P>In each case, the command sets each volume's creation date to the date
-and time at which it restores it. The creation date appears in the
-<TT>Creation</TT> field in the output from the <B>vos examine</B> and
-<B>vos listvol</B> commands.
-<P>If restoring all of the volumes that resided on a single partition, it is
-usually more efficient to use the <B>backup diskrestore</B>
-command. If restoring multiple volumes to many different sites, it can
-be more efficient to use the <B>backup volsetrestore</B> command.
-<P>By default, the <B>backup volrestore</B> command restores the most
-recent full dump and all subsequent incremental dumps for each volume,
-bringing the restored volumes to the most current possible state. To
-restore the volumes to their state at some time in the past, use the
-<B>-date</B> argument. The Backup System restores the most recent
-full dump and each subsequent incremental dump for which the <VAR>clone
-date</VAR> of the volume included in the dump is before the indicated date and
-time (the clone date timestamp appears in the <TT>clone date</TT> field of
-the output from the <B>backup volinfo</B> command). For backup and
-read-only volumes, the clone date represents the time at which the volume was
-copied from its read/write source; for read/write volumes, it represents
-the time at which the volume was locked for inclusion in the dump. The
-resemblance of a restored volume to its actual state at the indicated time
-depends on the amount of time that elapsed between the volume's clone
-date in the last eligible dump and the specified time.
-<P>If the <B>-volume</B> argument specifies the base (read/write) form of
-the volume name, the Backup System searches the Backup Database for the newest
-dump set that includes a dump of either the read/write or the backup version
-of the volume. It restores the dumps of that version of the volume,
-starting with the most recent full dump. If, in contrast, the volume
-name explicitly includes the <B>.backup</B> or
-<B>.readonly</B> extension, the Backup System restores dumps of the
-corresponding volume version only.
-<P>To generate a list of the tapes the Backup System needs to perform the
-restore operation, without actually performing it, combine the <B>-n</B>
-flag with the options to be used on the actual command.
-<P>If all of the full and incremental dumps of all relevant volumes were not
-written to a type of tape that a single Tape Coordinator can read, use the
-<B>-portoffset</B> argument to list multiple port offset numbers in the
-order in which the tapes are needed (first list the port offset for the full
-dump, second the port offset for the level 1 incremental dump, and so
-on). If restoring multiple volumes, the same ordered list of port
-offsets must apply to all of them. If not, either issue this command
-separately for each volume, or use the <B>vos volsetrestore</B> command
-after defining groups of volumes that were dumped to compatible tape
-types. For further discussion, see the <I>IBM AFS Administration
-Guide</I>.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape it needs by invoking the <B>MOUNT</B> instruction in the
-local <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by
-prompting the backup operator to insert the tape if there is no
-<B>MOUNT</B> instruction. However, if the <B>AUTOQUERY NO</B>
-instruction appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the
-issuer of the <B>butc</B> command included the <B>-noautoquery</B>
-flag, the Tape Coordinator instead expects the tape to be in the device
-already. If it is not, or is the wrong tape, the Tape Coordinator
-invokes the <B>MOUNT</B> instruction or prompts the operator. It
-also invokes the <B>MOUNT</B> instruction or prompts for any additional
-tapes needed to complete the restore operation; the backup operator must
-arrange to provide them.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Names the file server machine on which to restore each volume. If
-this argument and the <B>-partition</B> argument indicate a site other
-than the current site for each volume, and the <B>-extension</B> argument
-is not also provided, the Backup System removes the existing volumes from
-their current sites, places the restored contents at the specified site, and
-changes the site information in the volume's VLDB entry.
-<P><DT><B>-partition
-</B><DD>Names the partition to which to restore each volume. If this
-argument and the <B>-server</B> argument indicate a site other than the
-current site for each volume, and the <B>-extension</B> argument is not
-also provided, the Backup System removes the existing volumes from their
-current sites, places the restored contents at the specified site, and changes
-the site information in the volume's VLDB entry.
-<P><DT><B>-volume
-</B><DD>Names one or more volumes to restore, using the volume name as listed in
-the Backup Database. Provide the base (read/write) name of each volume
-to have the Backup System search the Backup Database for the newest dump set
-that includes a dump of either the read/write or the backup version of the
-volume; it restores the dumps of that version of the volume, starting
-with the most recent full dump. If, in contrast, a volume name
-explicitly includes the <B>.backup</B> or
-<B>.readonly</B> extension, the Backup System restores dumps of the
-corresponding volume version only.
-<P><DT><B>-extension
-</B><DD>Creates a new volume to house the restored data, with a name derived by
-appending the specified string to each volume named by the <B>-volume</B>
-argument. The Backup System creates a new VLDB entry for the
-volume. Any string other than <B>.readonly</B> or
-<B>.backup</B> is acceptable, but the combination of the existing
-volume name and extension cannot exceed 22 characters in length. To use
-a period to separate the extension from the name, specify it as the first
-character of the string (as in <B>.rst</B>, for example).
-<P><DT><B>-date
-</B><DD>Specifies a date and optionally time; the restored volume includes
-data from dumps performed before the date only. Provide a value in the
-format <VAR>mm</VAR>/<VAR>dd</VAR>/<VAR>yyyy</VAR> [<VAR>hh</VAR>:<VAR>MM</VAR>],
-where the required <VAR>mm/dd/yyyy</VAR> portion indicates the month
-(<VAR>mm</VAR>), day (<VAR>dd</VAR>), and year (<VAR>yyyy</VAR>), and the optional
-<VAR>hh:MM</VAR> portion indicates the hour and minutes in 24-hour format
-(for example, the value <B>14:36</B> represents 2:36
-p.m.). If omitted, the time defaults to 59 seconds after
-midnight (00:00:59 hours).
-<P>Valid values for the year range from <B>1970</B> to
-<B>2037</B>; higher values are not valid because the latest possible
-date in the standard UNIX representation is in February 2038. The
-command interpreter automatically reduces any later date to the maximum
-value.
-<P>If this argument is omitted, the Backup System restores all possible dumps
-including the most recently created.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A plus sign follows this argument in the command's syntax statement
-because it accepts a multiword value which does not need to be enclosed in
-double quotes or other delimiters, not because it accepts multiple
-dates. Provide only one date (and optionally, time) definition.
-</TD></TR></TABLE>
-<P><DT><B>-portoffset
-</B><DD>Specifies one or more port offset numbers (up to a maximum of 128), each
-corresponding to a Tape Coordinator to use in the operation. If there
-is more than one value, the Backup System uses the first one when restoring
-the full dump of each volume, the second one when restoring the level 1
-incremental dump of each volume, and so on. It uses the final value in
-the list when restoring dumps at the corresponding depth in the dump hierarchy
-and all dumps at lower levels.
-<P>Provide this argument unless the default value of 0 (zero) is appropriate
-for all dumps. If <B>0</B> is just one of the values in the list,
-provide it explicitly in the appropriate order.
-<P><DT><B>-n
-</B><DD>Displays the list of tapes that contain the dumps required by the restore
-operation, without actually performing the operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the issuer includes the <B>-n</B> flag with the command, the
-following string appears at the head of the list of the tapes necessary to
-complete the restore operation.
-<PRE> Tapes needed:
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command restores the volume <B>user.pat</B> to
-partition <B>/vicepa</B> on machine
-<B>fs5.abc.com</B>:
-<PRE> % <B>backup volrestore -server fs5.abc.com -partition a -volume user.pat</B>
-
-</PRE>
-<P>The following command restores the volumes <B>user.smith</B> and
-<B>user.terry</B> to partition <B>/vicepb</B> on machine
-<B>fs4.abc.com</B>, adding a <B>.rst</B>
-extension to each volume name and preserving the existing
-<B>user.smith</B> and <B>user.terry</B> volumes.
-Only dumps created before 5:00 p.m. on 31 January 1998 are
-restored. (The command is shown here on multiple lines only for
-legibility reasons.)
-<PRE> % <B>backup volrestore -server fs4.abc.com -partition b</B> \
- <B>-volume user.smith user.terry</B> \
- <B>-extension .rst -date 1/31/1998 17:00</B>
-
-</PRE>
-<P>The following command restores the volume <B>user.pat</B> to
-partition <B>/vicepb</B> on machine
-<B>fs4.abc.com</B>. The Tape Coordinator with port
-offset 1 handles the tape containing the full dump; the Tape Coordinator
-with port offset 0 handles all tapes containing incremental dumps. (The
-command is shown here on two lines only for legibility reasons.)
-<PRE> % <B>backup volrestore -server fs5.abc.com -partition a</B> \
- <B>-volume user.pat -portoffset 1 0</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server or Volume Location (VL) Server is
-running, and on every file server machine that houses an affected
-volume. If the <B>-localauth</B> flag is included, the issuer must
-instead be logged on to a server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf092.htm#HDRBK_VOLSETRESTORE">backup volsetrestore</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf090.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf092.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf091.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf093.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBK_VOLSETRESTORE" HREF="auarf002.htm#ToC_106">backup volsetrestore</A></H2>
-<A NAME="IDX4428"></A>
-<A NAME="IDX4429"></A>
-<A NAME="IDX4430"></A>
-<A NAME="IDX4431"></A>
-<A NAME="IDX4432"></A>
-<A NAME="IDX4433"></A>
-<A NAME="IDX4434"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restores all volumes in a volume set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>backup volsetrestore</B> [<B>-name</B> <<VAR>volume set name</VAR>>] [<B>-file</B> <<VAR>file name</VAR>>]
- [<B>-portoffset</B> <<VAR>TC port offset</VAR>><SUP>+</SUP>]
- [<B>-extension</B> <<VAR>new volume name extension</VAR>>]
- [<B>-n</B>] [<B>-localauth</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>backup vols</B> [<B>-na</B> <<VAR>volume set name</VAR>>] [<B>-f</B> <<VAR>file name</VAR>>]
- [<B>-p</B> <<VAR>TC port offset</VAR>><SUP>+</SUP>] [<B>-e</B> <<VAR>new volume name extension</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>backup volsetrestore</B> command restores the complete contents
-of a group of read/write volumes to the file system, by restoring data from
-the last full dump and all subsequent incremental dumps of each volume.
-It is most useful for recovering from loss of data on multiple partitions,
-since it can restore each of a defined set of volumes to a different
-site.
-<P>(If the <B>FILE YES</B> instruction appears in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file associated with the
-specified port offset, then the <B>backup volsetrestore</B> command
-restores data from the backup data file listed for that port offset in the
-Tape Coordinator's <B>/usr/afs/backup/tapeconfig</B> file, instead of
-from tape. For the sake of clarity, the following text refers to tapes
-only, but the Backup System handles backup data files in much the same
-way.)
-<P>If restoring one or more volumes to a single site only, it is usually more
-efficient to use the <B>backup volrestore</B> command. If restoring
-all volumes that resided on a single partition, it is usually more efficient
-to use the <B>backup diskrestore</B> command.
-<P>Indicate the volumes to restore by providing either the <B>-name</B>
-argument or the <B>-file</B> argument:
-<UL>
-<P><LI>The <B>-name</B> argument names a volume set. The Backup System
-restores all volumes listed in the Volume Location Database (VLDB) that match
-the server, partition, and volume name criteria defined in the volume
-set's volume entries, and for which dumps are available. It
-restores the volumes to their current site (machine and partition), and by
-default overwrites the existing volume contents.
-<P>It is not required that the volume set was previously used to back up
-volumes (was used as the <B>-volumeset</B> option to the <B>backup
-dump</B> command). It can be defined especially to match the volumes
-that need to be restored with this command, and that is usually the better
-choice. Indeed, a <I>temporary</I> volume set, created by including
-the <B>-temporary</B> flag to the <B>backup addvolset</B> command, can
-be especially useful in this context. A temporary volume set is not
-added to the Backup Database and exists only during the current interactive
-backup session, which is suitable if the volume set is needed only to complete
-the single restore operation initialized by this command.
-<P>The reason that a specially defined volume set is probably better is that
-volume sets previously defined for use in dump operations usually match the
-backup version of volumes, whereas for a restore operation it is best to
-define volume entries that match the base (read/write) name. In that
-case, the Backup System searches the Backup Database for the newest dump set
-that includes either the read/write or the backup version of the
-volume. If, in contrast, a volume entry explicitly matches the
-volume's backup or read-only version, the Backup System restores dumps of
-that volume version only.
-<P><LI>The <B>-file</B> argument names a file that lists specific volumes and
-the site to which to restore each. The volume name must match the name
-used in Backup Database dump records rather than in the VLDB, if they differ,
-because the Backup System does not look up volumes in the VLDB. The
-specified site can be different than the volume's current one; in
-that case, the Backup System removes the current version of the volume and
-updates the volume's location information in the VLDB.
-</UL>
-<P>If all of the full and incremental dumps of all relevant volumes were not
-written to a type of tape that a single Tape Coordinator can read, use the
-<B>-portoffset</B> argument to list multiple port offset numbers in the
-order in which the tapes are needed (first list the port offset for the full
-dump, second the port offset for the level 1 incremental dump, and so
-on). This implies that the full dumps of all relevant volumes must have
-been written to a type of tape that the first Tape Coordinator can read, the
-level 1 incremental dumps to a type of tape the second Tape Coordinator can
-read, and so on. If dumps are on multiple incompatible tape types, use
-the <B>backup volrestore</B> command to restore individual volumes, or use
-this command after defining new volume sets that group together volumes that
-were dumped to compatible tape types. For further discussion, see the
-<I>IBM AFS Administration Guide</I>.
-<P>By default, the Backup System overwrites the contents of an existing volume
-with the restored data. To create a new volume to house the restored
-version instead, use the <B>-extension</B> argument. The Backup
-System derives the new volume's name by adding the specified extension to
-the read/write base name, and creates a new VLDB entry. The command
-does not affect the existing volume in any way. However, if a volume
-with the specified extension also already exists, the command overwrites
-it.
-<P>The <B>-n</B> flag produces a list of the volumes to be restored if the
-<B>-n</B> flag were not included, without actually restoring any
-volumes. See the <B>Output</B> section of this reference page for a
-detailed description of the output, and suggestions on how to combine it most
-effectively with the <B>-file</B> and <B>-name</B> arguments.
-<P>The execution time for a <B>backup volsetrestore</B> command depends on
-the number of volumes to be restored and the amount of data in them, but it
-can take hours to restore a large number of volumes. One way to reduce
-the time is to run multiple instances of the command simultaneously, either
-using the <B>-name</B> argument to specify disjoint volume sets for each
-command, or the <B>-file</B> argument to name files that list different
-volumes. This is possible if there are multiple available Tape
-Coordinators that can read the required tapes. Depending on how the
-volumes to be restored were dumped to tape, specifying disjoint volume sets
-can also reduce the number of tape changes required.
-<P>The Tape Coordinator's default response to this command is to access
-the first tape it needs by invoking the <B>MOUNT</B> instruction in the
-local <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file, or by
-prompting the backup operator to insert the tape if there is no
-<B>MOUNT</B> instruction. However, if the <B>AUTOQUERY NO</B>
-instruction appears in the <B>CFG_</B><VAR>device_name</VAR> file, or if the
-issuer of the <B>butc</B> command included the <B>-noautoquery</B>
-flag, the Tape Coordinator instead expects the tape to be in the device
-already. If it is not, or is the wrong tape, the Tape Coordinator
-invokes the <B>MOUNT</B> instruction or prompts the operator. It
-also invokes the <B>MOUNT</B> instruction or prompts for any additional
-tapes needed to complete the restore operation; the backup operator must
-arrange to provide them.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names a volume set to restore. The Backup System restores all of
-the volumes listed in the VLDB that match the volume set's volume
-entries. Provide this argument or the <B>-file</B> argument, but
-not both.
-<P><DT><B>-file
-</B><DD>Specifies the full pathname of a file that lists one or more volumes and
-the site (file server machine and partition) to which to restore each.
-Use either this argument or the <B>-name</B> argument, but not
-both.
-<P>Each volume's entry must appear on its own (unbroken) line in the
-file, and have the following format:
-<PRE> <VAR>machine partition
- volume</VAR> [<VAR>comments...</VAR>]
-
-</PRE>
-<P>
-<P>where
-<DL>
-<P><DT><B><VAR>machine</VAR>
-</B><DD>Names the file server machine to which to restore the volume.
-<P><DT><B><VAR>partition</VAR>
-</B><DD>Names the partition to which to restore the volume.
-<P><DT><B><VAR>volume</VAR>
-</B><DD>Names the volume to restore. It is generally best to specify the
-base (read/write) name of each volume. In this case, the Backup System
-searches the Backup Database for the newest dump set that includes a dump of
-either the read/write or the backup version of the volume. It restores
-the dumps of that version of the volume, starting with the most recent full
-dump. If, in contrast, the name explicitly includes the
-<B>.backup</B> or <B>.readonly</B> extension, the Backup
-System restores dumps of that volume version only.
-<P><DT><B><VAR>comments...</VAR>
-</B><DD>Is any other text. The Backup System ignores any text on each line
-that appears after the volume name, so this field can be used for notes
-helpful to the backup operator or other administrator.
-</DL>
-<P>
-<P>Do not use wildcards (for example, <B>.*</B>) in the
-<VAR>machine</VAR>, <VAR>partition</VAR>, or <VAR>volume</VAR> fields. It is
-acceptable for multiple lines in the file to name the same volume, but the
-Backup System processes only the first of them.
-<P><DT><B>-extension
-</B><DD>Creates a new volume for each volume specified by the <B>-name</B> or
-<B>-file</B> argument, to house the restored data from that volume.
-The Backup System derives the new volume's name by appending the
-specified string to the read/write base name, and creates a new VLDB volume
-entry. It preserves the contents of each existing volume. Any
-string other than <B>.readonly</B> or <B>.backup</B> is
-acceptable, but the combination of the base name and extension cannot exceed
-22 characters in length. To use a period to separate the extension from
-the name, specify it as the first character of the string (as in
-<B>.rst</B>, for example).
-<P><DT><B>-portoffset
-</B><DD>Specifies one or more port offset numbers (up to a maximum of 128), each
-corresponding to a Tape Coordinator to use in the operation. If there
-is more than one value, the Backup System uses the first one when restoring
-the full dump of each volume, the second one when restoring the level 1
-incremental dump of each volume, and so on. It uses the final value in
-the list when restoring dumps at the corresponding depth in the dump hierarchy
-and all dumps at lower levels.
-<P>Provide this argument unless the default value of 0 (zero) is appropriate
-for all dumps. If <B>0</B> is just one of the values in the list,
-provide it explicitly in the appropriate order.
-<P><DT><B>-n
-</B><DD>Displays a list of the volumes to be restored if the flag were not
-included, without actually restoring them. The <B>Output</B>
-section of this reference page details the format of the output. When
-combined with the <B>-name</B> argument, its output is easily edited for
-use as input to the <B>-file</B> argument on a subsequent <B>backup
-volsetrestore</B> command.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>backup</B> command
-interpreter presents it to the Backup Server, Volume Server and VL Server
-during mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument. For more details, see the introductory
-<B>backup</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>backup</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the <B>-n</B> flag is not provided, the command displays a unique
-task ID number for the operation, in two places:
-<UL>
-<P><LI>In the shell window, directly following the command line
-<P><LI>In the Tape Coordinator window, if the <B>butc</B> process was started
-at debug level 1
-</UL>
-<P>The task ID number is not the same as the job ID number displayed by the
-<B>(backup) jobs</B> command when the <B>(backup) volsetrestore</B>
-command is issued in interactive mode. The Backup System does not
-assign either type of ID number until the restoration process actually
-begins.
-<P>When the <B>-n</B> flag is included, no task ID or job ID numbers are
-reported because none are assigned. Instead, the output begins with a
-count of the number of volumes to be restored, followed by a line for each
-dump of a volume. For each volume, the line representing the most
-recent full dump appears first, and lines for any subsequent incremental dumps
-follow, ordered by dump level. The lines for a given volume do not
-necessarily appear all together, however.
-<P>The format of each line is as follows (the output is shown here on two
-lines only for legibility reasons):
-<PRE> <VAR>machine partition volume_dumped</VAR> # as <VAR>volume_restored</VAR>; <VAR>tape_name</VAR> (<VAR>tape_ID</VAR>); \
- pos <VAR>position_number</VAR>; <VAR>date</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>machine</VAR>
-</B><DD>Names the file server machine that currently houses the volume, as listed
-in the VLDB.
-<P><DT><B><VAR>partition</VAR>
-</B><DD>Names the partition that currently houses the volume, as listed in the
-VLDB.
-<P><DT><B><VAR>volume_dumped</VAR>
-</B><DD>Specifies the version (read/write or backup) of the volume that was
-dumped, as listed in the Backup Database.
-<P><DT><B><VAR>volume_restored</VAR>
-</B><DD>Specifies the name under which to restore the volume. The Backup
-System only restores data to read/write volumes. If the
-<B>-extension</B> argument is included, then the specified extension
-appears on the name in this field (for example,
-<TT>user.pat.rst</TT>).
-<P><DT><B><VAR>tape_name</VAR>
-</B><DD>Names the tape containing the dump of the volume, from the Backup
-Database. If the tape has a permanent name, it appears here;
-otherwise, it is the AFS tape name.
-<P><DT><B><VAR>tape_ID</VAR>
-</B><DD>The tape ID of the tape containing the dump of the volume, from the Backup
-Database.
-<P><DT><B><VAR>position_number</VAR>
-</B><DD>Specifies the dump's position on the tape (for example, <TT>31</TT>
-indicates that 30 volume dumps precede the current one on the tape). If
-the dump was written to a backup data file, this number is the ordinal of the
-16 KB-offset at which the volume's data begins.
-<P><DT><B><VAR>date</VAR>
-</B><DD>The date and time when the volume was dumped.
-</DL>
-<P>One way to generate a file for use as input to the <B>-file</B>
-argument is to combine the <B>-name</B> and <B>-n</B> options,
-directing the output to a file. The <I>IBM AFS Administration
-Guide</I> section on using the Backup System to restore data explains how to
-edit the file as necessary before using it as input to the <B>-file</B>
-argument.
-<P>The output of this command includes only volumes for which the Backup
-Database includes at least one dump record. The command interpreter
-generates a message on the standard error stream about volumes that do not
-have dump records but either are listed in the file named by the
-<B>-file</B> argument, or appear in the VLDB as a match to a volume entry
-in the volume set named by the <B>-name</B> argument.
-<P><STRONG>Examples</STRONG>
-<P>The following command restores all volumes included in entries in the
-volume set named <B>data.restore</B>, which was created expressly
-to restore data to a pair of file server machines on which all data was
-corrupted due to a software error. All volumes are restored to the
-sites recorded in their entries in the VLDB.
-<PRE> % <B>backup volsetrestore -name data.restore</B>
- Starting restore
- backup: task ID of restore operation: 112
- backup: Finished doing restore
-
-</PRE>
-<P>The following command restores all volumes that have entries in the file
-named <B>/tmp/restore</B>:
-<PRE> % <B>backup volsetrestore -file /tmp/restore</B>
- Starting restore
- backup: task ID of restore operation: 113
- backup: Finished doing restore
-
-</PRE>
-<P>The <B>/tmp/restore</B> file has the following contents:
-<PRE> fs1.abc.com b user.pat
- fs1.abc.com b user.terry
- fs1.abc.com b user.smith
- fs2.abc.com c user.jones
- . . .
- . . .
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server or Volume Location (VL) Server is
-running, and on every file server machine that houses an affected
-volume. If the <B>-localauth</B> flag is included, the issuer must
-instead be logged on to a server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf064.htm#HDRBK_ADDVOLSET">backup addvolset</A>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf073.htm#HDRBK_DUMP">backup dump</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf091.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf093.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf092.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf094.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_INTRO" HREF="auarf002.htm#ToC_107">bos</A></H2>
-<A NAME="IDX4435"></A>
-<A NAME="IDX4436"></A>
-<A NAME="IDX4437"></A>
-<A NAME="IDX4438"></A>
-<A NAME="IDX4439"></A>
-<A NAME="IDX4440"></A>
-<A NAME="IDX4441"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>bos</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>bos</B> command suite are the administrative
-interface to the Basic OverSeer (BOS) Server, which runs on every file server
-machine to monitor the other server processes on it. If a process
-fails, the BOS Server can restart it automatically, taking into account
-interdependencies between it and other processes. The BOS Server frees
-system administrators from constantly monitoring the status of server machines
-and processes.
-<P>There are several categories of commands in the <B>bos</B> command
-suite:
-<UL>
-<P><LI>Commands to administer server process binary files: <B>bos
-getdate</B>, <B>bos install</B>, <B>bos prune</B>, and <B>bos
-uninstall</B>
-<P><LI>Commands to maintain system configuration files: <B>bos
-addhost</B>, <B>bos addkey</B>, <B>bos adduser</B>, <B>bos
-listhosts</B>, <B>bos listkeys</B>, <B>bos listusers</B>, <B>bos
-removehost</B>, <B>bos removekey</B>, <B>bos removeuser</B>, and
-<B>bos setcellname</B>
-<P><LI>Commands to start and stop processes: <B>bos create</B>,
-<B>bos delete</B>, <B>bos restart</B>, <B>bos shutdown</B>,
-<B>bos start</B>, <B>bos startup</B>, and <B>bos stop</B>
-<P><LI>Commands to set and verify server process and server machine status:
-<B>bos getlog</B>, <B>bos getrestart</B>, <B>bos setauth</B>,
-<B>bos setrestart</B>, and <B>bos status</B>
-<P><LI>A command to restore file system consistency: <B>bos salvage</B>
-<P><LI>Commands to obtain help: <B>bos apropos</B> and <B>bos
-help</B>
-</UL>
-<P>The BOS Server and the <B>bos</B> commands use and maintain the
-following configuration and log files:
-<UL>
-<P><LI>The <B>/usr/afs/etc/CellServDB</B> file lists the local cell's
-database server machines. These machines run the Authentication,
-Backup, Protection and Volume Location (VL) Server processes, which maintain
-databases of administrative information. The database server processes
-consult the file to learn about their peers, whereas the other server
-processes consult it to learn where to access database information as
-needed. To administer the <B>CellServDB</B> file, use the following
-commands: <B>bos addhost</B>, <B>bos listhosts</B>, <B>bos
-removehost</B>, and <B>bos setcellname</B>.
-<P><LI>The <B>/usr/afs/etc/KeyFile</B> file lists the server encryption keys
-that the server processes use to decrypt tickets presented by client processes
-and one another. To administer the <B>KeyFile</B> file, use the
-following commands: <B>bos addkey</B>, <B>bos listkeys</B>, and
-<B>bos removekey</B>.
-<P><LI>The <B>/usr/afs/etc/ThisCell</B> file defines the cell to which the
-server machine belongs for the purposes of server-to-server
-communication. Administer it with the <B>bos setcellname</B>
-command. There is also a <B>/usr/vice/etc/ThisCell</B> file that
-defines the machine's cell membership with respect to the AFS command
-suites and Cache Manager access to AFS data.
-<P><LI>The <B>/usr/afs/etc/UserList</B> file lists the user name of each
-administrator authorized to issue privileged <B>bos</B> and <B>vos</B>
-commands. To administer the <B>UserList</B> file, use the following
-commands: <B>bos adduser</B>, <B>bos listusers</B>, and <B>bos
-removeuser</B>.
-<P><LI>The <B>/usr/afs/local/BosConfig</B> file defines which AFS server
-processes run on the server machine, and whether the BOS Server restarts them
-automatically if they fail. It also defines when all processes restart
-automatically (by default once per week), and when the BOS Server restarts
-processes that have new binary files (by default once per day). To
-administer the <B>BosConfig</B> file, use the following commands:
-<B>bos create</B>, <B>bos delete</B>, <B>bos getrestart</B>,
-<B>bos setrestart</B>, <B>bos start</B>, and <B>bos
-stop</B>.
-<P><LI>The <B>/usr/afs/log/BosLog</B> file records important operations the
-BOS Server performs and error conditions it encounters.
-</UL>
-<P>For more details, see the reference page for each file.
-<P><STRONG>Options</STRONG>
-<P>The following arguments and flags are available on many commands in the
-<B>bos</B> suite. The reference page for each command also lists
-them, but they are described here in greater detail.
-<A NAME="IDX4442"></A>
-<A NAME="IDX4443"></A>
-<A NAME="IDX4444"></A>
-<DL>
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P>
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell.
-<A NAME="IDX4445"></A>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>
-<A NAME="IDX4446"></A>
-<B>-localauth</B>
-</B><DD>Constructs a server ticket using the server encryption key with the
-highest key version number in the local <B>/usr/afs/etc/KeyFile</B>
-file. The <B>bos</B> command interpreter presents the ticket, which
-never expires, to the BOS Server during mutual authentication.
-<P>Use this flag only when issuing a command on a server machine; client
-machines do not usually have a <B>/usr/afs/etc/KeyFile</B> file.
-The issuer of a command that includes this flag must be logged on to the
-server machine as the local superuser <B>root</B>. The flag is
-useful for commands invoked by an unattended application program, such as a
-process controlled by the UNIX <B>cron</B> utility or by a cron entry in
-the machine's <B>/usr/afs/local/BosConfig</B> file. It is also
-useful if an administrator is unable to authenticate to AFS but is logged in
-as the local superuser <B>root</B>.
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell. Also, do not combine the <B>-localauth</B> and
-<B>-noauth</B> flags.
-<P><DT><B>
-<A NAME="IDX4447"></A>
-<B>-noauth</B>
-</B><DD>Establishes an unauthenticated connection to the BOS Server, in which the
-BOS Server treats the issuer as the unprivileged user
-<B>anonymous</B>. It is useful only when authorization checking is
-disabled on the server machine (during the installation of a file server
-machine or when the <B>bos setauth</B> command has been used during other
-unusual circumstances). In normal circumstances, the BOS Server allows
-only privileged users to issue commands that change the status of a server or
-configuration file, and refuses to perform such an action even if the
-<B>-noauth</B> flag is provided. Do not combine the
-<B>-noauth</B> and <B>-localauth</B> flags.
-<P><DT><B><B>-server</B> <<VAR>machine name</VAR>>
-<A NAME="IDX4448"></A>
-</B><DD>Indicates the AFS server machine on which to run the command.
-Identify the machine by its IP address in dotted decimal format, its
-fully-qualified host name (for example, <B>fs1.abc.com</B>),
-or by an abbreviated form of its host name that distinguishes it from other
-machines. Successful use of an abbreviated form depends on the
-availability of a name service (such as the Domain Name Service or a local
-host table) at the time the command is issued.
-<P>For the commands that alter the administrative files shared by all server
-machines in the cell (the <B>bos addhost</B>, <B>bos addkey</B>,
-<B>bos adduser</B>, <B>bos removehost</B>, <B>bos removekey</B>,
-and <B>bos removeuser</B> commands), the appropriate machine depends on
-whether the cell uses the United States or international version of AFS:
-<UL>
-<P><LI>If the cell runs the United States edition of AFS and (as recommended)
-uses the Update Server to distribute the contents of the
-<B>/usr/afs/etc</B> directory, provide the name of the system control
-machine. After issuing the command, allow up to five minutes for the
-Update Server to distribute the changed file to the other AFS server machines
-in the cell. If the specified machine is not the system control machine
-but is running an <B>upclientetc</B> process that refers to the system
-control machine, then the change will be overwritten when the process next
-brings over the relevant file from the system control machine.
-<P><LI>If the cell runs the international edition of AFS, do not use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B>
-directory. Instead, repeatedly issue the command, naming each of the
-cell's server machines in turn. To avoid possible inconsistency
-problems, finish issuing the commands within a fairly short time.
-</UL>
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<A NAME="IDX4449"></A>
-<A NAME="IDX4450"></A>
-<P>To issue any <B>bos</B> command that changes a configuration file or
-alters process status, the issuer must be listed in the
-<B>/usr/afs/etc/UserList</B> file on the server machine named by the
-<B>-server</B> argument. Alternatively, if the
-<B>-localauth</B> flag is included the issuer must be logged on as the
-local superuser <B>root</B>.
-<P>To issue a <B>bos</B> command that only displays information (other
-than the <B>bos listkeys</B> command), no privilege is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf094.htm#HDRBOS_ADDHOST">bos addhost</A>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf096.htm#HDRBOS_ADDUSER">bos adduser</A>
-<P><A HREF="auarf097.htm#HDRBOS_APROPOS">bos apropos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf099.htm#HDRBOS_DELETE">bos delete</A>
-<P><A HREF="auarf100.htm#HDRBOS_EXEC">bos exec</A>
-<P><A HREF="auarf101.htm#HDRBOS_GETDATE">bos getdate</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf104.htm#HDRBOS_HELP">bos help</A>
-<P><A HREF="auarf105.htm#HDRBOS_INSTALL">bos install</A>
-<P><A HREF="auarf106.htm#HDRBOS_LISTHOSTS">bos listhosts</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P><A HREF="auarf108.htm#HDRBOS_LISTUSERS">bos listusers</A>
-<P><A HREF="auarf109.htm#HDRBOS_PRUNE">bos prune</A>
-<P><A HREF="auarf110.htm#HDRBOS_REMOVEHOST">bos removehost</A>
-<P><A HREF="auarf111.htm#HDRBOS_REMOVEKEY">bos removekey</A>
-<P><A HREF="auarf112.htm#HDRBOS_REMOVEUSER">bos removeuser</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf115.htm#HDRBOS_SETAUTH">bos setauth</A>
-<P><A HREF="auarf116.htm#HDRBOS_SETCELLNAME">bos setcellname</A>
-<P><A HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P><A HREF="auarf122.htm#HDRBOS_STOP">bos stop</A>
-<P><A HREF="auarf123.htm#HDRBOS_UNINSTALL">bos uninstall</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf092.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf094.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf093.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf095.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_ADDHOST" HREF="auarf002.htm#ToC_108">bos addhost</A></H2>
-<A NAME="IDX4451"></A>
-<A NAME="IDX4452"></A>
-<A NAME="IDX4453"></A>
-<A NAME="IDX4454"></A>
-<A NAME="IDX4455"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a database server machine to the <B>/usr/afs/etc/CellServDB</B>
-file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos addhost -server</B> <<VAR>machine name</VAR>> <B>-host</B> <<VAR>host name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos addh -s</B> <<VAR>machine name</VAR>> <B>-ho</B> <<VAR>host name</VAR>><SUP>+</SUP>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-he</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos addhost</B> command adds an entry for each database server
-machine specified with the <B>-host</B> argument to the
-<B>/usr/afs/etc/CellServDB</B> file on the machine named by the
-<B>-server</B> argument.
-<P><STRONG>Cautions</STRONG>
-<P>After executing this command (and waiting for the Update Server to
-propagate the changes, if it is used), restart the database server processes
-on all database server machines to force election of a quorum that includes
-the new set of machines listed in the <B>/usr/afs/etc/CellServDB</B>
-file. The <I>IBM AFS Quick Beginnings</I> explains in more detail
-how to add and remove database server machines.
-<P>It is best to maintain a one-to-one mapping between hostnames and IP
-addresses on a multihomed database server machine (this is actually the
-conventional configuration for any AFS machine). The BOS Server uses
-the <B>gethostbyname( )</B> routine to obtain the IP address
-associated with the hostname specified by the <B>-host</B>
-argument. If there is more than one address, the BOS Server records in
-the <B>CellServDB</B> entry the one that appears first in the list of
-addresses returned by the routine. The routine possibly returns
-addresses in a different order on different machines, which can create
-inconsistency.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Identifies the server machine on which to change the
-<B>/usr/afs/etc/CellServDB</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-host</B>
-</B><DD>Specifies the fully-qualified host name (such as
-<B>db1.abc.com</B>) of each database server machine to
-register in the <B>CellServDB</B> file.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command adds the database server machines
-<B>db2.abc.com</B> and <B>db3.abc.com</B>
-to the <B>/usr/afs/etc/CellServDB</B> file on the machine
-<B>fs1.abc.com</B> (the system control machine).
-<PRE> % <B>bos addhost -server fs1.abc.com -host db2.abc.com db3.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf106.htm#HDRBOS_LISTHOSTS">bos listhosts</A>
-<P><A HREF="auarf110.htm#HDRBOS_REMOVEHOST">bos removehost</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf093.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf095.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf094.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf096.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_ADDKEY" HREF="auarf002.htm#ToC_109">bos addkey</A></H2>
-<A NAME="IDX4456"></A>
-<A NAME="IDX4457"></A>
-<A NAME="IDX4458"></A>
-<A NAME="IDX4459"></A>
-<A NAME="IDX4460"></A>
-<A NAME="IDX4461"></A>
-<A NAME="IDX4462"></A>
-<A NAME="IDX4463"></A>
-<A NAME="IDX4464"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a new server encryption key to the <B>/usr/afs/etc/KeyFile</B>
-file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos addkey -server</B> <<VAR>machine name</VAR>> [<B>-key</B> <<VAR>key</VAR>>]
- <B>-kvno</B> <<VAR>key version number</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos addk -s</B> <<VAR>machine name</VAR>> [<B>-ke</B> <<VAR>key</VAR>>] <B>-kv</B> <<VAR>key version number</VAR>>
- [<B>-ce</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos addkey</B> command constructs a server encryption key from
-the text string provided, assigns it the key version number specified with the
-<B>-kvno</B> argument, and adds it to the <B>/usr/afs/etc/KeyFile</B>
-file on the machine specified with the <B>-server</B> argument. Be
-sure to use the <B>kas setpassword</B> or <B>kas setkey</B> command to
-add the same key to the <B>afs</B> entry in the Authentication
-Database.
-<P>Do not use the <B>-key</B> argument, which echoes the password string
-visibly on the screen. If the argument is omitted, the BOS Server
-prompts for the string and does not echo it visibly:
-<PRE> Input key:
- Retype input key:
-
-</PRE>
-<P>The BOS Server prohibits reuse of any key version number already listed in
-the <B>/usr/afs/etc/KeyFile</B> file. This ensures that users who
-still have tickets sealed with the current key are not prevented from
-communicating with a server process because the current key is overwritten
-with a new key. Use the <B>bos listkeys</B> command to display the
-key version numbers in the <B>/usr/afs/etc/KeyFile</B> file.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to change the
-<B>/usr/afs/etc/KeyFile</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-key</B>
-</B><DD>Specifies a character string just like a password; the BOS Server
-calls a DES conversion function to encode it into a form appropriate for use
-as an encryption key. Omit this argument to have the BOS Server prompt
-for the string instead.
-<P><DT><B><B>-kvno</B>
-</B><DD>Defines the new key's key version number. It must be an
-integer in the range from <B>0</B> (zero) through <B>255</B>.
-For the sake of simplicity, use the number one higher than the current highest
-key version number; use the <B>bos listkeys</B> command to display
-key version numbers.
-<A NAME="IDX4465"></A>
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the strings typed at the <TT>Input key</TT> and <TT>Retype input
-key</TT> prompts do not match, the following message appears, and the command
-exits without adding a new key:
-<PRE> Input key mismatch
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command adds a new server encryption key with key version
-number 14 to the <B>KeyFile</B> file kept on the machine
-<B>fs1.abc.com</B> (the system control machine). The
-issuer omits the <B>-key</B> argument, as recommended, and provides the
-password at the prompts.
-<PRE> % <B>bos addkey -server fs1.abc.com -kvno 14</B>
- Input key:
- Retype input key:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P><A HREF="auarf111.htm#HDRBOS_REMOVEKEY">bos removekey</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf094.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf096.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf095.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf097.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_ADDUSER" HREF="auarf002.htm#ToC_110">bos adduser</A></H2>
-<A NAME="IDX4466"></A>
-<A NAME="IDX4467"></A>
-<A NAME="IDX4468"></A>
-<A NAME="IDX4469"></A>
-<A NAME="IDX4470"></A>
-<A NAME="IDX4471"></A>
-<A NAME="IDX4472"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a privileged user to the <B>/usr/afs/etc/UserList</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos adduser -server</B> <<VAR>machine name</VAR>> <B>-user</B> <<VAR>user names</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos addu -s</B> <<VAR>machine name</VAR>> <B>-u</B> <<VAR>user names</VAR>><SUP>+</SUP>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos adduser</B> command adds each user name specified with the
-<B>-user</B> argument to the <B>/usr/afs/etc/UserList</B> file on the
-machine named by the <B>-server</B> argument. It is the
-issuer's responsibility to verify that an entry for the user exists in
-the Authentication and Protection Databases.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to change the
-<B>/usr/afs/etc/UserList</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-user</B>
-</B><DD>Specifies each user name to insert into the
-<B>/usr/afs/etc/UserList</B> file.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command adds the user names <B>pat</B> and
-<B>smith</B> to the <B>/usr/afs/etc/UserList</B> file on the machine
-<B>fs1.abc.com</B> (the system control machine).
-<PRE> % <B>bos adduser -server fs1.abc.com -user pat smith</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf108.htm#HDRBOS_LISTUSERS">bos listusers</A>
-<P><A HREF="auarf112.htm#HDRBOS_REMOVEUSER">bos removeuser</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf095.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf097.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf096.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf098.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_APROPOS" HREF="auarf002.htm#ToC_111">bos apropos</A></H2>
-<A NAME="IDX4473"></A>
-<A NAME="IDX4474"></A>
-<A NAME="IDX4475"></A>
-<A NAME="IDX4476"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>bos ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos apropos</B> command displays the first line of the online
-help entry for any <B>bos</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>bos help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-topic</B>
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>bos</B> command where the string specified with the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>bos</B> commands that include the
-word <B>restart</B> in their names or short descriptions:
-<PRE> % <B>bos apropos restart</B>
- getrestart: get restart times
- restart: restart all processes
- setrestart: set restart times
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf104.htm#HDRBOS_HELP">bos help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf096.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf098.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf097.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf099.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_CREATE" HREF="auarf002.htm#ToC_112">bos create</A></H2>
-<A NAME="IDX4477"></A>
-<A NAME="IDX4478"></A>
-<A NAME="IDX4479"></A>
-<A NAME="IDX4480"></A>
-<A NAME="IDX4481"></A>
-<A NAME="IDX4482"></A>
-<A NAME="IDX4483"></A>
-<A NAME="IDX4484"></A>
-<A NAME="IDX4485"></A>
-<A NAME="IDX4486"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Defines a new process in the <B>/usr/afs/local/BosConfig</B> file and
-starts it running
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos create -server</B> <<VAR>machine name</VAR>> <B>-instance</B> <<VAR>server process name</VAR>>
- <B>-type</B> <<VAR>server type</VAR>> <B>-cmd</B> <<VAR>command lines</VAR>><SUP>+</SUP>
- [<B>-notifier</B> <<VAR>Notifier program</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos c -s</B> <<VAR>machine name</VAR>> <B>-i</B> <<VAR>server process name</VAR>> <B>-t</B> <<VAR>server type</VAR>>
- <B>-cm</B> <<VAR>command lines</VAR>><SUP>+</SUP> [<B>-not</B> <<VAR>Notifier program</VAR>>] [<B>-ce</B> <<VAR>cell name</VAR>>]
- [<B>-noa</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos create</B> command creates a server process entry in the
-<B>/usr/afs/local/BosConfig</B> file on the server machine named by the
-<B>-server</B> argument, sets the process's status to <B>Run</B>
-in the <B>BosConfig</B> file and in memory, and starts the process.
-<P>A server process's entry in the <B>BosConfig</B> file defines its
-name, its type, the command that initializes it, and optionally, the name of a
-notifier program that runs when the process terminates.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to define and start the new
-process. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names the process to define and start. Any name is acceptable, but
-for the sake of simplicity it is best to use the last element of the
-process's binary file pathname, and to use the same name on every server
-machine. The conventional names, as used in all AFS documentation,
-are:
-<DL>
-<P><DT><B><B>buserver</B>
-</B><DD>The Backup Server process
-<A NAME="IDX4487"></A>
-<A NAME="IDX4488"></A>
-<P><DT><B><B>fs</B>
-</B><DD>The process that combines the File Server, Volume Server, and Salvager
-processes (<B>fileserver</B>, <B>volserver</B>, and
-<B>salvager</B>)
-<A NAME="IDX4489"></A>
-<A NAME="IDX4490"></A>
-<P><DT><B><B>kaserver</B>
-</B><DD>The Authentication Server process
-<A NAME="IDX4491"></A>
-<A NAME="IDX4492"></A>
-<P><DT><B><B>ptserver</B>
-</B><DD>The Protection Server process
-<A NAME="IDX4493"></A>
-<A NAME="IDX4494"></A>
-<P><DT><B><B>runntp</B>
-</B><DD>The controller process for the Network Time Protocol Daemon
-<A NAME="IDX4495"></A>
-<A NAME="IDX4496"></A>
-<P><DT><B><B>upclientbin</B>
-</B><DD>The client portion of the Update Server process that retrieves binary
-files from the <B>/usr/afs/bin</B> directory of the binary distribution
-machine for this machine's CPU/operating system type. (The name of
-the binary is <B>upclient</B>, but the <B>bin</B> suffix distinguishes
-this process from <B>upclientetc</B>.)
-<A NAME="IDX4497"></A>
-<A NAME="IDX4498"></A>
-<P><DT><B><B>upclientetc</B>
-</B><DD>The client portion of the Update Server process that retrieves
-configuration files from the <B>/usr/afs/etc</B> directory of the system
-control machine. Do not run this process in cells that use the
-international edition of AFS. (The name of the binary is
-<B>upclient</B>, but the <B>etc</B> suffix distinguishes this process
-from <B>upclientbin</B>.)
-<P><DT><B><B>upserver</B>
-</B><DD>The server portion of the Update Server process
-<A NAME="IDX4499"></A>
-<A NAME="IDX4500"></A>
-<P><DT><B><B>vlserver</B>
-</B><DD>The Volume Location (VL) Server process
-<A NAME="IDX4501"></A>
-<A NAME="IDX4502"></A>
-</DL>
-<P><DT><B><B>-type</B>
-</B><DD>Specifies the process's type. The acceptable values are:
-<P>
-<DL>
-<P><DT><B><B>cron</B>
-</B><DD>Use this value for cron-type processes that the BOS Server starts only at
-a defined daily or weekly time, rather than whenever it detects that the
-process has terminated. AFS does not define any such processes by
-default, but makes this value available for administrator use. Define
-the time for command execution as part of the <B>-cmd</B> argument to the
-<B>bos create</B> command.
-<P><DT><B><B>fs</B>
-</B><DD>Use this value only for the <B>fs</B> process, which combines the File
-Server, Volume Server and Salvager processes. If one of the component
-processes terminates, the BOS Server shuts down and restarts the processes in
-the appropriate order.
-<P><DT><B><B>simple</B>
-</B><DD>Use this value for all processes listed as acceptable values to the
-<B>-instance</B> argument, except for the <B>fs</B> process.
-There are no interdependencies between simple processes, so the BOS Server can
-stop and start them independently as necessary.
-</DL>
-<P><DT><B><B>-cmd</B>
-</B><DD>Specifies each command the BOS Server runs to start the process.
-Specify no more than six commands (which can include the command's
-options, in which case the entire string is surrounded by double quotes);
-any additional commands are ignored.
-<P>For a simple process, provide the complete pathname of the process's
-binary file on the local disk (for example, <B>/usr/afs/bin/ptserver</B>
-for the Protection Server). If including any of the initialization
-command's options, surround the entire command in double quotes (<B>"
-"</B>). The <B>upclient</B> process has a required argument, and
-the commands for all other processes take optional arguments.
-<A NAME="IDX4503"></A>
-<P>For the <B>fs</B> process, provide the complete pathname of the local
-disk binary file for each of the component processes:
-<B>fileserver</B>, <B>volserver</B>, and <B>salvager</B>, in that
-order. The standard binary directory is <B>/usr/afs/bin</B>.
-If including any of an initialization command's options, surround the
-entire command in double quotes (<B>" "</B>).
-<A NAME="IDX4504"></A>
-<P>For a <B>cron</B> process, provide two parameters:
-<A NAME="IDX4505"></A>
-<UL>
-<P><LI>The complete local disk pathname of either an executable file or a command
-from one of the AFS suites (complete with all of the necessary
-arguments). Surround this parameter with double quotes (<B>" "</B>)
-if it contains spaces.
-<P><LI>A specification of when the BOS Server executes the file or command
-indicated by the first parameter. There are three acceptable
-values:
-<UL>
-<P><LI>The string <B>now</B>, which directs the BOS Server to execute the
-file or command immediately and only once. It is usually simpler to
-issue the command directly or issue the <B>bos exec</B> command.
-<P><LI>A time of day. The BOS Server executes the file or command daily at
-the indicated time. Separate the hours and minutes with a colon
-(<I>hh</I>:<I>MM</I>), and use either 24-hour format, or a value
-in the range from <B>1:00</B> through <B>12:59</B> with
-the addition of <B>am</B> or <B>pm</B>. For example, both
-<B>14:30</B> and <B>"2:30 pm"</B> indicate 2:30 in
-the afternoon. Surround this parameter with double quotes (<B>"
-"</B>) if it contains a space.
-<P><LI>A day of the week and time of day, separated by a space and surrounded
-with double quotes (<B>" "</B>). The BOS Server executes the file
-or command weekly at the indicated day and time. For the day, provide
-either the whole name or the first three letters, all in lowercase letters
-(<B>sunday</B> or <B>sun</B>, <B>thursday</B> or <B>thu</B>,
-and so on). For the time, use the same format as when specifying the
-time alone.
-</UL>
-</UL>
-<P><DT><B><B>-notifier</B>
-</B><DD>Specifies the complete pathname on the local disk of a program that the
-BOS Server invokes when the process terminates. The AFS distribution
-does not include any notifier programs, but this argument is available for
-administrator use. See the <B>Related Information</B>
-section.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command defines and starts the simple process
-<B>kaserver</B> on the machine <B>fs3.abc.com</B>:
-<PRE> % <B>bos create -server fs3.abc.com -instance kaserver -type simple</B> \
- <B>-cmd /usr/afs/bin/kaserver</B>
-
-</PRE>
-<P>The following command defines and starts the simple process
-<B>upclientbin</B> on the machine
-<B>fs4.abc.com</B>. It references
-<B>fs1.abc.com</B> as the source for updates to binary
-files, checking for changes to the <B>/usr/afs/bin</B> directory every 120
-seconds.
-<PRE> % <B>bos create -server fs4.abc.com -instance upclientbin -type simple</B> \
- <B>-cmd "/usr/afs/bin/upclient fs1.abc.com -clear -t 120</B> \
- <B>/usr/afs/bin"</B>
-
-</PRE>
-<P>The following command creates the fs process <B>fs</B> on the machine
-<B>fs4.abc.com</B>. Type the command on a single
-line.
-<PRE> % <B>bos create -server fs4.abc.com -instance fs -type fs</B> \
- <B>-cmd /usr/afs/bin/fileserver /usr/afs/bin/volserver</B> \
- <B>/usr/afs/bin/salvager</B>
-
-</PRE>
-<P>The following command creates a <B>cron</B> process called
-<B>userbackup</B> on the machine <B>fs5.abc.com</B>, so
-that the BOS Server issues the indicated <B>vos backupsys</B> command each
-day at 3:00 a.m. (the command creates a backup version of
-every volume in the file system whose name begins with
-<B>user</B>). Note that the issuer provides the complete pathname
-to the <B>vos</B> command, includes the <B>-localauth</B> flag on it,
-and types the entire <B>bos create</B> command on one line.
-<PRE> % <B>bos create -server fs5.abc.com -instance userbackup -type cron</B> \
- <B>-cmd "/usr/afs/bin/vos backupsys -prefix user -localauth" 03:00</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P>If the <B>-notifier</B> argument is included when this command is used
-to define and start a process, the BOS Server invokes the indicated
-<I>notifier program</I> when the process exits. The intended use of
-a notifier program is to inform administrators when a process exits
-unexpectedly, but it can be used to perform any appropriate actions.
-The following paragraphs describe the <B>bnode</B> and
-<B>bnode_proc</B> structures in which the BOS Server records information
-about the exiting process. The list of AFS commands related to this one
-follows.
-<P>The BOS Server constructs and sends on the standard output stream one
-<B>bnode</B> and one <B>bnode_proc</B> structure for each exiting
-process associated with the notifier program. It brackets each
-structure with appropriate <TT>BEGIN</TT> and <TT>END</TT> statements
-(<TT>BEGIN bnode</TT> and <TT>END bnode</TT>, <TT>BEGIN bnode_proc</TT>
-and <TT>END bnode_proc</TT>), which immediately follow the preceding newline
-character with no intervening spaces or other characters. If the
-notifier program does not need information from a structure, it can scan ahead
-in the input stream for the <TT>END</TT> statement.
-<P>In general, each field in a structure is a string of ASCII text terminated
-by the newline character. The format of the information within a
-structure possibly varies slightly depending on the type of process associated
-with the notifier program.
-<P>The C code for the <B>bnode</B> and <B>bnode_proc</B> structures
-follows. Note that the structures sent by the BOS Server do not
-necessarily include all of the fields described here, because some are used
-only for internal record keeping. The notifier process must robustly
-handle the absence of expected fields, as well as the presence of unexpected
-fields, on the standard input stream.
-<P>For proper performance, the notifier program must continue processing the
-input stream until it detects the end-of-file (EOF). The BOS Server
-closes the standard input file descriptor to the notifier process when it has
-completed delivery of the data, and it is the responsibility of the notifier
-process to terminate properly.
-<P><B>struct bnode contents</B>
-<PRE> struct bnode {
- struct bnode *next; /* next pointer in top-level's list */
- char *name; /* instance name */
- long nextTimeout; /* next time this guy should be awakened */
- long period; /* period between calls */
- long rsTime; /* time we started counting restarts */
- long rsCount; /* count of restarts since rsTime */
- struct bnode_type *type; /* type object */
- struct bnode_ops *ops; /* functions implementing bnode class */
- long procStartTime; /* last time a process was started */
- long procStarts; /* number of process starts */
- long lastAnyExit; /* last time a process exited for any reason */
- long lastErrorExit; /* last time a process exited unexpectedly */
- long errorCode; /* last exit return code */
- long errorSignal; /* last proc terminating signal */
- char *lastErrorName; /* name of proc that failed last */
- short refCount; /* reference count */
- short flags; /* random flags */
- char goal; /* 1=running or 0=not running */
- char fileGoal; /* same, but to be stored in file */
-};
-
-</PRE>
-<P><B>format of struct bnode explosion</B>
-<PRE> printf("name: %s\n",tp->name);
- printf("rsTime: %ld\n", tp->rsTime);
- printf("rsCount: %ld\n", tp->rsCount);
- printf("procStartTime: %ld\n", tp->procStartTime);
- printf("procStarts: %ld\n", tp->procStarts);
- printf("lastAnyExit: %ld\n", tp->lastAnyExit);
- printf("lastErrorExit: %ld\n", tp->lastErrorExit);
- printf("errorCode: %ld\n", tp->errorCode);
- printf("errorSignal: %ld\n", tp->errorSignal);
- printf("lastErrorName: %s\n", tp->lastErrorName);
- printf("goal: %d\n", tp->goal);
-
-</PRE>
-<P><B>struct bnode_proc contents</B>
-<PRE> struct bnode_proc {
- struct bnode_proc *next; /* next guy in top-level's list */
- struct bnode *bnode; /* bnode creating this process */
- char *comLine; /* command line used to start this process */
- char *coreName; /* optional core file component name */
- long pid; /* pid if created */
- long lastExit; /* last termination code */
- long lastSignal; /* last signal that killed this guy */
- long flags; /* flags giving process state */
-};
-
-</PRE>
-<P><B>format of struct bnode_proc explosion</B>
-<PRE> printf("comLine: %s\n", tp->comLine);
- printf("coreName: %s\n", tp->coreName);
- printf("pid: %ld\n", tp->pid);
- printf("lastExit: %ld\n", tp->lastExit);
- printf("lastSignal: %ld\n", tp->lastSignal);
-
-</PRE>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P><A HREF="auarf230.htm#HDRRUNNTP">runntp</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P><A HREF="auarf256.htm#HDRVOS_BACKUPSYS">vos backupsys</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf097.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf099.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf098.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf100.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_DELETE" HREF="auarf002.htm#ToC_113">bos delete</A></H2>
-<A NAME="IDX4506"></A>
-<A NAME="IDX4507"></A>
-<A NAME="IDX4508"></A>
-<A NAME="IDX4509"></A>
-<A NAME="IDX4510"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a server process from the <B>/usr/afs/local/BosConfig</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos delete -server</B> <<VAR>machine name</VAR>> <B>-instance</B> <<VAR>server process name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos d -s</B> <<VAR>machine name</VAR>> <B>-i</B> <<VAR>server process name</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos delete</B> command removes the
-<B>/usr/afs/local/BosConfig</B> entry for each process indicated by the
-<B>-instance</B> argument, on the server machine named by the
-<B>-server</B> argument.
-<P>Before issuing this command, issue the <B>bos stop</B> command to stop
-the process and set its status flag in the <B>BosConfig</B> file to
-<TT>NotRun</TT>. The <B>bos delete</B> command fails with an
-error message if a process's status flag is <TT>Run</TT>.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to delete the server process entry
-from the <B>/usr/afs/local/BosConfig</B> file. Identify the machine
-by IP address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to delete. Use the name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command;
-process names appear in the output of the <B>bos status</B>
-command.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the <B>buserver</B>, <B>kaserver</B>,
-<B>ptserver</B>, and <B>vlserver</B> entries from the
-<B>BosConfig</B> file on <B>db3.abc.com</B>, a database
-server machine being decommissioned.
-<PRE> % <B>bos delete -server db3.abc.com -instance buserver kaserver ptserver vlserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf098.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf100.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf099.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf101.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_EXEC" HREF="auarf002.htm#ToC_114">bos exec</A></H2>
-<A NAME="IDX4511"></A>
-<A NAME="IDX4512"></A>
-<A NAME="IDX4513"></A>
-<A NAME="IDX4514"></A>
-<A NAME="IDX4515"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Executes a command on a remote server machine
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos exec -server</B> <<VAR>machine name</VAR>> <B>-cmd</B> <<VAR>command to execute</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos e -s</B> <<VAR>machine name</VAR>> <B>-cm</B> <<VAR>command to execute</VAR>> [<B>-ce</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos exec</B> command executes the indicated command on the file
-server machine named by the <B>-server</B> argument. Its intended
-use is to reboot the machine, using the <B>/etc/reboot</B> command or
-equivalent.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to execute the command.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-cmd</B>
-</B><DD>Specifies the complete local disk pathname of the command to execute (for
-example, <B>/etc/reboot</B>). Surround this argument with double
-quotes ("") if the command contains one or more spaces.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command reboots the machine
-<B>fs2.abc.com</B>. The issuer has previously issued
-the <B>bos shutdown</B> command to shutdown all processes cleanly.
-<PRE> % <B>bos exec -server fs2.abc.com -cmd /sbin/shutdown -r now</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf099.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf101.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf100.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf102.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_GETDATE" HREF="auarf002.htm#ToC_115">bos getdate</A></H2>
-<A NAME="IDX4516"></A>
-<A NAME="IDX4517"></A>
-<A NAME="IDX4518"></A>
-<A NAME="IDX4519"></A>
-<A NAME="IDX4520"></A>
-<A NAME="IDX4521"></A>
-<A NAME="IDX4522"></A>
-<A NAME="IDX4523"></A>
-<A NAME="IDX4524"></A>
-<A NAME="IDX4525"></A>
-<A NAME="IDX4526"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the time stamps on an AFS binary file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos getdate -server</B> <<VAR>machine name</VAR>> <B>-file</B> <<VAR>files to check</VAR>><SUP>+</SUP>
- [<B>-dir</B> <<VAR>destination dir</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos getd -s</B> <<VAR>machine name</VAR>> <B>-f</B> <<VAR>files to check</VAR>><SUP>+</SUP> [<B>-d</B> <<VAR>destination dir</VAR>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos getdate</B> command displays the time stamps on the current
-version,<TT> .BAK</TT> version (if any) and <TT>.OLD</TT>
-version (if any) of each binary file named by the <B>-file</B>
-argument. (The BOS Server automatically creates <TT>.BAK</TT>
-and <TT>.OLD</TT> versions when new binaries are installed with the
-<B>bos install</B> command.) The files must reside in the
-<B>/usr/afs/bin</B> directory on the server machine named by the
-<B>-server</B> argument unless the <B>-dir</B> argument indicates an
-alternate directory.
-<P>To revert to the <TT>.BAK</TT> version of a binary, use the
-<B>bos uninstall</B> command. To remove obsolete binary files from
-the <B>/usr/afs/bin</B> directory, use the <B>bos prune</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to list binary files.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P>All server machines of the same AFS system type show the same timestamps if
-the binaries were installed properly on the binary distribution machine for
-this machine's system type, and if all other machines of that type are
-running the appropriate <B>upclientbin</B> process.
-<P><DT><B><B>-file</B>
-</B><DD>Names each binary file to list.
-<P><DT><B><B>-dir</B>
-</B><DD>Specifies the complete pathname of the local disk directory containing
-each file named by the <B>-file</B> argument. It is necessary only
-if the files are not in the <B>/usr/afs/bin</B> directory.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>For each file specified with the <B>-file</B> argument, the output
-displays the time stamp on the current (unmarked), <TT>.BAK</TT>, and
-<TT>.OLD</TT> version. The output explicitly reports that a
-version does not exist, rather than simply omitting it.
-<P><STRONG>Examples</STRONG>
-<P>The following command examines the time stamps on the files with basename
-<B>kaserver</B> on the machine <B>fs2.abc.com</B>:
-<PRE> % <B>bos getdate -server fs2.abc.com -file kaserver</B>
- File /usr/afs/bin/kaserver dated Mon Jan 4 10:00:36 1999.
- .BAK file dated Wed Dec 9 18:55:04 1998, no .OLD file.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf105.htm#HDRBOS_INSTALL">bos install</A>
-<P><A HREF="auarf109.htm#HDRBOS_PRUNE">bos prune</A>
-<P><A HREF="auarf123.htm#HDRBOS_UNINSTALL">bos uninstall</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf100.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf102.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf101.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf103.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_GETLOG" HREF="auarf002.htm#ToC_116">bos getlog</A></H2>
-<A NAME="IDX4527"></A>
-<A NAME="IDX4528"></A>
-<A NAME="IDX4529"></A>
-<A NAME="IDX4530"></A>
-<A NAME="IDX4531"></A>
-<A NAME="IDX4532"></A>
-<A NAME="IDX4533"></A>
-<A NAME="IDX4534"></A>
-<A NAME="IDX4535"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Prints a server process's log file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos getlog -server</B> <<VAR>machine name</VAR>> <B>-file</B> <<VAR>log file to examine</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos getl -s</B> <<VAR>machine name</VAR>> <B>-f</B> <<VAR>log file to examine</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos getlog</B> command displays on the standard output stream
-the specified log file from the machine named by the <B>-server</B>
-argument. The BOS Server fetches the log file from the
-<B>/usr/afs/logs</B> directory unless an alternate pathname is provided as
-part of the <B>-file</B> argument.
-<P><STRONG>Cautions</STRONG>
-<P>Log files can grow quite large, especially for the database server
-processes. To keep them to a manageable size, periodically either use
-the UNIX <B>rm</B> command to truncate each log file, or use the <B>bos
-restart</B> command to restart each process.
-<P>It can take up to five minutes after the file is removed or process
-restarted for the space occupied by a log file to become available.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to retrieve the log file.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-file</B>
-</B><DD>Names the log file to display. If a filename only is provided, the
-BOS Server fetches the log file from the <B>/usr/afs/logs</B>
-directory; the standard values are:
-<DL>
-<P><DT><B><B>AuthLog</B>
-</B><DD>The Authentication Server (<B>kaserver</B>) log file
-<P><DT><B><B>BackupLog</B>
-</B><DD>The Backup Server (<B>buserver</B>) log file
-<P><DT><B><B>BosLog</B>
-</B><DD>The BOS Server (<B>bosserver</B>) log file
-<P><DT><B><B>FileLog</B>
-</B><DD>The File Server (<B>fileserver</B>) log file
-<P><DT><B><B>SalvageLog</B>
-</B><DD>The Salvager (<B>salvager</B>) log file
-<P><DT><B><B>VLLog</B>
-</B><DD>The Volume Location (VL) Server (<B>vlserver</B>) log file
-<P><DT><B><B>VolserLog</B>
-</B><DD>The Volume Server (<B>volserver</B>) log file
-</DL>
-<P>
-<P>If a pathname and filename are provided, the log file is retrieved from the
-indicated directory. Partial pathnames are interpreted relative to the
-<B>/usr/afs/logs</B> directory.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output is preceded by the line
-<PRE> Fetching log file '<VAR>filename</VAR>'...
-
-</PRE>
-<P>The remainder of the output depends on the particular log file.
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the <B>FileLog</B> file from the machine
-<B>fs3.abc.com</B>:
-<PRE> % <B>bos getlog -server fs3.abc.com -file FileLog</B>
- Fetching log file 'FileLog'...
- Sun Nov 8 04:00:34 1998 File server starting
- Sun Nov 8 04:00:39 1998 Partition /vicepa: attached 21 volumes;
- 0 volumes not attached
- Sun Nov 8 04:00:40 1998 File Server started Sun Nov 8 04:00:40
- 1998
- Mon Nov 9 21:45:06 1998 CB: RCallBack (zero fid probe in host.c)
- failed for host 28cf37c0.22811
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf101.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf103.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf102.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf104.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_GETRESTART" HREF="auarf002.htm#ToC_117">bos getrestart</A></H2>
-<A NAME="IDX4536"></A>
-<A NAME="IDX4537"></A>
-<A NAME="IDX4538"></A>
-<A NAME="IDX4539"></A>
-<A NAME="IDX4540"></A>
-<A NAME="IDX4541"></A>
-<A NAME="IDX4542"></A>
-<A NAME="IDX4543"></A>
-<A NAME="IDX4544"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the automatic restart times for server processes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos getrestart -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos getr -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos getrestart</B> command displays two restart times from the
-<B>/usr/afs/local/BosConfig</B> file on the server machine named by the
-<B>-server</B> argument:
-<UL>
-<P><LI>The <I>general restart</I> time at which the BOS Server process
-automatically restarts itself and all processes marked with status
-<TT>Run</TT> in the <B>BosConfig</B> file. The default is Sunday
-at 4:00 a.m.
-<P><LI>The <I>binary restart</I> time at which the BOS Server automatically
-restarts any process for which the time stamp on the binary file in the
-<B>/usr/afs/bin</B> directory is later than the last restart time for the
-process. The default is 5:00 a.m. Use the <B>bos
-getdate</B> command to list a binary file's timestamp, and the
-<B>-long</B> flag to the <B>bos status</B> command to display a
-process's most recent restart time.
-</UL>
-<P>Use the <B>bos setrestart</B> command to set the restart times.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine for which to display the restart
-times. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output consists of two lines:
-<PRE> Server <VAR>machine_name</VAR> restarts at <VAR>time</VAR>
- Server <VAR>machine_name</VAR> restarts for new binaries at <VAR>time</VAR>
-
-</PRE>
-<P>Possible values for <I>time</I> include:
-<UL>
-<P><LI><TT>never</TT>, indicating that the BOS Server never performs that type
-of restart
-<P><LI><TT>now</TT>, indicating that the BOS Server performs that type of
-restart only each time it restarts
-<P><LI>A specified day and time, indicating that the BOS Server performs that
-type of restart once per week. Example: <TT>sun 4:00
-am</TT>.
-<P><LI>A specified time, indicating that the BOS Server performs that type of
-restart once per day. Examples: <TT>11:00 pm</TT>,
-<TT>3:00 am</TT>.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the restart times for the machine
-<B>db2.abc.com</B>:
-<PRE> % <B>bos getrestart db2.abc.com</B>
- Server db2.abc.com restarts at sun 4:00 am
- Server db2.abc.com restarts for new binaries at 2:15 am
-
-</PRE>
-<P>In the following example, the issuer abbreviates the machine name
-<B>fs1.abc.com</B> to <B>fs1</B>, relying on the
-cell's name server to resolve the name. The output echoes the
-abbreviated form.
-<PRE> % <B>bos getrestart fs1</B>
- Server fs1 restarts at sat 5:00 am
- Server fs1 restarts for new binaries at 11:30 pm
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf101.htm#HDRBOS_GETDATE">bos getdate</A>
-<P><A HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf102.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf104.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf103.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf105.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_HELP" HREF="auarf002.htm#ToC_118">bos help</A></H2>
-<A NAME="IDX4545"></A>
-<A NAME="IDX4546"></A>
-<A NAME="IDX4547"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>bos</B> commands or lists
-functional descriptions of all <B>bos</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>bos h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>bos</B> command.
-<P>To list every <B>bos</B> command whose name or short description
-includes a specified keyword, use the <B>bos apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-topic</B>
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>bos</B> part of the command name, providing only
-the operation code (for example, specify <B>status</B>, not <B>bos
-status</B>). If this argument is omitted, the output briefly
-describes every <B>bos</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>bos</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>bos
-status</B> command:
-<PRE> %<B> bos help status</B>
- bos status: show server instance status
- Usage: bos status -server <machine name> [-instance <server
- process name>+] [-long] [-cell <cell name>] [-noauth]
- [-localauth] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf097.htm#HDRBOS_APROPOS">bos apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf103.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf105.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf104.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf106.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_INSTALL" HREF="auarf002.htm#ToC_119">bos install</A></H2>
-<A NAME="IDX4548"></A>
-<A NAME="IDX4549"></A>
-<A NAME="IDX4550"></A>
-<A NAME="IDX4551"></A>
-<A NAME="IDX4552"></A>
-<A NAME="IDX4553"></A>
-<A NAME="IDX4554"></A>
-<A NAME="IDX4555"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Installs a new version of a binary file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos install -server</B> <<VAR>machine name</VAR>> <B>-file</B> <<VAR>files to install</VAR>><SUP>+</SUP>
- [<B>-dir</B> <<VAR>destination dir</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos i -s</B> <<VAR>machine name</VAR>> <B>-f</B> <<VAR>files to install</VAR>><SUP>+</SUP>
- [<B>-d</B> <<VAR>destination dir</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos install</B> command copies each binary file specified with
-the <B>-file</B> argument to the local disk of the server machine named by
-the <B>-server</B> argument, which is normally the binary distribution
-machine for its CPU/operating system type. The destination directory is
-<B>/usr/afs/bin</B> unless the <B>-dir</B> argument indicates an
-alternate directory. The source file's UNIX mode bits are
-preserved in the transfer.
-<P>If there is already a file of the same name in the destination directory,
-the BOS Server automatically saves it by adding a <TT>.BAK</TT>
-extension. If there is a current <TT>.BAK</TT> version at
-least seven days old, it replaces the current <TT>.OLD</TT>
-version. If there is no current <TT>.OLD</TT> version, the
-current <TT>.BAK</TT> version becomes the <TT>.OLD</TT>
-version automatically. The <B>bos getdate</B> command displays the
-timestamps on the current versions of the file.
-<P>To start using the new binary immediately, issue the <B>bos restart</B>
-command. Otherwise, the BOS Server automatically restarts the process
-at the time defined in the <B>/usr/afs/local/BosConfig</B> file; use
-the <B>bos getrestart</B> command to display the time and the <B>bos
-setrestart</B> time to set it.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the binary distribution machine on which to install the new
-binaries. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P>If the machine is not a binary distribution machine and is running an
-<B>upclientbin</B> process, then the files are overwritten the next time
-the <B>upclientbin</B> process fetches the corresponding file from the
-distribution machine (by default within five minutes).
-<P><DT><B><B>-file</B>
-</B><DD>Specifies the complete pathname of each binary file to copy into the
-destination directory. Each source directory can be on the local disk
-or in AFS, in which case the issuer of the <B>bos install</B> command must
-have the necessary AFS access rights and the local machine must run the Cache
-Manager. For the BOS Server to create <TT>.BAK</TT> and
-<TT>.OLD</TT> versions, the last element in the pathname (the
-filename) must match the name of a file in the destination directory.
-The reference page for the <B>bos create</B> command lists the standard
-binary file names.
-<P><DT><B><B>-dir</B>
-</B><DD>Provides the complete pathname of the local disk directory in which to
-install binary files. It is necessary only if the destination directory
-is not <B>/usr/afs/bin</B>.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command copies the file
-<B>/afs/abc.com/rs_aix42/usr/afs/bin/vlserver</B> to the file
-<B>/usr/afs/bin/vlserver</B> on the machine
-<B>fs3.abc.com</B>, which is the binary distribution machine
-for server machines running AIX 4.2 in the <B>abc.com</B>
-cell. The current version of the <B>/usr/afs/bin/vlserver</B> file
-is moved to <B>/usr/afs/bin/vlserver.BAK</B>.
-<PRE> % <B>bos install -server fs3.abc.com </B> \
- <B>-file /afs/abc.com/rs_aix42/usr/afs/bin/vlserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf101.htm#HDRBOS_GETDATE">bos getdate</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf104.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf106.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf105.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf107.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_LISTHOSTS" HREF="auarf002.htm#ToC_120">bos listhosts</A></H2>
-<A NAME="IDX4556"></A>
-<A NAME="IDX4557"></A>
-<A NAME="IDX4558"></A>
-<A NAME="IDX4559"></A>
-<A NAME="IDX4560"></A>
-<A NAME="IDX4561"></A>
-<A NAME="IDX4562"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the contents of the <B>/usr/afs/etc/CellServDB</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos listhosts -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos listh -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-
-<B>bos getcell -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos getc -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos listhosts</B> command formats and displays the list of a
-cell's database server machines from the
-<B>/usr/afs/etc/CellServDB</B> file on the server machine named by the
-<B>-server</B> argument.
-<P>To alter the list of machines, use the <B>bos addhost</B> and <B>bos
-removehost</B> commands.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to display the
-<B>/usr/afs/etc/CellServDB</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>For consistent performance in the cell, the output must be the same on
-every server machine. The <B>bos addhost</B> reference page
-explains how to keep the machines synchronized.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of the output names the cell to which the server machine
-belongs. Each of the following lines names a database server machine
-for that cell.
-<P>The <TT>Host</TT> number assigned to each database server machine is for
-server-internal use only and is not the same as, nor necessarily related to,
-the machine's IP address. The BOS Server assigned it as part of
-performing the <B>bos addhost</B> command.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the database server machines listed in the
-<B>/usr/afs/etc/CellServDB</B> file on the machine
-<B>fs7.abc.com</B>.
-<PRE> % <B>bos listhosts fs7.abc.com</B>
- Cell name is abc.com
- Host 1 is db1.abc.com
- Host 2 is db2.abc.com
- Host 3 is db3.abc.com
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf094.htm#HDRBOS_ADDHOST">bos addhost</A>
-<P><A HREF="auarf110.htm#HDRBOS_REMOVEHOST">bos removehost</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf105.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf107.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf106.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf108.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_LISTKEYS" HREF="auarf002.htm#ToC_121">bos listkeys</A></H2>
-<A NAME="IDX4563"></A>
-<A NAME="IDX4564"></A>
-<A NAME="IDX4565"></A>
-<A NAME="IDX4566"></A>
-<A NAME="IDX4567"></A>
-<A NAME="IDX4568"></A>
-<A NAME="IDX4569"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the server encryption keys from the
-<B>/usr/afs/etc/KeyFile</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos listkeys -server</B> <<VAR>machine name</VAR>> [<B>-showkey</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos listk -se</B> <<VAR>machine name</VAR>> [<B>-sh</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos listkeys</B> command formats and displays the list of server
-encryption keys from the <B>/usr/afs/etc/KeyFile</B> file on the server
-machine named by the <B>-server</B> argument.
-<P>To edit the list of keys, use the <B>bos addkey</B> and <B>bos
-removekey</B> commands.
-<P><STRONG>Cautions</STRONG>
-<P>Displaying actual keys on the standard output stream (by including the
-<B>-showkey</B> flag) is a security exposure. Displaying a checksum
-is sufficient for most purposes.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to display the <B>KeyFile</B>
-file. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P>For consistent performance in the cell, the output must be the same on
-every server machine. The <B>bos addkey</B> reference page explains
-how to keep the machines synchronized.
-<P><DT><B><B>-showkey</B>
-</B><DD>Displays the octal digits that constitute each key.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes one line for each server encryption key listed in the
-<B>KeyFile</B> file, identified by its key version number.
-<P>If the <B>-showkey</B> flag is included, the output displays the actual
-string of eight octal numbers that constitute the key. Each octal
-number is a backslash and three decimal digits.
-<P>If the <B>-showkey</B> flag is not included, the output represents each
-key as a checksum, which is a decimal number derived by encrypting a constant
-with the key.
-<P>Following the list of keys or checksums, the string <TT>Keys last
-changed</TT> indicates when a key was last added to the <B>KeyFile</B>
-file. The words <TT>All done</TT> indicate the end of the
-output.
-<P>For mutual authentication to work properly, the output from the command
-<B>kas examine afs</B> must match the key or checksum with the same key
-version number in the output from this command.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the checksums for the keys stored in the
-<B>KeyFile</B> file on the machine
-<B>fs3.abc.com</B>.
-<PRE> % <B>bos listkeys fs3.abc.com</B>
- key 1 has cksum 972037177
- key 3 has cksum 2825175022
- key 4 has cksum 260617746
- key 6 has cksum 4178774593
- Keys last changed on Mon Apr 12 11:24:46 1999.
- All done.
-
-</PRE>
-<P>The following example shows the actual keys from the <B>KeyFile</B>
-file on the machine <B>fs6.abc.com</B>.
-<PRE> % <B>bos listkeys fs6.abc.com -showkey</B>
- key 0 is '\040\205\211\241\345\002\023\211'
- key 1 is '\343\315\307\227\255\320\135\244'
- key 2 is '\310\310\255\253\326\236\261\211'
- Keys last changed on Wed Mar 31 11:24:46 1999.
- All done.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf111.htm#HDRBOS_REMOVEKEY">bos removekey</A>
-<P><A HREF="auarf115.htm#HDRBOS_SETAUTH">bos setauth</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf106.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf108.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf107.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf109.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_LISTUSERS" HREF="auarf002.htm#ToC_122">bos listusers</A></H2>
-<A NAME="IDX4570"></A>
-<A NAME="IDX4571"></A>
-<A NAME="IDX4572"></A>
-<A NAME="IDX4573"></A>
-<A NAME="IDX4574"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Lists the privileged users from the <B>/usr/afs/etc/UserList</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos listusers -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos listu -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos listusers</B> command lists the user names from the
-<B>/usr/afs/etc/UserList</B> file on the file server machine named by the
-<B>-server</B> argument. The users are authorized to issue
-privileged <B>bos</B> and <B>vos</B> commands.
-<P>To edit the list of users, use the <B>bos adduser</B> and <B>bos
-removeuser</B> commands.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to display the <B>UserList</B>
-file. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P>For consistent performance in the cell, the output must be the same on
-every server machine. The <B>bos adduser</B> reference page
-explains how to keep the machines synchronized.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output lists the user name of each user entitled to issue privileged
-<B>bos</B> and <B>vos</B> commands.
-<P><STRONG>Examples</STRONG>
-<P>The following example lists the users from <B>UserList</B> file on the
-machine <B>fs4.abc.com</B>.
-<PRE> % <B>bos listusers fs4.abc.com</B>
- SUsers are: pat smith jones terry
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf096.htm#HDRBOS_ADDUSER">bos adduser</A>
-<P><A HREF="auarf112.htm#HDRBOS_REMOVEUSER">bos removeuser</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf107.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf109.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf108.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf110.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_PRUNE" HREF="auarf002.htm#ToC_123">bos prune</A></H2>
-<A NAME="IDX4575"></A>
-<A NAME="IDX4576"></A>
-<A NAME="IDX4577"></A>
-<A NAME="IDX4578"></A>
-<A NAME="IDX4579"></A>
-<A NAME="IDX4580"></A>
-<A NAME="IDX4581"></A>
-<A NAME="IDX4582"></A>
-<A NAME="IDX4583"></A>
-<A NAME="IDX4584"></A>
-<A NAME="IDX4585"></A>
-<A NAME="IDX4586"></A>
-<A NAME="IDX4587"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes obsolete versions of files from the <B>/usr/afs/bin</B> and
-<B>/usr/afs/logs</B> directories
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos prune -server</B> <<VAR>machine name</VAR>> [<B>-bak</B>] [<B>-old</B>] [<B>-core</B>] [<B>-all</B>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos p -s</B> <<VAR>machine name</VAR>> [<B>-b</B>] [<B>-o</B>] [<B>-co</B>] [<B>-a</B>]
- [<B>-ce</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos prune</B> command removes files from the local disk of the
-server machine named by the <B>-server</B> argument, as specified by one
-or more of the following flags provided on the command line:
-<UL>
-<P><LI>The <B>-bak</B> flag removes all files from the
-<B>/usr/afs/bin</B> directory that have a <TT>.BAK</TT>
-extension.
-<P><LI>The <B>-old</B> flag removes all files from the
-<B>/usr/afs/bin</B> directory that have a <TT>.OLD</TT>
-extension.
-<P><LI>The <B>-core</B> flag removes all files from the
-<B>/usr/afs/logs</B> directory that have a <TT>core.</TT>
-prefix.
-<P><LI>The <B>-all</B> flag removes all three types of files at once.
-</UL>
-<P>(If none of these flags are included, the command appears to succeed, but
-removes no files at all.)
-<P>To display the timestamp on the current, <TT>.BAK</TT>, and
-<TT>.OLD</TT> versions of one or more files, use the <B>bos
-getdate</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine from which to remove files. Identify
-the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-bak</B>
-</B><DD>Removes all files from the <B>/usr/afs/bin</B> directory that have a
-<TT>.BAK</TT> extension. Do not combine this flag and the
-<B>-all</B> flag.
-<P><DT><B><B>-old</B>
-</B><DD>Removes all files from the <B>/usr/afs/bin</B> directory that have a
-<TT>.OLD</TT> extension. Do not combine this flag and the
-<B>-all</B> flag.
-<P><DT><B><B>-core</B>
-</B><DD>Removes all files from the <B>/usr/afs/logs</B> directory that have a
-<TT>core.</TT> prefix. Do not combine this flag and the
-<B>-all</B> flag.
-<P><DT><B><B>-all</B>
-</B><DD>Combines the effect of the <B>-bak</B>, <B>-old</B>, and
-<B>-core</B> flags. Do not combine this flag with any of those
-three.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example removes all files from the <B>/usr/afs/bin</B>
-directory on the machine <B>fs3.abc.com</B> that have a
-<TT>.BAK</TT> or <TT>.OLD</TT> extension.
-<PRE> % <B>bos prune -server fs3.abc.com -bak -old</B>
-
-</PRE>
-<P>The following example removes all files from the <B>/usr/afs/bin</B>
-directory on the machine <B>db2.abc.com</B> that have a
-<TT>.BAK</TT> or <TT>.OLD</TT> extension, and all files from
-the <B>/usr/afs/logs</B> directory that have a <TT>core.</TT>
-prefix.
-<PRE> % <B>bos prune -server db2.abc.com -all</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf101.htm#HDRBOS_GETDATE">bos getdate</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf108.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf110.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf109.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf111.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_REMOVEHOST" HREF="auarf002.htm#ToC_124">bos removehost</A></H2>
-<A NAME="IDX4588"></A>
-<A NAME="IDX4589"></A>
-<A NAME="IDX4590"></A>
-<A NAME="IDX4591"></A>
-<A NAME="IDX4592"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a database server machine from the
-<B>/usr/afs/etc/CellServDB</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos removehost -server</B> <<VAR>machine name</VAR>> <B>-host</B> <<VAR>host name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos removeh -s</B> <<VAR>machine name</VAR>> <B>-ho</B> <<VAR>host name</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-he</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos removehost</B> command removes the entry for each database
-server machine specified with the <B>-host</B> argument from the
-<B>/usr/afs/etc/CellServDB</B> file on the server machine named by the
-<B>-server</B> argument.
-<P><STRONG>Cautions</STRONG>
-<P>After executing this command (and waiting for the Update Server to
-propagate the changes, if it is used), restart the database server processes
-on all database server machines to force election of a quorum that includes
-the new set of machines listed in the <B>/usr/afs/etc/CellServDB</B>
-file. The <I>IBM AFS Quick Beginnings</I> explains in more detail
-how to add and remove database server machines.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to change the
-<B>/usr/afs/etc/CellServDB</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-host</B>
-</B><DD>Specifies the fully-qualified host name (such as
-<B>fs2.abc.com</B>) of each database server machine to
-remove from the <B>CellServDB</B> file.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the former database server machine
-<B>db2.abc.com</B> from the <B>CellServDB</B> file on
-the system control machine <B>fs1.abc.com</B>.
-<PRE> % <B>bos removehost -server fs1.abc.com -host db2.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf094.htm#HDRBOS_ADDHOST">bos addhost</A>
-<P><A HREF="auarf106.htm#HDRBOS_LISTHOSTS">bos listhosts</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf109.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf111.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf110.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf112.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_REMOVEKEY" HREF="auarf002.htm#ToC_125">bos removekey</A></H2>
-<A NAME="IDX4593"></A>
-<A NAME="IDX4594"></A>
-<A NAME="IDX4595"></A>
-<A NAME="IDX4596"></A>
-<A NAME="IDX4597"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a server encryption key from the <B>/usr/afs/etc/KeyFile</B>
-file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos removekey -server</B> <<VAR>machine name</VAR>> <B>-kvno</B> <<VAR>key version number</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos removek -s</B> <<VAR>machine name</VAR>> <B>-k</B> <<VAR>key version number</VAR>><SUP>+</SUP>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos removekey</B> command removes each specified encryption key
-from the <B>/usr/afs/etc/KeyFile</B> file on the machine named by the
-<B>-server</B> argument. Use the <B>-kvno</B> argument to
-identify each key by its key version number; use the <B>bos
-listkeys</B> command to display the key version numbers.
-<P><STRONG>Cautions</STRONG>
-<P>Before removing a obsolete key, verify that the cell's maximum ticket
-lifetime has passed since the current key was defined using the <B>kas
-setpassword</B> and <B>bos addkey</B> commands. This ensures that
-no clients still possess tickets encrypted with the obsolete key.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to change the
-<B>/usr/afs/etc/KeyFile</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-kvno</B>
-</B><DD>Specifies the key version number of each key to remove.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the keys with key version numbers 5 and 6
-from the <B>KeyFile</B> file on the system control machine
-<B>fs1.abc.com</B>.
-<PRE> % <B>bos removekey -server fs1.abc.com -kvno 5 6</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf110.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf112.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf111.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf113.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_REMOVEUSER" HREF="auarf002.htm#ToC_126">bos removeuser</A></H2>
-<A NAME="IDX4598"></A>
-<A NAME="IDX4599"></A>
-<A NAME="IDX4600"></A>
-<A NAME="IDX4601"></A>
-<A NAME="IDX4602"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a privileged user from the <B>/usr/afs/etc/UserList</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos removeuser -server</B> <<VAR>machine name</VAR>> <B>-user</B> <<VAR>user names</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos removeu -s</B> <<VAR>machine name</VAR>> <B>-u</B> <<VAR>user names</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos removeuser</B> command removes each user name specified with
-the <B>-user</B> argument from the <B>/usr/afs/etc/UserList</B> file
-on the machine named by the <B>-server</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to change the
-<B>/usr/afs/etc/UserList</B> file. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>In cells that run the United States edition of AFS and use the Update
-Server to distribute the contents of the <B>/usr/afs/etc</B> directory, it
-is conventional to specify only the system control machine as a value for the
-<B>-server</B> argument. In cells that run the international
-version of AFS, repeat the command for each file server machine. For
-further discussion, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-user</B>
-</B><DD>Specifies each user name to remove.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example removes the users <B>pat</B> and <B>jones</B>
-from the <B>UserList</B> file on the system control machine
-<B>fs1.abc.com</B>.
-<PRE> % <B>bos removeuser -server fs1.abc.com -user pat jones</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf111.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf113.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf112.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf114.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_RESTART" HREF="auarf002.htm#ToC_127">bos restart</A></H2>
-<A NAME="IDX4603"></A>
-<A NAME="IDX4604"></A>
-<A NAME="IDX4605"></A>
-<A NAME="IDX4606"></A>
-<A NAME="IDX4607"></A>
-<A NAME="IDX4608"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restarts a server process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos restart -server</B> <<VAR>machine name</VAR>> [<B>-instance</B> <<VAR>instances</VAR>><SUP>+</SUP>] [<B>-bosserver</B>]
- [<B>-all</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos res -s</B> <<VAR>machine name</VAR>> [<B>-i</B> <<VAR>instances</VAR>><SUP>+</SUP>] [<B>-b</B>] [<B>-a</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos restart</B> command stops and immediately restarts server
-processes on the server machine named by the <B>-server</B>
-argument. Indicate which process or processes to restart by providing
-one of the following arguments:
-<UL>
-<P><LI>The <B>-instance</B> argument names each AFS server process to stop
-and restart immediately, regardless of its status flag in the
-<B>/usr/afs/local/BosConfig</B> file. Do not include
-<B>bosserver</B> in the list of processes; use the
-<B>-bosserver</B> flag instead.
-<P><LI>The <B>-bosserver</B> flag stops all AFS server processes running on
-the machine, including the BOS Server. A new BOS Server starts
-immediately, and it starts a new instance of each process that is marked with
-the <TT>Run</TT> status flag in the <B>BosConfig</B> file.
-<P><LI>The <B>-all</B> flag stops all AFS server processes running on the
-machine, except the BOS Server, and immediately restarts the processes that
-are marked with the <TT>Run</TT> status flag in the <B>BosConfig</B>
-file.
-</UL>
-<P>This command does not change a process's status flag in the
-<B>BosConfig</B> file.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to restart each process.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to stop and then restart immediately regardless of its
-status flag setting. Use the process name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command. The
-output from the <B>bos status</B> command lists the names. Provide
-this flag or one of the <B>-bosserver</B> or <B>-all</B> options, but
-do not combine them.
-<P><DT><B><B>-bosserver</B>
-</B><DD>Stops all AFS server processes running on the machine, including the BOS
-Server. A new BOS Server instance immediately starts, and starts all
-processes marked with the <TT>Run</TT> status flag in the
-<B>BosConfig</B> file. Provide this flag or one of the
-<B>-instance</B> or <B>-all</B> options, but do not combine
-them.
-<P><DT><B><B>-all</B>
-</B><DD>Stops all AFS server processes running on the machine other than the BOS
-Server, and immediately restarts the processes marked with the <B>Run</B>
-status flag in the <B>BosConfig</B> file. Provide this flag or one
-of the <B>-instance</B> or <B>-bosserver</B> options, but do not
-combine them.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command stops and restarts all processes running on the
-machine <B>fs3.abc.com</B>, including the BOS Server.
-<PRE> % <B>bos restart -server fs3.abc.com -bosserver</B>
-
-</PRE>
-<P>The following command stops and restarts all processes running on the
-machine <B>fs5.abc.com</B>, excluding the BOS Server.
-<PRE> % <B>bos restart -server fs5.abc.com -all</B>
-
-</PRE>
-<P>The following command stops and restarts the Protection Server and Volume
-Location (VL) Server processes on the machine
-<B>db3.abc.com</B>:
-<PRE> % <B>bos restart -server db3.abc.com -instance ptserver vlserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf112.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf114.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf113.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf115.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_SALVAGE" HREF="auarf002.htm#ToC_128">bos salvage</A></H2>
-<A NAME="IDX4609"></A>
-<A NAME="IDX4610"></A>
-<A NAME="IDX4611"></A>
-<A NAME="IDX4612"></A>
-<A NAME="IDX4613"></A>
-<A NAME="IDX4614"></A>
-<A NAME="IDX4615"></A>
-<A NAME="IDX4616"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Restores internal consistency to a file system or volume
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos salvage -server</B> <<VAR>machine name</VAR>> [<B>-partition</B> <<VAR>salvage partition</VAR>>]
- [<B>-volume</B> <<VAR>salvage volume number or volume name</VAR>>]
- [<B>-file</B> <<VAR>salvage log output file</VAR>>] [<B>-all</B>] [<B>-showlog</B>]
- [<B>-parallel</B> <<VAR># of max parallel partition salvaging</VAR>>]
- [<B>-tmpdir</B> <<VAR>directory to place tmp files</VAR>>]
- [<B>-orphans</B> <<B>ignore</B> | <B>remove</B> | <B>attach</B>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos sa -se</B> <<VAR>machine name</VAR>> [<B>-part</B> <<VAR>salvage partition</VAR>>]
- [<B>-v</B> <<VAR>salvage volume number or volume name</VAR>>]
- [<B>-f</B> <<VAR>salvage log output file</VAR>>] [<B>-a</B>] [<B>-sh</B>]
- [<B>-para</B> <<VAR># of max parallel partition salvaging</VAR>>]
- [<B>-t</B> <<VAR>directory to place tmp files</VAR>>]
- [<B>-o</B> <<B>ignore</B> | <B>remove</B> | <B>attach</B>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos salvage</B> command salvages (restores internal consistency
-to) one or more volumes on the file server machine named by the
-<B>-server</B> argument. When processing one or more partitions,
-the command restores consistency to corrupted read/write volumes where
-possible. For read-only or backup volumes, it inspects only the volume
-header:
-<UL>
-<P><LI>If the volume header is corrupted, the Salvager removes the volume
-completely and records the removal in its log file,
-<B>/usr/afs/logs/SalvageLog</B>. Issue the <B>vos release</B>
-or <B>vos backup</B> command to create the read-only or backup volume
-again.
-<P><LI>If the volume header is intact, the Salvager skips the volume (does not
-check for corruption in the contents). However, if the File Server
-notices corruption as it initializes, it sometimes refuses to attach the
-volume or bring it online. In this case, it is simplest to remove the
-volume by issuing the <B>vos remove</B> or <B>vos zap</B>
-command. Then issue the <B>vos release</B> or <B>vos backup</B>
-command to create it again.
-</UL>
-<P>Use the indicated arguments to salvage a specific number of volumes:
-<UL>
-<P><LI>To process all volumes on a file server machine, provide the
-<B>-server</B> argument and the <B>-all</B> flag. No volumes on
-the machine are accessible to Cache Managers during the salvage operation,
-because the BOS Server stops the File Server and Volume Server processes while
-the Salvager runs. The BOS Server automatically restarts them when the
-operation completes.
-<P><LI>To process all volumes on one partition, provide the <B>-server</B>
-and <B>-partition</B> arguments. As for a salvage of the entire
-machine, no volumes on the machine are accessible to Cache Managers during the
-salvage operation. The BOS Server automatically restarts the File
-Server and Volume Server when the operation completes.
-<P><LI>To salvage only one read/write volume, combine the <B>-server</B>,
-<B>-partition</B>, and <B>-volume</B> arguments. Only that
-volume is inaccessible to Cache Managers, because the BOS Server does not
-shutdown the File Server and Volume Server processes during the salvage of a
-single volume. Do not name a read-only or backup volume with the
-<B>-volume</B> argument. Instead, remove the volume, using the
-<B>vos remove</B> or <B>vos zap</B> command. Then create a new
-copy of the volume with the <B>vos release</B> or <B>vos backup</B>
-command.
-</UL>
-<P>During the salvage of an entire machine or partition, the <B>bos
-status</B> command reports the <B>fs</B> process's auxiliary status
-as <TT>Salvaging file system</TT>.
-<P>The Salvager always writes a trace to the
-<B>/usr/afs/logs/SalvageLog</B> file on the file server machine where it
-runs. To record the trace in another file as well (either in AFS or on
-the local disk of the machine where the <B>bos salvage</B> command is
-issued), name the file with the <B>-file</B> argument. To display
-the trace on the standard output stream as it is written to the
-<B>/usr/afs/logs/SalvageLog</B> file, include the <B>-showlog</B>
-flag.
-<P>By default, multiple Salvager subprocesses run in parallel: one for
-each partition up to four, and four subprocesses for four or more
-partitions. To increase or decrease the number of subprocesses running
-in parallel, provide a positive integer value for the <B>-parallel</B>
-argument.
-<P>If there is more than one server partition on a physical disk, the Salvager
-by default salvages them serially to avoid the inefficiency of constantly
-moving the disk head from one partition to another. However, this
-strategy is often not ideal if the partitions are configured as logical
-volumes that span multiple disks. To force the Salvager to salvage
-logical volumes in parallel, provide the string <B>all</B> as the value
-for the <B>-parallel</B> argument. Provide a positive integer to
-specify the number of subprocesses to run in parallel (for example,
-<B>-parallel 5all</B> for five subprocesses), or omit the integer to run
-up to four subprocesses, depending on the number of logical volumes being
-salvaged.
-<P>The Salvager creates temporary files as it runs, by default writing them to
-the partition it is salvaging. The number of files can be quite large,
-and if the partition is too full to accommodate them, the Salvager terminates
-without completing the salvage operation (it always removes the temporary
-files before exiting). Other Salvager subprocesses running at the same
-time continue until they finish salvaging all other partitions where there is
-enough disk space for temporary files. To complete the interrupted
-salvage, reissue the command against the appropriate partitions, adding the
-<B>-tmpdir</B> argument to redirect the temporary files to a local disk
-directory that has enough space.
-<P>The <B>-orphans</B> argument controls how the Salvager handles orphaned
-files and directories that it finds on server partitions it is
-salvaging. An <I>orphaned</I> element is completely inaccessible
-because it is not referenced by the vnode of any directory that can act as its
-parent (is higher in the filespace). Orphaned objects occupy space on
-the server partition, but do not count against the volume's quota.
-<P><STRONG>Cautions</STRONG>
-<P>Running this command can result in data loss if the Salvager process can
-repair corruption only by removing the offending data. Consult the
-<I>IBM AFS Administration Guide</I> for more information.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Indicates the file server machine on which to salvage volumes.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Specifies a single partition on which to salvage all volumes.
-Provide the complete partition name (for example <B>/vicepa</B>) or one of
-the following abbreviated forms:
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P><DT><B>-volume
-</B><DD>Specifies the name or volume ID number of a read/write volume to
-salvage. The <B>-partition</B> argument must be provided along with
-this one.
-<P><DT><B>-file
-</B><DD>Specifies the complete pathname of a file into which to write a trace of
-the salvage operation, in addition to the <B>/usr/afs/logs/SalvageLog</B>
-file on the server machine. If the file pathname is local, the trace is
-written to the specified file on the local disk of the machine where the
-<B>bos salvage</B> command is issued. If the <B>-volume</B>
-argument is included, the file can be in AFS, though not in the volume being
-salvaged. Do not combine this argument with the <B>-showlog</B>
-flag.
-<P><DT><B>-all
-</B><DD>Salvages all volumes on all of the partitions on the machine named by the
-<B>-server</B> argument.
-<P><DT><B>-showlog
-</B><DD>Displays the trace of the salvage operation on the standard output stream,
-as well as writing it to the <B>/usr/afs/logs/SalvageLog</B> file.
-Do not combine this flag with the <B>-file</B> argument.
-<P><DT><B>-parallel
-</B><DD>Specifies the maximum number of Salvager subprocesses to run in
-parallel. Provide one of three values:
-<UL>
-<P><LI>An integer from the range <B>1</B> to <B>32</B>. A value of
-<B>1</B> means that a single Salvager process salvages the partitions
-sequentially.
-<P><LI>The string <B>all</B> to run up to four Salvager subprocesses in
-parallel on partitions formatted as logical volumes that span multiple
-physical disks. Use this value only with such logical volumes.
-<P><LI>The string <B>all</B> followed immediately (with no intervening space)
-by an integer from the range <B>1</B> to <B>32</B>, to run the
-specified number of Salvager subprocesses in parallel on partitions formatted
-as logical volumes. Use this value only with such logical
-volumes.
-</UL>
-<P>The BOS Server never starts more Salvager subprocesses than there are
-partitions, and always starts only one process to salvage a single
-volume. If this argument is omitted, up to four Salvager subprocesses
-run in parallel.
-<P><DT><B>-tmpdir
-</B><DD>Specifies the full pathname of a local disk directory to which the
-Salvager process writes temporary files as it runs. If this argument is
-omitted, or specifies an ineligible or nonexistent directory, the Salvager
-process writes the files to the partition it is currently salvaging.
-<P><DT><B>-orphans
-</B><DD>Controls how the Salvager handles orphaned files and directories.
-Choose one of the following three values:
-<DL>
-<P><DT><B>ignore
-</B><DD>Leaves the orphaned objects on the disk, but prints a message to the
-<B>/usr/afs/logs/SalvageLog</B> file reporting how many orphans were found
-and the approximate number of kilobytes they are consuming. This is the
-default if the <B>-orphans</B> argument is omitted.
-<P><DT><B>remove
-</B><DD>Removes the orphaned objects, and prints a message to the
-<B>/usr/afs/logs/SalvageLog</B> file reporting how many orphans were
-removed and the approximate number of kilobytes they were consuming.
-<P><DT><B>attach
-</B><DD>Attaches the orphaned objects by creating a reference to them in the vnode
-of the volume's root directory. Since each object's actual
-name is now lost, the Salvager assigns each one a name of the following
-form:
-<DL>
-<DD><P><B>_ _ORPHANFILE_ _.</B><VAR>index</VAR> for files
-<DD><P><B>_ _ORPHANDIR_ _.</B><VAR>index</VAR> for directories
-</DL>
-<P>
-<P>where <VAR>index</VAR> is a two-digit number that uniquely identifies each
-object. The orphans are charged against the volume's quota and
-appear in the output of the <B>ls</B> command issued against the
-volume's root directory.
-</DL>
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command salvages all volumes on the <B>/vicepd</B>
-partition of the machine <B>db3.abc.com</B>:
-<PRE> % <B>bos salvage -server db3.abc.com -partition /vicepd</B>
-
-</PRE>
-<P>The following command salvages the volume with volume ID number 536870988
-on partition <B>/vicepb</B> of the machine
-<B>fs2.abc.com</B>:
-<PRE> % <B>bos salvage -server fs2.abc.com -partition /vicepb -volume 536870988</B>
-
-</PRE>
-<P>The following command salvages all volumes on the machine
-<B>fs4.abc.com</B>. Six Salvager processes run in
-parallel rather than the default four.
-<PRE> % <B>bos salvage -server fs4.abc.com -all -parallel 6</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf030.htm#HDRSALVAGELOG">SalvageLog</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P><A HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf113.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf115.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf114.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf116.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_SETAUTH" HREF="auarf002.htm#ToC_129">bos setauth</A></H2>
-<A NAME="IDX4617"></A>
-<A NAME="IDX4618"></A>
-<A NAME="IDX4619"></A>
-<A NAME="IDX4620"></A>
-<A NAME="IDX4621"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets authorization checking requirements for all server processes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos setauth -server</B> <<VAR>machine name</VAR>>
- <B>-authrequired</B> <<VAR>on or off: authentication required for admin requests</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos seta -s</B> <<VAR>machine name</VAR>>
- <B>-a</B> <<VAR>on or off: authentication required for admin requests</VAR>>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos setauth</B> command enables or disables authorization
-checking on the server machine named by the <B>-server</B>
-argument. When authorization checking is enabled (the normal case), the
-AFS server processes running on the machine verify that the issuer of a
-command meets its privilege requirements. When authorization checking
-is disabled, server processes perform any action for anyone, including the
-unprivileged user <B>anonymous</B>; this security exposure precludes
-disabling of authorization checking except during installation or
-emergencies.
-<P>To indicate to the server processes that authorization checking is
-disabled, the BOS Server creates the zero-length file
-<B>/usr/afs/local/NoAuth</B> on its local disk. All AFS server
-processes constantly monitor for the <B>NoAuth</B> file's presence
-and do not check for authorization when it is present. The BOS Server
-removes the file when this command is used to reenable authorization
-checking.
-<P><STRONG>Cautions</STRONG>
-<P>Do not create the <B>NoAuth</B> file directly, except when directed by
-instructions for dealing with emergencies (doing so requires being logged in
-as the local superuser <B>root</B>). Use this command
-instead.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to enable or disable authorization
-checking. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P><DT><B><B>-authrequired</B>
-</B><DD>Enables authorization checking if the value is <B>on</B>, or disables
-it if the value is <B>off</B>.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example disables authorization checking on the machine
-<B>fs7.abc.com</B>:
-<PRE> % <B>bos setauth -server fs7.abc.com -authrequired off</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf028.htm#HDRNOAUTH">NoAuth</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf114.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf116.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf115.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf117.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_SETCELLNAME" HREF="auarf002.htm#ToC_130">bos setcellname</A></H2>
-<A NAME="IDX4622"></A>
-<A NAME="IDX4623"></A>
-<A NAME="IDX4624"></A>
-<A NAME="IDX4625"></A>
-<A NAME="IDX4626"></A>
-<A NAME="IDX4627"></A>
-<A NAME="IDX4628"></A>
-<A NAME="IDX4629"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the cell's name in the <B>/usr/afs/etc/ThisCell</B> and
-<B>/usr/afs/etc/CellServDB</B> files
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos setcellname -server</B> <<VAR>machine name</VAR>> <B>-name</B> <<VAR>cell name</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos setc -s</B> <<VAR>machine name</VAR>> <B>-n</B> <<VAR>cell name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos setcellname</B> command establishes the cell's name and
-makes the server machine named by the <B>-server</B> argument a member of
-it, by recording the value of the <B>-name</B> argument in two files which
-it creates on the local disk:
-<UL>
-<P><LI><B>/usr/afs/etc/ThisCell</B>
-<P><LI><B>/usr/afs/etc/CellServDB</B>. The cell name appears on the
-first line in the file, preceded by the required <TT>></TT> symbol.
-The machine name specified with the <B>-server</B> argument appears on the
-second line along with its IP address as obtained from the cell's naming
-service. The machine is thus designated as the cell's first
-database server machine.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>Issue this command only when the installing the cell's first AFS
-server machine. The <I>IBM AFS Quick Beginnings</I> explains how to
-copy over the <B>ThisCell</B> and <B>CellServDB</B> files from this or
-another appropriate machine during installation of additional server
-machines.
-<P>Be sure to choose a satisfactory cell name when issuing this command,
-because changing a cell's name is very complicated; for one thing,
-it requires changing every password in the Authentication Database.
-Consult the <I>IBM AFS Administration Guide</I> for advice on choosing a
-cell name. If changing the cell's name is absolutely necessary,
-contact AFS Product Support for complete instructions.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to set the cell name in the
-<B>ThisCell</B> and <B>CellServDB</B> file. It is always the
-first machine installed in a cell. Identify the machine by IP address
-or its host name (either fully-qualified or abbreviated unambiguously).
-For details, see the introductory reference page for the <B>bos</B>
-command suite.
-<P><DT><B><B>-name</B>
-</B><DD>Defines the cell name, using standard Internet domain name format (the
-actual domain name is usually appropriate). Examples are
-<B>abc.com</B> for the ABC Corporation and
-<B>stateu.edu</B> for the State University. It must match
-the value of the <B>-cell</B> argument, if that is provided.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command defines the cell name <B>abc.com</B> in
-the <B>ThisCell</B> and <B>CellServDB</B> files on the machine
-<B>fs1.abc.com</B> as it is installed as the cell's
-first server machine.
-<PRE> % <B>bos setcellname -server fs1.abc.com -name abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>Authorization checking is normally turned off during installation, which is
-the only recommended time to use this command; in this case no privilege
-is required. If authorization checking is turned on, the issuer must be
-listed in the <B>/usr/afs/etc/UserList</B> file on the machine named by
-the <B>-server</B> argument, or must be logged in as the local superuser
-<B>root</B> if the <B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf033.htm#HDRSV_THISCELL">ThisCell (server version)</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf115.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf117.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf116.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf118.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_SETRESTART" HREF="auarf002.htm#ToC_131">bos setrestart</A></H2>
-<A NAME="IDX4630"></A>
-<A NAME="IDX4631"></A>
-<A NAME="IDX4632"></A>
-<A NAME="IDX4633"></A>
-<A NAME="IDX4634"></A>
-<A NAME="IDX4635"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the date and time at which the BOS Server restarts processes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos setrestart -server</B> <<VAR>machine name</VAR>> <B>-time</B> <<VAR>time to restart server</VAR>>
- [<B>-general</B>] [<B>-newbinary</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos setr -s</B> <<VAR>machine name</VAR>> <B>-t</B> <<VAR>time to restart server</VAR>> [<B>-g</B>] [<B>-ne</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos setrestart</B> command records in the
-<B>/usr/afs/local/BosConfig</B> file the times at which the BOS Server
-running on the server machine named by the <B>-server</B> argument
-performs two types of restarts:
-<UL>
-<P><LI>A <I>general restart</I>. By default, once per week the BOS
-Server restarts itself and then any AFS process marked with the <TT>Run</TT>
-status flag in the <B>BosConfig</B> file (equivalent in effect to issuing
-the <B>bos restart</B> command with the <B>-bosserver</B>
-flag). The default setting is 4:00 a.m. each Sunday
-morning.
-<P><LI>A <I>binary restart</I>. By default, once per day the BOS
-Server restarts any currently running process for which the timestamp on the
-binary file in the <B>/usr/afs/bin</B> directory is later than the time
-the process last started or restarted. The default is 5:00
-a.m. each day.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>Restarting a process makes it unavailable for a period of time. The
-<B>fs</B> process has potentially the longest outage, depending on how
-many volumes the file server machine houses (the File Server and Volume Server
-reattach each volume when they restart). The default settings are
-designed to coincide with periods of low usage, so that the restarts disturb
-the smallest possible number of users.
-<P>If the setting specified with the <B>-time</B> argument is within one
-hour of the current time, the BOS Server does not restart any processes until
-the next applicable opportunity (the next day for binary restarts, or the next
-week for general restarts).
-<P>The command changes only one type of restart setting at a time; issue
-the command twice to change both settings.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Indicates the server machine on which to set a new restart time.
-Identify the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B>-time
-</B><DD>Specifies the restart time. By convention the general restart is
-defined as weekly (specifies both a day and a time), and the binary restart is
-defined as daily (specifies only a time). However, it is acceptable to
-define a daily general restart or weekly binary restart.
-<P>There are four acceptable values for either type of restart setting:
-<UL>
-<P><LI>The string <B>never</B>, which directs the BOS Server never to perform
-the indicated type of restart.
-<P><LI>The string <B>now</B>, which directs the BOS Server to perform the
-restart immediately and never again.
-<P><LI>A time of day (the conventional type of value for the binary restart
-time). Separate the hours and minutes with a colon
-(<I>hh</I>:<I>MM</I>), and use either 24-hour format, or a value
-in the range from <B>1:00</B> through <B>12:59</B> with
-the addition of <B>am</B> or <B>pm</B>. For example, both
-<B>14:30</B> and <B>"2:30 pm"</B> indicate 2:30 in
-the afternoon. Surround this parameter with double quotes (<B>"
-"</B>) if it contains a space.
-<P><LI>A day of the week and time of day, separated by a space and surrounded
-with double quotes (<B>" "</B>). This is the conventional type of
-value for the general restart. For the day, provide either the whole
-name or the first three letters, all in lowercase letters (<B>sunday</B>
-or <B>sun</B>, <B>thursday</B> or <B>thu</B>, and so on).
-For the time, use the same format as when specifying the time alone.
-</UL>
-<P>If desired, precede a time or day and time definition with the string
-<B>every</B> or <B>at</B>. These words do not change the
-meaning, but possibly make the output of the <B>bos getrestart</B> command
-easier to understand.
-<P><DT><B><B>-general</B>
-</B><DD>Sets the general restart time.
-<P><DT><B><B>-newbinary</B>
-</B><DD>Sets the binary restart time.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command sets the general restart time on the machine
-<B>fs4.abc.com</B> to Saturday at 3:30 am.
-<PRE> % <B>bos setrestart -server fs4.abc.com -time "sat 3:30" -general</B>
-
-</PRE>
-<P>The following command sets the binary restart time on the machine
-<B>fs6.abc.com</B> to 11:45 pm.
-<PRE> % <B>bos setrestart -server fs6.abc.com -time 23:45 -newbinary</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf116.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf118.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf117.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf119.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_SHUTDOWN" HREF="auarf002.htm#ToC_132">bos shutdown</A></H2>
-<A NAME="IDX4636"></A>
-<A NAME="IDX4637"></A>
-<A NAME="IDX4638"></A>
-<A NAME="IDX4639"></A>
-<A NAME="IDX4640"></A>
-<A NAME="IDX4641"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Stops a process without changing its status flag in the
-<B>/usr/afs/local/BosConfig</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos shutdown -server</B> <<VAR>machine name</VAR>> [<B>-instance</B> <<VAR>instances</VAR>><SUP>+</SUP>] [<B>-wait</B>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos sh -s</B> <<VAR>machine name</VAR>> [<B>-i</B> <<VAR>instances</VAR>><SUP>+</SUP>] [<B>-w</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos shutdown</B> command stops, on the server machine named by
-the <B>-server</B> argument, either
-<UL>
-<P><LI>All of the currently running AFS server processes, except the BOS Server
-<P><LI>Only the processes specified by the <B>-instance</B> argument
-</UL>
-<P>This command does not change a process's status flag in the
-<B>/usr/afs/local/BosConfig</B> file, but only in the BOS Server's
-memory. To stop a process and change its <B>BosConfig</B> status
-flag, use the <B>bos stop</B> command instead.
-<P>Once stopped with this command, a process does not run again until an
-administrator starts it by using the <B>bos start</B>, <B>bos
-startup</B>, or <B>bos restart</B> command, or until the BOS Server
-restarts (assuming that the process's <B>BosConfig</B> status flag is
-<TT>Run</TT>).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to stop processes. Identify
-the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to stop. Use the process name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command. The
-output from the <B>bos status</B> command lists the names. Omit
-this argument to stop all processes other than the BOS Server.
-<P><DT><B><B>-wait</B>
-</B><DD>Delays the return of the command shell prompt until all processes actually
-stop. If this argument is omitted, the prompt returns almost
-immediately even if all processes are not stopped.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command stops all processes other than the BOS Server on the
-machine <B>fs3.abc.com</B>.
-<PRE> % <B>bos shutdown fs3.abc.com</B>
-
-</PRE>
-<P>The following command stops the <B>upserver</B> process (server portion
-of the Update Server) on the machine
-<B>fs5.abc.com</B>.
-<PRE> % <B>bos shutdown -server fs5.abc.com -instance upserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf117.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf119.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf118.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf120.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_START" HREF="auarf002.htm#ToC_133">bos start</A></H2>
-<A NAME="IDX4642"></A>
-<A NAME="IDX4643"></A>
-<A NAME="IDX4644"></A>
-<A NAME="IDX4645"></A>
-<A NAME="IDX4646"></A>
-<A NAME="IDX4647"></A>
-<A NAME="IDX4648"></A>
-<A NAME="IDX4649"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Starts a process after setting its status flag in the
-<B>/usr/afs/local/BosConfig</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos start -server</B> <<VAR>machine name</VAR>> <B>-instance</B> <<VAR>server process name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos start -s</B> <<VAR>machine name</VAR>> <B>-i</B> <<VAR>server process name</VAR>><SUP>+</SUP>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos start</B> command sets the status flag for each process
-specified by the <B>-instance</B> argument to <TT>Run</TT> in the
-<B>/usr/afs/local/BosConfig</B> file and in the BOS Server's memory
-on the server machine named by the <B>-server</B> argument, then starts
-it. If the process is already running, the command's only effect
-is to guarantee that the status flag is <TT>Run</TT>; it does not
-restart the process.
-<P>To start a process without changing its status flag in the
-<B>BosConfig</B> file, use the <B>bos startup</B> command
-instead.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to start processes. Identify
-the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to start. Use the process name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command. The
-output from the <B>bos status</B> command lists the names.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command changes the status flag for the
-<B>upclientbin</B> and <B>upclientetc</B> processes to <TT>Run</TT>
-in the <B>BosConfig</B> file on the machine
-<B>fs6.abc.com</B> and starts them running.
-<PRE> % <B>bos start -server fs6.abc.com -instance upclientbin upclientetc</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf118.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf120.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf119.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf121.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_STARTUP" HREF="auarf002.htm#ToC_134">bos startup</A></H2>
-<A NAME="IDX4650"></A>
-<A NAME="IDX4651"></A>
-<A NAME="IDX4652"></A>
-<A NAME="IDX4653"></A>
-<A NAME="IDX4654"></A>
-<A NAME="IDX4655"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Starts a process without changing its status flag in the
-<B>/usr/afs/local/BosConfig</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos startup -server</B> <<VAR>machine name</VAR>> [<B>-instance</B> <<VAR>instances</VAR>><SUP>+</SUP>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos startu -s</B> <<VAR>machine name</VAR>> [<B>-i</B> <<VAR>instances</VAR>><SUP>+</SUP>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos startup</B> command starts, on the server machine named by
-the <B>-server</B> argument, either
-<UL>
-<P><LI>All AFS server processes not currently running but marked with the
-<TT>Run</TT> status flag in the <B>/usr/afs/local/BosConfig</B> file
-<P><LI>Each process specified by <B>-instance</B> argument, even if its
-status flag in the <B>BosConfig</B> file is <TT>NotRun</TT>.
-</UL>
-<P>To start a process and set its <B>BosConfig</B> status flag to
-<TT>Run</TT>, use the <B>bos start</B> command instead.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to start processes. Identify
-the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to start. Use the process name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command. The
-output from the <B>bos status</B> command lists the names.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command starts all processes marked with status flag
-<TT>Run</TT> in the <B>BosConfig</B> file on the machine
-<B>fs3.abc.com</B> that are not currently running.
-<PRE> % <B>bos startup fs3.abc.com</B>
-
-</PRE>
-<P>The following command starts the <B>buserver</B>, <B>kaserver</B>,
-<B>ptserver</B>, and <B>vlserver</B> processes running on the machine
-<B>db2.abc.com</B>, even if their status flags in the
-<B>BosConfig</B> file are <TT>NotRun</TT>.
-<PRE> %<B> bos startup -server db2.abc.com -instance buserver kaserver ptserver vlserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf119.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf121.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf120.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf122.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_STATUS" HREF="auarf002.htm#ToC_135">bos status</A></H2>
-<A NAME="IDX4656"></A>
-<A NAME="IDX4657"></A>
-<A NAME="IDX4658"></A>
-<A NAME="IDX4659"></A>
-<A NAME="IDX4660"></A>
-<A NAME="IDX4661"></A>
-<A NAME="IDX4662"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the status of server processes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos status -server</B> <<VAR>machine name</VAR>> [<B>-instance</B> <<VAR>server process name</VAR>><SUP>+</SUP>]
- [<B>-long</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos stat -s</B> <<VAR>machine name</VAR>> [<B>-i</B> <<VAR>server process name</VAR>><SUP>+</SUP>]
- [<B>-lon</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-loc</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos status</B> command reports the status of processes on the
-server machine named by the <B>-server</B> argument, either
-<UL>
-<P><LI>All of the AFS server processes listed in the
-<B>/usr/afs/local/BosConfig</B> file
-<P><LI>Only these processes named by the <B>-instance</B> argument
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine for which to report server process
-status. Identify the machine by IP address or its host name (either
-fully-qualified or abbreviated unambiguously). For details, see the
-introductory reference page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process for which to report status. Use the process name
-assigned with the <B>-instance</B> argument to the <B>bos</B>
-command. The output from the <B>bos status</B> command lists the
-names.
-<P><DT><B><B>-long</B>
-</B><DD>Produces more detailed status information.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output for a process includes at least one line, which reports one of
-the following as the process's current status:
-<UL>
-<P><LI><TT>currently running normally</TT>. The process's status
-flag in the <B>BosConfig</B> file is <TT>Run</TT>. For
-<B>cron</B> entries, this message indicates only that the command is
-scheduled to run, not necessarily that it was executing when the <B>bos
-status</B> command was issued.
-<P><LI><TT>disabled</TT>. The process is not running, and its
-<B>BosConfig</B> status flag is <TT>NotRun</TT>.
-<P><LI><TT>temporarily disabled</TT>. The process is not running
-although its status flag in the <B>BosConfig</B> file is
-<TT>Run</TT>. Either an administrator used the <B>bos
-shutdown</B> command to stop it, or the
-<P><LI>BOS Server stopped trying to restart it after numerous failed
-attempts. In the second case, the auxiliary message is <TT>stopped for
- too many errors</TT>.
-<P><LI><TT>temporarily enabled</TT>. The process is running although its
-status flag in the <B>BosConfig</B> file is <TT>NotRun</TT>. An
-administrator has used the <B>bos startup</B> command to start it.
-</UL>
-<P>If one of the following special circumstances applies to the process, the
-indicated message appears in its entry:
-<UL>
-<P><LI><TT>has core file</TT>. The process failed and created a core
-file in the <B>/usr/afs/logs</B> directory. If the BOS Server was
-able to restart the process after the failure, the primary status is
-<TT>currently running normally</TT>.
-<P><LI><TT>stopped for too many errors</TT>. The reason for the primary
-status <TT>temporarily disabled</TT> is that the BOS Server's attempts
-to restart the process all failed.
-</UL>
-<P>The entry for the <B>fs</B> process always includes a second line to
-report the process's <TT>Auxiliary status</TT>, which is one of the
-following:
-<UL>
-<P><LI><TT>file server running</TT>. The File Server and Volume Server
-components of the File Server process are running normally.
-<P><LI><TT>salvaging file system</TT>. The Salvager is running, so the
-File Server and Volume Server are temporarily disabled. The BOS Server
-restarts them as soon as the Salvager is finished.
-</UL>
-<P>The entry for a <B>cron</B> process includes an <TT>Auxiliary
-status</TT> that reports when the command will next execute.
-<P>If the <B>-long</B> flag is used, each entry includes the following
-additional information:
-<UL>
-<P><LI>The process's type (<TT>simple</TT>, <TT>fs</TT>, or
-<TT>cron</TT>).
-<P><LI>The day and time the process last started or restarted.
-<P><LI>The number of <TT>proc starts</TT>, which is how many times the BOS
-Server has started or restarted the process since it started itself.
-<P><LI>The <TT>Last exit</TT> time when the process (or one of the component
-processes in the <B>fs</B> process) last terminated. This line does
-not appear if the process has not terminated since the BOS Server
-started.
-<P><LI>The <TT>Last error exit</TT> time when the process (or one of the
-component processes in the <B>fs</B> process) last failed due to an
-error. A further explanation such as <TT>due to shutdown request</TT>
-sometimes appears. This line does not appear if the process has not
-failed since the BOS Server started.
-<P><LI>Each command that the BOS Server invokes to start the process, as
-specified by the <B>-cmd</B> argument to the <B>bos create</B>
-command.
-<P><LI>The pathname of the notifier program that the BOS Server invokes when the
-process terminates (if any), as specified by the <B>-notifier</B> argument
-to the <B>bos create</B> command.
-</UL>
-<P>If the <B>-long</B> flag is provided and the BOS Server discovers that
-the mode bits on files and subdirectories in the local <B>/usr/afs</B>
-directory differ from the expected values, it prints the following warning
-message:
-<PRE> Bosserver reports inappropriate access on server directories
-
-</PRE>
-<P>The following chart summarizes the expected mode bit settings. A
-question mark indicates that the BOS Server does not check that bit.
-<BR>
-<TABLE WIDTH="100%">
-<TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/backup</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/bin</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/db</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc/KeyFile</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>-rw</TT>????<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc/UserList</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>-rw</TT>?????<TT>--</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/local</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/logs</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR></TABLE>
-<P><STRONG>Examples</STRONG>
-<P>The following example command displays the status of processes on the
-machine <B>fs3.abc.com</B>:
-<PRE> %<B> bos status fs3.abc.com</B>
- Instance buserver, currently running normally.
- Instance kaserver, currently running normally.
- Instance ptserver, currently running normally.
- Instance vlserver, currently running normally.
- Instance fs, has core file, currently running normally.
- Auxiliary status is: file server running.
- Instance upserver, currently running normally.
- Instance runntp, currently running normally.
-
-</PRE>
-<P>The following example command displays a detailed status report for the
-<B>fs</B> and <B>ptserver</B> processes on the machine
-<B>fs1.abc.com</B>.
-<PRE> % <B>bos status -server fs1.abc.com -instance fs ptserver -long</B>
- Instance fs, (type is fs), currently running normally.
- Auxiliary status is: file server running.
- Process last started at Wed Jan 7 5:34:49 1998 (3 proc starts)
- Last exit at Wed Jan 7 5:34:49 1998
- Last error exit at Wed Jan 7 5:34:49 1998, due to shutdown
- request
- Command 1 is '/usr/afs/bin/fileserver'
- Command 2 is '/usr/afs/bin/volserver'
- Command 3 is '/usr/afs/bin/salvager'
- Instance ptserver, (type is simple) currently running normally.
- Process last started at Tue Jan 6 8:29:19 1998 (1 proc starts)
- Command 1 is '/usr/afs/bin/ptserver'
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf120.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf122.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf121.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf123.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_STOP" HREF="auarf002.htm#ToC_136">bos stop</A></H2>
-<A NAME="IDX4663"></A>
-<A NAME="IDX4664"></A>
-<A NAME="IDX4665"></A>
-<A NAME="IDX4666"></A>
-<A NAME="IDX4667"></A>
-<A NAME="IDX4668"></A>
-<A NAME="IDX4669"></A>
-<A NAME="IDX4670"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Stops a process after changing its status flag in the
-<B>/usr/afs/local/BosConfig</B> file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos stop -server</B> <<VAR>machine name</VAR>> <B>-instance</B> <<VAR>server process name</VAR>><SUP>+</SUP>
- [<B>-wait</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos sto -s</B> <<VAR>machine name</VAR>> <B>-i</B> <<VAR>server process name</VAR>><SUP>+</SUP>
- [<B>-w</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos stop</B> command sets the status flag for each process
-specified with the <B>-instance</B> argument to <TT>NotRun</TT> in the
-<B>/usr/afs/local/BosConfig</B> file on the server machine named by the
-<B>-server</B> argument, then stops it.
-<P>To stop a process without changing its <B>BosConfig</B> status flag,
-use the <B>bos shutdown</B> command instead.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the server machine on which to stop processes. Identify
-the machine by IP address or its host name (either fully-qualified or
-abbreviated unambiguously). For details, see the introductory reference
-page for the <B>bos</B> command suite.
-<P><DT><B><B>-instance</B>
-</B><DD>Names each process to stop. Use the process name assigned with the
-<B>-instance</B> argument to the <B>bos create</B> command. The
-output from the <B>bos status</B> command lists the names.
-<P><DT><B><B>-wait</B>
-</B><DD>Delays the return of the command shell prompt until all processes actually
-stop. If this argument is omitted, the prompt returns almost
-immediately even if all processes are not stopped.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command stops the <B>upserver</B> and
-<B>runntp</B> on the machine <B>fs7.abc.com</B>.
-<PRE> % <B>bos stop -server fs7.abc.com -instance upserver runntp</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf121.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf123.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf122.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf124.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOS_UNINSTALL" HREF="auarf002.htm#ToC_137">bos uninstall</A></H2>
-<A NAME="IDX4671"></A>
-<A NAME="IDX4672"></A>
-<A NAME="IDX4673"></A>
-<A NAME="IDX4674"></A>
-<A NAME="IDX4675"></A>
-<A NAME="IDX4676"></A>
-<A NAME="IDX4677"></A>
-<A NAME="IDX4678"></A>
-<A NAME="IDX4679"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reverts to the former version of a process's binary file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bos uninstall -server</B> <<VAR>machine name</VAR>> <B>-file</B> <<VAR>files to uninstall</VAR>><SUP>+</SUP>
- [<B>-dir</B> <<VAR>destination dir</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-help</B>]
-
-<B>bos u -s</B> <<VAR>machine name</VAR>> <B>-f</B> <<VAR>files to uninstall</VAR>><SUP>+</SUP> [<B>-d</B> <<VAR>destination dir</VAR>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>bos uninstall</B> command replaces each binary file specified by
-the <B>-file</B> argument with its <TT>.BAK</TT>version on the
-server machine named by the <B>-server</B> argument, which is normally the
-binary distribution machine for its CPU/operating system type. It also
-changes the extension on the current <TT>.OLD</TT> version (if any)
-to <TT>.BAK</TT>. Each binary file must reside in the local
-<B>/usr/afs/bin</B> directory unless the <B>-dir</B> argument names an
-alternate directory.
-<P>To start using the reverted binary immediately, issue the <B>bos
-restart</B> command. Otherwise, the BOS Server automatically restarts
-the process at the time defined in the <B>/usr/afs/local/BosConfig</B>
-file; use the <B>bos getrestart</B> command to display the time and
-the <B>bos setrestart</B> time to set it.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Indicates the binary distribution machine on which to revert to the
-<TT>.BAK</TT> version of binaries. Identify the machine by IP
-address or its host name (either fully-qualified or abbreviated
-unambiguously). For details, see the introductory reference page for
-the <B>bos</B> command suite.
-<P>If the machine is not a binary distribution machine and is running an
-<B>upclientbin</B> process, then the files are overwritten the next time
-the <B>upclientbin</B> process fetches the corresponding file from the
-distribution machine (by default within five minutes).
-<P><DT><B><B>-file</B>
-</B><DD>Names each binary file to replace with its <TT>.BAK</TT>
-version.
-<P><DT><B><B>-dir</B>
-</B><DD>Provides the complete pathname of the local disk directory containing each
-file named by the <B>-file</B> argument. It is necessary only if
-the binaries are not in the <B>/usr/afs/bin</B> directory.
-<P><DT><B><B>-cell</B>
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>bos</B> reference page.
-<P><DT><B><B>-noauth</B>
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>bos</B> reference
-page.
-<P><DT><B><B>-localauth</B>
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>bos</B> command
-interpreter presents the ticket to the BOS Server during mutual
-authentication. Do not combine this flag with the <B>-cell</B> or
-<B>-noauth</B> options. For more details, see the introductory
-<B>bos</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command overwrites the
-<B>/usr/afs/bin/kaserver</B> file on the machine
-<B>fs4.abc.com</B> with its <TT>.BAK</TT>version,
-and the current <TT>.BAK</TT> version by the
-<TT>.OLD</TT>version.
-<PRE> % <B>bos uninstall -server fs4.abc.com -file kaserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine named by the <B>-server</B> argument, or must be logged onto a
-server machine as the local superuser <B>root</B> if the
-<B>-localauth</B> flag is included.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf117.htm#HDRBOS_SETRESTART">bos setrestart</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf122.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf124.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf123.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf125.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBOSSERVER" HREF="auarf002.htm#ToC_138">bosserver</A></H2>
-<A NAME="IDX4680"></A>
-<A NAME="IDX4681"></A>
-<A NAME="IDX4682"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the BOS Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>bosserver</B> [<B>-noauth</B>] [<B>-log</B>] [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>]
- [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>bosserver</B> command initializes the Basic OverSeer (BOS)
-Server (<B>bosserver</B> process). In the conventional
-configuration, the binary file is located in the <B>/usr/afs/bin</B>
-directory on a file server machine.
-<P>The BOS Server must run on every file server machine and helps to automate
-file server administration by performing the following tasks:
-<UL>
-<P><LI>Monitors the other AFS server processes on the local machine, to make sure
-they are running correctly.
-<P><LI>Automatically restarts failed processes, without contacting a human
-operator. When restarting multiple server processes simultaneously, the
-BOS Server takes interdependencies into account and initiates restarts in the
-correct order.
-<A NAME="IDX4683"></A>
-<A NAME="IDX4684"></A>
-<P><LI>Processes commands from the <B>bos</B> suite that administrators issue
-to verify the status of server processes, install and start new processes,
-stop processes either temporarily or permanently, and restart halted
-processes.
-<P><LI>Manages system configuration information: the files that list the
-cell's server encryption keys, database server machines, and users
-privileged to issue commands from the <B>bos</B> and <B>vos</B>
-suites.
-</UL>
-<P>The BOS Server logs a default set of important events in the file
-<B>/usr/afs/logs/BosLog</B>. To record the name of any user who
-performs a privileged <B>bos</B> command (one that requires being listed
-in the <B>/usr/afs/etc/UserList</B> file), add the <B>-log</B>
-flag. To display the contents of the <B>BosLog</B> file, use the
-<B>bos getlog</B> command.
-<P>The first time that the BOS Server initializes on a server machine, it
-creates several files and subdirectories in the local <B>/usr/afs</B>
-directory, and sets their mode bits to protect them from unauthorized
-access. Each time it restarts, it checks that the mode bits still
-comply with the settings listed in the following chart. A question mark
-indicates that the BOS Server initially turns off the bit (sets it to the
-hyphen), but does not check it at restart.
-<BR>
-<TABLE WIDTH="100%">
-<TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/backup</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/bin</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/db</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc/KeyFile</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>-rw</TT>????<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/etc/UserList</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>-rw</TT>?????<TT>--</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/local</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwx</TT>???<TT>---</TT>
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><B>/usr/afs/logs</B>
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%"><TT>drwxr</TT>?<TT>xr-x</TT>
-</TD></TR></TABLE>
-<P>If the mode bits do not comply, the BOS Server writes the following warning
-to the <B>BosLog</B> file:
-<PRE> Bosserver reports inappropriate access on server directories
-
-</PRE>
-<P>However, the BOS Server does not reset the mode bits, so the administrator
-can set them to alternate values if desired (with the understanding that the
-warning message then appears at startup).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the issuer,
-which is useful only when authorization checking is disabled on the server
-machine (for instance, during the installation of a file server
-machine.)
-<P><DT><B>-log
-</B><DD>Records in the <B>/usr/afs/logs/BosLog</B> file the names of all users
-who successfully issue a privileged <B>bos</B> command (one that requires
-being listed in the <B>/usr/afs/etc/UserList</B> file).
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command initializes the BOS Server and logs the names of
-users who issue privileged <B>bos</B> commands.
-<PRE> % <B>bosserver -log &</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer most be logged onto a file server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf015.htm#HDRBOSLOG">BosLog</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf100.htm#HDRBOS_EXEC">bos exec</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf103.htm#HDRBOS_GETRESTART">bos getrestart</A>
-<P><A HREF="auarf113.htm#HDRBOS_RESTART">bos restart</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf119.htm#HDRBOS_START">bos start</A>
-<P><A HREF="auarf120.htm#HDRBOS_STARTUP">bos startup</A>
-<P><A HREF="auarf121.htm#HDRBOS_STATUS">bos status</A>
-<P><A HREF="auarf122.htm#HDRBOS_STOP">bos stop</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf123.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf125.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf124.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf126.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBUSERVER" HREF="auarf002.htm#ToC_139">buserver</A></H2>
-<A NAME="IDX4685"></A>
-<A NAME="IDX4686"></A>
-<A NAME="IDX4687"></A>
-<A NAME="IDX4688"></A>
-<A NAME="IDX4689"></A>
-<A NAME="IDX4690"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Backup Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>buserver</B> [<B>-database</B> <<VAR>database directory</VAR>>]
- [<B>-cellservdb</B> <<VAR>cell configuration directory</VAR>>]
- [<B>-resetdb</B>] [<B>-noauth</B>] [<B>-smallht</B>]
- [<B>-servers</B> <<VAR>list of ubik database servers</VAR>><SUP>+</SUP>]
- [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>]
- [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>buserver</B> command initializes the Backup Server, which runs
-on database server machines and maintains the Backup Database. In the
-conventional configuration, the binary file is located in the
-<B>/usr/afs/bin</B> directory on a file server machine.
-<P>The <B>buserver</B> command is not normally issued at the command shell
-prompt, but rather placed into a database server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a file server machine as the local superuser
-<B>root</B>.
-<P>As it initializes, the Backup Server process creates the two files that
-constitute the Backup Database, <B>bdb.DB0</B> and
-<B>bdb.DBSYS1</B>, in the <B>/usr/afs/db</B> directory if they
-do not already exist. The Backup Database houses information about
-volume sets and entries, the dump hierarchy, Tape Coordinators, and previously
-performed dump sets. Use the commands in the <B>backup</B> suite to
-administer the database.
-<P>The Backup Server records a trace of its activity in the
-<B>/usr/afs/logs/BackupLog</B> file. Use the <B>bos getlog</B>
-command to display the contents of the file.
-<P><STRONG>Cautions</STRONG>
-<P>The <B>buserver</B> process reserves port <B>7021</B> for its
-use. Unexpected behavior can occur if another process tries to reserve
-this port while the <B>buserver</B> process is running.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-database
-</B><DD>Specifies the pathname of an alternate directory for the Backup Database
-files, ending in a final slash (<B>/</B>). If this argument is not
-provided, the default is the <B>/usr/afs/db</B> directory.
-<P><DT><B>-cellservdb
-</B><DD>Specifies the pathname of the directory from which the Backup Server reads
-in an alternate version of the <B>CellServDB</B> file. This
-argument is mandatory for correct functioning when the Backup Server is
-running on a subset of the cell's database server machines that is not a
-majority of the machines listed in the standard
-<B>/usr/afs/etc/CellServDB</B> file (which the Backup Server consults if
-this argument is not provided). It is not appropriate in any other
-circumstances.
-<P><DT><B>-resetdb
-</B><DD>Removes all of the information in the Backup Database files in the
-<B>/usr/afs/db</B> directory, leaving zero-length versions of them.
-The backup operator must recreate the configuration entries in the database
-(for volume sets, the dump hierarchy and so on) before performing backup
-operations.
-<P><DT><B>-noauth
-</B><DD>Establishes an unauthenticated connection between the issuer and the
-Backup Server, in which the Backup Server treats the issuer as the
-unprivileged user <B>anonymous</B>. It is useful only when
-authorization checking is disabled on the database server machine. In
-normal circumstances, the Backup Server allows only authorized (privileged)
-users to issue commands that affect or contact the Backup Database, and
-refuses to perform such an action even if the <B>-noauth</B> flag is
-used.
-<P><DT><B>-smallht
-</B><DD>Directs the Backup Server to use smaller internal hash tables for the
-Backup Database, which reduces memory requirements but can make data access
-take longer.
-<P><DT><B>-servers
-</B><DD>Specifies the database server machines on which to start the Backup
-Server. Use this argument if running the Backup Server on a subset of
-the database server machines that is not a majority of the machines listed in
-the <B>/usr/afs/etc/CellServDB</B> file.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>bos create</B> command creates a
-<B>buserver</B> process on the file server machine
-<B>fs3.abc.com</B>. It appears here on two lines only
-for legibility.
-<PRE> % <B>bos create -server fs3.abc.com -instance buserver</B> \
- <B>-type simple -cmd /usr/afs/bin/buserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf014.htm#HDRBACKUPLOG">BackupLog</A>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf042.htm#HDRBDBDB">bdb.DB0 and bdb.DBSYS1</A>
-<P><A HREF="auarf060.htm#HDRBK_INTRO">backup</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf124.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf126.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf125.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf127.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRBUTC" HREF="auarf002.htm#ToC_140">butc</A></H2>
-<A NAME="IDX4691"></A>
-<A NAME="IDX4692"></A>
-<A NAME="IDX4693"></A>
-<A NAME="IDX4694"></A>
-<A NAME="IDX4695"></A>
-<A NAME="IDX4696"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Tape Coordinator process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>butc</B> [<B>-port</B> <<VAR>port offset</VAR>>] [<B>-debuglevel</B> < <B>0</B> | <B>1</B> | <B>2</B> >]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noautoquery</B>]
- [<B>-localauth</B>] [<B>-help</B>]
-
-<B>butc</B> [<B>-p</B> <<VAR>port offset</VAR>>] [<B>-d</B> < <B>0</B> | <B>1</B> | <B>2</B> >]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>butc</B> command initializes a Tape Coordinator process on a
-Tape Coordinator machine, enabling an operator to direct Backup System
-requests to the associated tape device or backup data file. (The Tape
-Coordinator controls a backup data file if the <B>FILE YES</B> instruction
-appears in the <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file that
-corresponds to the Tape Coordinator's entry in the
-<B>/usr/afs/backup/tapeconfig</B> file. For the sake of simplicity,
-the following discusses tape devices only.)
-<P>It is conventional to start and run the Tape Coordinator in the
-foreground. In this case, it runs on its own connection, which is
-unavailable for any other use and must remain open the entire time the Tape
-Coordinator is to accept backup requests and while it is executing
-them. (When using a window manager, the connection corresponds to a
-separate command shell window.) The Tape Coordinator can run in the
-background if the <B>CFG_</B><VAR>device_name</VAR> file is configured to
-eliminate any need for the Tape Coordinator to prompt the operator. In
-both the foreground and background, the Tape Coordinator writes operation
-traces and other output to the standard output stream on the connection over
-which it was started. Use the <B>-debuglevel</B> argument to
-control the amount of information that appears. The Tape Coordinator
-also writes traces and error messages to two files in the local
-<B>/usr/afs/backup</B> directory:
-<UL>
-<P><LI>The <B>TE_</B><VAR>device_name</VAR> file records problems that the Tape
-Coordinator encounters as it executes backup operations.
-<P><LI>The <B>TL_</B><VAR>device_name</VAR> file records a trace of operations
-as well as the same errors written to the <B>TE_</B><VAR>device_name</VAR>
-file.
-</UL>
-<P>The Tape Coordinator creates the files automatically as it
-initializes. If there are existing files, the Tape Coordinator renames
-them with a <B>.old</B> extension, overwriting the existing
-<B>.old</B> files if they exist. It derives the
-<VAR>device_name</VAR> part of the file names by stripping off the device
-name's <B>/dev/</B> prefix and replacing any other slashes with
-underscores. For example, the files are called <B>TE_rmt_4m</B> and
-<B>TL_rmt_4m</B> for a device called <B>/dev/rmt/4m</B>.
-<P>By default, at the beginning of each operation the Tape Coordinator prompts
-for the operator to insert the first tape into the drive and press
-<<B>Return</B>>. To suppress this prompt, include the
-<B>-noautoquery</B> flag on the command line or the instruction
-<B>AUTOQUERY NO</B> in the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file. When the
-prompt is suppressed, the first required tape must be in the drive before a
-<B>backup</B> command is issued. For subsequent tapes, the Tape
-Coordinator uses its normal tape acquisition routine: if the
-<B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file includes a
-<B>MOUNT</B> instruction, the Tape Coordinator invokes the indicated
-command; otherwise, it prompts the operator for the next tape.
-<P>To stop the Tape Coordinator process, enter an interrupt signal such as
-<<B>Ctrl-c</B>> over the dedicated connection (in the command shell
-window).
-<P>To cancel a <B>backup</B> operation that involves a tape before it
-begins (assuming the initial tape prompt has not been suppressed), enter the
-letter <B>a</B> (for <B>abort</B>) and press <<B>Return</B>> at
-the Tape Coordinator's prompt for the first tape.
-<P>Tape Coordinator operation depends on the correct configuration of certain
-files, as described in the following list:
-<UL>
-<P><LI>The local <B>/usr/afs/backup/tapeconfig</B> file must include an entry
-for the Tape Coordinator that specifies its device name and port offset
-number, among other information; for details, see the
-<B>tapeconfig</B> reference page.
-<P><LI>The port offset number recorded in the Tape Coordinator's entry in
-the Backup Database must match the one in the <B>tapeconfig</B>
-file. Create the Backup Database entry by using the <B>backup
-addhost</B> command.
-<P><LI>The optional <B>/usr/afs/backup/CFG_</B><VAR>device_name</VAR> file can
-contain instructions for mounting and unmounting tapes automatically (when
-using a tape stacker or jukebox, for instance) or automating other aspects of
-the backup process. The <VAR>device_name</VAR> part of the name is
-derived as described previously for the <B>TE_</B><VAR>device_name</VAR> and
-<B>TL_</B><VAR>device_name</VAR> files.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>If the Tape Coordinator machine is an AIX machine, use the <B>SMIT</B>
-utility to set the device's block size to 0 (zero), indicating variable
-block size. Otherwise, tape devices attached to machines running other
-operating systems sometimes cannot read tapes written on AIX machines.
-For instructions, see the <I>IBM AFS Administration Guide</I> chapter
-about configuring the Backup System.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-port
-</B><DD>Specifies the port offset number of the Tape Coordinator to
-initialize.
-<P><DT><B>-debuglevel
-</B><DD>Controls the amount and type of messages the Tape Coordinator displays on
-the standard output stream. Provide one of three acceptable
-values:
-<UL>
-<P><LI><B>0</B> to display the minimum level of detail required to describe
-Tape Coordinator operations, including prompts for tapes, messages that
-indicate the beginning and end of operations, and error messages. This
-is the default value.
-<P><LI><B>1</B> to display the names of the volumes being dumped or restored
-as well as the information displayed at level 0.
-<P><LI><B>2</B> to display all messages also being written to the
-<B>TL_</B><VAR>device_name</VAR> log file.
-</UL>
-<P><DT><B>-cell
-</B><DD>Names the cell in which the Tape Coordinator operates (the cell to which
-the file server machines that house affected volumes belong). If this
-argument is omitted, the Tape Coordinator runs in the local cell as defined in
-the local <B>/usr/vice/etc/ThisCell</B> file. Do not combine this
-flag with the <B>-localauth</B> argument.
-<P><DT><B>-noautoquery
-</B><DD>Suppresses the Tape Coordinator's prompt for insertion of the first
-tape needed for an operation. The operator must insert the tape into
-the drive before issuing the <B>backup</B> command that initializes the
-operation.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using the server encryption key with the
-highest key version number in the local
-<B>/usr/afs/etc/KeyFile</B>. The <B>butc</B> command
-interpreter presents the ticket, which never expires, to the Volume Server and
-Volume Location Server to use in mutual authentication.
-<P>Do not combine this argument with the <B>-cell</B> flag, and use it
-only when logged on to a server machine as the local superuser
-<B>root</B>; client machines do not have
-<B>/usr/afs/etc/KeyFile</B> file.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command starts the Tape Coordinator with port offset
-<B>7</B> at debug level <B>1</B>, meaning the Tape Coordinator reports
-the names of volumes it is dumping or restoring.
-<PRE> % <B>butc -port 7 -debuglevel 1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-every machine where the Backup Server or Volume Location (VL) Server is
-running, and on every file server machine that houses a volume to be backed
-up. If the <B>-localauth</B> flag is included, the issuer must
-instead be logged on to the Tape Coordinator machine as the local superuser
-<B>root.</B> In addition, the issuer must be able to read and write
-to the log and configuration files in the local <B>/usr/afs/backup</B>
-directory.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf018.htm#HDRCFG">CFG_<I>device_name</I></A>
-<P><A HREF="auarf023.htm#HDRKEYFILE">KeyFile</A>
-<P><A HREF="auarf031.htm#HDRTE">TE_<I>device_name</I></A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf034.htm#HDRTL">TL_<I>device_name</I></A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P><A HREF="auarf062.htm#HDRBK_ADDHOST">backup addhost</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf125.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf127.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf126.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf128.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRDLOG" HREF="auarf002.htm#ToC_141">dlog</A></H2>
-<A NAME="IDX4697"></A>
-<A NAME="IDX4698"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Authenticates to the DCE Security Service
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>dlog</B> [<B>-principal</B> <<VAR>user name</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-password</B> <<VAR>user's password</VAR>>] [<B>-servers</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>]
- [<B>-lifetime</B> <<VAR>ticket lifetime in hh[:mm[:ss]]</VAR>>]
- [<B>-setpag</B>] [<B>-pipe</B>] [<B>-help</B>]
-
-<B>dlog</B> [<B>-pr</B> <<VAR>user name</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-pw</B> <<VAR>user's password</VAR>>]
- [<B>-ser</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>]
- [<B>-l</B> <<VAR>ticket lifetime in hh[:mm[:ss]]</VAR>>] [<B>-set</B>] [<B>-pi</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>dlog</B> command obtains DCE credentials for the issuer from the
-DCE Security Service in the cell named by the <B>-cell</B> argument, and
-stores them on the AFS client machine on which the user issues the
-command. The AFS/DFS Migration Toolkit Protocol Translator processes
-running on machines in the DCE cell accept the credentials, which enables the
-user to access the DCE cell's filespace from the AFS client. The
-user's identity in the local file system is unchanged.
-<P>If the issuer does not provide the <B>-principal</B> argument, the
-<B>dlog</B> command interpreter uses the user name under which the issuer
-is logged into the local file system. Provide the DCE password for the
-appropriate user name. As with the <B>klog</B> command, the
-password does not cross the network in clear text (unless the issuer is logged
-into the AFS client from a remote machine).
-<P>The credentials are valid for a lifetime equivalent to the smallest of the
-following, all but the last of which is defined by the DCE cell's
-Security Server:
-<UL>
-<P><LI>The maximum certificate lifetime for the issuer's DCE account
-<P><LI>The maximum certificate lifetime for the <B>afs</B> principal's
-DCE account
-<P><LI>The registry-wide maximum certificate lifetime
-<P><LI>The registry-wide default certificate lifetime
-<P><LI>The lifetime requested using the <B>-lifetime</B> argument
-</UL>
-<P>If the previous maximum certificate lifetime values are set to
-<B>default-policy</B>, the maximum possible ticket lifetime is defined by
-the default certificate lifetime. Refer to the DCE vendor's
-administration guide for more information before setting any of these
-values.
-<P>The AFS Cache Manager stores the ticket in a credential structure
-associated with the name of the issuer (or the user named by the
-<B>-principal</B> argument. If the user already has a ticket for
-the DCE cell, the ticket resulting from this command replaces it in the
-credential structure.
-<P>The AFS <B>tokens</B> command displays the ticket obtained by the
-<B>dlog</B> command for the server principal <B>afs</B>, regardless of
-the principal to which it is actually granted. Note that the
-<B>tokens</B> command does not distinguish tickets for a DFS<SUP>TM</SUP>
-File Server from tickets for an AFS File Server.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-principal
-</B><DD>Specifies the DCE user name for which to obtain DCE credentials. If
-this option is omitted, the <B>dlog</B> command interpreter uses the name
-under which the issuer is logged into the local file system.
-<P><DT><B>-cell
-</B><DD>Specifies the DCE cell in which to authenticate. During a single
-login session on a given machine, a user can authenticate in multiple cells
-simultaneously, but can have only one ticket at a time for each cell (that is,
-it is possible to authenticate under only one identity per cell per
-machine). It is legal to abbreviate the cell name to the shortest form
-that distinguishes it from the other cells listed in the
-<B>/usr/vice/etc/CellServDB</B> file on the local client machine.
-<P>If the issuer does not provide the <B>-cell</B> argument, the
-<B>dlog</B> command attempts to authenticate with the DCE Security Server
-for the cell defined by
-<OL TYPE=1>
-<P><LI>The value of the environment variable AFSCELL on the local AFS client
-machine, if defined. The issuer can set the AFSCELL environment
-variable to name the desired DCE cell.
-<P><LI>The cell name in the <B>/usr/vice/etc/ThisCell</B> file on the local
-AFS client machine. The machine's administrator can place the
-desired DCE cell's name in the file.
-</OL>
-<P><DT><B>-password
-</B><DD>Specifies the password for the issuer (or for the user named by the
-<B>-principal</B> argument). Using this argument is not
-recommended, because it makes the password visible on the command line.
-If this argument is omitted, the command prompts for the password and does not
-echo it visibly.
-<P><DT><B>-servers
-</B><DD>Specifies a list of DFS database server machines running the Translator
-Server through which the AFS client machine can attempt to
-authenticate. Specify each server by hostname, shortened machine name,
-or IP address. If this argument is omitted, the <B>dlog</B> command
-interpreter randomly selects a machine from the list of DFS Fileset Location
-(FL) Servers in the <B>/usr/vice/etc/CellServDB</B> file for the DCE cell
-specified by the <B>-cell</B> argument. This argument is useful for
-testing when authentication seems to be failing on certain server
-machines.
-<P><DT><B>-lifetime
-</B><DD>Requests a ticket lifetime using the format
-<VAR>hh</VAR><B>:</B><VAR>mm</VAR>[<B>:</B><VAR>ss</VAR>]
-(hours, minutes, and optionally a number seconds between 00 and 59).
-For example, the value <B>168:30</B> requests a ticket lifetime of 7
-days and 30 minutes, and <B>96:00</B> requests a lifetime of 4
-days. Acceptable values range from <B>00:05</B> (5 minutes)
-to <B>720:00</B> (30 days). If this argument is not provided
-and no other determinants of ticket lifetime have been changed from their
-defaults, ticket lifetime is 10 hours.
-<P>The requested lifetime must be smaller than any of the DCE cell's
-determinants for ticket lifetime; see the discussion in the preceding
-<B>Description</B> section.
-<P><DT><B>-setpag
-</B><DD>Creates a process authentication group (PAG) in which the newly created
-ticket is placed. If this flag is omitted, the ticket is instead
-associated with the issuers' local user ID (UID).
-<P><DT><B>-pipe
-</B><DD>Suppresses any prompts that the command interpreter otherwise produces,
-including the prompt for the issuer's password. Instead, the
-command interpreter accepts the password via the standard input stream.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the <B>dlog</B> command interpreter cannot contact a Translator
-Server, it produces a message similar to the following:
-<PRE> dlog: server or network not responding -- failed to contact
- authentication service
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command authenticates the issuer as <B>cell_admin</B> in
-the <B>dce.abc.com</B> cell.
-<PRE> % <B>dlog -principal cell_admin -cell dce.abc.com</B>
- Password: <VAR>cell_admin's password</VAR>
-
-</PRE>
-<P>In the following example, the issuer authenticates as <B>cell_admin</B>
-to the <B>dce.abc.com</B> cell and request a ticket lifetime
-of 100 hours. The <B>tokens</B> command confirms that the user
-obtained DCE credentials as the user <B>cell_admin</B>: the AFS ID
-is equivalent to the UNIX ID of <B>1</B> assigned to <B>cell_admin</B>
-in <B>dce.abc.com</B> cell's DCE registry.
-<PRE> % <B>dlog -principal cell_admin -cell dce.abc.com -lifetime 100</B>
- Password: <VAR>cell_admin's password</VAR>
-
- % <B>tokens</B>
- Tokens held by the Cache Manager:
-
- User's (AFS ID 1) tokens for afs@dce.abc.com [Expires Jul 6 14:12]
- User's (AFS ID 4758) tokens for afs@abc.com [Expires Jul 2 13:14]
-
- --End of list--
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf128.htm#HDRDPASS">dpass</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P><A HREF="auarf238.htm#HDRUNLOG">unlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf126.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf128.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf127.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf129.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRDPASS" HREF="auarf002.htm#ToC_142">dpass</A></H2>
-<A NAME="IDX4699"></A>
-<A NAME="IDX4700"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Returns the DCE password for a new DCE account
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>dpass</B> [<B>-cell</B> <<VAR>original AFS cell name</VAR>>] [<B>-help</B>]
-
-<B>dpass</B> [<B>-c</B> <<VAR>original AFS cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>dpass</B> command returns the DCE password that an administrator
-assigned to the issuer when using the <B>dm pass</B> command to migrate
-AFS user accounts into a DCE cell.
-<P>The <B>dpass</B> command, issued on an AFS client, requests the
-issuer's new DCE password from the AFS cell specified with the
-<B>-cell</B> argument.
-<P>The issuer must be authenticated as the AFS user whose AFS account was
-moved into DCE, and be able to provide the user's AFS password when
-prompted by the <B>dpass</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Specifies the name of the AFS cell from which the AFS account was moved
-into DCE and from which to fetch the new DCE password.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>By default, the <B>dpass</B> command writes a message similar to the
-following to the standard output stream.
-<PRE> Please read the following message before entering your password.
-
- This program will display your new, temporary DCE password on your
- terminal, and you should change the assigned password as soon as
- possible (from a DCE client). The program assumes that the AFS cell
- uses the AFS Authentication Server and that an administrator used the
- utilities in the AFS/DFS Migration Toolkit to migrate the account from
- AFS to DCE. The password you enter should be the AFS password that was
- in effect when your DCE account was created; this is not necessarily
- the same password you have at the moment. The cell name (which you
- may override with a command line option), must be the name of the AFS
- cell from which the authentication information was taken.
-
-</PRE>
-<P>To suppress this message, set the DPASS_NO_MESSAGE environment
-variable. It is then possible to substitute a customized message if
-desired by using a script similar to the following example:
-<PRE> #! /bin/csh
- echo "<VAR>Start of customized message</VAR>"
- echo "<VAR>Continuation of customized message</VAR>"
- .
- .
- .
- echo "<VAR>Conclusion of customized message</VAR>"
- setenv DPASS_NO_MESSAGE
- dpass $*
-
-</PRE>
-<P>After the standard or customized message, if any, the <B>dpass</B>
-command generates the following prompt for the original AFS password:
-<PRE> Original password for AFS cell <VAR>cell</VAR>:
- Re-enter password to verify:
-
-</PRE>
-<P>If the AFS passwords match and are correct, the command reports the
-temporary DCE password in the following message.
-<PRE> The new DCE password is: <VAR>Issuer's_temporary_DCE_password</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example returns the DCE password of the issuer, whose AFS
-account is in the <B>abc.com</B> cell. The DPASS_NO_MESSAGE
-variable has been set to suppress the standard message.
-<PRE> % <B>dpass</B>
- Original password for AFS cell abc.com: <VAR>Issuer's_AFS_password</VAR>
- Re-enter password to verify: <VAR>Issuer's_AFS_password</VAR>
- The new DCE password is: 8655--eg8e-dcdc-8157
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be authenticated as the AFS user for whom to display the
-corresponding DCE password.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf127.htm#HDRDLOG">dlog</A>
-<P><B>dm pass</B> reference page in <I>IBM AFS/DFS Migration Toolkit
-Administration Guide and Reference</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf127.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf129.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf128.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf130.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFILESERVER" HREF="auarf002.htm#ToC_143">fileserver</A></H2>
-<A NAME="IDX4701"></A>
-<A NAME="IDX4702"></A>
-<A NAME="IDX4703"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the File Server component of the <B>fs</B> process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fileserver</B> [<B>-d</B> <<VAR>debug level</VAR>>] [<B>-p</B> <<VAR>number of processes</VAR>>]
- [<B>-spare</B> <<VAR>number of spare blocks</VAR>>]
- [<B>-pctspare</B> <<VAR>percentage spare</VAR>>] [<B>-b</B> <<VAR>buffers</VAR>>]
- [<B>-l</B> <<VAR>large vnodes</VAR>>] [<B>-s</B> <<VAR>small nodes</VAR>>]
- [<B>-vc</B> <<VAR>volume cachesize</VAR>>] [<B>-w</B> <<VAR>call back wait interval</VAR>>]
- [<B>-cb</B> <<VAR>number of call backs</VAR>>]
- [<B>-banner</B> (print banner every 10 minutes)]
- [<B>-novbc</B> (whole volume cbs disabled)]
- [<B>-implicit</B> <<VAR>admin mode bits: rlidwka</VAR>>]
- [<B>-hr</B> <<VAR>number of hours between refreshing the host cps</VAR>>]
- [<B>-busyat</B> <<VAR>redirect clients when queue > n</VAR>>]
- [<B>-rxpck</B> <<VAR>number of rx extra packets</VAR>>]
- [<B>-rxdbg</B> (enable rx debugging)]
- [<B>-rxdbge</B> (enable rxevent debugging)]
- [<B>-m</B> <<VAR>min percentage spare in partition</VAR>>]
- [<B>-lock</B> (keep fileserver from swapping)]
- [<B>-L</B> (large server conf)] [<B>-S</B> (small server conf)]
- [<B>-k</B> <<VAR>stack size</VAR>>] [<B>-realm</B> <<VAR>Kerberos realm name</VAR>>]
- [<B>-udpsize</B> <<VAR>size of socket buffer in bytes</VAR>>]
- [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>]
- [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>fileserver</B> command initializes the File Server component of
-the <B>fs</B> process. In the conventional configuration, its
-binary file is located in the <B>/usr/afs/bin</B> directory on a file
-server machine.
-<P>The <B>fileserver</B> command is not normally issued at the command
-shell prompt, but rather placed into a database server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a file server machine as the local superuser
-<B>root</B>.
-<P>The File Server creates the <B>/usr/afs/logs/FileLog</B> log file as it
-initializes, if the file does not already exist. It does not write a
-detailed trace by default, but use the <B>-d</B> option to increase the
-amount of detail. Use the <B>bos getlog</B> command to display the
-contents of the log file.
-<P>The command's arguments enable the administrator to control many
-aspects of the File Server's performance, as detailed in the
-<B>Options</B> section. By default the <B>fileserver</B>
-command sets values for many arguments that are suitable for a medium-sized
-file server machine. To set values suitable for a small or large file
-server machine, use the <B>-S</B> or <B>-L</B> flag
-respectively. The following list describes the parameters and
-corresponding argument for which the <B>fileserver</B> command sets
-default values, and <A HREF="#TBLFILESERVER-ARGS">Table 1</A> summarizes the setting for each of the three machine
-sizes.
-<UL>
-<P><LI>The maximum number of lightweight processes (LWPs) the File Server uses to
-handle requests for data; corresponds to the <B>-p</B>
-argument. The File Server always uses a minimum of 32 KB for these
-processes.
-<P><LI>The maximum number of directory blocks the File Server caches in
-memory; corresponds to the <B>-b</B> argument. Each cached
-directory block (buffer) consumes 2,092 bytes of memory.
-<P><LI>The maximum number of large vnodes the File Server caches in memory for
-tracking directory elements; corresponds to the <B>-l</B>
-argument. Each large vnode consumes 292 bytes of memory.
-<P><LI>The maximum number of small vnodes the File Server caches in memory for
-tracking file elements; corresponds to the <B>-s</B> argument.
-Each small vnode consumes 100 bytes of memory.
-<P><LI>The maximum volume cache size, which determines how many volumes the File
-Server can cache in memory before having to retrieve data from disk;
-corresponds to the <B>-vc</B> argument.
-<P><LI>The maximum number of callback structures the File Server caches in
-memory; corresponds to the <B>-cb</B> argument. Each callback
-structure consumes 16 bytes of memory.
-<P><LI>The maximum number of <B>Rx</B> packets the File Server uses;
-corresponds to the <B>-rxpck</B> argument. Each packet consumes
-1544 bytes of memory.
-</UL>
-<BR>
-<P><B><A NAME="TBLFILESERVER-ARGS" HREF="auarf003.htm#FT_TBLFILESERVER-ARGS">Table 1. File Server configuration parameters</A></B><BR>
-<TABLE WIDTH="100%" BORDER>
-<TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Parameter (Argument)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">Small configuration (<B>-S</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">Medium configuration (default)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">Large configuration (<B>-L</B>)
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of LWPs (<B>-p</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">6
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">9
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">12
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of cached directory blocks (<B>-b</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">70
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">90
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">120
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of cached large vnodes (<B>-l</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">200
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">400
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">600
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of cached small vnodes (<B>-s</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">200
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">400
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">600
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Maximum volume cache size (<B>-vc</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">200
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">400
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">600
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of callbacks (<B>-cb</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">20,000
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">60,000
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">64,000
-</TD></TR><TR>
-<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="40%">Number of <B>Rx</B> packets (<B>-rxpck</B>)
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="20%">100
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="19%">150
-</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="21%">200
-</TD></TR></TABLE>
-<P>To override any of the values, provide the indicated argument (which can be
-combined with the <B>-S</B> or <B>-L</B> flag).
-<P>The amount of memory required for the File Server varies. The
-approximate default memory usage is 751 KB when the <B>-S</B> flag is used
-(small configuration), 1.1 MB when all defaults are used (medium
-configuration), and 1.4 MB when the <B>-L</B> flag is used (large
-configuration). If additional memory is available, increasing the value
-of the <B>-cb</B> and <B>-vc</B> arguments can improve File Server
-performance most directly.
-<P>By default, the File Server allows a volume to exceed its quota by 1 MB
-when an application is writing data to an existing file in a volume that is
-full. The File Server still does not allow users to create new files in
-a full volume. To change the default, use one of the following
-arguments:
-<A NAME="IDX4704"></A>
-<UL>
-<P><LI>Set the <B>-spare</B> argument to the number of extra kilobytes that
-the File Server allows as overage. A value of <B>0</B> allows no
-overage.
-<P><LI>Set the <B>-pctspare</B> argument to the percentage of the
-volume's quota the File Server allows as overage.
-</UL>
-<P>By default, the File Server implicitly grants the <B>a</B>
-(<B>administer</B>) and <B>l</B> (<B>lookup</B>) permissions to
-the <B>system:administrators</B> on the access control list (ACL) of
-every directory in the volumes stored on its file server machine. In
-other words, the group's members can exercise those two permissions even
-when an entry for the group does not appear on an ACL. To change the
-set of default permissions, use the <B>-implicit</B> argument.
-<P>The File Server maintains a <I>host current protection subgroup</I>
-(<I>host CPS</I>) for each client machine from which it has received a
-data access request. Like the CPS for a user, a host CPS lists all of
-the Protection Database groups to which the machine belongs, and the File
-Server compares the host CPS to a directory's ACL to determine in what
-manner users on the machine are authorized to access the directory's
-contents. When the <B>pts adduser</B> or <B>pts removeuser</B>
-command is used to change the groups to which a machine belongs, the File
-Server must recompute the machine's host CPS in order to notice the
-change. By default, the File Server contacts the Protection Server
-every two hours to recompute host CPSs, implying that it can take that long
-for changed group memberships to become effective. To change this
-frequency, use the <B>-hr</B> argument.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">The AIX operating system does not automatically reserve a part of each
-partition to avoid the negative consequences that can result when the space on
-a partition is completely exhausted. Therefore, the AIX version of the
-File Server creates an 8% disk reserve automatically. To change the
-percentage, use the <B>-m</B> argument.
-</TD></TR></TABLE>
-<P>The File Server generates the following message when a partition is nearly
-full:
-<PRE> No space left on device
-
-</PRE>
-<P><STRONG>Cautions</STRONG>
-<P>Do not use the <B>-k</B> and <B>-w</B> arguments, which are
-intended for use by the AFS Development group only. Changing them from
-their default values can result in unpredictable File Server behavior.
-In any case, on many operating systems the File Server uses native threads
-rather than the LWP threads, so using the <B>-k</B> argument to set the
-number of LWP threads has no effect.
-<P>Do not specify both the <B>-spare</B> and <B>-pctspare</B>
-arguments. Doing so causes the File Server to exit, leaving an error
-message in the <B>/usr/afs/logs/FileLog</B> file.
-<P>Options that are available only on some system types, such as the
-<B>-m</B> and <B>-lock</B> options, appear in the output generated by
-the <B>-help</B> option only on the relevant system type.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-d
-</B><DD>Sets the detail level for the debugging trace written to the
-<B>/usr/afs/logs/FileLog</B> file. Provide one of the following
-values, each of which produces an increasingly detailed trace:
-<B>0</B>, <B>1</B>, <B>5</B>, <B>25</B>, and
-<B>125</B>. The default value of <B>0</B> produces only a few
-messages.
-<P><DT><B>-p
-</B><DD>Sets the number of threads to run. Provide a positive
-integer. The File Server creates and uses five threads for special
-purposes, in addition to the number specified (but if this argument specifies
-the maximum possible number, the File Server automatically uses five of the
-threads for its own purposes).
-<P>The maximum number of threads can differ in each release of AFS.
-Consult the <I>IBM AFS Release Notes</I> for the current release.
-<P><DT><B>-spare
-</B><DD>Specifies the number of additional kilobytes an application can store in a
-volume after the quota is exceeded. Provide a positive integer; a
-value of <B>0</B> prevents the volume from ever exceeding its
-quota. Do not combine this argument with the <B>-pctspare</B>
-argument.
-<P><DT><B>-pctspare
-</B><DD>Specifies the amount by which the File Server allows a volume to exceed
-its quota, as a percentage of the quota. Provide an integer between
-<B>0</B> and <B>99</B>. A value of <B>0</B> prevents the
-volume from ever exceeding its quota. Do not combine this argument with
-the <B>-spare</B> argument.
-<P><DT><B>-b
-</B><DD>Sets the number of directory buffers. Provide a positive
-integer.
-<P><DT><B>-l
-</B><DD>Sets the number of large vnodes available in memory for caching directory
-elements. Provide a positive integer.
-<P><DT><B>-s
-</B><DD>Sets the number of small vnodes available in memory for caching file
-elements. Provide a positive integer.
-<P><DT><B>-vc
-</B><DD>Sets the number of volumes the File Server can cache in memory.
-Provide a positive integer.
-<P><DT><B>-w
-</B><DD>Sets the interval at which the daemon spawned by the File Server performs
-its maintenance tasks. Do not use this argument; changing the
-default value can cause unpredictable behavior.
-<P><DT><B>-cb
-</B><DD>Sets the number of callbacks the File Server can track. Provide a
-positive integer.
-<P><DT><B>-banner
-</B><DD>Prints the following banner to <B>/dev/console</B> about every 10
-minutes.
-<PRE> File Server is running at <VAR>time</VAR>.
-
-</PRE>
-<P><DT><B>-novbc
-</B><DD>Prevents the File Server from breaking the callbacks that Cache Managers
-hold on a volume that the File Server is reattaching after the volume was
-offline (as a result of the <B>vos restore</B> command, for
-example). Use of this flag is strongly discouraged.
-<P><DT><B>-implicit
-</B><DD>Defines the set of permissions granted by default to the
-<B>system:administrators</B> group on the ACL of every directory in
-a volume stored on the file server machine. Provide one or more of the
-standard permission letters (<B>rlidwka</B>) and auxiliary permission
-letters (<B>ABCDEFGH</B>), or one of the shorthand notations for groups of
-permissions (<B>all</B>, <B>none</B>, <B>read</B>, and
-<B>write</B>). To review the meaning of the permissions, see the
-<B>fs setacl</B> reference page.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">The File Server always implicitly grants the <B>a</B> permission to the
-<B>system:administrators</B> group, even if you use the
-<B>none</B> value.
-</TD></TR></TABLE>
-<P><DT><B><B>-hr</B>
-</B><DD>Specifies how often the File Server refreshes its knowledge of the
-machines that belong to protection groups (refreshes the host CPSs for
-machines). The File Server must update this information to enable users
-from machines recently added to protection groups to access data for which
-those machines now have the necessary ACL permissions.
-<P><DT><B>-busyat
-</B><DD>Defines the number of incoming RPCs that can be waiting for a response
-from the File Server before the File Server returns the error code
-<B>VBUSY</B> to the Cache Manager that sent the latest RPC. In
-response, the Cache Manager retransmits the RPC after a delay. This
-argument prevents the accumulation of so many waiting RPCs that the File
-Server can never process them all. Provide a positive integer.
-The default value is 600.
-<P><DT><B>-rxpck
-</B><DD>Controls the number of Rx packets the File Server uses to store data for
-incoming RPCs that it is currently handling, that are waiting for a response,
-and for replies that are not yet complete. Provide a positive
-integer.
-<P><DT><B>-rxdbg
-</B><DD>Writes a trace of the File Server's operations on Rx packets to the
-file <B>/usr/afs/logs/rx_dbg</B>.
-<P><DT><B>-rxdbge
-</B><DD>Writes a trace of the File Server's operations on Rx events (such as
-retransmissions) to the file <B>/usr/afs/logs/rx_dbg</B>.
-<P><DT><B>-m
-</B><DD>Specifies the percentage of each AFS server partition that the AIX version
-of the File Server creates as a reserve. Specify an integer value
-between <B>0</B> and <B>30</B>; the default is 8%. A value
-of <B>0</B> means that the partition can become completely full, which can
-have serious negative consequences.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">This argument is available only on machines running the AIX operating system,
-and so does not appear in the syntax statement when the <B>-help</B> flag
-is used on other system types.
-</TD></TR></TABLE>
-<P><DT><B>-lock
-</B><DD>Prevents any portion of the <B>fileserver</B> binary from being paged
-(swapped) out of memory on a file server machine running the IRIX operating
-system.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">This argument is available only on machines running the IRIX operating
-system, and so does not appear in the syntax statement when the
-<B>-help</B> flag is used on other system types.
-</TD></TR></TABLE>
-<P><DT><B><B>-L</B>
-</B><DD>Sets values for many arguments in a manner suitable for a large file
-server machine. Combine this flag with any option except the
-<B>-S</B> flag; omit both flags to set values suitable for a
-medium-sized file server machine.
-<P><DT><B><B>-S</B>
-</B><DD>Sets values for many arguments in a manner suitable for a small file
-server machine. Combine this flag with any option except the
-<B>-L</B> flag; omit both flags to set values suitable for a
-medium-sized file server machine.
-<P><DT><B>-k
-</B><DD>Sets the LWP stack size in units of 1 kilobyte. Do not use this
-argument, and in particular do not specify a value less than the default of
-24.
-<P><DT><B>-realm
-</B><DD>Defines the Kerberos realm name for the File Server to use. If this
-argument is not provided, it uses the realm name corresponding to the cell
-listed in the local <B>/usr/afs/etc/ThisCell</B> file.
-<P><DT><B>-udpsize
-</B><DD>Sets the size of the UDP buffer, which is 64 KB by default. Provide
-a positive integer, preferably larger than the default.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates an <B>fs</B>
-process on the file server machine <B>fs2.abc.com</B> that
-uses the large configuration size, and allows volumes to exceed their quota by
-10%. Type the command on a single line:
-<PRE> % <B>bos create -server fs2.abc.com -instance fs -type fs</B> \
- <B>-cmd "/usr/afs/bin/fileserver -pctspare 10</B> \
- <B>-L" /usr/afs/bin/volserver /usr/afs/bin/salvager</B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf021.htm#HDRFILELOG">FileLog</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf157.htm#HDRFS_SETACL">fs setacl</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf128.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf130.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf129.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf131.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFMS" HREF="auarf002.htm#ToC_144">fms</A></H2>
-<A NAME="IDX4705"></A>
-<A NAME="IDX4706"></A>
-<A NAME="IDX4707"></A>
-<A NAME="IDX4708"></A>
-<A NAME="IDX4709"></A>
-<A NAME="IDX4710"></A>
-<A NAME="IDX4711"></A>
-<A NAME="IDX4712"></A>
-<A NAME="IDX4713"></A>
-<A NAME="IDX4714"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Determine a tape's capacity and a tape device's filemark size
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fms -tape</B> <<VAR>tape special file</VAR>> [<B>-help</B>]
-
-<B>fms -t</B> <<VAR>tape special file</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fms</B> command determines the capacity of the tape currently in
-the tape device identified by the <B>-tape</B> argument, along with the
-size of the filemark for the device. The filemark is also referred to
-as the device's end-of-file (EOF) marker, and can differ for each
-combination of tape and tape device.
-<P>As the Tape Coordinator writes a dump, it writes a filemark between the
-data included from each volume and also tracks the amount of space left before
-the end of the tape (EOT). For some tape devices, the filemark is large
-enough (multiple megabytes) that failure to consider it leads the Tape
-Coordinator significantly to overestimate the available space.
-<P>The intended use of this command is to determine tape capacity and filemark
-size values that can be specified in a tape device's entry in the
-<B>/usr/afs/backup/tapeconfig</B> file. For certain types of tape
-drives, the Tape Coordinator operates more efficiently when the
-<B>tapeconfig</B> file lists accurate values. For further
-discussion, see the <I>IBM AFS Administration Guide</I> chapter on
-configuring the Backup System.
-<P>Insert a tape in the drive before issuing this command.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command on compressing tape devices in compression mode or
-with tape devices that handle tapes of multigigabyte (or multiterabyte)
-capacity. It does not produce accurate results in those cases.
-For alternate suggestions on the values to record in the <B>tapeconfig</B>
-file for compressing drives, see the <I>IBM AFS Administration Guide</I>
-chapter on configuring the Backup System.
-<P>Running the command completely overwrites the tape, so use a blank one or
-one that can be recycled.
-<P>Because it writes filemarks to the complete length of the tape, the command
-can take from several hours to more than a day to complete.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-tape
-</B><DD>Specifies the UNIX device name of the tape device for which to determine
-filemark size and the capacity of the tape it currently contains. The
-format varies on different system types, but usually begins with
-<B>/dev</B>; an example is <B>/dev/sd0a</B>.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command generates output both on the standard output stream and in the
-<B>fms.log</B> file that it creates in the current working
-directory. The output reports the capacity of the tape in the device
-and the device's filemark size.
-<P>The first few lines of output include status information about the
-execution of the command, including such information as the number of blocks
-and the number of file marks written to the tape by the command. The
-last two lines of both screen and file output provide the following
-information:
-<UL>
-<P><LI><TT>Tape capacity is</TT> <VAR>number</VAR> <TT>bytes</TT>:
-specifies the size, in bytes, of the tape in the device.
-<P><LI><TT>File marks are</TT> <VAR>number</VAR> <TT>bytes</TT>:
-specifies the device's filemark size in bytes.
-</UL>
-<P>The following message indicates that the <B>fms</B> command interpreter
-cannot access the tape device. The command halts.
-<PRE> Can't open tape drive <VAR>device</VAR>
-
-</PRE>
-<P>The following message indicates that the command interpreter cannot create
-the <B>fms.log</B> log file. Again, the command
-halts.
-<PRE> Can't open log file
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command illustrates the output for the device called
-<B>/dev/rmt1h</B>:
-<PRE> % <B>fms /dev/rmt1h</B>
- wrote block: 130408
- Finished data capacity test - rewinding
- wrote 1109 blocks, 1109 file marks
- Finished file mark test
- Tape capacity is 2136604672 bytes
- File marks are 1910205 bytes
-
-</PRE>
-<P>The following appears in the <B>fms.log</B> file:
-<PRE> fms test started
- wrote 9230 blocks
- Finished file mark test
- Tape capacity is 151224320 bytes
- File marks are 2375680 bytes
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be able to insert and write to files in the currently
-working directory, if the <B>fms.log</B> file does not already
-exist. If it already exists, the issuer need only be able to write to
-it.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf044.htm#HDRFMSLOG">fms.log</A>
-<P><A HREF="auarf050.htm#HDRTAPECONFIG">tapeconfig</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf129.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf131.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf130.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf132.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_INTRO" HREF="auarf002.htm#ToC_145">fs</A></H2>
-<A NAME="IDX4715"></A>
-<A NAME="IDX4716"></A>
-<A NAME="IDX4717"></A>
-<A NAME="IDX4718"></A>
-<A NAME="IDX4719"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>fs</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>fs</B> command suite constitute the main
-administrative interface to the Cache Manager on an AFS client machine, which
-is responsible for fetching AFS data from file server machines on behalf of
-applications running on the client machine.
-<P>There are several categories of commands in the <B>fs</B> command
-suite:
-<UL>
-<P><LI>Commands to set and report how the Cache Manager interacts with server
-machines: <B>fs checkservers</B>, <B>fs getcellstatus</B>,
-<B>fs getserverprefs</B>, <B>fs listcells</B>, <B>fs newcell</B>,
-<B>fs setcell</B>,
-<P><B>fs setserverprefs</B>, <B>fs sysname</B>, and <B>fs
-wscell</B>
-<P><LI>Commands to administer access control lists (ACLs): <B>fs
-cleanacl</B>, <B>fs copyacl</B>, <B>fs listacl</B>, and <B>fs
-setacl</B>
-<P><LI>Commands to administer server machines, volumes or partitions that house a
-given file or directory: <B>fs diskfree</B>, <B>fs examine</B>,
-<B>fs listquota</B>, <B>fs quota</B>, <B>fs setquota</B>, <B>fs
-setvol</B>,
-<P><B>fs whereis</B>, and <B>fs whichcell</B>
-<P><LI>Commands to administer the local client cache and related
-information: <B>fs checkvolumes</B>, <B>fs flush</B>, <B>fs
-flushvolume</B>, <B>fs getcacheparms</B>, and <B>fs setcachesize</B>
-<P><LI>Commands to administer volume mount points: <B>fs lsmount</B>,
-<B>fs mkmount</B>, and <B>fs rmmount</B>
-<P><LI>Commands to control monitoring and tracing: <B>fs debug</B>, and
-<B>fs messages</B>
-<P><LI>A command to administer the Cache Manager's interaction with other
-file systems: <B>fs exportafs</B>
-<P><LI>Commands to obtain help: <B>fs apropos</B> and <B>fs
-help</B>
-</UL>
-<P>The Cache Manager and the <B>fs</B> commands use and maintain the
-following configuration files:
-<UL>
-<P><LI>The <B>/usr/vice/etc/CellServDB</B> file lists the database server
-machines in the local cell and any foreign cell to which the administrator
-wishes to enable AFS access for users working on the machine. The
-database server machines run the Authentication, Backup, Protection and Volume
-Location (VL) Server processes, which maintain databases of administrative
-information. For users to access a cell, its
-<B>root.cell</B> volume must also be mounted in the local
-cell's AFS file tree.
-<P><LI>The <B>/usr/vice/etc/ThisCell</B> file defines the machine's cell
-membership with respect to the AFS command suites and Cache Manager access to
-AFS data.
-<P><LI>The <B>/usr/vice/etc/cacheinfo</B> file defines configuration
-parameters for the cache, including its size and whether it is in memory or on
-disk.
-</UL>
-<P>In addition, the Cache Manager automatically creates files on the cache
-partition (by default, <B>/usr/vice/cache</B> for caching and tracking
-files fetched from file server machines.
-<P>For more details, see the reference page for each file.
-<P><STRONG>Options</STRONG>
-<P>The following flag is available on every command in the <B>fs</B>
-suite. The reference page for each command also lists it, but it is
-described here in greater detail.
-<A NAME="IDX4720"></A>
-<A NAME="IDX4721"></A>
-<A NAME="IDX4722"></A>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<A NAME="IDX4723"></A>
-<A NAME="IDX4724"></A>
-<P>The privileges required for <B>fs</B> commands vary more than for other
-command suites. Pay special attention to the <B>Privilege
-Required</B> section of each command description.
-<P>The various types of necessary privilege include:
-<UL>
-<P><LI>Having permissions on a directory's ACL. For example, creating
-and removing mount points requires <B>a</B> (<B>administer</B>),
-<B>i</B> (<B>insert</B>), and <B>d</B> (<B>delete</B>)
-permissions on the ACL of the directory in which the mount point
-resides.
-<P><LI>Being logged onto the machine as the local superuser
-<B>root</B>. This is necessary when issuing commands that affect
-Cache Manager configuration.
-<P><LI>Belonging to the <B>system:administrators</B> group in the
-Protection Database.
-<P><LI>No privilege. Many <B>fs</B> commands simply list
-information.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf017.htm#HDRCACHEITEMS">CacheItems</A>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf036.htm#HDRVN">V<I>n</I></A>
-<P><A HREF="auarf040.htm#HDRVOLUMEITEMS">VolumeItems</A>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<P><A HREF="auarf132.htm#HDRFS_APROPOS">fs apropos</A>
-<P><A HREF="auarf133.htm#HDRFS_CHECKSERVERS">fs checkservers</A>
-<P><A HREF="auarf134.htm#HDRFS_CHECKVOLUMES">fs checkvolumes</A>
-<P><A HREF="auarf135.htm#HDRFS_CLEANACL">fs cleanacl</A>
-<P><A HREF="auarf136.htm#HDRFS_COPYACL">fs copyacl</A>
-<P><A HREF="auarf137.htm#HDRFS_DISKFREE">fs diskfree</A>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P><A HREF="auarf139.htm#HDRFS_EXPORTAFS">fs exportafs</A>
-<P><A HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<P><A HREF="auarf141.htm#HDRFS_FLUSHMOUNT">fs flushmount</A>
-<P><A HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<P><A HREF="auarf143.htm#HDRFS_GETCACHEPARMS">fs getcacheparms</A>
-<P><A HREF="auarf144.htm#HDRFS_GETCELLSTATUS">fs getcellstatus</A>
-<P><A HREF="auarf145.htm#HDRFS_GETCLIENTADDRS">fs getclientaddrs</A>
-<P><A HREF="auarf146.htm#HDRFS_GETSERVERPREFS">fs getserverprefs</A>
-<P><A HREF="auarf147.htm#HDRFS_HELP">fs help</A>
-<P><A HREF="auarf148.htm#HDRFS_LISTACL">fs listacl</A>
-<P><A HREF="auarf149.htm#HDRFS_LISTCELLS">fs listcells</A>
-<P><A HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<P><A HREF="auarf151.htm#HDRFS_LSMOUNT">fs lsmount</A>
-<P><A HREF="auarf152.htm#HDRFS_MESSAGES">fs messages</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf154.htm#HDRFS_NEWCELL">fs newcell</A>
-<P><A HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<P><A HREF="auarf156.htm#HDRFS_RMMOUNT">fs rmmount</A>
-<P><A HREF="auarf157.htm#HDRFS_SETACL">fs setacl</A>
-<P><A HREF="auarf158.htm#HDRFS_SETCACHESIZE">fs setcachesize</A>
-<P><A HREF="auarf159.htm#HDRFS_SETCELL">fs setcell</A>
-<P><A HREF="auarf160.htm#HDRFS_SETCLIENTADDRS">fs setclientaddrs</A>
-<P><A HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<P><A HREF="auarf162.htm#HDRFS_SETSERVERPREFS">fs setserverprefs</A>
-<P><A HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<P><A HREF="auarf164.htm#HDRFS_STOREBEHIND">fs storebehind</A>
-<P><A HREF="auarf165.htm#HDRFS_SYSNAME">fs sysname</A>
-<P><A HREF="auarf166.htm#HDRFS_WHEREIS">fs whereis</A>
-<P><A HREF="auarf167.htm#HDRFS_WHICHCELL">fs whichcell</A>
-<P><A HREF="auarf168.htm#HDRFS_WSCELL">fs wscell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf130.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf132.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf131.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf133.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_APROPOS" HREF="auarf002.htm#ToC_146">fs apropos</A></H2>
-<A NAME="IDX4725"></A>
-<A NAME="IDX4726"></A>
-<A NAME="IDX4727"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>fs ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs apropos</B> command displays the first line of the online
-help entry for any <B>fs</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>fs help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>fs</B> command where the string specified with the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>fs</B> commands that include the
-word <B>cache</B> in their names or short online descriptions:
-<PRE> % <B>fs apropos cache</B>
- setcachesize: set cache size
- flush: flush file from cache
- getcacheparms: get cache usage info
- monitor: set cache monitor host address
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf131.htm#HDRFS_INTRO">fs</A>
-<P><A HREF="auarf147.htm#HDRFS_HELP">fs help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf131.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf133.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf132.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf134.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_CHECKSERVERS" HREF="auarf002.htm#ToC_147">fs checkservers</A></H2>
-<A NAME="IDX4728"></A>
-<A NAME="IDX4729"></A>
-<A NAME="IDX4730"></A>
-<A NAME="IDX4731"></A>
-<A NAME="IDX4732"></A>
-<A NAME="IDX4733"></A>
-<A NAME="IDX4734"></A>
-<A NAME="IDX4735"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the status of server machines
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs checkservers</B> [<B>-cell</B> <<VAR>cell to check</VAR>>] [<B>-all</B>] [<B>-fast</B>]
- [<B>-interval</B> <<VAR>seconds between probes</VAR>>] [<B>-help</B>]
-
-<B>fs checks</B> [<B>-c</B> <<VAR>cell to check</VAR>>] [<B>-a</B>] [<B>-f</B>]
- [<B>-i</B> <<VAR>seconds between probes</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs checkservers</B> command reports whether certain AFS server
-machines are accessible from the local client machine. The machines
-belong to one of two classes, and the Cache Manager maintains a list of them
-in kernel memory:
-<UL>
-<P><LI>The database server machines in every cell listed in the local
-<B>/usr/vice/etc/CellServDB file</B>, plus any machines added to the
-memory list by the <B>fs newcell</B> command since the last reboot.
-<P><LI>All file server machines the Cache Manager has recently contacted, and
-which it probably needs to contact again soon. In most cases, the Cache
-Manager holds a callback on a file or volume fetched from the machine.
-</UL>
-<P>If the Cache Manager is unable to contact the <B>vlserver</B> process
-on a database server machine or the <B>fileserver</B> process on a file
-server machine, it marks the machine as inaccessible. (Actually, if a
-file server machine is multihomed, the Cache Manager attempts to contact all
-of the machine's interfaces, and only marks the machine as down if the
-<B>fileserver</B> fails to reply via any of them.) The Cache
-Manager then periodically (by default, every three minutes) sends a probe to
-each marked machine, to see if it is still inaccessible. If a
-previously inaccessible machine responds, the Cache Manager marks it as
-accessible and no longer sends the periodic probes to it.
-<P>The <B>fs checkservers</B> command updates the list of inaccessible
-machines by having the Cache Manager probe a specified set of them:
-<UL>
-<P><LI>By default, only machines that are marked inaccessible and belong to the
-local cell (the cell listed in the local <B>/usr/vice/etc/ThisCell</B>
-file)
-<P><LI>If the <B>-cell</B> argument is included, only machines that are
-marked inaccessible and belong to the specified cell
-<P><LI>If the <B>-all</B> flag is included, all machines marked inaccessible
-</UL>
-<P>If the <B>-fast</B> flag is included, the Cache Manager does not probe
-any machines, but instead reports the results of the most recent previous
-probe.
-<P>To set the interval between probes rather than produce a list of
-inaccessible machines, use the <B>-interval</B> argument. The
-non-default setting persists until the machine reboots; to preserve it
-across reboots, put the appropriate <B>fs checkservers</B> command in the
-machine's AFS initialization files.
-<P><STRONG>Cautions</STRONG>
-<P>The command can take quite a while to complete, if a number of machines do
-not respond to the Cache Manager's probe. The Cache Manager probes
-machines sequentially and waits a standard timeout period before marking the
-machine as unresponsive, to allow for slow network communication. To
-make the command shell prompt return quickly, put the command in the
-background. It is harmless to interrupt the command by typing
-<B>Ctrl-c</B> or another interrupt signal.
-<P>Note that the Cache Manager probes only server machines marked inaccessible
-in its memory list. A server machine's absence from the output
-does not necessarily mean that it is functioning, because it possibly is not
-included in the memory list at all (if, for example, the Cache Manager has not
-contacted it recently). For the same reason, the output is likely to
-vary on different client machines.
-<P>Unlike most <B>fs</B> commands, the <B>fs checkservers</B> command
-does not refer to the AFSCELL environment variable.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Names each cell in which to probe server machines marked as
-inaccessible. Provide the fully qualified domain name, or a shortened
-form that disambiguates it from the other cells listed in the local
-<B>/usr/vice/etc/CellServDB</B> file. Combine this argument with
-the <B>-fast</B> flag if desired, but not with the <B>-all</B>
-flag. Omit both this argument and the <B>-all</B> flag to probe
-machines in the local cell only.
-<P><DT><B>-all
-</B><DD>Probes all machines in the Cache Manager's memory list that are
-marked inaccessible. Combine this argument with the <B>-fast</B>
-flag if desired, but not with the <B>-cell</B> argument. Omit both
-this flag and the <B>-cell</B> argument to probe machines in the local
-cell only.
-<P><DT><B>-fast
-</B><DD>Displays the Cache Manager's current list of machines that are
-inaccessible, rather than sending new probes. The output can as old as
-the current setting of the probe interval (by default three minutes, and
-maximum ten minutes).
-<P><DT><B>-interval
-</B><DD>Sets or reports the number of seconds between the Cache Manager's
-probes to machines in the memory list that are marked inaccessible:
-<UL>
-<P><LI>To set the interval, specify a value from the range between <B>1</B>
-and <B>600</B> (10 minutes); the default is <B>180</B> (three
-minutes). The issuer must be logged in as the local superuser
-<B>root</B>. The altered setting persists until again changed with
-this command, or until the machine reboots, at which time the setting returns
-to the default.
-<P><LI>Provide a value of <B>0</B> (zero) to display the current interval
-setting. No privilege is required. Do not combine this argument
-with any other.
-</UL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If there are no machines marked as inaccessible, or if all of them now
-respond to the Cache Manager's probe, the output is:
-<PRE> All servers are running.
-
-</PRE>
-<P>Note that this message does not mean that all server machines in each
-relevant cell are running. The output indicates the status of only
-those machines that the Cache Manager probes.
-<P>If a machine fails to respond to the probe within the timeout period, the
-output begins with the string
-<PRE> These servers unavailable due to network or server problems:
-
-</PRE>
-<P>and lists the hostname of each machine on its own line. The Cache
-Manager stores machine records by Internet address, so the format of each
-hostname (uppercase or lowercase letters, or an Internet address in dotted
-decimal format) depends on how the local cell's name service translates
-it at the time the command is issued. If a server machine is
-multihomed, the output lists only one of its interfaces (usually, the
-currently most preferred one).
-<P>If the <B>-interval</B> argument is provided with a value between
-<B>1</B> and <B>600</B>, there is no output. If the value is
-<B>0</B>, the output reports the probe interval as follows:
-<PRE> The current down server probe interval is <VAR>interval</VAR> secs
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the Cache Manager's current list of
-unresponsive machines in the local cell, rather than probing them
-again. The output indicates that if there were any machines marked
-inaccessible, they all responded to the previous probe.
-<PRE> % <B>fs checkservers -fast</B>
- All servers are running.
-
-</PRE>
-<P>The following example probes machines in the Cache Manager's memory
-list that belong to the <B>stateu.edu</B> cell:
-<PRE> % <B>fs checkservers -cell stateu.edu</B>
- All servers are running.
-
-</PRE>
-<P>The following example probes all server machines in the Cache
-Manager's memory list. It reports that two machines did not
-respond to the probe.
-<PRE> % <B>fs checkservers -all</B>
- These servers unavailable due to network or server problems:
- fs1.abc.com SV3.STATE.EDU.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To set the probe interval, the issuer must be logged in as the local
-superuser <B>root</B>. Otherwise, no privilege is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf154.htm#HDRFS_NEWCELL">fs newcell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf132.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf134.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf133.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf135.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_CHECKVOLUMES" HREF="auarf002.htm#ToC_148">fs checkvolumes</A></H2>
-<A NAME="IDX4736"></A>
-<A NAME="IDX4737"></A>
-<A NAME="IDX4738"></A>
-<A NAME="IDX4739"></A>
-<A NAME="IDX4740"></A>
-<A NAME="IDX4741"></A>
-<A NAME="IDX4742"></A>
-<A NAME="IDX4743"></A>
-<A NAME="IDX4744"></A>
-<A NAME="IDX4745"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Forces the Cache Manager to update volume-related information
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs checkvolumes</B> [<B>-help</B>]
-
-<B>fs checkv</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs checkvolumes</B> command discards the table of mappings
-between volume names and volume ID numbers that the Cache Manager stores in
-memory and uses when fetching data from volumes. The next time an
-application requests AFS data, the Cache Manager must contact the Volume
-Location (VL) Server for volume location information, and then an appropriate
-file server machine for the actual data.
-<P>The Cache Manager updates the table of mappings periodically (by default,
-hourly), but this command is useful if the issuer knows that a volume's
-name has changed, or that new read-only replicas of a volume have been
-released, because issuing it forces the Cache Manager to reference the changed
-volume.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The following message confirms that the command ran successfully.
-<PRE> All volumeID/name mappings checked.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf133.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf135.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf134.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf136.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_CLEANACL" HREF="auarf002.htm#ToC_149">fs cleanacl</A></H2>
-<A NAME="IDX4746"></A>
-<A NAME="IDX4747"></A>
-<A NAME="IDX4748"></A>
-<A NAME="IDX4749"></A>
-<A NAME="IDX4750"></A>
-<A NAME="IDX4751"></A>
-<A NAME="IDX4752"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Remove obsolete entries from an ACL
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs cleanacl </B>[<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs cl</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs cleanacl</B> command removes from the access control list
-(ACL) of each specified directory or file any entry that refers to a user or
-group that no longer has a Protection Database entry. Such an entry
-appears on the ACL as an AFS user ID number (UID) rather than a name, because
-without a Protection Database entry, the File Server cannot translate the UID
-into a name.
-<P>Cleaning access control lists in this way not only keeps them from becoming
-crowded with irrelevant information, but also prevents the new possessor of a
-recycled AFS UID from obtaining access intended for the former possessor of
-the AFS UID. (Note that recycling UIDs is not recommended in any
-case.)
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each directory for which to clean the ACL (specifying a filename
-cleans its directory's ACL). If this argument is omitted, the
-current working directory's ACL is cleaned.
-<P>Specify the read/write path to each directory, to avoid the failure that
-results from attempting to change a read-only volume. By convention,
-the read/write path is indicated by placing a period before the cell name at
-the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If there are no obsolete entries on the ACL, the following message
-appears:
-<PRE> Access list for <VAR>dir/file path</VAR> is fine.
-
-</PRE>
-<P>Otherwise, the output reports the resulting state of the ACL, following the
-header
-<PRE> Access list for <VAR>dir/file path</VAR> is now
-
-</PRE>
-<P>At the same time, the following error message appears for each file in the
-cleaned directories:
-<PRE> fs: '<VAR>filename</VAR>': Not a directory
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example illustrates the cleaning of the ACLs on the current
-working directory and two of its subdirectories. Only the second
-subdirectory had obsolete entries on it.
-<PRE> % <B>fs cleanacl -path . ./reports ./sources</B>
- Access list for . is fine.
- Access list for ./reports is fine.
- Access list for ./sources is now
- Normal rights:
- system:authuser rl
- pat rlidwka
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>a</B> (<B>administer</B>) permission on
-each directory's ACL (or the ACL of each file's parent
-directory); the directory's owner and the members of the
-<B>system:administrators</B> group have the right implicitly, even
-if it does not appear on the ACL.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf148.htm#HDRFS_LISTACL">fs listacl</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf134.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf136.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf135.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf137.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_COPYACL" HREF="auarf002.htm#ToC_150">fs copyacl</A></H2>
-<A NAME="IDX4753"></A>
-<A NAME="IDX4754"></A>
-<A NAME="IDX4755"></A>
-<A NAME="IDX4756"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Copies an ACL from one directory to one or more other directories
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs copyacl -fromdir</B> <<VAR>source directory (or DFS file)</VAR>>
- <B>-todir</B> <<VAR>destination directory (or DFS file)</VAR>><SUP>+</SUP>
- [<B>-clear</B>] [<B>-id</B>] [<B>-if</B>] [<B>-help</B>]
-
-<B>fs co -f</B> <<VAR>source directory (or DFS file)</VAR>>
- <B>-t</B> <<VAR>destination directory (or DFS file)</VAR>><SUP>+</SUP>
- [<B>-c</B>] [<B>-id</B>] [<B>-if</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs copyacl</B> command copies the access control list (ACL) from
-a source directory to each specified destination directory. The source
-directory's ACL is unchanged, and changes to the destination
-directory's ACL obey the following rules:
-<UL>
-<P><LI>If an entry on the source ACL does not already exist on the destination
-ACL, it is added.
-<P><LI>If an entry exists on both the source and destination ACLs, the
-permissions from the source ACL entry replace the current permissions on the
-destination ACL entry.
-<P><LI>If an entry on the destination ACL has no corresponding entry on the
-source ACL, it is removed if the <B>-clear</B> flag is included and is
-unchanged otherwise. In other words, if the <B>-clear</B> flag is
-provided, the source ACL completely replaces the destination ACL.
-</UL>
-<P>When using this command to copy ACLs between objects in DFS filespace
-accessed via the AFS/DFS Migration Toolkit Protocol Translator, it is possible
-to specify files, as well as directories, with the <B>-fromdir</B> and
-<B>-todir</B> arguments. For more information on copying ACLs
-between DFS directories and files, refer to the <I>IBM AFS/DFS Migration
-Toolkit Administration Guide and Reference</I>.
-<P><STRONG>Cautions</STRONG>
-<P>Do not copy ACLs between AFS and DFS files or directories. The ACL
-formats are incompatible.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-fromdir
-</B><DD>Specifies the source directory from which to copy the ACL.
-(Specifying an AFS file copies its directory's ACL, but specifying a DFS
-file copies its own ACL). A partial pathname is interpreted relative to
-the current working directory.
-<P><DT><B>-todir
-</B><DD>Specifies each directory for which to alter the ACL to match the source
-ACL. (Specifying an AFS file halts the command with an error, but
-specifying a DFS file alters the file's ACL). A partial pathname
-is interpreted relative to the current working directory.
-<P>Specify the read/write path to each directory (or DFS file), to avoid the
-failure that results from attempting to change a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-clear
-</B><DD>Replaces the ACL of each destination directory with the source ACL.
-<P><DT><B>-id
-</B><DD>Modifies the Initial Container ACL of each DFS directory named by the
-<B>-todir</B> argument, rather than the regular Object ACL. This
-argument is supported only when both the source and each destination directory
-reside in DFS and are accessed via the AFS/DFS Migration Toolkit Protocol
-Translator.
-<P><DT><B>-if
-</B><DD>Modifies the Initial Object ACL of each DFS directory named by the
-<B>-todir</B> argument, rather than the regular Object ACL. This
-argument is supported only when both the source and each destination directory
-reside in DFS and are accessed via the AFS/DFS Migration Toolkit Protocol
-Translator.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command copies the current working directory's
-ACL to its subdirectory called <B>reports</B>. Note that the source
-directory's ACL is unaffected. Entries on the <B>reports</B>
-directory's that are not on the source ACL of the current directory
-remain unaffected as well, because the <B>-clear</B> flag is not
-used.
-<PRE> % <B>fs listacl . reports</B>
- Access list for . is
- Normal rights:
- pat rlidwka
- smith rlidwk
- Access list for reports is
- Normal rights:
- pat rl
- pat:friends rl
- Negative rights
- jones rlidwka
-
- % <B>fs copyacl -fromdir . -todir reports</B>
-
- % <B>fs listacl . reports</B>
- Access list for . is
- Normal rights:
- pat rlidwka
- smith rlidwk
- Access list for reports is
- Normal rights:
- pat rlidwka
- pat:friends rl
- smith rlidwk
- Negative rights
- jones rlidwka
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To copy an ACL between AFS objects, the issuer must have the <B>l</B>
-(<B>lookup)</B>) permission on the source directory's ACL and the
-<B>a</B> (<B>administer</B>) permission on each destination
-directory's ACL. If the <B>-fromdir</B> argument names a file
-rather than a directory, the issuer must have both the <B>l</B> and
-<B>r</B> (<B>read</B>) permissions on the ACL of the file's
-directory.
-<P>To copy an ACL between DFS objects, the issuer must have the <B>r</B>
-permission on the source directory or file's ACL and the <B>c</B>
-(<B>control</B>) permission on each destination directory or file's
-ACL.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf148.htm#HDRFS_LISTACL">fs listacl</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf157.htm#HDRFS_SETACL">fs setacl</A>
-<P><I>IBM AFS/DFS Migration Toolkit Administration Guide and Reference</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf135.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf137.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf136.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf138.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_DISKFREE" HREF="auarf002.htm#ToC_151">fs diskfree</A></H2>
-<A NAME="IDX4757"></A>
-<A NAME="IDX4758"></A>
-<A NAME="IDX4759"></A>
-<A NAME="IDX4760"></A>
-<A NAME="IDX4761"></A>
-<A NAME="IDX4762"></A>
-<A NAME="IDX4763"></A>
-<A NAME="IDX4764"></A>
-<A NAME="IDX4765"></A>
-<A NAME="IDX4766"></A>
-<A NAME="IDX4767"></A>
-<A NAME="IDX4768"></A>
-<A NAME="IDX4769"></A>
-<A NAME="IDX4770"></A>
-<A NAME="IDX4771"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays information about the partition housing a directory or file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs diskfree</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs df</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs di</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs diskfree</B> command formats and displays information about
-the partition that houses the volume containing the specified directory or
-file, including its size and how much space is currently used.
-<P>To display information about the volume itself, use the <B>fs
-examine</B> command. The <B>fs examine</B> and <B>fs
-quota</B> commands also display information about a volume.
-<P><STRONG>Cautions</STRONG>
-<P>The partition-related statistics in this command's output do not
-always agree with the corresponding values in the output of the standard UNIX
-<B>df</B> command. The statistics reported by this command can be
-up to five minutes old, because the Cache Manager polls the File Server for
-partition information at that frequency. Also, on some operating
-systems, the <B>df</B> command's report of partition size includes
-reserved space not included in this command's calculation, and so is
-likely to be about 10% larger.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names a file or directory that resides on the partition about which to
-produce output. Partial pathnames are interpreted relative to the
-current working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output reports the following information about the volume and partition
-that houses each file or directory:
-<DL>
-<P><DT><B><TT>Volume Name</TT>
-</B><DD>The name of the volume
-<P><DT><B><TT>kbytes</TT>
-</B><DD>The partition's total size in kilobytes
-<P><DT><B><TT>used</TT>
-</B><DD>The number of kilobytes used on the partition
-<P><DT><B><TT>avail</TT>
-</B><DD>The number of kilobytes available on the partition
-<P><DT><B><TT>%used</TT>
-</B><DD>The percentage of the partition's total space that is used (the
-<TT>used</TT> statistic divided by the <TT>kbytes</TT> statistic, times
-100)
-</DL>
-<P>If the <TT>%used</TT> statistic is greater than 90%, it is marked with
-the string <TT><<WARNING</TT> at the right margin.
-<P>If the volume is a read-only volume, the output includes information about
-only one of the partitions that houses it, generally the one on the file
-server machine with the lowest preference rank. To verify which machine
-the output is referring to, use the <B>vos listvldb</B> command to list
-the volume's locations, and the <B>vos partinfo</B> command to
-display the size of each one.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the partitions housing the
-volumes <B>user.smith</B> and <B>sun4x_56.bin</B>:
-<PRE> % <B>fs diskfree -path /afs/abc.com/usr/smith /afs/abc.com/sun4x_56/bin</B>
- Volume Name kbytes used avail %used
- user.smith 4177920 3841258 336662 92% <<WARNING
- sun4x_56.bin 4423680 3174500 1249180 72%
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf136.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf138.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf137.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf139.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_EXAMINE" HREF="auarf002.htm#ToC_152">fs examine</A></H2>
-<A NAME="IDX4772"></A>
-<A NAME="IDX4773"></A>
-<A NAME="IDX4774"></A>
-<A NAME="IDX4775"></A>
-<A NAME="IDX4776"></A>
-<A NAME="IDX4777"></A>
-<A NAME="IDX4778"></A>
-<A NAME="IDX4779"></A>
-<A NAME="IDX4780"></A>
-<A NAME="IDX4781"></A>
-<A NAME="IDX4782"></A>
-<A NAME="IDX4783"></A>
-<A NAME="IDX4784"></A>
-<A NAME="IDX4785"></A>
-<A NAME="IDX4786"></A>
-<A NAME="IDX4787"></A>
-<A NAME="IDX4788"></A>
-<A NAME="IDX4789"></A>
-<A NAME="IDX4790"></A>
-<A NAME="IDX4791"></A>
-<A NAME="IDX4792"></A>
-<A NAME="IDX4793"></A>
-<A NAME="IDX4794"></A>
-<A NAME="IDX4795"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays information about the volume containing a directory or file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs examine</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs exa</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs listvol</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs listv</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs lv</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs examine</B> command displays information about the volume
-containing each specified directory or file, including its volume ID number,
-quota and the percentage of its quota that is used.
-<P>This command provides the most information about a volume, but the <B>fs
-listquota</B> command displays similar information in tabular format, and
-the <B>fs quota</B> command reports only the percentage of quota
-used.
-<P>To set volume quota, use the <B>fs setquota</B> or <B>fs setvol</B>
-command.
-<P><STRONG>Cautions</STRONG>
-<P>The partition-related statistics in this command's output do not
-always agree with the corresponding values in the output of the standard UNIX
-<B>df</B> command. The statistics reported by this command can be
-up to five minutes old, because the Cache Manager polls the File Server for
-partition information at that frequency. Also, on some operating
-systems, the <B>df</B> command's report of partition size includes
-reserved space not included in this command's calculation, and so is
-likely to be about 10% larger.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names a file or directory that resides in the volume about which to
-produce output. Partial pathnames are interpreted relative to the
-current working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays information about the volume that houses each specified
-directory or file, in the following format
-<PRE> Volume status for vid = <VAR>volume ID</VAR> named <VAR>volume name</VAR>
- Current offline message is <VAR>message</VAR>
- Current disk quota is <VAR>quota in kilobytes</VAR>
- Current blocks used are <VAR>volume size in kilobytes</VAR>
- The partition has <VAR>available partition</VAR> blocks available out of
- <VAR>partition size</VAR>
-
-</PRE>
-<P>where the first line specifies the volume's ID number and name.
-The <TT>Current</TT> <TT>offline</TT> <TT>message</TT> line appears only
-if an administrator has included the <B>-offlinemsg</B> argument to the
-<B>fs setvol</B> command. The remaining lines report, respectively,
-<UL>
-<P><LI>the volume's quota in kilobytes, or the string <TT>unlimited</TT>
-to indicate an unlimited quota
-<P><LI>the volume's current size in kilobytes
-<P><LI>the number of blocks available and total size of the host partition, both
-in kilobytes.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the volume
-<B>user.smith</B> and the partition housing it:
-<PRE> % <B>fs examine -path /afs/abc.com/usr/smith</B>
- Volume status for vid = 50489902 named user.smith
- Current maximum quota is 15000
- Current blocks used are 5073
- The partition has 336662 blocks available out of 4177920
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<P><A HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<P><A HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<P><A HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf137.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf139.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf138.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf140.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_EXPORTAFS" HREF="auarf002.htm#ToC_153">fs exportafs</A></H2>
-<A NAME="IDX4796"></A>
-<A NAME="IDX4797"></A>
-<A NAME="IDX4798"></A>
-<A NAME="IDX4799"></A>
-<A NAME="IDX4800"></A>
-<A NAME="IDX4801"></A>
-<A NAME="IDX4802"></A>
-<A NAME="IDX4803"></A>
-<A NAME="IDX4804"></A>
-<A NAME="IDX4805"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports or sets whether the machine can export AFS to clients of other file
-systems
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs exportafs -type</B> <<VAR>exporter name</VAR>>
- [<B>-start</B> <<VAR>start/stop translator (on | off)</VAR>>]
- [<B>-convert</B> <<VAR>convert from afs to unix mode (on | off)</VAR>>]
- [<B>-uidcheck</B> <<VAR>run on strict 'uid check' mode (on | off)</VAR>>]
- [<B>-submounts</B> <<VAR>allow nfs mounts to subdirs of /afs/.. (on | off)</VAR>>]
- [<B>-help</B>]
-
-<B>fs exp -t</B> <<VAR>exporter name</VAR>>
- [<B>-st</B> <<VAR>start/stop translator (on | off)</VAR>>]
- [<B>-c</B> <<VAR>convert from afs to unix mode (on | off)</VAR>>]
- [<B>-u</B> <<VAR>run on strict 'uid check' mode (on | off)</VAR>>]
- [<B>-su</B> <<VAR>allow nfs mounts to subdirs of /afs/.. (on | off)</VAR>>]
- [<B>-help</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs exportafs</B> command sets (if the <B>-start</B> argument
-is provided) or reports (if it is omitted) whether the machine can reexport
-the AFS filespace to clients of a non-AFS file system. To control
-certain features of the translation protocol, use the following
-arguments:
-<UL>
-<P><LI>To control whether the UNIX <B>group</B> and <B>other</B> mode
-bits on an AFS file or directory are set to match the <B>owner</B> mode
-bits when it is exported to the non-AFS file system, use the
-<B>-convert</B> argument.
-<P><LI>To control whether tokens can be placed in a credential structure
-identified by a UID that differs from the local UID of the entity that is
-placing the tokens in the structure, use the <B>-uidcheck</B>
-argument. The most common use is to control whether issuers of the
-<B>knfs</B> command can specify a value for its <B>-id</B> argument
-that does not match their local UID on the NFS/AFS translator machine.
-<P><LI>To control whether users can create mounts in the non-AFS filespace to an
-AFS directory other than <B>/afs</B>, use the <B>-submounts</B>
-argument.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-type
-</B><DD>Names the alternate file system to which to reexport the AFS
-filespace. The only acceptable value is <B>nfs</B>, in lowercase
-letters only.
-<P><DT><B>-start
-</B><DD>Enables the local machine to reexport the AFS filespace if the value is
-<B>on</B>, or disables it if the value is <B>off</B>. Omit this
-argument to report the current setting for all of the configurable
-parameters.
-<P><DT><B>-convert
-</B><DD>Controls the setting of the UNIX <B>group</B> and <B>other</B>
-mode bits on AFS files and directories exported to the non-AFS file
-system. If the value is <B>on</B>, they are set to match the
-<B>owner</B> mode bits. If the value is <B>off</B>, the bits
-are not changed. If this argument is omitted, the default value is
-<B>on</B>.
-<P><DT><B>-uidcheck
-</B><DD>Controls whether tokens can be placed in a credential structure identified
-by a UID that differs from the local UID of the entity that is placing the
-tokens in the structure.
-<UL>
-<P><LI>If the value is <B>on</B>, the UID that identifies the credential
-structure must match the local UID.
-<P>With respect to the <B>knfs</B> command, this value means that the
-value of <B>-id</B> argument must match the issuer's local UID on the
-translator machine. In practice, this setting makes it pointless to
-include the <B>-id</B> argument to the <B>knfs</B> command, because
-the only acceptable value (the issuer's local UID) is already used when
-the <B>-id</B> argument is omitted.
-<P>Enabling UID checking also makes it impossible to issue the <B>klog</B>
-and <B> pagsh</B> commands on a client machine of the non-AFS file system
-even though it is a system type supported by AFS. For an explanation,
-see the reference page for the <B>klog</B> command.
-<P><LI>If the value is <B>off</B> (the default), tokens can be assigned to a
-local UID in the non-AFS file system that does not match the local UID of the
-entity assigning the tokens.
-<P>With respect to the <B>knfs</B> command, it means that the issuer can
-use the <B>-id</B> argument to assign tokens to a local UID on the NFS
-client machine that does not match his or her local UID on the translator
-machine. (An example is assigning tokens to the MFS client
-machine's local superuser <B>root</B>.) This setting allows
-more than one issuer of the <B>knfs</B> command to make tokens available
-to the same user on the NFS client machine. Each time a different user
-issues the <B>knfs</B> command with the same value for the <B>-id</B>
-argument, that user's tokens overwrite the existing ones. This can
-result in unpredictable access for the user on the NFS client machine.
-</UL>
-<P><DT><B>-submounts
-</B><DD>Controls whether a user of the non-AFS filesystem can mount any directory
-in the AFS filespace other than the top-level <B>/afs</B>
-directory. If the value is <B>on</B>, such submounts are
-allowed. If the value is off, only mounts of the <B>/afs</B>
-directory are allowed. If this argument is omitted, the default value
-is <B>off</B>.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the machine is not even configured as a server of the non-AFS file
-system, the following message appears:
-<PRE> Sorry, the <VAR>file_system</VAR>-exporter type is currently not supported on
- this AFS client
-
-</PRE>
-<P>If the machine is configured as a server of the non-AFS file system but is
-not currently enabled to reexport AFS to it (because the <B>-start</B>
-argument to this command is not set to <B>on</B>), the message is as
-follows:
-<PRE> '<VAR>file_system</VAR>' translator is disabled
-
-</PRE>
-<P>If the machine is enabled to reexport AFS, the following message precedes
-messages that report the settings of the other parameters.
-<PRE> '<VAR>file_system</VAR>' translator is enabled with the following options:
-
-</PRE>
-<P>The following messages indicate that the <B>-convert</B> argument is
-set to <B>on</B> or <B>off</B> respectively:
-<PRE> Running in convert owner mode bits to world/other mode
- Running in strict unix mode
-
-</PRE>
-<P>The following messages indicate that the <B>-uidcheck</B> argument is
-set to <B>on</B> or <B>off</B> respectively:
-<PRE> Running in strict 'passwd sync' mode
- Running in no 'passwd sync' mode
-
-</PRE>
-<P>The following messages indicate that the <B>-submounts</B> argument is
-set to <B>on</B> or <B>off</B> respectively:
-<PRE> Allow mounts of /afs/.. subdirs
- Only mounts to /afs allowed
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows that the local machine can export AFS to NFS
-client machines.
-<PRE> % <B>fs exportafs nfs</B>
- 'nfs' translator is enabled with the following options:
- Running in convert owner mode bits to world/other mode
- Running in no 'passwd sync' mode
- Only mounts to /afs allowed
-
-</PRE>
-<P>The following example enables the machine as an NFS server and converts the
-UNIX <B>group</B> and <B>other</B> mode bits on exported AFS
-directories and files to match the UNIX <B>owner</B> mode bits.
-<PRE> % <B>fs exportafs -type nfs -start on -convert on</B>
-
-</PRE>
-<P>The following example disables the machine from reexporting AFS to NFS
-client machines:
-<PRE> %<B> fs exportafs -type nfs -start off</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf201.htm#HDRKNFS">knfs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf138.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf140.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf139.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf141.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_FLUSH" HREF="auarf002.htm#ToC_154">fs flush</A></H2>
-<A NAME="IDX4806"></A>
-<A NAME="IDX4807"></A>
-<A NAME="IDX4808"></A>
-<A NAME="IDX4809"></A>
-<A NAME="IDX4810"></A>
-<A NAME="IDX4811"></A>
-<A NAME="IDX4812"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Forces the Cache Manager to discard a cached file or directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs flush</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs flush</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs flush</B> command removes from the cache all data and status
-information associated with each specified file or directory. The next
-time an application requests data from the flushed directory or file, the
-Cache Manager fetches the most current version from a File Server, along with
-a new callback (if necessary) and associated status information. This
-command has no effect on two types of data:
-<OL TYPE=1>
-<P><LI>Data in application program buffers
-<P><LI>Data that has been changed locally and written to the cache but not yet
-written to the copy on the file server machine
-</OL>
-<P>To flush all data in the cache that was fetched from the same volume as a
-specified file or directory, use the <B>fs flushvolume</B> command.
-To flush a corrupted mount point, use the <B>fs flushmount</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each file or directory to flush from the cache. If it is a
-directory, only the directory element itself is flushed, not data cached from
-files or subdirectories that reside in it. Partial pathnames are
-interpreted relative to the current working directory, which is also the
-default value if this argument is omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command flushes from the cache the file
-<B>projectnotes</B> in the current working directory and all data from the
-subdirectory <B>plans</B>:
-<PRE> % <B>fs flush -path projectnotes ./plans/*</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf141.htm#HDRFS_FLUSHMOUNT">fs flushmount</A>
-<P><A HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf139.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf141.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf140.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf142.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_FLUSHMOUNT" HREF="auarf002.htm#ToC_155">fs flushmount</A></H2>
-<A NAME="IDX4813"></A>
-<A NAME="IDX4814"></A>
-<A NAME="IDX4815"></A>
-<A NAME="IDX4816"></A>
-<A NAME="IDX4817"></A>
-<A NAME="IDX4818"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Forces the Cache Manager to discard a mount point
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs flushmount</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs flushm</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs flushmount</B> command removes from the cache all information
-associated with each mount point named by the <B>-path</B>
-argument. The next time an application accesses the mount point, the
-Cache Manager fetches the most current version of it from the File
-Server. Data cached from the associated volume is not affected.
-<P>The command's intended use is to discard information about mount
-points that has become corrupted in the cache. (The Cache Manager
-periodically refreshes cached mount points, but the only other way to discard
-them immediately is to reinitialize the Cache Manager by rebooting the
-machine.) Symptoms of a corrupted mount point included garbled output
-from the <B>fs lsmount</B> command, and failed attempts to change
-directory to or list the contents of a mount point.
-<P>To flush cached data rather than a mount point, use the <B>fs flush</B>
-or <B>fs flushvolume</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each mount point to flush from the cache. Partial pathnames
-are interpreted relative to the current working directory, which is also the
-default value if this argument is omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command flushes from the cache the mount point for user
-<B>pat</B>'s home directory:
-<PRE> % <B>fs flushm /afs/abc.com/usr/pat</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<P><A HREF="auarf142.htm#HDRFS_FLUSHVOLUME">fs flushvolume</A>
-<P><A HREF="auarf151.htm#HDRFS_LSMOUNT">fs lsmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf140.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf142.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf141.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf143.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_FLUSHVOLUME" HREF="auarf002.htm#ToC_156">fs flushvolume</A></H2>
-<A NAME="IDX4819"></A>
-<A NAME="IDX4820"></A>
-<A NAME="IDX4821"></A>
-<A NAME="IDX4822"></A>
-<A NAME="IDX4823"></A>
-<A NAME="IDX4824"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Forces the Cache Manager to discard all cached data from the volume
-containing a file or directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs flushvolume</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs flushv</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs flushvolume</B> command removes from the cache all data that
-was fetched from the same volume as each specified directory or file.
-It does not discard cached status information. The next time an
-application requests data from a flushed directory or file, the Cache Manager
-fetches the most current version from a File Server, along with a new callback
-(if necessary) and associated status information. This command has no
-effect on two types of data:
-<OL TYPE=1>
-<P><LI>Data in application program buffers
-<P><LI>Data that has been changed locally and written to the cache but not yet
-written to the copy on the file server machine
-</OL>
-<P>To discard the data and status information associated with individual files
-and directories, use the <B>fs flush</B> command. To flush a
-corrupted mount point, use the <B>fs flushmount</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names a file or directory from each volume for which to discard all cached
-data. Partial pathnames are interpreted relative to the current working
-directory, which is also the default value if this argument is omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command flushes from the cache all data fetched from the
-volume that contains the current working directory:
-<PRE> % <B>fs flushvolume </B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf140.htm#HDRFS_FLUSH">fs flush</A>
-<P><A HREF="auarf141.htm#HDRFS_FLUSHMOUNT">fs flushmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf141.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf143.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf142.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf144.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_GETCACHEPARMS" HREF="auarf002.htm#ToC_157">fs getcacheparms</A></H2>
-<A NAME="IDX4825"></A>
-<A NAME="IDX4826"></A>
-<A NAME="IDX4827"></A>
-<A NAME="IDX4828"></A>
-<A NAME="IDX4829"></A>
-<A NAME="IDX4830"></A>
-<A NAME="IDX4831"></A>
-<A NAME="IDX4832"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the current size of the cache and the amount being used
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs getcacheparms</B> [<B>-help</B>]
-
-<B>fs getca</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs getcacheparms</B> command displays the current size of the
-cache (which can be in memory or on disk), and the amount currently in
-use.
-<P>The reported statistics are from kernel memory, so the reported size can
-differ from the setting specified in the <B>/usr/vice/etc/cacheinfo</B>
-file on a machine using a disk cache, if the <B>fs setcachesize</B>
-command has been used to alter cache size.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output reports
-<PRE> AFS using <VAR>amount used</VAR> of the cache's available <VAR>size</VAR> 1K byte blocks.
-
-</PRE>
-<P>where <VAR>amount used</VAR> is the number of kilobyte blocks currently used
-to cache data and status information, and <VAR>size</VAR> is the total current
-cache size.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output on a machine with a 25000 kilobyte
-cache.
-<PRE> % <B>fs getcacheparms</B>
- AFS using 22876 of the cache's available 25000 1K byte blocks.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf158.htm#HDRFS_SETCACHESIZE">fs setcachesize</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf142.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf144.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf143.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf145.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_GETCELLSTATUS" HREF="auarf002.htm#ToC_158">fs getcellstatus</A></H2>
-<A NAME="IDX4833"></A>
-<A NAME="IDX4834"></A>
-<A NAME="IDX4835"></A>
-<A NAME="IDX4836"></A>
-<A NAME="IDX4837"></A>
-<A NAME="IDX4838"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports whether the machine can run setuid programs from a specified cell
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs getcellstatus -cell</B> <<VAR>cell name</VAR>><SUP>+</SUP> [<B>-help</B>]
-
-<B>fs getce -c</B> <<VAR>cell name</VAR>><SUP>+</SUP> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs getcellstatus</B> command reports whether the Cache Manager
-allows programs fetched from each specified cell to run with setuid
-permission. To set a cell's setuid status, use the <B>fs
-setcell</B> command; its reference page fully describes how AFS treats
-setuid programs.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Names each cell for which to report setuid status. Provide the
-fully qualified domain name, or a shortened form that disambiguates it from
-the other cells listed in the local <B>/usr/vice/etc/CellServDB</B>
-file.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output reports one of the following two values as appropriate:
-<PRE> Cell <VAR>cell</VAR> status: setuid allowed
- Cell <VAR>cell</VAR> status: no setuid allowed
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example indicates that programs from the cell
-<B>abc.com</B> are not allowed to run with setuid
-permission.
-<PRE> % <B>fs getcellstatus abc.com</B>
- Cell abc.com status: no setuid allowed
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf159.htm#HDRFS_SETCELL">fs setcell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf143.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf145.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf144.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf146.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_GETCLIENTADDRS" HREF="auarf002.htm#ToC_159">fs getclientaddrs</A></H2>
-<A NAME="IDX4839"></A>
-<A NAME="IDX4840"></A>
-<A NAME="IDX4841"></A>
-<A NAME="IDX4842"></A>
-<A NAME="IDX4843"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the client interfaces to register with the File Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs getclientaddrs</B> [<B>-help</B>]
-
-<B>fs gc</B> [<B>-h</B>]
-
-<B>fs getcl </B>[<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs getclientaddrs</B> command displays the IP addresses of the
-interfaces that the local Cache Manager registers with a File Server when
-first establishing a connection to it.
-<P>The File Server uses the addresses when it initiates a remote procedure
-call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by
-the Cache Manager). There are two common circumstances in which the
-File Server initiates RPCs: when it breaks callbacks and when it pings
-the client machine to verify that the Cache Manager is still
-accessible.
-<P>If an RPC to that interface fails, the File Server simultaneously sends
-RPCs to all of the other interfaces in the list, to learn which of them are
-still available. Whichever interface replies first is the one to which
-the File Server then sends pings and RPCs to break callbacks.
-<P>The <B>fs setclientaddrs</B> reference page explains how the Cache
-Manager constructs the list automatically in kernel memory as it initializes,
-and how to use that command to alter the kernel list after
-initialization.
-<P><STRONG>Cautions</STRONG>
-<P>The File Server uses the list of interfaces displayed by this command only
-when selecting an alternative interface after a failed attempt to break a
-callback or ping the Cache Manager. When responding to the Cache
-Manager's request for file system data, the File Server replies to the
-interface which the Cache Manager used when sending the request. If the
-File Server's reply to a data request fails, the file server
-machine's network routing configuration determines which alternate
-network routes to the client machine are available for resending the
-reply.
-<P>The displayed list applies to all File Servers to which the Cache Manager
-connects in the future. It is not practical to register different sets
-of addresses with different File Servers, because it requires using the
-<B>fs setclientaddrs</B> command to change the list and then rebooting
-each relevant File Server immediately.
-<P>The displayed list is not necessarily governing the behavior of a given
-File Server, if an administrator has issued the <B>fs setclientaddrs</B>
-command since the Cache Manager first contacted that File Server. It
-determines only which addresses the Cache Manager registers when connecting to
-File Servers in the future.
-<P>The list of interfaces does not influence the Cache Manager's choice
-of interface when establishing a connection to a File Server.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays the IP address of each interface that the Cache Manager
-is currently registering with File Server processes that it contacts, with one
-address per line. The File Server initially uses the first address for
-breaking callbacks and pinging the Cache Manager, but the ordering of the
-other interfaces is not meaningful.
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the two interfaces that the Cache Manager is
-registering with File Servers.
-<PRE> % <B>fs getclientaddrs</B>
- 192.12.105.68
- 192.12.108.84
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf160.htm#HDRFS_SETCLIENTADDRS">fs setclientaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf144.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf146.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf145.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf147.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_GETSERVERPREFS" HREF="auarf002.htm#ToC_160">fs getserverprefs</A></H2>
-<A NAME="IDX4844"></A>
-<A NAME="IDX4845"></A>
-<A NAME="IDX4846"></A>
-<A NAME="IDX4847"></A>
-<A NAME="IDX4848"></A>
-<A NAME="IDX4849"></A>
-<A NAME="IDX4850"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the Cache Manager's preference ranks for file server or VL
-Server machines
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs getserverprefs</B> [<B>-file</B> <<VAR>output to named file</VAR>>]
- [<B>-numeric</B>] [<B>-vlservers</B>] [<B>-help</B>]
-
-<B>fs gets</B> [<B>-f</B> <<VAR>output to named file</VAR>>] [<B>-n</B>] [<B>-v</B>] [<B>-h</B>]
-
-<B>fs gp</B> [<B>-f</B> <<VAR>output to named file</VAR>>] [<B>-n</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs getserverprefs</B> command displays preference ranks for file
-server machine interfaces (file server machines run the <B>fs</B> process)
-or, if the <B>-vlserver</B> flag is provided, for Volume Location (VL)
-Server machines (which run the <B>vlserver</B> process). For file
-server machines, the Cache Manager tracks up to 15 interfaces per machine and
-assigns a separate rank to each interface. The ranks indicate the order
-in which the local Cache Manager attempts to contact the interfaces of
-machines that are housing a volume when it needs to fetch data from the
-volume. For VL Server machines, the ranks indicate the order in which
-the Cache Manager attempts to contact a cell's VL Servers when requesting
-VLDB information. For both types of rank, lower integer values are more
-preferred.
-<P>The Cache Manager stores ranks in kernel memory. Once set, a rank
-persists until the machine reboots, or until the <B>fs setserverprefs</B>
-command is used to change it. The reference page for the <B>fs
-setserverprefs</B> command explains how the Cache Manager sets default
-ranks, and how to use that command to change the default values.
-<P>Default VL Server ranks range from 10,000 to 10,126, and the Cache Manager
-assigns them to every machine listed in its copy of the
-<B>/usr/vice/etc/CellServDB</B> file. When the Cache Manager needs
-to fetch VLDB information from a cell, it compares the ranks for the VL Server
-machines belonging to that cell, and attempts to contact the VL Server with
-the lowest integer rank. If the Cache Manager cannot reach the VL
-Server (because of server process, machine or network outage), it tries to
-contact the VL Server with the next lowest integer rank, and so on. If
-all of a cell's VL Server machines are unavailable, the Cache Manager
-cannot fetch data from the cell.
-<P>Default file server ranks range from 5,000 to 40,000, excluding the range
-used for VL Servers (10,000 to 10,126); the maximum possible rank is
-65,534. When the Cache Manager needs to fetch data from a volume, it
-compares the ranks for the interfaces of machines that house the volume, and
-attempts to contact the interface that has the lowest integer rank. If
-it cannot reach the <B>fileserver</B> process via that interface (because
-of server process, machine or network outage), it tries to contact the
-interface with the next lowest integer rank, and so on. If it cannot
-reach any of the interfaces for machines that house the volume, it cannot
-fetch data from the volume.
-<P>For both file server machines and VL Server machines, it is possible for a
-machine or interface in a foreign cell to have the same rank as a machine or
-interface in the local cell. This does not present a problem, because
-the Cache Manager only ever compares ranks for machines belonging to one cell
-at a time.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-file
-</B><DD>Specifies the full pathname of a file to which to write the preference
-ranks. If the specified file already exists, the command overwrites its
-contents. If the pathname is invalid, the command fails. If this
-argument is not provided, the preference ranks appear on the standard output
-stream.
-<P><DT><B>-numeric
-</B><DD>Displays the IP addresses of file server machine interfaces or VL Server
-machines, rather than their hostnames. If this argument is not
-provided, the <B>fs</B> command interpreter has the IP addresses
-translated to hostnames such as <B>fs1.abc.com</B>.
-<P><DT><B>-vlservers
-</B><DD>Displays preference ranks for VL Server machines rather than file server
-machine interfaces.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output consists of a separate line for each file server machine
-interface or VL Server machine, pairing the machine's hostname or IP
-address with its rank. The Cache Manager stores IP addresses in its
-kernel list of ranks, but the command by default identifies interfaces by
-hostname, by calling a translation routine that refers to either the
-cell's name service (such as the Domain Name Server) or the local host
-table. If an IP address appears in the output, it is because the
-translation attempt failed. To bypass the translation step and display
-IP addresses rather than hostnames, include the <B>-numeric</B>
-flag. This can significantly speed the production of output.
-<P>By default, the command writes to the standard output stream. Use
-the <B>-file</B> argument to write the output to a file instead.
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the local Cache Manager's preference
-ranks for file server machines. The local machine belongs to the AFS
-cell named <B>abc.com</B>, and in this example the ranks of file
-server machines in its local cell are lower than the ranks of file server
-machines from the foreign cell, <B>def.com</B>. It is not
-possible to translate the IP addresses of two machines on the 138.255
-network.
-<PRE> % <B>fs getserverprefs</B>
- fs2.abc.com 20007
- fs3.abc.com 30002
- fs1.abc.com 20011
- fs4.abc.com 30010
- server1.def.com 40002
- 138.255.33.34 40000
- server6.def.com 40012
- 138.255.33.37 40005
-
-</PRE>
-<P>The following example shows hows the output displays IP addresses when the
-<B>-numeric</B> flag is included, and illustrates how network proximity
-determines default ranks (as described on the <B>fs setserverprefs</B>
-reference page). The local machine has IP address
-192.12.107.210, and the two file server machines on its
-subnetwork have ranks of 20,007 and 20,011. The two file server
-machines on a different subnetwork of the local machine's network have
-higher ranks, 30,002 and 30,010, whereas the ranks of the remaining machines
-range from 40,000 to 40,012 because they are in a completely different
-network.
-<PRE> % <B>fs getserverprefs -numeric</B>
- 192.12.107.214 20007
- 192.12.105.99 30002
- 192.12.107.212 20011
- 192.12.105.100 30010
- 138.255.33.41 40002
- 138.255.33.34 40000
- 138.255.33.36 40012
- 138.255.33.37 40005
-
-</PRE>
-<P>The example shows how the <B>-vlservers</B> flag displays preference
-ranks for VL Server machines:
-<PRE> % <B>fs getserverprefs -vlservers</B>
- fs2.abc.com 10052
- fs3.abc.com 10113
- fs1.abc.com 10005
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf162.htm#HDRFS_SETSERVERPREFS">fs setserverprefs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf145.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf147.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf146.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf148.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_HELP" HREF="auarf002.htm#ToC_161">fs help</A></H2>
-<A NAME="IDX4851"></A>
-<A NAME="IDX4852"></A>
-<A NAME="IDX4853"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>fs</B> commands or lists functional
-descriptions of all <B>fs</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>fs</B> command.
-<P>To display every <B>fs</B> command whose name or short description
-includes a specified keyword, use the <B>fs apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>fs</B> part of the command name, providing only
-the operation code (for example, specify <B>setacl</B>, not <B>fs
-setacl</B>). If this argument is omitted, the output briefly
-describes every <B>fs</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>fs</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>fs
-setacl</B> command:
-<PRE> % <B>fs help setacl</B>
- fs setacl: set access control list
- aliases: sa
- Usage: fs setacl -dir <directory><SUP>+</SUP>
- -acl <access list entries><SUP>+</SUP> [-clear] [-negative] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf131.htm#HDRFS_INTRO">fs</A>
-<P><A HREF="auarf132.htm#HDRFS_APROPOS">fs apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf146.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf148.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf147.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf149.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_LISTACL" HREF="auarf002.htm#ToC_162">fs listacl</A></H2>
-<A NAME="IDX4854"></A>
-<A NAME="IDX4855"></A>
-<A NAME="IDX4856"></A>
-<A NAME="IDX4857"></A>
-<A NAME="IDX4858"></A>
-<A NAME="IDX4859"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays ACLs
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs listacl</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-id</B>] [<B>-if</B>] [<B>-help</B>]
-
-<B>fs la</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-id</B>] [<B>-if</B>] [<B>-h</B>]
-
-<B>fs lista</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-id</B>] [<B>-if</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs listacl</B> command displays the access control list (ACL)
-associated with each specified file, directory, or symbolic link. The
-specified element can reside in the DFS filespace if the issuer is using the
-AFS/DFS Migration Toolkit Protocol Translator to access DFS data (and DFS does
-implement per-file ACLs). To display the ACL of the current working
-directory, omit the <B>-path</B> argument.
-<P>To alter an ACL, use the <B>fs setacl</B> command. To copy an
-ACL from one directory to another, use the <B>fs copyacl</B>
-command. To remove obsolete entries from an ACL, use the <B>fs
-cleanacl</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>Placing a user or group on the <TT>Negative rights</TT> section of the
-ACL does not guarantee denial of permissions, if the <TT>Normal rights</TT>
-section grants the permissions to members of the
-<B>system:anyuser</B> group. In that case, the user needs
-only to issue the <B>unlog</B> command to obtain the permissions granted
-to the <B>system:anyuser</B> group.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each directory or file for which to display the ACL. For AFS
-files, the output displays the ACL from the file's parent directory;
-DFS files do have their own ACL. Incomplete pathnames are interpreted
-relative to the current working directory, which is also the default value if
-this argument is omitted.
-<P><DT><B>-id
-</B><DD>Displays the Initial Container ACL of each DFS directory. This
-argument is supported only on DFS directories accessed via the AFS/DFS
-Migration Toolkit Protocol Translator.
-<P><DT><B>-if
-</B><DD>Displays the Initial Object ACL of each DFS directory. This
-argument is supported only on DFS directories accessed via the AFS/DFS
-Migration Toolkit Protocol Translator.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of the output for each file, directory, or symbolic link
-reads as follows:
-<PRE> Access list for <VAR>directory</VAR> is
-
-</PRE>
-<P>If the issuer used shorthand notation in the pathname, such as the period
-(<B>.</B>) to represent the current current directory, that
-notation sometimes appears instead of the full pathname of the
-directory.
-<P>Next, the <TT>Normal rights</TT> header precedes a list of users and
-groups who are granted the indicated permissions, with one pairing of user or
-group and permissions on each line. If negative permissions have been
-assigned to any user or group, those entries follow a <TT>Negative
-rights</TT> header. The format of negative entries is the same as
-those on the <TT>Normal rights</TT> section of the ACL, but the user or
-group is denied rather than granted the indicated permissions.
-<P>AFS does not implement per-file ACLs, so for a file the command displays
-the ACL on its directory. The output for a symbolic link displays the
-ACL that applies to its target file or directory, rather than the ACL on the
-directory that houses the symbolic link.
-<P>The permissions for AFS enable the possessor to perform the indicated
-action:
-<DL>
-<P><DT><B><TT>a</TT>
-</B><DD>(<B>administer</B>): change the entries on the ACL
-<P><DT><B><TT>d</TT>
-</B><DD>(<B>delete</B>): remove files and subdirectories from the
-directory or move them to other directories
-<P><DT><B><TT>i</TT>
-</B><DD>(<B>insert</B>): add files or subdirectories to the directory by
-copying, moving or creating
-<P><DT><B><TT>k</TT>
-</B><DD>(<B>lock</B>): set read locks or write locks on the files in the
-directory
-<P><DT><B><TT>l</TT>
-</B><DD>(<B>lookup</B>): list the files and subdirectories in the
-directory, stat the directory itself, and issue the <B>fs listacl</B>
-command to examine the directory's ACL
-<P><DT><B><TT>r</TT>
-</B><DD>(<B>read</B>): read the contents of files in the directory;
-issue the <B>ls -l</B> command to stat the elements in the directory
-<P><DT><B><TT>w</TT>
-</B><DD>(<B>write</B>): modify the contents of files in the directory,
-and issue the UNIX <B>chmod</B> command to change their mode bits
-<P><DT><B><TT>A</TT>, <TT>B</TT>, <TT>C</TT>, <TT>D</TT>, <TT>E</TT>,
-<TT>F</TT>, <TT>G</TT>, <TT>H</TT>:
-</B><DD>Have no default meaning to the AFS server processes, but are made
-available for applications to use in controlling access to the
-directory's contents in additional ways. The letters must be
-uppercase.
-</DL>
-<P>For DFS files and directories, the permissions are similar, except that the
-DFS <B>x</B> (<B>execute</B>) permission replaces the AFS <B>l</B>
-(<B>lookup</B>) permission, DFS <B>c</B> (<B>control</B>) replaces
-AFS <B>a</B> (<B>administer</B>), and there is no DFS equivalent to
-the AFS <B>k</B> (<B>lock</B>) permission. The meanings of the
-various permissions also differ slightly, and DFS does not implement negative
-permissions. For a complete description of DFS permissions, see the DFS
-documentation and the <I>IBM AFS/DFS Migration Toolkit Administration Guide
-and Reference</I>.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the ACL on the home directory of the user
-<B>pat</B> (the current working directory), and on its <B>private</B>
-subdirectory.
-<PRE> % <B>fs listacl -path . private</B>
- Access list for . is
- Normal rights:
- system:authuser rl
- pat rlidwka
- pat:friends rlid
- Negative rights:
- smith rlidwka
- Access list for private is
- Normal rights:
- pat rlidwka
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>If the <B>-path</B> argument names an AFS directory, the issuer must
-have the <B>l</B> (<B>lookup</B>) permission on its ACL and the ACL
-for every directory that precedes it in the pathname.
-<P>If the <B>-path</B> argument names an AFS file, the issuer must have
-the <B>l</B> (<B>lookup</B>) and <B>r</B> (<B>read</B>)
-permissions on the ACL of the file's directory, and the <B>l</B>
-permission on the ACL of each directory that precedes it in the
-pathname.
-<P>If the <B>-path</B> argument names a DFS directory or file, the issuer
-must have the <B>x</B> (<B>execute</B>) permission on its ACL and on
-the ACL of each directory that precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf135.htm#HDRFS_CLEANACL">fs cleanacl</A>
-<P><A HREF="auarf136.htm#HDRFS_COPYACL">fs copyacl</A>
-<P><A HREF="auarf157.htm#HDRFS_SETACL">fs setacl</A>
-<P><I>IBM AFS/DFS Migration Toolkit Administration Guide and Reference</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf147.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf149.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf148.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf150.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_LISTCELLS" HREF="auarf002.htm#ToC_163">fs listcells</A></H2>
-<A NAME="IDX4860"></A>
-<A NAME="IDX4861"></A>
-<A NAME="IDX4862"></A>
-<A NAME="IDX4863"></A>
-<A NAME="IDX4864"></A>
-<A NAME="IDX4865"></A>
-<A NAME="IDX4866"></A>
-<A NAME="IDX4867"></A>
-<A NAME="IDX4868"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the database server machines in each cell known to the Cache
-Manager
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs listcells</B> [<B>-numeric</B>] [<B>-help</B>]
-
-<B>fs listc</B> [<B>-n</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs listcells</B> command formats and displays the list of the
-database server machines that the Cache Manager stores in kernel memory for
-its home cell and foreign cells.
-<P>At each reboot of the client machine, the Cache Manager copies the contents
-of <B>/usr/vice/etc/CellServDB</B> into kernel memory. To modify
-the list between reboots, use the <B>fs newcell</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-numeric
-</B><DD>Displays each database server machine's IP address rather than
-hostname.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes a line for each cell included in the Cache
-Manager's kernel memory list, in the following format:
-<PRE> Cell <VAR>cell</VAR> on hosts <VAR>database server machines</VAR>
-
-</PRE>
-<P>The Cache Manager stores IP addresses, but by default has them translated
-to hostnames before reporting them, by passing them to the cell's name
-service (such as the Domain Name Service or a local host table). The
-name service sometimes returns hostnames in uppercase letters, or an IP
-address if it cannot resolve a name.
-<P>Using the <B>-numeric</B> flag bypasses the translation to hostnames,
-which can result in significantly faster production of output. The
-output includes IP addresses only.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows output for several cells as illustrations of
-the different formats for machine names:
-<PRE> % <B>fs listcells</B>
- Cell abc.com on hosts fs1.abc.com fs2.abc.com fs3.abc.com
- Cell stateu.edu on hosts DB1.FS.STATEU.EDU
- DB2.FS.STATEU.EDU DB3.FS.STATEU.EDU
- Cell def.gov on hosts 138.255.0.2 sv3.def.gov
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf154.htm#HDRFS_NEWCELL">fs newcell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf148.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf150.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf149.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf151.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_LISTQUOTA" HREF="auarf002.htm#ToC_164">fs listquota</A></H2>
-<A NAME="IDX4869"></A>
-<A NAME="IDX4870"></A>
-<A NAME="IDX4871"></A>
-<A NAME="IDX4872"></A>
-<A NAME="IDX4873"></A>
-<A NAME="IDX4874"></A>
-<A NAME="IDX4875"></A>
-<A NAME="IDX4876"></A>
-<A NAME="IDX4877"></A>
-<A NAME="IDX4878"></A>
-<A NAME="IDX4879"></A>
-<A NAME="IDX4880"></A>
-<A NAME="IDX4881"></A>
-<A NAME="IDX4882"></A>
-<A NAME="IDX4883"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays quota information for the volume containing a file or
-directory.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs listquota</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs listq</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs lq</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs listquota</B> command displays information about the volume
-containing each specified directory or file (its name, quota, and amount of
-disk space used), along with an indicator of the percentage of space used on
-the host partition.
-<P>To display more information about the host partition, use the <B>fs
-examine</B> command.
-<P>To set volume quota, use the <B>fs setquota</B> or <B>fs setvol</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names a file or directory that resides in the volume about which to
-produce output. Partial pathnames are interpreted relative to the
-current working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays information about the volume that houses each specified
-directory or file, in a tabular format that uses the following headers:
-<DL>
-<P><DT><B><TT>Volume Name</TT>
-</B><DD>The name of the volume.
-<P><DT><B><TT>Quota</TT>
-</B><DD>The volume's quota in kilobytes, or the string <TT>no limit</TT> to
-indicate an unlimited quota.
-<P><DT><B><TT>Used</TT>
-</B><DD>The number of kilobytes of quota used.
-<P><DT><B><TT>% Used</TT>
-</B><DD>The percentage of the volume's quota that is used (the
-<TT>Used</TT> statistic divided by the <TT>Quota</TT> statistic, times
-100).
-<P><DT><B><TT>Partition</TT>
-</B><DD>The percentage of space used on the partition that houses the
-volume. Although not directly related to how much of the user's
-quota is used, it is reported because a full partition can cause writing of
-data back to the volume to fail even when the volume has not reached its
-quota.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the volume
-<B>user.smith</B>:
-<PRE> %<B> fs listquota -path /afs/abc.com/usr/smith</B>
- Volume Name Quota Used % Used Partition
- user.smith 15000 5071 34% 86%
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf137.htm#HDRFS_DISKFREE">fs diskfree</A>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P><A HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<P><A HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<P><A HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf149.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf151.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf150.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf152.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_LSMOUNT" HREF="auarf002.htm#ToC_165">fs lsmount</A></H2>
-<A NAME="IDX4884"></A>
-<A NAME="IDX4885"></A>
-<A NAME="IDX4886"></A>
-<A NAME="IDX4887"></A>
-<A NAME="IDX4888"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports the volume for which a directory is the mount point.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs lsmount -dir</B> <<VAR>directory</VAR>><SUP>+</SUP> [<B>-help</B>]
-
-<B>fs ls -d</B> <<VAR>directory</VAR>><SUP>+</SUP> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs lsmount</B> command reports the volume for which each
-specified directory is a mount point, or indicates with an error message that
-a directory is not a mount point or is not in AFS.
-<P>To create a mount point, use the <B>fs mkmount</B> command. To
-remove one, use the <B>fs rmmount</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dir
-</B><DD>Names the directory that serves as a mount point for a volume. The
-last element in the pathname provided must be an actual name, not a shorthand
-notation such as one or two periods (<B>.</B> or
-<B>..</B>).
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the specified directory is a mount point, the output is of the following
-form:
-<PRE> '<VAR>directory</VAR>' is a mount point for volume '<VAR>volume name</VAR>'
-
-</PRE>
-<P>where
-<UL>
-<P><LI>A number sign (<TT>#</TT>) precedes the <VAR>volume name</VAR> string for
-a regular mount point.
-<P><LI>A percent sign (<TT>%</TT>) precedes the <VAR>volume name</VAR> string for
-a read/write mount point.
-<P><LI>A cell name and colon (<TT>:</TT>) follow the number or percent
-sign and precede the <VAR>volume name</VAR> string for a cellular mount
-point.
-</UL>
-<P>The <B>fs mkmount</B> reference page explains how the Cache Manager
-interprets each of the three types of mount points.
-<P>If the directory is a symbolic link to a mount point, the output is of the
-form:
-<PRE> '<VAR>directory</VAR>' is a symbolic link, leading to a mount point for volume '<VAR>volume name</VAR>'
-
-</PRE>
-<P>If the directory is not a mount point or is not in AFS, the output
-reads:
-<PRE> '<VAR>directory</VAR>' is not a mount point.
-
-</PRE>
-<P>If the output is garbled, it is possible that the mount point has become
-corrupted in the local AFS client cache. Use the <B>fs
-flushmount</B> command to discard it, which forces the Cache Manager to
-refetch the mount point.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the mount point for the home directory of user
-<B>smith</B>:
-<PRE> % <B>fs lsmount /afs/abc.com/usr/smith</B>
- '/afs/abc.com/usr/smith' is a mount point for volume '#user.smith'
-
-</PRE>
-<P>The following example shows both the regular and read/write mount points
-for the ABC Corporation cell's <TT>root.cell</TT> volume.
-<PRE> % <B>fs lsmount /afs/abc.com</B>
- '/afs/abc.com' is a mount point for volume '#root.cell'
-
- % <B>fs lsmount /afs/.abc.com</B>
- '/afs/.abc.com' is a mount point for volume '%root.cell'
-
-</PRE>
-<P>The following example shows a cellular mount point: the State
-University cell's <TT>root.cell</TT> volume as mounted in the
-ABC Corporation cell's tree.
-<PRE> % <B>fs lsmount /afs/stateu.edu</B>
- '/afs/stateu.edu' is a mount point for volume '#stateu.edu:root.cell'
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-dir</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf141.htm#HDRFS_FLUSHMOUNT">fs flushmount</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf156.htm#HDRFS_RMMOUNT">fs rmmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf150.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf152.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf151.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf153.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_MESSAGES" HREF="auarf002.htm#ToC_166">fs messages</A></H2>
-<A NAME="IDX4889"></A>
-<A NAME="IDX4890"></A>
-<A NAME="IDX4891"></A>
-<A NAME="IDX4892"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets whether the Cache Manager writes log messages
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs messages</B> [<B>-show</B> <[<B>user</B>|<B>console</B>|<B>all</B>|<B>none</B>]>] [<B>-help</B>]
-
-<B>fs me</B> [<B>-s</B> <[<B>user</B>|<B>console</B>|<B>all</B>|<B>none</B>]>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs messages</B> command controls whether the Cache Manager
-displays status and warning messages on user screens, the client machine
-console, on both, or on neither.
-<P>There are two types of Cache Manager messages:
-<UL>
-<P><LI>User messages provide user-level status and warning information, and the
-Cache Manager directs them to user screens.
-<P><LI>Console messages provide system-level status and warning information, and
-the Cache Manager directs them to the client machine's designated
-console.
-</UL>
-<P>Disabling messaging completely is not recommended, because the messages
-provide useful status and warning information.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-show
-</B><DD>Specifies the types of messages to display. Choose one of the
-following values:
-<DL>
-<P><DT><B>user
-</B><DD>Send user messages to user screens
-<P><DT><B>console
-</B><DD>Send console messages to the console
-<P><DT><B>all
-</B><DD>Send user messages to user screens and console messages to the console
-(the default if the <B>-show</B> argument is omitted)
-<P><DT><B>none
-</B><DD>Do not send any messages to user screens or the console
-</DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command instructs the Cache Manager to display both types of
-messages:
-<PRE> % <B>fs messages -show all</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf151.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf153.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf152.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf154.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_MKMOUNT" HREF="auarf002.htm#ToC_167">fs mkmount</A></H2>
-<A NAME="IDX4893"></A>
-<A NAME="IDX4894"></A>
-<A NAME="IDX4895"></A>
-<A NAME="IDX4896"></A>
-<A NAME="IDX4897"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a mount point for a volume
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs mkmount -dir</B> <<VAR>directory</VAR>> <B>-vol</B> <<VAR>volume name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-rw</B>] [<B>-fast</B>] [<B>-help</B>]
-
-<B>fs mk -d</B> <<VAR>directory</VAR>> <B>-v</B> <<VAR>volume name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-r</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs mkmount</B> command creates a mount point for the volume
-named by the <B>-vol</B> argument at the location in the AFS file space
-specified by the <B>-dir</B> argument. The mount point looks like a
-standard directory element, and serves as the volume's root directory,
-but is actually a special file system object that refers to an AFS
-volume. When the Cache Manager first encounters a given mount point
-during pathname traversal, it contacts the VL Server to learn which file
-server machines house the indicated volume, then fetches a copy of the
-volume's root directory from the appropriate file server machine.
-<P>It is possible, although not recommended, to create more than one mount
-point to a volume. The Cache Manager can become confused if a volume is
-mounted in two places along the same path through the filespace.
-<P>The Cache Manager observes three basic rules as it traverses the AFS
-filespace and encounters mount points:
-<UL>
-<P><LI><B>Rule 1:</B> Access Backup and Read-only Volumes When
-Specified
-<P>When the Cache Manager encounters a mount point that specifies a volume
-with either a <B>.readonly</B> or a <B>.backup</B>
-extension, it accesses that type of volume only. If a mount point does
-not have either a <B>.backup</B> or <B>.readonly</B>
-extension, the Cache Manager uses Rules 2 and 3.
-<P>For example, the Cache Manager never accesses the read/write version of a
-volume if the mount point names the backup version. If the specified
-version is inaccessible, the Cache Manager reports an error.
-<P><LI><B>Rule 2:</B> Follow the Read-only Path When Possible
-<P>If a mount point resides in a read-only volume and the volume that it
-references is replicated, the Cache Manager attempts to access a read-only
-copy of the volume; if the referenced volume is not replicated, the Cache
-Manager accesses the read/write copy. The Cache Manager is thus said to
-prefer a <I>read-only path</I> through the filespace, accessing read-only
-volumes when they are available.
-<P>The Cache Manager starts on the read-only path in the first place because
-it always accesses a read-only copy of the <B>root.afs</B> volume
-if it exists; the volume is mounted at the root of a cell's AFS
-filespace (named <B>/afs</B> by convention). That is, if the
-<B>root.afs</B> volume is replicated, the Cache Manager attempts to
-access a read-only copy of it rather than the read/write copy. This
-rule then keeps the Cache Manager on a read-only path as long as each
-successive volume is replicated. The implication is that both the
-<B>root.afs</B> and <B>root.cell</B> volumes must be
-replicated for the Cache Manager to access replicated volumes mounted below
-them in the AFS filespace. The volumes are conventionally mounted at
-the <B>/afs</B> and <B>/afs/</B><VAR>cellname</VAR> directories,
-respectively.
-<P><LI><B>Rule 3:</B> Once on a Read/write Path, Stay There
-<P>If a mount point resides in a read/write volume and the volume name does
-not have a <B>.readonly</B> or a <B>.backup</B>
-extension, the Cache Manager attempts to access only the a read/write version
-of the volume. The access attempt fails with an error if the read/write
-version is inaccessible, even if a read-only version is accessible. In
-this situation the Cache Manager is said to be on a <I>read/write path</I>
-and cannot switch back to the read-only path unless mount point explicitly
-names a volume with a <B>.readonly</B> extension. (Cellular
-mount points are an important exception to this rule, as explained in the
-following discussion.
-</UL>
-<P>There are three types of mount points, each appropriate for a different
-purpose because of the manner in which the Cache Manager interprets
-them.
-<UL>
-<P><LI>When the Cache Manager crosses a <I>regular</I> mount point, it obeys
-all three of the mount point traversal rules previously described. To
-create a regular mount point, include only the required <B>-dir</B> and
-<B>-vol</B> arguments to the <B>fs mkmount</B> command.
-<A NAME="IDX4898"></A>
-<A NAME="IDX4899"></A>
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">A regular mount point does not force the Cache Manager always to access
-read-only volumes (it is explicitly not a "read-only mount point"). If
-a volume is not replicated, the third traversal rule means that the Cache
-Manager still accesses the read/write volume when that is the only type
-available. However, if the Cache Manager is to access the read-only
-version of a replicated volume named by a regular mount point, all volumes
-that are mounted above it in the pathname must also be replicated.
-</TD></TR></TABLE>
-<P><LI>When the Cache Manager crosses a <I>read/write</I> mount point, it
-attempts to access only the volume version named in the mount point. If
-the volume name is the base (read/write) form, without a
-<B>.readonly</B> or <B>.backup</B> extension, the Cache
-Manager accesses the read/write version of the volume, even if it is
-replicated. In other words, the Cache Manager disregards the second
-mount point traversal rule when crossing a read/write mount point: it
-switches to the read/write path through the filespace.
-<A NAME="IDX4900"></A>
-<A NAME="IDX4901"></A>
-<P>To create a read/write mount point, include the <B>-rw</B> flag on the
-<B>fs mkmount</B> command. It is conventional to create only one
-read/write mount point in a cell's filespace, using it to mount the
-cell's <B>root.cell</B> volume just below the AFS filespace
-root (by convention, <B>/afs/.</B><VAR>cellname</VAR>). See
-the <I>IBM AFS Quick Beginnings</I> for instructions and the chapter about
-volume management in the <I>IBM AFS Administration Guide</I> for further
-discussion.
-<P>Creating a read/write mount point for a read-only or backup volume is
-acceptable, but unnecessary. The first rule of mount point traversal
-already specifies that the Cache Manager accesses them if the volume name in a
-regular mount point has a <B>.readonly</B> or
-<B>.backup</B> extension.
-<P><LI>When the Cache Manager crosses a <I>cellular</I> mount point, it
-accesses the indicated volume in the specified cell, which is normally a
-foreign cell. (If the mount point does not name a cell along with the
-volume, the Cache Manager accesses the volume in the cell where the mount
-point resides.) The Cache Manager disregards the third mount point
-traversal rule when crossing a regular cellular mount point: it accesses
-a read-only version of the volume if it is replicated, even if the volume that
-houses the mount point is read/write. Switching to the read-only path
-in this way is designed to avoid imposing undue load on the file server
-machines in foreign cells.
-<A NAME="IDX4902"></A>
-<A NAME="IDX4903"></A>
-<A NAME="IDX4904"></A>
-<P>To create a regular cellular mount point, include the <B>-cell</B>
-argument on the <B>fs mkmount</B> command. It is conventional to
-create cellular mount points only at the second level in a cell's
-filespace, using them to mount foreign cells' <B>root.cell</B>
-volumes just below the AFS filespace root (by convention, at
-<B>/afs/</B><VAR>foreign_cellname</VAR>). The mount point enables
-local users to access the foreign cell's filespace, assuming they have
-the necessary permissions on the ACL of the volume's root directory and
-that there is an entry for the foreign cell in each local client
-machine's <B>/usr/vice/etc/CellServDB</B> file. In the output
-of the <B>fs lsmount</B> command, the cell name and a colon
-(<TT>:</TT>) appear between the initial number sign and the volume
-name in a regular cellular mount point name.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dir
-</B><DD>Names the directory to create as a mount point. The directory must
-not already exist. Relative pathnames are interpreted with respect to
-the current working directory.
-<P>Specify the read/write path to the directory, to avoid the failure that
-results from attempting to create a new mount point in a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>Description</B> section of this reference page.
-<P><DT><B>-vol
-</B><DD>Specifies the name or volume ID number of the volume to mount. If
-appropriate, add the <TT>.readonly</TT> or <TT>.backup</TT>
-extension to the name, or specify the appropriate volume ID number.
-<P><DT><B>-cell
-</B><DD>Names the cell in which the volume resides (creates a cellular mount
-point). Provide the fully qualified domain name, or a shortened form
-that disambiguates it from the other cells listed in the local
-<B>/usr/vice/etc/CellServDB</B> file.
-<P>If this argument is omitted, no cell indicator appears in the mount
-point. When the Cache Manager interprets it, it assumes that the volume
-named in the mount point resides in the same cell as the volume that houses
-the mount point.
-<P><DT><B>-rw
-</B><DD>Creates a read/write mount point. Omit this flag to create a
-regular mount point.
-<P><DT><B>-fast
-</B><DD>Prevents the Volume Location (VL) Server from checking that the volume has
-a VLDB entry and printing a warning message if it does not. Whether or
-not this flag is included, the File Server creates the mount point even when
-the volume has no VLDB entry.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command creates a regular mount point, mounting the volume
-<B>user.smith</B> at
-<B>/afs/abc.com/usr/smith</B>:
-<PRE> % <B>cd /afs/abc.com/usr</B>
-
- %<B> fs mkmount -dir smith -vol user.smith</B>
-
-</PRE>
-<P>The following commands create a read/write mount point and a regular mount
-point for the ABC Corporation cell's <TT>root.cell</TT> volume
-in that cell's file tree. The second command follows the
-convention of putting a period at the beginning of the read/write mount
-point's name.
-<PRE> % <B>fs mkmount -dir /afs/abc.com -vol root.cell</B>
-
- %<B> fs mkmount -dir /afs/.abc.com -vol root.cell -rw</B>
-
-</PRE>
-<P>The following command mounts the State University cell's
-<TT>root.cell</TT> volume in the ABC Corporation cell's file
-tree, creating a regular cellular mount point called
-<B>/afs/stateu.edu</B>. When a ABC Corporation Cache Manager
-encounters this mount point, it crosses into the State University cell on a
-read-only path.
-<PRE> % <B>fs mkmount -dir /afs/stateu.edu -vol root.cell -c stateu.edu</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>i</B> (<B>insert</B>) and <B>a</B>
-(<B>administer</B>) permissions on the ACL of the directory that is to
-house the mount point.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf151.htm#HDRFS_LSMOUNT">fs lsmount</A>
-<P><A HREF="auarf156.htm#HDRFS_RMMOUNT">fs rmmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf152.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf154.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf153.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf155.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_NEWCELL" HREF="auarf002.htm#ToC_168">fs newcell</A></H2>
-<A NAME="IDX4905"></A>
-<A NAME="IDX4906"></A>
-<A NAME="IDX4907"></A>
-<A NAME="IDX4908"></A>
-<A NAME="IDX4909"></A>
-<A NAME="IDX4910"></A>
-<A NAME="IDX4911"></A>
-<A NAME="IDX4912"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes the kernel-resident list of a cell's database server machines
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs newcell -name</B> <<VAR>cell name</VAR>> <B>-servers</B> <<VAR>primary servers</VAR>><SUP>+</SUP>
- [<B>-linkedcell</B> <<VAR>linked cell name</VAR>>] [<B>-help</B>]
-
-<B>fs n -n</B> <<VAR>cell name</VAR>> <B>-s</B> <<VAR>primary servers</VAR>><SUP>+</SUP> [<B>-l</B> <<VAR>linked cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs newcell</B> command removes the Cache Manager's
-kernel-resident list of database server machines for the cell specified by the
-<B>-name</B> argument and replaces it with the database server machines
-named by the <B>-servers</B> argument.
-<P>Each time the machine reboots, the Cache Manager constructs the kernel list
-of cells and database server machines by reading the local
-<B>/usr/vice/etc/CellServDB</B> file. This command does not change
-the <B>CellServDB</B> file, so any changes made with it persist only until
-the next reboot, unless the issuer also edits the file. The output of
-the <B>fs listcells</B> command reflects changes made with this command,
-because that command consults the kernel-resident list rather than the
-<B>CellServDB</B> file.
-<P>This command can introduce a completely new cell into the kernel-resident
-list, but cannot make a cell inaccessible (it is not possible to remove a
-cell's entry from the kernel-resident list by providing no values for the
-<B>-server</B> argument). To make a cell inaccessible, remove its
-entry from the <B>CellServDB</B> file and reboot the machine.
-<P>If the <B>-name</B> argument names a DCE cell, then the
-<B>-servers</B> argument names DFS Fileset Location (FL) Server
-machines. The <B>-linkedcell</B> argument specifies the name of the
-AFS cell to link to a DCE cell for the purpose of DFS fileset location.
-Refer to the <I>IBM AFS/DFS Migration Toolkit Administration Guide and
-Reference</I> for more information on linking AFS clients to DCE cells using
-this command or by editing the <B>/usr/vice/etc/CellServDB</B>
-file.
-<P><STRONG>Cautions</STRONG>
-<P>Some commands, such as the <B>klog</B> command, work correctly only
-when the information is accurate for a cell in both the <B>CellServDB</B>
-file and the kernel-resident list.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies the fully-qualified cell name of the AFS or DCE cell.
-<P><DT><B>-servers
-</B><DD>Specifies the fully-qualified hostnames of all AFS database server
-machines or DFS Fileset Location (FL) Server machines for the cell named by
-the <B>-name</B> argument. If FL Server machines are specified, the
-local machine must be running the AFS/DFS Migration Toolkit Protocol
-Translator.
-<P><DT><B>-linkedcell
-</B><DD>Specifies the name of the AFS cell to link to a DCE cell for the purpose
-of DFS fileset location.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example changes the machine's kernel-resident list of
-database server machines for the ABC Corporation cell to include the machines
-<B>db1.abc.com</B> and
-<B>db2.abc.com</B>:
-<PRE> % <B>fs newcell -name abc.com -servers db1.abc.com db2.abc.com</B>
-
-</PRE>
-<P>The following example links the DCE cell
-<B>dce.abc.com</B> to the AFS cell
-<B>abc.com</B>. The AFS client contacts the Fileset Location
-(FL) servers <B>db1.dce.abc.com</B> and
-<B>db2.dce.abc.com</B> for fileset location
-information as it interprets a DFS pathname.
-<PRE> % <B>fs newcell -name dce.abc.com -servers db1.dce.abc.com db2.dce.abc.com</B> \
- <B>-linkedcell abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf149.htm#HDRFS_LISTCELLS">fs listcells</A>
-<P><I>IBM AFS/DFS Migration Toolkit Administration Guide and Reference</I>
-<P><I>IBM AFS/DFS Migration Toolkit Administration Installation and
-Configuration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf153.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf155.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf154.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf156.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_QUOTA" HREF="auarf002.htm#ToC_169">fs quota</A></H2>
-<A NAME="IDX4913"></A>
-<A NAME="IDX4914"></A>
-<A NAME="IDX4915"></A>
-<A NAME="IDX4916"></A>
-<A NAME="IDX4917"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the percentage of quota used in the volume containing a directory
-or file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs quota</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs q</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs quota</B> command displays the percent of quota consumed in
-the volume that contains each specified directory or file.
-<P>To display more detailed information about the volume and the partition it
-resides on, use the <B>fs examine</B> and <B>fs listquota</B>
-commands.
-<P>To set volume quota, use the <B>fs setquota</B> or <B>fs setvol</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each file or directory for which to display the quota consumed in
-its parent volume. Partial pathnames are interpreted relative to the
-current working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output reports the percent of volume quota used, in the following
-format:
-<PRE> <VAR>percent</VAR>% of quota used.
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command lists the percent quota used of the volume housing
-the current working directory:
-<PRE> %<B> fs quota</B>
- 17% of quota used.
-
-</PRE>
-<P>The following command lists the percent quota used of both the volume
-housing the current working directory's parent directory and the volume
-housing the directory <B>/afs/abc.com/usr/smith</B>:
-<PRE> % <B>fs quota -path .. /afs/abc.com/usr/smith</B>
- 43% of quota used.
- 92% of quota used.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>l</B> (<B>lookup</B>) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the <B>-path</B> argument, and on the ACL of each directory that
-precedes it in the pathname.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P><A HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<P><A HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<P><A HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf154.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf156.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf155.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf157.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_RMMOUNT" HREF="auarf002.htm#ToC_170">fs rmmount</A></H2>
-<A NAME="IDX4918"></A>
-<A NAME="IDX4919"></A>
-<A NAME="IDX4920"></A>
-<A NAME="IDX4921"></A>
-<A NAME="IDX4922"></A>
-<A NAME="IDX4923"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a mount point
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs rmmount -dir</B> <<VAR>directory</VAR>><SUP>+</SUP> [<B>-help</B>]
-
-<B>fs rm -d</B> <<VAR>directory</VAR>><SUP>+</SUP> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs rmmount</B> command removes the mount point named by the
-<B>-dir</B> argument from the file system. The corresponding volume
-remains on its host partition or partitions, but is inaccessible if there are
-no other mount points for it.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dir
-</B><DD>Names the mount point to delete from the file system. The last
-element in the pathname must be an actual name, not a shorthand notation such
-as "dot" (.) or "dot dot" (. .).
-<P>Specify the read/write path to the directory, to avoid the failure that
-results from attempting to delete a mount point from a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the mount points <B>jones</B> and
-<B>terry</B> from the current working directory (the
-<B>/afs/abc.com/usr</B> directory).
-<PRE> % <B>fs rmmount jones terry</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>d</B> (<B>delete</B>) permission on the
-ACL of the directory that houses each mount point.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf151.htm#HDRFS_LSMOUNT">fs lsmount</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf155.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf157.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf156.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf158.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETACL" HREF="auarf002.htm#ToC_171">fs setacl</A></H2>
-<A NAME="IDX4924"></A>
-<A NAME="IDX4925"></A>
-<A NAME="IDX4926"></A>
-<A NAME="IDX4927"></A>
-<A NAME="IDX4928"></A>
-<A NAME="IDX4929"></A>
-<A NAME="IDX4930"></A>
-<A NAME="IDX4931"></A>
-<A NAME="IDX4932"></A>
-<A NAME="IDX4933"></A>
-<A NAME="IDX4934"></A>
-<A NAME="IDX4935"></A>
-<A NAME="IDX4936"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the ACL for a directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setacl -dir</B> <<VAR>directory</VAR>><SUP>+</SUP> <B>-acl</B> <<VAR>access list entries</VAR>><SUP>+</SUP>
- [<B>-clear</B>] [<B>-negative</B>] [<B>-id</B>] [<B>-if</B>] [<B>-help</B>]
-
-<B>fs sa -d</B> <<VAR>directory</VAR>><SUP>+</SUP> <B>-a</B> <<VAR>access list entries</VAR>><SUP>+</SUP>
- [<B>-c</B>] [<B>-n</B>] [<B>-id</B>] [<B>-if</B>] [<B>-h</B>]
-
-<B>fs seta -d</B> <<VAR>directory</VAR>><SUP>+</SUP> <B>-a</B> <<VAR>access list entries</VAR>><SUP>+</SUP>
- [<B>-c</B>] [<B>-n</B>] [<B>-id</B>] [<B>-if</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setacl</B> command adds the access control list (ACL) entries
-specified with the <B>-acl</B> argument to the ACL of each directory named
-by the <B>-dir</B> argument.
-<P>If the <B>-dir</B> argument designates a pathname in DFS filespace
-(accessed via the AFS/DFS Migration Toolkit Protocol Translator), it can be a
-file as well as a directory. The ACL must already include an entry for
-<B>mask_obj</B>, however. For more details, refer to the <I>IBM
-AFS/DFS Migration Toolkit Administration Guide and Reference</I>.
-<P>Only user and group entries are acceptable values for the <B>-acl</B>
-argument. Do not place machine entries (IP addresses) directly on an
-ACL; instead, make the machine entry a group member and place the group
-on the ACL.
-<P>To completely erase the existing ACL before adding the new entries, provide
-the <B>-clear</B> flag. To add the specified entries to the
-<TT>Negative</TT> <TT>rights</TT> section of the ACL (deny rights to
-specified users or groups), provide the <B>-negative</B> flag.
-<P>To display an ACL, use the <B>fs listacl</B> command. To copy an
-ACL from one directory to another, use the <B>fs copyacl</B>
-command.
-<P><STRONG>Cautions</STRONG>
-<P>If the ACL already grants certain permissions to a user or group, the
-permissions specified with the <B>fs setacl</B> command replace the
-existing permissions, rather than being added to them.
-<P>Setting negative permissions is generally unnecessary and not
-recommended. Simply omitting a user or group from the <TT>Normal</TT>
-<TT>rights</TT> section of the ACL is normally adequate to prevent
-access. In particular, note that it is futile to deny permissions that
-are granted to members of the <B>system:anyuser</B> group on the
-same ACL; the user needs only to issue the <B>unlog</B> command to
-receive the denied permissions.
-<P>When including the <B>-clear</B> option, be sure to reinstate an entry
-for each directory's owner that includes at least the <B>l</B>
-(<B>lookup</B>) permission. Without that permission, it is
-impossible to resolve the "dot" ( . ) and "dot dot" ( . .
-) shorthand from within the directory. (The directory's owner does
-implicitly have the <B>a</B> [<B>administer</B>] permission even on a
-cleared ACL, but must know to use it to add other permissions.)
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dir
-</B><DD>Names each AFS directory, or DFS directory or file, for which the set the
-ACL. Partial pathnames are interpreted relative to the current working
-directory.
-<P>Specify the read/write path to each directory (or DFS file), to avoid the
-failure that results from attempting to change a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-acl
-</B><DD>Defines a list of one or more ACL entries, each a pair that names
-<UL>
-<P><LI>A user name or group name as listed in the Protection Database
-<P><LI>One or more ACL permissions, indicated either by combining the individual
-letters or by one of the four acceptable shorthand words
-</UL>
-<P>
-<P>in that order, separated by a space (thus every instance of this argument
-has two parts). The accepted AFS abbreviations and shorthand words, and
-the meaning of each, are as follows:
-<DL>
-<P><DT><B>a
-</B><DD>(<B>administer</B>): change the entries on the ACL
-<P><DT><B>d
-</B><DD>(<B>delete</B>): remove files and subdirectories from the
-directory or move them to other directories
-<P><DT><B>i
-</B><DD>(<B>insert</B>): add files or subdirectories to the directory by
-copying, moving or creating
-<P><DT><B>k
-</B><DD>(<B>lock</B>): set read locks or write locks on the files in the
-directory
-<P><DT><B>l
-</B><DD>(<B>lookup</B>): list the files and subdirectories in the
-directory, stat the directory itself, and issue the <B>fs listacl</B>
-command to examine the directory's ACL
-<P><DT><B>r
-</B><DD>(<B>read</B>): read the contents of files in the directory;
-issue the <B>ls -l</B> command to stat the elements in the directory
-<P><DT><B>w
-</B><DD>(<B>write</B>): modify the contents of files in the directory,
-and issue the UNIX <B>chmod</B> command to change their mode bits
-<P><DT><B>A, B, C, D, E, F, G, H
-</B><DD>Have no default meaning to the AFS server processes, but are made
-available for applications to use in controlling access to the
-directory's contents in additional ways. The letters must be
-uppercase.
-<P><DT><B>all
-</B><DD>Equals all seven permissions (<B>rlidwka</B>).
-<A NAME="IDX4937"></A>
-<A NAME="IDX4938"></A>
-<A NAME="IDX4939"></A>
-<A NAME="IDX4940"></A>
-<P><DT><B>none
-</B><DD>No permissions. Removes the user/group from the ACL, but does not
-guarantee they have no permissions if they belong to groups that remain on the
-ACL.
-<A NAME="IDX4941"></A>
-<A NAME="IDX4942"></A>
-<P><DT><B>read
-</B><DD>Equals the <B>r</B> (<B>read</B>) and <B>l</B>
-(<B>lookup</B>) permissions.
-<A NAME="IDX4943"></A>
-<A NAME="IDX4944"></A>
-<P><DT><B>write
-</B><DD>Equals all permissions except <B>a</B> (<B>administer</B>), that
-is, <B>rlidwk</B>.
-<A NAME="IDX4945"></A>
-<A NAME="IDX4946"></A>
-</DL>
-<P>
-<P>It is acceptable to mix entries that combine the individual letters with
-entries that use the shorthand words, but not use both types of notation
-within an individual pairing of user or group and permissions.
-<P>To learn the proper format and acceptable values for DFS ACL entries, see
-the <I>IBM AFS/DFS Migration Toolkit Administration Guide and
-Reference</I>.
-<P><DT><B>-clear
-</B><DD>Removes all existing entries on each ACL before adding the entries
-specified with the <B>-acl</B> argument.
-<P><DT><B>-negative
-</B><DD>Places the specified ACL entries in the <TT>Negative</TT>
-<TT>rights</TT> section of each ACL, explicitly denying the rights to the
-user or group, even if entries on the accompanying <TT>Normal</TT>
-<TT>rights</TT> section of the ACL grant them permissions.
-<P>This argument is not supported for DFS files or directories, because DFS
-does not implement negative ACL permissions.
-<P><DT><B>-id
-</B><DD>Places the ACL entries on the Initial Container ACL of each DFS directory,
-which are the only file system objects for which this flag is
-supported.
-<P><DT><B>-if
-</B><DD>Places the ACL entries on the Initial Object ACL of each DFS directory,
-which are the only file system objects for which this flag is
-supported.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example adds two entries to the <TT>Normal rights</TT>
-section of the current working directory's ACL: the first entry
-grants <B>r</B> (<B>read</B>) and <B>l</B> (<B>lookup</B>)
-permissions to the group <B>pat:friends</B>, while the other (using
-the <B>write</B> shorthand) gives all permissions except <B>a</B>
-(<B>administer</B>) to the user <B>smith</B>.
-<PRE> % <B>fs setacl -dir . -acl pat:friends rl smith write</B>
-
- % <B>fs listacl -path </B>.
- Access list for . is
- Normal rights:
- pat:friends rl
- smith rlidwk
-
-</PRE>
-<P>The following example includes the <B>-clear</B> flag, which removes
-the existing permissions (as displayed with the <B>fs listacl</B> command)
-from the current working directory's <B>reports</B> subdirectory and
-replaces them with a new set.
-<PRE> % <B>fs listacl -dir reports</B>
- Access list for reports is
- Normal rights:
- system:authuser rl
- pat:friends rlid
- smith rlidwk
- pat rlidwka
- Negative rights:
- terry rl
-
- % <B>fs setacl -clear -dir reports -acl pat all smith write system:anyuser rl</B>
-
- % <B>fs listacl -dir reports</B>
- Access list for reports is
- Normal rights:
- system:anyuser rl
- smith rlidwk
- pat rlidwka
-
-</PRE>
-<P>The following example use the <B>-dir</B> and <B>-acl</B> switches
-because it sets the ACL for more than one directory (both the current working
-directory and its <B>public</B> subdirectory).
-<PRE> % <B>fs setacl -dir . public -acl pat:friends rli</B>
-
- % <B>fs listacl -path . public</B>
- Access list for . is
- Normal rights:
- pat rlidwka
- pat:friends rli
- Access list for public is
- Normal rights:
- pat rlidwka
- pat:friends rli
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>a</B> (<B>administer</B>) permission on
-the directory's ACL; the directory's owner and the members of
-the <B>system:administrators</B> group have the right implicitly,
-even if it does not appear on the ACL.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf136.htm#HDRFS_COPYACL">fs copyacl</A>
-<P><A HREF="auarf148.htm#HDRFS_LISTACL">fs listacl</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><I>IBM AFS/DFS Migration Toolkit Administration Guide and Reference</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf156.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf158.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf157.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf159.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETCACHESIZE" HREF="auarf002.htm#ToC_172">fs setcachesize</A></H2>
-<A NAME="IDX4947"></A>
-<A NAME="IDX4948"></A>
-<A NAME="IDX4949"></A>
-<A NAME="IDX4950"></A>
-<A NAME="IDX4951"></A>
-<A NAME="IDX4952"></A>
-<A NAME="IDX4953"></A>
-<A NAME="IDX4954"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the size of the disk cache
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setcachesize</B> [<B>-blocks</B> <<VAR>size in 1K byte blocks (0 => reset)</VAR>>]
- [<B>-reset</B>] [<B>-help</B>]
-
-<B>fs setca</B> [<B>-b</B> <<VAR>size in 1K byte blocks (0 => reset)</VAR>>] [<B>-r</B>] [<B>-h</B>]
-
-<B>fs cachesize</B> [<B>-b</B> <<VAR>size in 1K byte blocks (0 => reset)</VAR>>] [<B>-r</B>] [<B>-h</B>]
-
-<B>fs ca</B> [<B>-b</B> <<VAR>size in 1K byte blocks (0 => reset)</VAR>>] [<B>-r</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setcachesize</B> command changes the number of kilobyte
-blocks of local disk space available to the Cache Manager for its data cache,
-on machines that use a disk cache. The command is not operative on
-machines that use a memory cache.
-<P>To return the cache size to the default value specified in the third field
-of the local <B>/usr/vice/etc/cacheinfo</B> file, provide a value of
-<B>0</B> to the <B>-blocks</B> argument.
-<P>To return the cache size to the value set when the machine was last
-rebooted, use the <B>-reset</B> flag instead of the <B>-blocks</B>
-argument. This is normally the amount specified in the
-<B>cacheinfo</B> file, unless the <B>-blocks</B> argument was included
-on the <B>afsd</B> command to override the <B>cacheinfo</B>
-value.
-<P>To display the current cache size and amount of cache in use, for both disk
-and memory caches, use the <B>fs getcacheparms</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>This command is not operative on machines using a memory cache, and results
-in an error message. To change memory cache size, edit the
-<B>cacheinfo</B> file and reboot, or reboot and provide the
-<B>-blocks</B> argument to the <B>afsd</B> command.
-<P>On machines using a disk cache, do not set the cache size to exceed 85% to
-90% of the actual disk space available for the cache directory. The
-cache implementation itself requires a small amount of space on the
-partition.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-blocks
-</B><DD>Specifies the number of one-kilobyte blocks of disk space available for
-the Cache Manager to devote to the cache. Provide a value of
-<B>0</B> to set cache size to the default specified in the
-<B>cacheinfo</B> file.
-<P><DT><B>-reset
-</B><DD>Returns the cache size to the value set when the machine was last
-booted. This agrees with the value in the <B>cacheinfo</B> file
-unless the <B>-blocks</B> argument was used on the <B>afsd</B>
-command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command sets the disk cache size to 25000 kilobyte
-blocks.
-<PRE> % <B>fs setcachesize -blocks 25000</B>
-
-</PRE>
-<P>Both of the following commands reset the disk cache size to the value in
-the <B>cacheinfo</B> file, assuming that the <B>-blocks</B> argument
-to the <B>afsd</B> command was not used.
-<PRE> % <B>fs setcachesize -blocks 0</B>
-
- % <B>fs setcachesize -reset</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf043.htm#HDRCACHEINFO">cacheinfo</A>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf143.htm#HDRFS_GETCACHEPARMS">fs getcacheparms</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf157.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf159.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf158.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf160.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETCELL" HREF="auarf002.htm#ToC_173">fs setcell</A></H2>
-<A NAME="IDX4955"></A>
-<A NAME="IDX4956"></A>
-<A NAME="IDX4957"></A>
-<A NAME="IDX4958"></A>
-<A NAME="IDX4959"></A>
-<A NAME="IDX4960"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Allows or disallows running of setuid programs from specified cells
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setcell -cell</B> <<VAR>cell name</VAR>><SUP>+</SUP> [<B>-suid</B>] [<B>-nosuid</B>] [<B>-help</B>]
-
-<B>fs setce -c</B> <<VAR>cell name</VAR>><SUP>+</SUP> [<B>-s</B>] [<B>-n</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setcell</B> command sets whether the Cache Manager allows
-programs (and other executable files) from each cell named by the
-<B>-cell</B> argument to run with setuid permission. By default,
-the Cache Manager allows programs from its home cell to run with setuid
-permission, but not programs from any foreign cells. A program belongs
-to the same cell as the file server machine that houses the volume in which
-the program's binary file resides, as specified in the file server
-machine's <B>/usr/afs/etc/ThisCell</B> file. The Cache Manager
-determines its own home cell by reading the <B>/usr/vice/etc/ThisCell</B>
-file at initialization.
-<P>To enable programs from each specified cell to run with setuid permission,
-include the <B>-suid</B> flag. To prohibit programs from running
-with setuid permission, include the <B>-nosuid</B> flag, or omit both
-flags.
-<P>The <B>fs setcell</B> command directly alters a cell's setuid
-status as recorded in kernel memory, so rebooting the machine is
-unnecessary. However, non-default settings do not persist across
-reboots of the machine unless the appropriate <B>fs setcell</B> command
-appears in the machine's AFS initialization file.
-<P>To display a cell's setuid status, issue the <B>fs
-getcellstatus</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>AFS does not recognize effective UID: if a setuid program accesses
-AFS files and directories, it does so using the current AFS identity of the
-AFS user who initialized the program, not of the program's owner.
-Only the local file system recognizes effective UID.
-<P>Only members of the <B>system:administrators</B> group can turn
-on the setuid mode bit on an AFS file or directory.
-<P>When the setuid mode bit is turned on, the UNIX <B>ls -l</B> command
-displays the third user mode bit as an <TT>s</TT> instead of an
-<TT>x</TT>. However, the <TT>s</TT> does not appear on an AFS file
-or directory unless setuid permission is enabled for the cell in which the
-file resides.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Names each cell for which to set setuid status. Provide the fully
-qualified domain name, or a shortened form that disambiguates it from the
-other cells listed in the local <B>/usr/vice/etc/CellServDB</B>
-file.
-<P><DT><B>-suid
-</B><DD>Allows programs from each specified cell to run with setuid
-privilege. Provide it or the <B>-nosuid</B> flag, or omit both
-flags to disallow programs from running with setuid privilege.
-<P><DT><B>-nosuid
-</B><DD>Prevents programs from each specified cell from running with setuid
-privilege. Provide it or the <B>-suid</B> flag, or omit both flags
-to disallow programs form running with setuid privilege.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command enables executable files from the State University
-cell to run with setuid privilege on the local machine:
-<PRE> % <B>fs setcell -cell stateu.edu -suid</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf144.htm#HDRFS_GETCELLSTATUS">fs getcellstatus</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf158.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf160.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf159.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf161.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETCLIENTADDRS" HREF="auarf002.htm#ToC_174">fs setclientaddrs</A></H2>
-<A NAME="IDX4961"></A>
-<A NAME="IDX4962"></A>
-<A NAME="IDX4963"></A>
-<A NAME="IDX4964"></A>
-<A NAME="IDX4965"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the client interfaces to register with the File Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setclientaddrs</B> [<B>-address</B> <<VAR>client network interfaces</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs setcl</B> [<B>-a</B> <<VAR>client network interfaces</VAR>><SUP>+</SUP>] [<B>-h</B>]
-
-<B>fs sc</B> [<B>-a</B> <<VAR>client network interfaces</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setclientaddrs</B> command defines the IP addresses of the
-interfaces that the local Cache Manager registers with a File Server when
-first establishing a connection to it.
-<P>The File Server uses the addresses when it initiates a remote procedure
-call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by
-the Cache Manager). There are two common circumstances in which the
-File Server initiates RPCs: when it breaks callbacks and when it pings
-the client machine to verify that the Cache Manager is still
-accessible.
-<P>The list of interfaces specified with this command replaces the list that
-the Cache Manager constructs and records in kernel memory as it
-initializes. At that time, if the file <B>/usr/vice/etc/NetInfo</B>
-exists on the client machine's local disk, the Cache Manager uses its
-contents as the basis for the list of interfaces addresses. If the file
-does not exist, the Cache Manager instead uses the network interfaces
-configured with the operating system. It then removes from the list any
-address included in the local <B>/usr/vice/etc/NetRestrict</B>
-file. It records the final list in kernel memory. (An
-administrator must create the <B>NetInfo</B> and <B>NetRestrict</B>
-files; there are no default versions of them.)
-<P>If an RPC to that interface fails, the File Server simultaneously sends
-RPCs to all of the other interfaces in the list, to learn which of them are
-still available. Whichever interface replies first is the one to which
-the File Server then sends pings and RPCs to break callbacks.
-<P>To list the interfaces that the Cache Manager is currently registering with
-File Servers, use the <B>fs getclientaddrs</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>The list specified with this command persists in kernel memory only until
-the client machine reboots. To preserve it across reboots, either list
-the interfaces in the local <B>/usr/vice/etc/NetInfo</B> file, or place
-the appropriate <B>fs setclientaddrs</B> command in the machine's AFS
-initialization script.
-<P>Changes made with this command do not propagate automatically to File
-Servers to which the Cache Manager has already established a
-connection. To force such File Servers to use the revised list, either
-reboot each file server machine, or change the <B>NetInfo</B> file and
-reboot the client machine.
-<P>The <B>fs</B> command interpreter verifies that each of the addresses
-specified as a value for the <B>-address</B> argument is actually
-configured with the operating system on the client machine. If it is
-not, the command fails with an error message that marks the address as a
-<TT>Nonexistent</TT> <TT>interface</TT>.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-address
-</B><DD>Specifies each IP address to place in the list of interfaces, in dotted
-decimal format. Hostnames are not acceptable. Separate each
-address with one or more spaces.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The message
-<PRE> Adding <VAR>interface</VAR>
-
-</PRE>
-<P>confirms that each new interface was added to the Cache Manager's
-list. The address appears in hexadecimal format to match the notation
-used in the File Server log, <B>/usr/afs/logs/FileLog</B>.
-<P><STRONG>Examples</STRONG>
-<P>The following example sets the two interfaces that the Cache Manager
-registers with File Servers.
-<PRE> % <B>fs setclientaddrs 191.255.105.68 191.255.108.84</B>
- Adding 0xbfff6944
- Adding 0xbfff6c54
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf024.htm#HDRCLI_NETINFO">NetInfo (client version)</A>
-<P><A HREF="auarf026.htm#HDRCLI_NETRESTRICT">NetRestrict (client version)</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf145.htm#HDRFS_GETCLIENTADDRS">fs getclientaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf159.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf161.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf160.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf162.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETQUOTA" HREF="auarf002.htm#ToC_175">fs setquota</A></H2>
-<A NAME="IDX4966"></A>
-<A NAME="IDX4967"></A>
-<A NAME="IDX4968"></A>
-<A NAME="IDX4969"></A>
-<A NAME="IDX4970"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the maximum quota for the volume containing a file or directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setquota</B> [<B>-path</B> <<VAR>dir/file path</VAR>>] <B>-max</B> <<VAR>max quota in kbytes</VAR>> [<B>-help</B>]
-
-<B>fs setq</B> [<B>-p</B> <<VAR>dir/file path</VAR>>] <B>-m</B> <<VAR>max quota in kbytes</VAR>> [<B>-h</B>]
-
-<B>fs sq</B> [<B>-p</B> <<VAR>dir/file path</VAR>>] <B>-m</B> <<VAR>max quota in kbytes</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setquota</B> command sets the quota (maximum possible size)
-of the read/write volume that contains the directory or file named by the
-<B>-path</B> argument.
-<P>To set the quota on multiple volumes at the same time, use the <B>fs
-setvol</B> command.
-<P>To display a volume's quota, use the <B>fs examine</B>, <B>fs
-listquota</B> or <B>fs quota</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names the directory or file for which to set the host volume's
-quota. Partial pathnames are interpreted relative to the current
-working directory, which is also the default value if this argument is
-omitted.
-<P>Specify the read/write path to the file or directory, to avoid the failure
-that results from attempting to change a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-max
-</B><DD>Sets the maximum amount of file server disk space the volume can
-occupy. Specify the number of one-kilobyte blocks as a positive integer
-(<B>1024</B> is one megabyte). A value of <B>0</B> sets an
-unlimited quota, but the size of the disk partition that houses the volume
-places an absolute limit on the volume's size.
-<P>If the <B>-path</B> argument is omitted (to set the quota of the volume
-housing the current working directory), the <B>-max</B> switch must be
-included with this argument.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command imposes a maximum quota of 3000 kilobytes on the
-volume that houses the <B>/afs/abc.com/usr/smith</B>
-directory:
-<PRE> % <B>fs setquota -path /afs/abc.com/usr/smith -max 3000</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B>
-group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P><A HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<P><A HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf163.htm#HDRFS_SETVOL">fs setvol</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf160.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf162.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf161.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf163.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETSERVERPREFS" HREF="auarf002.htm#ToC_176">fs setserverprefs</A></H2>
-<A NAME="IDX4971"></A>
-<A NAME="IDX4972"></A>
-<A NAME="IDX4973"></A>
-<A NAME="IDX4974"></A>
-<A NAME="IDX4975"></A>
-<A NAME="IDX4976"></A>
-<A NAME="IDX4977"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the Cache Manager's preference ranks for file server or VL Server
-machines
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setserverprefs</B> [<B>-servers</B> <<VAR>fileserver names and ranks</VAR>><SUP>+</SUP>]
- [<B>-vlservers</B> <<VAR>VL server names and ranks</VAR>><SUP>+</SUP>]
- [<B>-file</B> <<VAR>input from named file</VAR>>] [<B>-stdin</B>] [<B>-help</B>]
-
-<B>fs sets</B> [<B>-se</B> <<VAR>fileserver names and ranks</VAR>><SUP>+</SUP>] [<B>-vl</B> <<VAR>VL server names and ranks</VAR>><SUP>+</SUP>]
- [<B>-f</B> <<VAR>input from named file</VAR>>] [<B>-st</B>] [<B>-h</B>]
-
-<B>fs sp</B> [<B>-se</B> <<VAR>fileserver names and ranks</VAR>><SUP>+</SUP>] [<B>-vl</B> <<VAR>VL server names and ranks></VAR><SUP>+</SUP>]
- [<B>-f</B> <<VAR>input from named file</VAR>>] [<B>-st</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setserverprefs</B> command sets the local Cache
-Manager's preference ranks for one or more file server machine interfaces
-or, if the <B>-vlserver</B> argument is provided, for Volume Location (VL)
-Server machines. For file server machines, the numerical ranks
-determine the order in which the Cache Manager attempts to contact the
-interfaces of machines that are housing a volume. For VL Server
-machines, the ranks determine the order in which the Cache Manager attempts to
-contact a cell's VL Servers when requesting VLDB information.
-<P>The <B>fs getserverprefs</B> reference page explains how the Cache
-Manager uses preference ranks when contacting file server machines or VL
-Server machines. The following paragraphs explain how the Cache Manager
-calculates default ranks, and how to use this command to change the
-defaults.
-<P><B>Calculation of Default Preference Ranks</B>
-<P>The Cache Manager stores a preference rank in kernel memory as a paired IP
-address and numerical rank. If a file server machine is multihomed, the
-Cache Manager assigns a distinct rank to each of the machine's addresses
-(up to the number of addresses that the VLDB can store per machine, which is
-specified in the <I>IBM AFS Release Notes</I>). Once calculated, a
-rank persists until the machine reboots, or until this command is used to
-change it.
-<P>The Cache Manager sets default VL Server preference ranks as it
-initializes, randomly assigning a rank from the range 10,000 to 10,126 to each
-of the machines listed in the local <B>/usr/vice/etc/CellServDB</B>
-file. Machines from different cells can have the same rank, but this
-does not present a problem because the Cache Manager consults only one
-cell's ranks at a time.
-<P>The Cache Manager sets default preference ranks for file server machine as
-it fetches volume location information from the VLDB. Each time it
-learns about file server machine interfaces for which it has not already set
-ranks, it assigns a rank to each interface. If the local client machine
-has only one IP address, the Cache Manager compares it to the server
-interface's IP address and sets a rank according to the following
-algorithm. If the client machine is multihomed, the Cache Manager
-applies the algorithm to each of the client machine's addresses and
-assigns to the file server machine interface the lowest rank that
-results.
-<UL>
-<P><LI>If the local machine is a file server machine, the base rank for each of
-its interfaces is 5,000.
-<P><LI>If the file server machine interface is on the same subnetwork as the
-client interface, its base rank is 20,000.
-<P><LI>If the file server machine interface is on the same network as the client
-interface, or is at the distant end of a point-to-point link with the client
-interface, its base rank is 30,000.
-<P><LI>If the file server machine interface is on a different network than the
-client interface, or the Cache Manager cannot obtain network information about
-it, its base rank is 40,000.
-</UL>
-<P>After assigning a base rank to a file server machine interface, the Cache
-Manager adds to it a number randomly chosen from the range 0 (zero) to
-14. As an example, a file server machine interface in the same
-subnetwork as the local machine receives a base rank of 20,000, but the Cache
-Manager records the actual rank as an integer between 20,000 and
-20,014. This process reduces the number of interfaces that have exactly
-the same rank. As with VL Server machine ranks, it is possible for file
-server machine interfaces from foreign cells to have the same rank as
-interfaces in the local cell, but this does not present a problem. Only
-the relative ranks of the interfaces that house a given volume are relevant,
-and AFS only supports storage of a volume in one cell at a time.
-<P><B>Setting Non-default Preference Ranks</B>
-<P>Use the <B>fs setserverprefs</B> command to reset an existing
-preference rank, or to set the initial rank of a file server machine interface
-or VL Server machine for which the Cache Manager has no rank. To make a
-rank persist across a reboot of the local machine, place the appropriate
-<B>fs setserverprefs</B> command in the machine's AFS initialization
-file.
-<P>Specify each preference rank as a pair of values separated by one or more
-spaces:
-<UL>
-<P><LI>The first member of the pair is the fully-qualified hostname (for example,
-<B>fs1.abc.com</B>), or the IP address in dotted decimal
-format, of a file server machine interface or VL Server machine
-<P><LI>The second member of the pair is an integer. The possible ranks
-range from <B>1</B> through <B>65535</B>.
-</UL>
-<P>As with default ranks, the Cache Manager adds a randomly chosen integer to
-a rank specified by this command. For file server machine interfaces,
-the integer is from the range 0 (zero) to 14; for VL Server machines, it
-is from the range 0 (zero) to 126. For example, if the administrator
-assigns a rank of 15,000 to a file server machine interface, the Cache Manager
-stores an integer between 15,000 to 15,014.
-<P>There are several ways to provide ranks for file server machine interfaces
-(but not for VL Server machines):
-<UL>
-<P><LI>On the command line, following the <B>-servers</B> argument.
-<P><LI>In a file named by the <B>-file</B> argument. Place each pair
-on its own line in the file. Directing the output from the <B>fs
-getserverprefs</B> command to a file automatically generates a file with the
-proper format.
-<P><LI>Via the standard input stream, by providing the <B>-stdin</B>
-flag. This method enables the issuer to feed in values directly from a
-program or script that generates preference ranks by using an algorithm
-appropriate to the local cell. The AFS distribution does not include
-such programs or scripts.
-</UL>
-<P>When setting file server machine preference ranks, it is legal to combine
-the <B>-servers</B>, <B>-file</B>, and <B>-stdin</B> options on a
-single command line. If different options specify a different rank for
-the same interface, the Cache Manager stores and uses the rank assigned with
-the <B>-servers</B> argument.
-<P>The <B>-vlservers</B> argument is the only way to assign VL Server
-machine ranks. It can be combined with one or more of the
-<B>-servers</B>, <B>-file</B>, and <B>-stdin</B> options, but the
-Cache Manager applies the values provided for those options to file server
-machine ranks only.
-<P>The <B>fs</B> command interpreter does not verify hostnames or IP
-addresses, and so assigns preference ranks to invalid machine names or
-addresses. The Cache Manager never uses such ranks unless the same
-incorrect information is in the VLDB.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-servers
-</B><DD>Specifies one or more file server machine preference ranks. Each
-rank pairs the fully-qualified hostname or IP address (in dotted decimal
-format) of a file server machine's interface with an integer rank,
-separated by one or more spaces; also separate each pair with one or more
-spaces. Acceptable values for the rank range from <B>1</B> through
-<B>65521</B>; a lower value indicates a greater preference.
-Providing ranks outside this range can have unpredictable results.
-Providing a value no larger than <B>65521</B> guarantees that the rank
-does not exceed the maximum possible value of 65,535 even if the largest
-random factor (14) is added.
-<P>This argument can be combined with the <B>-file</B> argument,
-<B>-stdin</B> flag, or both. If more than one of the arguments sets
-a rank for the same interface, the rank set by this argument takes
-precedence. It can also be combined with the <B>-vlservers</B>
-argument, but does not interact with it.
-<P><DT><B>-vlservers
-</B><DD>Specifies one or more VL Server preference ranks. Each rank pairs
-the fully-qualified hostname or IP address (in dotted decimal format) of a VL
-Server machine with an integer rank, separated by one or more spaces;
-also separate each pair with one or more spaces. Acceptable values for
-the rank range from <B>1</B> through <B>65521</B>; a lower value
-indicates a greater preference. Providing ranks outside this range can
-have unpredictable results. Providing a value no larger than
-<B>65521</B> guarantees that the rank does not exceed the maximum possible
-value of 65,535 even if the largest random factor (14) is added.
-<P>This argument can be combined with the <B>-servers</B> argument,
-<B>-file</B> argument, <B>-stdin</B> flag, or any combination of the
-three, but does not interact with any of them. They apply only to file
-server machine ranks.
-<P><DT><B>-file
-</B><DD>Specifies the full pathname of a file from which to read pairs of file
-server machine interfaces and their ranks, using the same notation and range
-of values as for the <B>-servers</B> argument. In the file, place
-each pair on its own line and separate the two parts of each pair with one or
-more spaces.
-<P>This argument can be combined with the <B>-servers</B> argument,
-<B>-stdin</B> flag, or both. If more than one of the arguments sets
-a rank for the same interface, the rank set by the <B>-server</B> argument
-takes precedence. It can also be combined with the
-<B>-vlservers</B> argument, but does not interact with it.
-<P><DT><B>-stdin
-</B><DD>Reads pairs of file server machine interface and integer rank from the
-standard input stream. The intended use is to accept input piped in
-from a user-defined program or script that generates ranks in the appropriate
-format, but it also accepts input typed to the shell. Format the
-interface and rank pairs as for the <B>-file</B> argument. If
-typing at the shell, type <B><Ctrl-d></B> after the final newline to
-complete the input.
-<P>This argument can be combined with the <B>-servers</B> argument, the
-<B>-file</B> argument, or both. If more than one of the arguments
-sets a rank for the same interface, the rank set by the <B>-server</B>
-argument takes precedence. It can also be combined with the
-<B>-vlservers</B> argument, but does not interact with it.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command sets the Cache Manager's preference ranks for
-the file server machines named <B>fs3.abc.com</B> and
-<B>fs4.abc.com</B>, the latter of which is specified by its
-IP address, 192.12.105.100. The machines reside in
-another subnetwork of the local machine's network, so their default base
-rank is 30,000. To increase the Cache Manager's preference for
-these machines, the issuer assigns a rank of <B>25000</B>, to which the
-Cache Manager adds an integer in the range from 0 to 15.
-<PRE> # <B>fs setserverprefs -servers fs3.abc.com 25000 192.12.105.100 25000</B>
-
-</PRE>
-<P>The following command uses the <B>-servers</B> argument to set the
-Cache Manager's preference ranks for the same two file server machines,
-but it also uses the <B>-file</B> argument to read a collection of
-preference ranks from a file that resides in the local file
-<B>/etc/fs.prefs</B>:
-<PRE> # <B>fs setserverprefs -servers fs3.abc.com 25000 192.12.105.100 25000</B> \
- <B>-file /etc/fs.prefs</B>
-
-</PRE>
-<P>The <B>/etc/fs.prefs</B> file has the following contents and
-format:
-<PRE> 192.12.108.214 7500
- 192.12.108.212 7500
- 138.255.33.41 39000
- 138.255.33.34 39000
- 128.0.45.36 41000
- 128.0.45.37 41000
-
-</PRE>
-<P>The following command uses the <B>-stdin</B> flag to read preference
-ranks from the standard input stream. The ranks are piped to the
-command from a program, <B>calc_prefs</B>, which was written by the issuer
-to calculate preferences based on values significant to the local cell.
-<PRE> # <B>calc_prefs | fs setserverprefs -stdin</B>
-
-</PRE>
-<P>The following command uses the <B>-vlservers</B> argument to set the
-Cache Manager's preferences for the VL server machines named
-<B>fs1.abc.com</B>, <B>fs3.abc.com</B>,
-and <B>fs4.abc.com</B> to base ranks of 1, 11000, and 65521,
-respectively:
-<PRE> # <B>fs setserverprefs -vlservers fs1.abc.com 1 fs3.abc.com 11000</B> \
- <B>fs4.abc.com 65521</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf146.htm#HDRFS_GETSERVERPREFS">fs getserverprefs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf161.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf163.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf162.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf164.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SETVOL" HREF="auarf002.htm#ToC_177">fs setvol</A></H2>
-<A NAME="IDX4978"></A>
-<A NAME="IDX4979"></A>
-<A NAME="IDX4980"></A>
-<A NAME="IDX4981"></A>
-<A NAME="IDX4982"></A>
-<A NAME="IDX4983"></A>
-<A NAME="IDX4984"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Set maximum quota and messages for the volume containing a file or
-directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs setvol</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-max</B> <<VAR>disk space quota in 1K units</VAR>>]
- [<B>-offlinemsg</B> <<VAR>offline message</VAR>>] [<B>-help</B>]
-
-<B>fs setv</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-ma</B> <<VAR>disk space quota in 1K units</VAR>>]
- [<B>-o</B> <<VAR>offline message</VAR>>] [<B>-h</B>]
-
-<B>fs sv</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-ma</B> <<VAR>disk space quota in 1K units</VAR>>]
- [<B>-o</B> <<VAR>offline message</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs setvol</B> command sets the quota (maximum possible size) of
-the read/write volume that contains each directory or file named by the
-<B>-path</B> argument. To associate a message with the volume which
-then appears in the output of the <B>fs examine</B> command, include the
-<B>-offlinemsg</B> argument.
-<P>To display all of the settings made with this command, use the <B>fs
-examine</B> command. The <B>fs listquota</B> command reports a
-fileset's quota, and the <B>fs quota</B> command the percent of quota
-used.
-<P>To set quota on one volume at a time, use the <B>fs setquota</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each file or directory for which to set the host volume's quota
-and offline message. Partial pathnames are interpreted relative to the
-current working directory, which is also the default value if this argument is
-omitted.
-<P>Specify the read/write path to the file or directory, to avoid the failure
-that results from attempting to change a read-only volume. By
-convention, the read/write path is indicated by placing a period before the
-cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-max
-</B><DD>Sets the maximum amount of file server disk space the volume can
-occupy. Provide a positive integer to indicate the number of
-one-kilobyte blocks (<B>1024</B> is one megabyte). A value of
-<B>0</B> sets an unlimited quota, but the size of the disk partition that
-houses the volume places an absolute limit on the volume's size.
-<P>If the <B>-path</B> argument is omitted (so that the command sets the
-quota of the volume housing the current working directory), the
-<B>-max</B> switch must be provided.
-<P><DT><B><B>-offlinemsg</B>
-</B><DD>Associates a message with the volume which then appears in the output of
-the <B>fs examine</B> command. Its intended use is to explain why
-the volume is currently offline.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command imposes a 6500 kilobyte quota on the volumes mounted
-at the home directories <B>/afs/abc.com/usr/smith</B> and
-<B>/afs/abc.com/usr/pat</B>:
-<PRE> % <B>cd /afs/abc.com/usr</B>
-
- % <B>fs setvol -path smith pat -max 6500</B><B></B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B>
-group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf138.htm#HDRFS_EXAMINE">fs examine</A>
-<P><A HREF="auarf150.htm#HDRFS_LISTQUOTA">fs listquota</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf155.htm#HDRFS_QUOTA">fs quota</A>
-<P><A HREF="auarf161.htm#HDRFS_SETQUOTA">fs setquota</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf162.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf164.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf163.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf165.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_STOREBEHIND" HREF="auarf002.htm#ToC_178">fs storebehind</A></H2>
-<A NAME="IDX4985"></A>
-<A NAME="IDX4986"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Enables asynchronous writes to the file server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs storebehind</B> [<B>-kbytes</B> <<VAR>asynchrony for specified names</VAR>>]
- [<B>-files</B> <<VAR>specific pathnames</VAR>><SUP>+</SUP>]
- [<B>-allfiles</B> <<VAR>new default (KB)</VAR>>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>fs st</B> [<B>-k</B> <<VAR>asynchrony for specified names</VAR>>] [<B>-f</B> <<VAR>specific pathnames</VAR>><SUP>+</SUP>]
- [<B>-a</B> <<VAR>new default (KB)</VAR>>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs storebehind</B> command enables the Cache Manager to perform
-a delayed asynchronous write to the File Server when an application closes a
-file. By default, the Cache Manager writes all data to the File Server
-immediately and synchronously when an application program closes a
-file--that is, the <B>close</B> system call does not return until the
-Cache Manager has actually transferred the final chunk of the file to the File
-Server. This command specifies the number of kilobytes of a file that
-can still remain to be written to the File Server when the Cache Manager
-returns control to the application. It is useful if users working on
-the machine commonly work with very large files, but also introduces the
-complications discussed in the <B>Cautions</B> section.
-<P>Set either or both of the following in a single command:
-<UL>
-<P><LI>To set a value that applies to all AFS files manipulated by applications
-running on the machine, use the <B>-allfiles</B> argument. This
-value is termed the <I>default store asynchrony</I> for the machine, and
-persists until the machine reboots. If it is not set, the default value
-is zero, indicating that the Cache Manager performs synchronous writes.
-<P>
-<P>As an example, the following setting means that when an application closes
-a file, the Cache Manager can return control to the application as soon as no
-more than 10 kilobytes of the file remain to be written to the File
-Server.
-<PRE> <B>-allfiles 10</B>
-
-</PRE>
-<P><LI>To set a value that applies to one or more individual files, and overrides
-the value of the <B>-allfiles</B> argument for them, combine the
-<B>-kbytes</B> and <B>-files</B> arguments. The setting
-persists as long as there is an entry for the file in the kernel table that
-the Cache Manager uses to track certain information about files. In
-general, such an entry persists at least until an application closes the file
-or exits, but the Cache Manager is free to recycle the entry if the file is
-inactive and it needs to free up slots in the table. To increase the
-certainty that there is an entry for the file in the table, issue the <B>fs
-storebehind</B> command shortly before closing the file.
-<P>As an example, the following setting means that when an application closes
-either of the files <B>bigfile</B> and <B>biggerfile</B>, the Cache
-Manager can return control to the application as soon as no more than a
-megabyte of the file remains to be written to the File Server.
-<PRE> <B>-kbytes 1024 -files bigfile biggerfile</B>
-
-</PRE>
-<P>Note that once an explicit value has been set for a file, the only way to
-make it subject to the default store asynchrony once again is to set
-<B>-kbytes</B> to that value. In other words, there is no
-combination of arguments that automatically makes a file subject to the
-default store asynchrony once another value has been set for the file.
-</UL>
-<P>To display the settings that currently apply to individual files or to all
-files, provide the command's arguments in certain combinations as
-specified in the <B>Output</B> section of this reference page.
-<P><STRONG>Cautions</STRONG>
-<P>For the following reasons, use of this command is not recommended in most
-cases.
-<P>In normal circumstances, an asynchronous setting results in the Cache
-Manager returning control to applications earlier than it otherwise does, but
-this is not guaranteed.
-<P>If a delayed write fails, there is no way to notify the application, since
-the <B>close</B> system call has already returned with a code indicating
-success.
-<P>Writing asynchronously increases the possibility that the user will not
-notice if a write operation makes the volume that houses the file exceed its
-quota. As always, the portion of the file that exceeds the
-volume's quota is lost, which prompts a message such as the
-following:
-<PRE> No space left on device
-
-</PRE>
-<P>To avoid losing data, it is advisable to verify that the volume housing the
-file has space available for the amount of data anticipated to be
-written.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-kbytes
-</B><DD>Specifies the number of kilobytes of data from each file named by the
-<B>-files</B> argument that can remain to be written to the file server
-when the Cache Manager returns control to an application program that closed
-the file. The <B>-files</B> argument is required along with this
-argument. Provide an integer from the range <B>0</B> (which
-reinstates the Cache Manager's default behavior or writing synchronously)
-to the maximum AFS file size.
-<P><DT><B>-files
-</B><DD>Names each file to which the value set with the <B>-kbytes</B>
-argument applies. The setting persists as long as there is an entry for
-the file in the kernel table that the Cache Manager uses to track certain
-information about files. Because closing a file generally erases the
-entry, when reopening a file the only way to guarantee that the setting still
-applies is to reissue the command. If this argument is provided without
-the <B>-kbytes</B> argument, the command reports the current setting for
-the specified files, and the default store asynchrony.
-<P><DT><B>-allfiles
-</B><DD>Sets the default store asynchrony for the local machine, which is the
-number of kilobytes of data that can remain to be written to the file server
-when the Cache Manager returns control to the application program that closed
-a file. The value applies to all AFS files manipulated by applications
-running on the machine, except those for which settings have been made with
-the <B>-kbytes</B> and <B>-files</B> arguments. Provide an
-integer from the range <B>0</B> (which indicates the default of
-synchronous writes) to the maximum AFS file size.
-<P><DT><B>-verbose
-</B><DD>Produces output confirming the settings made with the accompanying
-<B>-kbytes</B> and <B>-files</B> arguments, the <B>-allfiles</B>
-argument, or all three. If provided by itself, reports the current
-default store asynchrony.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If none of the command's options are included, or if only the
-<B>-verbose</B> flag is included, the following message reports the
-default store asynchrony (the setting that applies to all files manipulated by
-applications running on the local machine and for which not more specific
-asynchrony is set).
-<PRE> Default store asynchrony is <VAR>x</VAR> kbytes.
-
-</PRE>
-<P>A value of <TT>0</TT> (zero) indicates synchronous writes and is the
-default if no one has included the <B>-allfiles</B> argument on this
-command since the machine last rebooted.
-<P>If the <B>-files</B> argument is provided without the
-<B>-kbytes</B> argument, the output reports the value that applies to each
-specified file along with the default store asynchrony. If a particular
-value has previously been set for a file, the following message reports
-it:
-<PRE> Will store up to <VAR>y</VAR> kbytes of <VAR>file</VAR> asynchronously.
- Default store asynchrony is <VAR>x</VAR> kbytes.
-
-</PRE>
-<P>If the default store asynchrony applies to a file because no explicit
-<B>-kbytes</B> value has been set for it, the message is instead as
-follows:
-<PRE> Will store <VAR>file</VAR> according to default.
- Default store asynchrony is <VAR>x</VAR> kbytes.
-
-</PRE>
-<P>If the <B>-verbose</B> flag is combined with arguments that set values
-(<B>-files</B> and <B>-kbytes</B>, or <B>-allfiles</B>, or all
-three), there is a message that confirms immediately that the setting has
-taken effect. When included without other arguments or flags, the
-<B>-verbose</B> flag reports the default store asynchrony only.
-<P><STRONG>Examples</STRONG>
-<P>The following command enables the Cache Manager to return control to the
-application program that closed the file <B>test.data</B> when 100
-kilobytes still remain to be written to the File Server. The
-<B>-verbose</B> flag produces output that confirms the new setting, and
-that the default store asynchrony is zero.
-<PRE> % <B>fs storebehind -kbytes 100 -files test.data -verbose</B>
- Will store up to 100 kbytes of test.data asynchronously.
- Default store asynchrony is 0 kbytes.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To include the <B>-allfiles</B> argument, the issuer must be logged in
-as the local superuser <B>root</B>.
-<P>To include the <B>-kbytes</B> and <B>-files</B> arguments, the
-issuer must either be logged in as the local superuser <B>root</B> or have
-the <B>w</B> (<B>write</B>) permission on the ACL of each file's
-directory.
-<P>To view the current settings (by including no arguments, the
-<B>-file</B> argument alone, or the <B>-verbose</B> argument alone),
-no privilege is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf163.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf165.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf164.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf166.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_SYSNAME" HREF="auarf002.htm#ToC_179">fs sysname</A></H2>
-<A NAME="IDX4987"></A>
-<A NAME="IDX4988"></A>
-<A NAME="IDX4989"></A>
-<A NAME="IDX4990"></A>
-<A NAME="IDX4991"></A>
-<A NAME="IDX4992"></A>
-<A NAME="IDX4993"></A>
-<A NAME="IDX4994"></A>
-<A NAME="IDX4995"></A>
-<A NAME="IDX4996"></A>
-<A NAME="IDX4997"></A>
-<A NAME="IDX4998"></A>
-<A NAME="IDX4999"></A>
-<A NAME="IDX5000"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports or sets the CPU/operating system type
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs sysname</B> [<B>-newsys</B> <<VAR>new sysname</VAR>>] [<B>-help</B>]
-
-<B>fs sy</B> [<B>-n</B> <<VAR>new sysname</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs sysname</B> command sets or displays the local machine's
-CPU/operating system type as recorded in kernel memory. The Cache
-Manager substitutes the string for the <VAR>@sys</VAR> variable which can occur
-in AFS pathnames; the <I>IBM AFS Quick Beginnings</I> and <I>IBM
-AFS Administration Guide</I> explain how using <VAR>@sys</VAR> can simplify
-cell configuration. It is best to use it sparingly, however, because it
-can make the effect of changing directories unpredictable.
-<P>The command always applies to the local machine only. If issued on
-an NFS client machine accessing AFS via the NFS/AFS Translator, the string is
-set or reported for the NFS client machine. The Cache Manager on the
-AFS client machine serving as the NFS client's NFS/AFS translator machine
-stores the value in its kernel memory, and so can provide the NFS client with
-the proper version of program binaries when the user issues commands for which
-the pathname to the binaries includes <I>@sys</I>. There is a
-separate record for each user logged into the NFS client, which implies that
-if a user adopts a new identity (UNIX UID) during a login session on the NFS
-client--perhaps by using the UNIX <B>su</B> command--he or she
-must verify that the correct string is set for the new identity also.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-newsys
-</B><DD>Sets the CPU/operating system indicator string for the local
-machine. If this argument is omitted, the output displays the current
-setting instead. AFS uses a standardized set of strings; consult
-the <I>IBM AFS Quick Beginnings</I> or <I>AFS Release
-Notes</I>.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>When the <B>-newsys</B> argument is omitted, the output reports the
-machine's system type in the following format:
-<PRE> Current sysname is '<VAR>system_type</VAR>'
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output produced on a Sun SPARCStation
-running Solaris 5.7:
-<PRE> % <B>fs sysname</B>
- Current sysname is 'sun4x_57'
-
-</PRE>
-<P>The following command defines a machine to be a IBM RS/6000 running AIX
-4.2:
-<PRE> % <B>fs sysname -newsys rs_aix42</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To display the current setting, no privilege is required. To include
-the <B>-newsys</B> argument on an AFS client machine, the issuer must be
-logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf139.htm#HDRFS_EXPORTAFS">fs exportafs</A>
-<P><A HREF="auarf234.htm#HDRSYS">sys</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf164.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf166.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf165.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf167.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_WHEREIS" HREF="auarf002.htm#ToC_180">fs whereis</A></H2>
-<A NAME="IDX5001"></A>
-<A NAME="IDX5002"></A>
-<A NAME="IDX5003"></A>
-<A NAME="IDX5004"></A>
-<A NAME="IDX5005"></A>
-<A NAME="IDX5006"></A>
-<A NAME="IDX5007"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports the name of each file server machine housing a file or directory
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs whereis</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs whe</B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs whereis</B> command returns the name of each file server
-machine that houses the volume containing each directory or file named by the
-<B>-path</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each AFS file or directory for which to return the host file server
-machine. Partial pathnames are interpreted relative to the current
-working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes a line for each specified directory or file. It
-names the file server machine on which the volume that houses the specified
-directory or file resides. A list of multiple machines indicates that
-the directory or file is in a replicated volume.
-<P>Machine names usually have a suffix indicating their cell
-membership. If the cell is not clear, use the <B>fs whichcell</B>
-command to display the cell in which the directory or file resides. To
-display the cell membership of the local machine, use the <B>fs wscell</B>
-command.
-<P><STRONG>Examples</STRONG>
-<P>The following example indicates that volume housing the directory
-<B>/afs/abc.com</B> resides is replicated on both
-<B>fs1.abc.com</B> and
-<B>fs3.abc.com</B>:
-<PRE> % <B>fs whereis -path /afs/abc.com</B>
- File /afs/abc.com is on hosts fs1.abc.com fs3.abc.com
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf167.htm#HDRFS_WHICHCELL">fs whichcell</A>
-<P><A HREF="auarf168.htm#HDRFS_WSCELL">fs wscell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf165.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf167.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf166.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf168.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_WHICHCELL" HREF="auarf002.htm#ToC_181">fs whichcell</A></H2>
-<A NAME="IDX5008"></A>
-<A NAME="IDX5009"></A>
-<A NAME="IDX5010"></A>
-<A NAME="IDX5011"></A>
-<A NAME="IDX5012"></A>
-<A NAME="IDX5013"></A>
-<A NAME="IDX5014"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Returns the name of the cell to which a file or directory belongs
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs whichcell</B> [<B>-path</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fs whi </B> [<B>-p</B> <<VAR>dir/file path</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs whichcell</B> command returns the name of the cell in which
-the volume that houses each indicated directory or file resides.
-<P>To display the file server machine on which the volume housing a directory
-or file resides, use the <B>fs whichcell</B> command. To display
-the cell membership of the local machine, use the <B>fs wscell</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-path
-</B><DD>Names each AFS file or directory for which to return the cell
-membership. Partial pathnames are interpreted relative to the current
-working directory, which is also the default value if this argument is
-omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes a line for each directory or file, naming the cell to
-which the volume that houses the directory or file resides.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows that the current working directory resides in a
-volume in the ABC Corporation cell:
-<PRE> % <B>fs whichcell</B>
- File . lives in cell 'abc.com'
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf168.htm#HDRFS_WSCELL">fs wscell</A>
-<P><A HREF="auarf166.htm#HDRFS_WHEREIS">fs whereis</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf166.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf168.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf167.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf169.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFS_WSCELL" HREF="auarf002.htm#ToC_182">fs wscell</A></H2>
-<A NAME="IDX5015"></A>
-<A NAME="IDX5016"></A>
-<A NAME="IDX5017"></A>
-<A NAME="IDX5018"></A>
-<A NAME="IDX5019"></A>
-<A NAME="IDX5020"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Returns the name of the cell to which a machine belongs
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fs wscell</B> [<B>-help</B>]
-
-<B>fs ws</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs wscell</B> command returns the name of the local
-machine's home cell.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays the contents of the local
-<B>/usr/vice/etc/ThisCell</B> file, in the format
-<PRE> This workstation belongs to cell '<VAR>cellname</VAR>'
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example results when the <B>fs wscell</B> is issued on a
-machine in the State University cell:
-<PRE> % <B>fs wscell</B>
- This workstation belongs to cell 'stateu.edu'
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf166.htm#HDRFS_WHEREIS">fs whereis</A>
-<P><A HREF="auarf167.htm#HDRFS_WHICHCELL">fs whichcell</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf167.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf169.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf168.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf170.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_INTRO" HREF="auarf002.htm#ToC_183">fstrace</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5021"></A>
-<A NAME="IDX5022"></A>
-<A NAME="IDX5023"></A>
-<A NAME="IDX5024"></A>
-<A NAME="IDX5025"></A>
-<A NAME="IDX5026"></A>
-<P>Introduction to the <B>fstrace</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>fstrace</B> command suite are the interface that
-system administrators employ to trace Cache Manager operations for debugging
-purposes. Examples of Cache Manager operations are fetching file data
-or the status information used to produce output for the UNIX <B>ls</B>
-command.
-<P>The <B>fstrace</B> command interpreter defines an extensive set of
-Cache Manager operations as the <B>cm</B> <I>event set</I>.
-When the event set is activated, the Cache Manager writes a message to the
-<B>cmfx</B> <I>trace log</I> in kernel memory each time it performs
-one of the defined operations. The log expands only to a defined size
-(by default, 60 KB), after which it is overwritten in a circular fashion (new
-trace messages overwrite the oldest ones). If an operation of
-particular interest occurs, the administrator can afterward display the log on
-the standard output stream or write it to a file for later study. For
-more specific procedural instructions, see the <I>IBM AFS Administration
-Guide</I>.
-<P>There are several categories of commands in the <B>fstrace</B> command
-suite:
-<UL>
-<P><LI>Commands to administer or display information about the trace log:
-<P><B>fstrace clear</B>, <B>fstrace lslog</B>, <B>fstrace
-setlog</B>
-<P><LI>Commands to set or display the status of the event set:
-<P><B>fstrace lsset</B> and <B>fstrace setset</B>
-<P><LI>A command to display the contents of the trace log: <B>fstrace
-dump</B>
-<P><LI>Commands to obtain help: <B>fstrace apropos</B> and <B>fstrace
-help</B>
-</UL>
-<P><STRONG>Options</STRONG>
-<P>All <B>fstrace</B> commands accept the following optional flag.
-It is listed in the command descriptions and described in detail here:
-<A NAME="IDX5027"></A>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>To issue most <B>fstrace</B> commands, the issuer must be logged on as
-the local superuser <B>root</B> on the machine that is generating the
-trace log.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf170.htm#HDRFSTRACE_APROPOS">fstrace apropos</A>
-<P><A HREF="auarf171.htm#HDRFSTRACE_CLEAR">fstrace clear</A>
-<P><A HREF="auarf172.htm#HDRFSTRACE_DUMP">fstrace dump</A>
-<P><A HREF="auarf173.htm#HDRFSTRACE_HELP">fstrace help</A>
-<P><A HREF="auarf174.htm#HDRFSTRACE_LSLOG">fstrace lslog</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P><A HREF="auarf176.htm#HDRFSTRACE_SETLOG">fstrace setlog</A>
-<P><A HREF="auarf177.htm#HDRFSTRACE_SETSET">fstrace setset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf168.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf170.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf169.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf171.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_APROPOS" HREF="auarf002.htm#ToC_184">fstrace apropos</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5028"></A>
-<A NAME="IDX5029"></A>
-<A NAME="IDX5030"></A>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>fstrace ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace apropos</B> command displays the first line of the
-online help entry for any <B>fstrace</B> command that contains in its name
-or short description the string specified with the <B>-topic</B>
-argument.
-<P>To display a command's complete syntax, use the <B>fstrace
-help</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>fstrace</B> command where the string specified with the
-<B>-topic</B> argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>fstrace</B> commands that include
-the word <B>set</B> in their names or short descriptions:
-<PRE> % <B>fstrace apropos set</B>
- clear: clear logs by logname or by event set
- lsset: list available event sets
- setlog: set the size of a log
- setset: set state of event sets
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf173.htm#HDRFSTRACE_HELP">fstrace help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf169.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf171.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf170.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf172.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_CLEAR" HREF="auarf002.htm#ToC_185">fstrace clear</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Clears the trace log
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace clear</B> [<B>-set</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-log</B> <<VAR>log_name</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fstrace c</B> [<B>-s</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-l</B> <<VAR>log_name</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace clear</B> command erases the contents of the trace log
-from kernel memory, but leaves kernel memory allocated for the log.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-set
-</B><DD>Names the event set for which to clear the associated trace log.
-The only acceptable value is <B>cm</B> (for which the associated trace log
-is <B>cmfx</B>). Provide either this argument or the
-<B>-log</B> argument, or omit both to clear the <B>cmfx</B> log by
-default.
-<P><DT><B>-log
-</B><DD>Names the trace log to clear. The only acceptable value is
-<B>cmfx</B>. Provide either this argument or the <B>-set</B>
-argument, or omit both to clear the <B>cmfx</B> log by default.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command clears the <B>cmfx</B> trace log on the local
-machine:
-<PRE> # <B>fstrace clear</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf174.htm#HDRFSTRACE_LSLOG">fstrace lslog</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf170.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf172.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf171.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf173.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_DUMP" HREF="auarf002.htm#ToC_186">fstrace dump</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5031"></A>
-<A NAME="IDX5032"></A>
-<P>Dumps a trace log
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace dump</B> [<B>-set</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-follow</B> <<VAR>log_name</VAR>>]
- [<B>-file</B> <<VAR>output_filename</VAR>>]
- [<B>-sleep</B> <<VAR>seconds_between_reads</VAR>>] [<B>-help</B>]
-
-<B>fstrace d</B> [<B>-se</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-fo</B> <<VAR>log_name</VAR>>] [<B>-fi</B> <<VAR>output_filename</VAR>>]
- [<B>-sl</B> <<VAR>seconds_between_reads</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace dump</B> command displays the current contents of the
-<B>cmfx</B> trace log on the standard output stream or writes it to the
-file named by the <B>-file</B> argument.
-<P>To write the log continuously to the standard output stream or to a file,
-use the <B>-follow</B> argument. By default, the log's
-contents are written out every ten seconds and then automatically
-cleared. To change the interval between writes, use the
-<B>-sleep</B> argument.
-<P><STRONG>Cautions</STRONG>
-<P>This command produces output only if the <B>cm</B> event set is
-active. To display or set the event set's state, use the
-<B>fstrace lsset</B> or <B>fstrace setset</B> command
-respectively.
-<P>To make the output from this command maximally readable, the message
-catalog file called <B>afszcm.cat</B> must reside in the local
-<B>/usr/vice/etc/C</B> directory. If necessary, copy the file to
-that directory from the AFS Binary Distribution before activating
-tracing.
-<P>When the <B>cm</B> event set is active, a defined amount of kernel
-memory (by default, 60 KB) is allocated for the <B>cmfx</B> trace
-log. As described on the introductory <B>fstrace</B> reference
-page, when the buffer is full, messages are overwritten in a circular fashion
-(new messages overwrite the oldest ones). To allocate more kernel
-memory for the log, use the <B>fstrace setlog</B> command; to display
-the log buffer's current size, use the <B>fstrace lslog</B> command
-with the <B>-long</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-set
-</B><DD>Names the event set for which to write out the associated trace
-log. The only acceptable value is <B>cm</B> (for which the
-associated trace log is <B>cmfx</B>). Provide either this argument
-or the <B>-log</B> argument, or omit both to write out the <B>cmfx</B>
-log by default.
-<P><DT><B>-follow
-</B><DD>Names the trace log to write out continuously at a specified interval (by
-default, every ten seconds; use the <B>-sleep</B> argument to change
-the interval). The log is cleared after each write operation.
-<P>The only acceptable value is <B>cmfx</B>. Provide either this
-argument or the <B>-set</B> argument, or omit both to write out the
-<B>cmfx</B> log by default.
-<P><DT><B>-file
-</B><DD>Specifies the pathname of the file to which to write the trace log's
-contents. It can be in AFS or on the local disk. Partial
-pathnames are interpreted relative to the current working directory. If
-this argument is omitted, the trace log appears on the standard output
-stream.
-<P><DT><B>-sleep
-</B><DD>Sets the number of seconds between writes of the trace log's contents
-when it is dumped continuously. Provide the <B>-follow</B> argument
-along with this one. If this argument is omitted, the default interval
-is ten seconds.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output begins with a header specifying the date and time at which the
-write operation began. If the <B>-follow</B> argument is not
-included, the header also reports the number of logs being dumped; it is
-always <TT>1</TT>, since there is only the <B>cmfx</B> trace log.
-The format of the header is as follows:
-<PRE> AFS Trace Dump -
- Date: <VAR>starting_timestamp</VAR>
- Found 1 logs.
- Contents of log cmfx:
-
-</PRE>
-<P>Each subsequent message describes a Cache Manager operation in the
-following format:
-<PRE> time <VAR>timestamp</VAR>, pid <VAR>pid</VAR>:<VAR>event_message</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>timestamp</VAR>
-</B><DD>Specifies the time at which the Cache Manager performed the operation, as
-the number of seconds since the dump began
-<P><DT><B><VAR>pid</VAR>
-</B><DD>Specifies the process ID of the process or thread associated with the
-message
-<P><DT><B><VAR>event_message</VAR>
-</B><DD>Is the message itself. They are generally meaningful only to
-someone familiar with the AFS source code.
-</DL>
-<P>In addition, every 1024 seconds the <B>fstrace</B> command interpreter
-writes a message that records the current clock time, in the following
-format:
-<PRE> time <VAR>timestamp</VAR>, pid <VAR>pid</VAR>: Current time: <VAR>unix_time</VAR>
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><VAR>timestamp</VAR>
-</B><DD>Is the number of seconds from the start of trace logging
-<P><DT><B><VAR>pid</VAR>
-</B><DD>Is the process ID number
-<P><DT><B><VAR>unix_time</VAR>
-</B><DD>Is the machine's clock time, represent in the standard UNIX time
-format as the number of seconds since midnight on January 1, 1970.
-</DL>
-<P>Use this message to determine the actual clock time associated with each
-log message. Determine the actual time as follows:
-<OL TYPE=1>
-<P><LI>Locate the message of interest.
-<P><LI>Search backward through the trace file for the closest current time
-message.
-<P><LI>If the current time message's <VAR>timestamp</VAR> is smaller than the
-log message's <VAR>timestamp</VAR>, subtract former from the latter.
-If the current time message's <VAR>timestamp</VAR> is larger than the log
-message's <VAR>timestamp</VAR>, add 1024 to the latter and subtract the
-former from the result.
-<P><LI>Add the resulting number to the current time message's
-<VAR>unix_time</VAR> to determine the log message's actual time.
-</OL>
-<P>If any of the data in the kernel trace buffer has been overwritten since
-tracing was activated, the following message appears at the appropriate place
-in the output:
-<PRE> Log wrapped; data missing.
-
-</PRE>
-<P>To reduce the likelihood of overwriting, use the <B>fstrace setlog</B>
-command to increase the kernel buffer's size. To display the
-current defined buffer size, use the <B>fstrace lslog</B> command with the
-<B>-long</B> argument.
-<P>The following message at the end of the log dump indicates that it is
-completed:
-<PRE> AFS Trace Dump - Completed
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command dumps the log associated with the <B>cm</B> event
-set to the standard output stream.
-<PRE> # <B>fstrace dump -set cm</B>
- AFS Trace Dump -
- Date: Tue Apr 7 10:54:57 1998
- Found 1 logs.
- time 32.965783, pid 0: Tue Apr 7 10:45:52 1998
- time 32.965783, pid 33657: Close 0x5c39ed8 flags 0x20
- time 32.965897, pid 33657: Gn_close vp 0x5c39ed8 flags 0x20 (returns 0x0)
- time 35.159854, pid 10891: Breaking callback for 5bd95e4 states 1024 (volume 0)
- time 35.407081, pid 10891: Breaking callback for 5c0fadc states 1024 (volume 0)
- .
- .
- .
- time 71.440456, pid 33658: Lookup adp 0x5bbdcf0 name g3oCKs \
- fid (756 4fb7e:588d240.2ff978a8.6)
- time 71.440569, pid 33658: Returning code 2 from 19
- time 71.440619, pid 33658: Gn_lookup vp 0x5bbdcf0 name g3oCKs (returns 0x2)
- time 71.464989, pid 38267: Gn_open vp 0x5bbd000 flags 0x0 (returns 0x0)
- AFS Trace Dump - Completed
-
-</PRE>
-<P>The following command dumps the trace log associated with the <B>cm</B>
-event set on the local machine to the file
-<B>cmfx.dump.file.1</B>, using the default interval
-of 10 seconds between successive dumps:
-<PRE> # <B>fstrace dump -follow cmfx -file cmfx.dump.file.1</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf041.htm#HDRAFSZCM">afszcm.cat</A>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf174.htm#HDRFSTRACE_LSLOG">fstrace lslog</A>
-<P><A HREF="auarf176.htm#HDRFSTRACE_SETLOG">fstrace setlog</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf171.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf173.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf172.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf174.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_HELP" HREF="auarf002.htm#ToC_187">fstrace help</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5033"></A>
-<A NAME="IDX5034"></A>
-<A NAME="IDX5035"></A>
-<P>Displays the syntax of specified <B>fstrace</B> commands or lists
-functional descriptions of all <B>fstrace</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fstrace h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>fstrace</B>
-command.
-<P>To list every <B>fstrace</B> command whose name or short description
-includes a specified keyword, use the <B>fstrace apropos</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>fstrace</B> part of the command name, providing
-only the operation code (for example, specify <B>clear</B>, not
-<B>fstrace clear</B>). If this argument is omitted, the output
-briefly describes every <B>fstrace</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>fstrace</B> command consists of two
-or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>fstrace
-setset</B> command:
-<PRE> %<B> fstrace help -topic setset</B>
- fstrace setset: set state of event sets
- Usage: fstrace setset [-set <set_name><SUP>+</SUP>] [-active] [-inactive]
- [-dormant] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf170.htm#HDRFSTRACE_APROPOS">fstrace apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf172.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf174.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf173.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf175.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_LSLOG" HREF="auarf002.htm#ToC_188">fstrace lslog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5036"></A>
-<A NAME="IDX5037"></A>
-<P>Displays information about a log
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace lslog</B> [<B>-set</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-log</B> <<VAR>log_name</VAR>>] [<B>-long</B>] [<B>-help</B>]
-
-<B>fstrace lsl</B> [<B>-s</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-log</B> <<VAR>log_name</VAR>>] [<B>-lon</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace lslog</B> command reports whether the <B>cmfx</B>
-log is available for use. If the <B>-long</B> argument is included,
-the output reports the log's defined size, and whether that amount of
-space is currently allocated in kernel memory or not.
-<P>To change the <B>cmfx</B> trace log's size, use the <B>fstrace
-setlog</B> command. To display or set whether space is allocated for
-it in kernel memory, use the <B>fstrace lsset</B> or <B>fstrace
-setset</B> command to display or set the state of the corresponding
-<B>cm</B> event set, respectively.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-set
-</B><DD>Names the event set for which to display information about the
-corresponding trace log. The only acceptable value is <B>cm</B>
-(for which the associated trace log is <B>cmfx</B>). Provide either
-this argument or the <B>-log</B> argument, or omit both to display
-information about the <B>cmfx</B> log by default.
-<P><DT><B>-log
-</B><DD>Names the trace log about which to report. The only acceptable
-value is <B>cmfx</B>. Provide either this argument or the
-<B>-set</B> argument, or omit both to report on the <B>cmfx</B> log by
-default.
-<P><DT><B>-long
-</B><DD>Reports the defined size of the log in kilobyte units and whether that
-amount of space is currently allocated in kernel memory.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>By default, the <B>fstrace lslog</B> command displays only the name of
-the available log, <B>cmfx</B>, in the following format:
-<PRE> Available logs:
- cmfx
-
-</PRE>
-<P>When the <B>-long</B> flag is included, the output also reports the
-defined size of the log in kilobytes, and whether or not that amount of space
-is currently allocated in kernel memory, in the following format:
-<PRE> Available logs:
- cmfx : <VAR>log_size</VAR> kbytes (allocated | unallocated)
-
-</PRE>
-<P>The <TT>allocated</TT> state indicates that the indicated number of
-kilobytes is reserved for the <B>cmfx</B> trace log in kernel
-memory. The <B>cm</B> event set's state is either
-<TT>active</TT> or <TT>inactive</TT>, as reported by the <B>fstrace
-lsset</B> command, and set by the <B>fstrace setset</B> command's
-<B>-active</B> or <B>-inactive</B> flags respectively.
-<P>The <TT>unallocated</TT> state indicates that no kernel memory is
-currently reserved for the <B>cmfx</B> trace log. The <B>cm</B>
-event set's state is <TT>dormant</TT>, as reported by the <B>fstrace
-lsset</B> command and set by the <B>fstrace setset</B> command's
-<B>-dormant</B> flag. If the event set's state is later
-changed to active or inactive, the number of kilobytes indicated as
-<VAR>log_size</VAR> are again allocated in kernel memory.
-<P><STRONG>Examples</STRONG>
-<P>The following example uses the <B>-long</B> flag to display information
-about the <B>cmfx</B> log:
-<PRE> # <B>fstrace lslog -log cmfx -long</B>
- Available logs:
- cmfx : 60 kbytes (allocated)
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P><A HREF="auarf176.htm#HDRFSTRACE_SETLOG">fstrace setlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf173.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf175.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf174.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf176.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_LSSET" HREF="auarf002.htm#ToC_189">fstrace lsset</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5038"></A>
-<A NAME="IDX5039"></A>
-<P>Reports the status of an event set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace lsset</B> [<B>-set</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>fstrace lss</B> [<B>-s</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace lsset</B> command displays a list of the available event
-sets and reports their current status (active, inactive, or dormant).
-<P>To change an event set's status, use the <B>fstrace setset</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-set
-</B><DD>Names the event set for which to display the status. The only
-acceptable value is <B>cm</B>, which is also the default if this argument
-is omitted.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output lists the available event sets and the status of each, in the
-following format:
-<PRE> Available sets:
- cm {active | inactive | dormant}
-
-</PRE>
-<P>where
-<DL>
-<P><DT><B><TT>active</TT>
-</B><DD>Indicates that tracing is enabled for the event set, and kernel memory
-allocated for the corresponding trace log.
-<P><DT><B><TT>inactive</TT>
-</B><DD>Indicates that tracing is temporarily disabled for the event set, but
-kernel memory still allocated for the corresponding trace log.
-<P><DT><B><TT>dormant</TT>
-</B><DD>Indicates that tracing is disabled for the event set, and no kernel memory
-allocated for the corresponding trace log.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the available event set and its
-status:
-<PRE> # <B>fstrace lsset</B>
- Available sets:
- cm active
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf177.htm#HDRFSTRACE_SETSET">fstrace setset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf174.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf176.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf175.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf177.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_SETLOG" HREF="auarf002.htm#ToC_190">fstrace setlog</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5040"></A>
-<A NAME="IDX5041"></A>
-<P>Sets the size of a trace log
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace setlog</B> [<B>-log</B> <<VAR>log_name</VAR>><SUP>+</SUP>] <B>-buffersize</B> <<VAR>1-kilobyte_units</VAR>> [<B>-help</B>]
-
-<B>fstrace setl</B> [<B>-l</B> <<VAR>log_name</VAR>><SUP>+</SUP>] <B>-b</B> <<VAR>1-kilobyte_units</VAR>> [<B>-h</B>]
-
-<B>fstrace sl</B> [<B>-l</B> <<VAR>log_name</VAR>><SUP>+</SUP>] <B>-b</B> <<VAR>1-kilobyte_units</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace setlog</B> command defines the number of kilobytes of
-kernel memory allocated for the <B>cmfx</B> trace log. If kernel
-memory is currently allocated, the command clears the current log and creates
-a new log buffer of the specified size.
-<P>To display the current defined size of the log buffer, issue the
-<B>fstrace lslog</B> command with the <B>-long</B> argument. To
-control whether the indicated amount of space is actually allocated, use the
-<B>fstrace setset</B> command to set the status of the <B>cm</B> event
-set; to display the event set's status, use the <B>fstrace
-lsset</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-log
-</B><DD>Names trace log for which to set the size. The only acceptable
-value is <B>cmfx</B>, which is also the default if this argument is
-omitted.
-<P><DT><B>-buffersize
-</B><DD>Specifies the number of 1-kilobyte blocks of kernel memory to allocate for
-the trace log.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command allocated 80 KB of kernel memory for the
-<B>cmfx</B> trace log:
-<PRE> # <B>fstrace setlog -log cmfx -buffersize 80</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf174.htm#HDRFSTRACE_LSLOG">fstrace lslog</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P><A HREF="auarf177.htm#HDRFSTRACE_SETSET">fstrace setset</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf175.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf177.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf176.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf178.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFSTRACE_SETSET" HREF="auarf002.htm#ToC_191">fstrace setset</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5042"></A>
-<A NAME="IDX5043"></A>
-<P>Sets the status of an event set
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>fstrace setset</B> [<B>-set</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-active</B>] [<B>-inactive</B>] [<B>-dormant</B>] [<B>-help</B>]
-
-<B>fs set</B> [<B>-s</B> <<VAR>set_name</VAR>><SUP>+</SUP>] [<B>-a</B>] [<B>-i</B>] [<B>-d</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fstrace setset</B> command sets the status of the <B>cm</B>
-kernel event set on the local machine, which determines whether trace messages
-are recorded in the log buffer in kernel memory.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-set
-</B><DD>Names the event set for which to set the status. The only
-acceptable value <B>cm</B>, which is also the default if this argument is
-omitted.
-<P><DT><B>-active
-</B><DD>Enables tracing for the event set and allocates kernel memory for the
-associated trace log buffer. Provide one of this flag, the
-<B>-inactive</B> flag, or the <B>-dormant</B> flag.
-<P><DT><B>-inactive
-</B><DD>Temporarily disables tracing for the event set, but does not change the
-allocation of kernel memory for the associated trace log buffer.
-Provide one of this flag, the <B>-active</B> flag, or the
-<B>-dormant</B> flag.
-<P><DT><B>-dormant
-</B><DD>Disables tracing for the event set and frees the kernel memory previously
-allocated for the associated trace log buffer. Provide one of this
-flag, the <B>-active</B> flag, or the <B>-inactive</B> flag.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example sets the <B>cm</B> event set's status to
-<B>inactive</B>:
-<PRE> #<B> fstrace setset -set cm -inactive</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P><A HREF="auarf175.htm#HDRFSTRACE_LSSET">fstrace lsset</A>
-<P><A HREF="auarf176.htm#HDRFSTRACE_SETLOG">fstrace setlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf176.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf178.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf177.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf179.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRFTPD" HREF="auarf002.htm#ToC_192">ftpd (AFS version)</A></H2>
-<A NAME="IDX5044"></A>
-<A NAME="IDX5045"></A>
-<A NAME="IDX5046"></A>
-<A NAME="IDX5047"></A>
-<A NAME="IDX5048"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Internet File Transfer Protocol server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>ftpd</B> [<B>-d</B>] [<B>-l</B>] [<B>-t</B> <<VAR>timeout</VAR>>] [<B>-v</B>] [<B>-T</B> <<VAR>MaxTimeOut</VAR>>] [<B>-u</B>] [<B>-s</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The AFS-modified <B>ftpd</B> program functions like the standard UNIX
-<B>ftpd</B> program, but also authenticates the issuer of the
-<B>ftp</B> command (who is presumably working on a remote machine) with
-the Authentication Server in the local cell (the home cell of the machine
-where the <B>ftpd</B> process is running, as defined in the local
-<B>/usr/vice/etc/ThisCell</B> file). The authentication is based on
-the user name and password provided at the <TT>ftp></TT> prompts on the
-remote machine. The Cache Manager on the machine running the
-<B>ftpd</B> process stores the newly created token, identifying it by
-process authentication group (PAG) rather than by the user's UNIX
-UID.
-<P>The issuer of the <B>ftp</B> command can be working in a foreign cell,
-as long as the user name and password provided are valid in the cell where the
-<B>ftpd</B> process is running. If the user name under which the
-<B>ftp</B> command is issued does not exist in the Authentication Database
-for the cell where the <B>ftpd</B> process is running, or the issuer
-provides the wrong password, then the <B>ftpd</B> process logs the user
-into the local file system of the machine where the <B>ftpd</B> process is
-running. The success of this local login depends on the user name
-appearing in the local password file and on the user providing the correct
-local password. In the case of a local login, AFS server processes
-consider the issuer of the <B>ftp</B> command to be the user
-<B>anonymous</B>.
-<P>In the recommended configuration, the AFS version of the <B>ftpd</B>
-process is substituted for the standard version (only one of the versions can
-run at a time). The administrator then has two choices:
-<UL>
-<P><LI>Name the binary for the AFS version something like
-<B>ftpd.afs</B>, leaving the standard version as the
-<B>ftpd</B> process. Change the <B>inetd.conf</B>
-configuration file to refer to the <B>ftpd.afs</B> file rather than
-to the standard version.
-<P><LI>Rename the binary for the AFS version to the standard name (such as
-<B>ftpd</B>) and rename the binary for the standard version to something
-like <B>ftpd.orig</B>. No change to the
-<B>inetd.conf</B> file is necessary, but it is not as obvious that
-the standard version of the <B>ftpd</B> process is no longer in
-use.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>The AFS distribution does not include an AFS-modified version of this
-command for every system type. On system types that use an integrated
-authentication system, it is appropriate instead to control the
-<B>ftpd</B> daemon's handling of AFS authentication through the
-integrated system. For example, on system types that use the Pluggable
-Authentication Module (PAM), add an <B>ftpd</B> entry that references the
-AFS PAM module to the PAM configuration file. For instructions on
-incorporating AFS into a machine's integrated authentication system, see
-the <I>IBM AFS Quick Beginnings</I>.
-<P>Some system types impose the following requirement. If the issuer of
-the <B>ftp</B> command on the remote machine is using a shell other than
-<B>/bin/csh</B>, then the <B>/etc/shells</B> file on the local disk of
-the machine being accessed (the machine running the <B>ftpd</B> process)
-must include an entry for the alternate shell.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-d
-</B><DD>Directs debugging information to the system log daemon.
-<P><DT><B>-l
-</B><DD>Directs each FTP session to be logged to the system log daemon.
-<P><DT><B>-t
-</B><DD>Specifies a timeout period. By default, the FTP server will timeout
-an inactive session after 15 minutes.
-<P><DT><B>-v
-</B><DD>Same as <B>-d</B>.
-<P><DT><B>-T
-</B><DD>Specifies a timeout period in seconds. By default, the FTP server
-will timeout after 2 hours (7200 seconds).
-<P><DT><B>-s
-</B><DD>Turns on socket level debugging. Do not use this flag. It is
-valid only on an operating system level that AFS does not support.
-<P><DT><B>-u
-</B><DD>Specifies the default UNIX mode bit file mask to use.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>See the UNIX manual page for the <B>ftpd</B> process.
-<P><STRONG>Related Information</STRONG>
-<P>UNIX manual page for <B>ftp</B>
-<P>UNIX manual page for <B>ftpd</B>
-<P><I>IBM AFS Quick Beginnings</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf177.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf179.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf178.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf180.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRINETD" HREF="auarf002.htm#ToC_193">inetd (AFS version)</A></H2>
-<A NAME="IDX5049"></A>
-<A NAME="IDX5050"></A>
-<A NAME="IDX5051"></A>
-<A NAME="IDX5052"></A>
-<A NAME="IDX5053"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Internet service daemon
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>inetd</B> [<B>-d</B>] [<<VAR>configfile</VAR>>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The AFS-modified <B>inetd</B> program functions like the standard UNIX
-<B>inetd</B> program, but also enables users of the remote services it
-supports to access them as authenticated AFS users, provided that the
-supported services are also AFS-modified versions that pass AFS tokens
-(authentication information). Examples of supported services are the
-<B>rcp</B> and <B>rsh</B> programs.
-<P>The AFS <B>inetd</B> program can service the standard UNIX versions of
-the remote services, but it is instead recommended that the standard UNIX
-version of the <B>inetd</B> program be run in parallel with the AFS
-version. Name the AFS version something like
-<B>inetd.afs</B> and use it to service requests from AFS-modified
-programs; use the standard <B>inetd</B> program to service requests
-from standard UNIX programs. This separation requires using two
-different <B>inetd.conf</B> files, as described in the following
-section.
-<P><STRONG>Cautions</STRONG>
-<P>Several configuration changes are necessary for token passing to work
-correctly with the AFS version of the <B>inetd</B> program. There
-are possibly other UNIX-based requirements or restrictions not mentioned
-here; consult the UNIX manual page. (One important restriction is
-that there can be no blank lines in the configuration file other than at the
-end.)
-<P>The requirements and restrictions include the following. They assume
-that the <B>inetd.afs</B> process is running in parallel with the
-standard <B>inetd</B> process.
-<UL>
-<P><LI>For token passing to work, the request must come from the AFS version of
-the remote service (such as the AFS <B>rcp</B> or AFS <B>rsh</B>
-command). If the remote service is the standard UNIX version, it cannot
-pass a token. The issuer of the remote command is authenticated only in
-the local file system, not with AFS.
-<P><LI>The machine's initialization files (<B>/etc/rc</B> file or
-equivalent) must invoke both the standard <B>inetd</B> and
-<B>inetd.afs</B> programs.
-<P><LI>An AFS-specific <B>inetd.conf</B> file, perhaps called
-<B>inetd.conf.afs</B>, must exist alongside the standard
-one. When initializing the <B>inetd.afs</B> program, specify
-this configuration file rather than the standard one. Each line in the
-<B>inetd.conf.afs</B> file must include an additional field,
-fifth from the left, to specify the identity under which the program is to
-run. The normal choice is the local superuser <B>root</B>.
-The following sample shows the only lines that need to appear in this
-file:
-<PRE> ta-rauth stream tcp nowait root internal ta-rauth
- shell stream tcp nowait root /usr/etc/rshd rshd
- login stream tcp nowait root /usr/etc/rlogind rlogind
-</PRE>
-<P>Substitute appropriate values for the binary locations and names in the
-instructions, particularly for the <TT>shell</TT> and <TT>login</TT>
-processes. Include the <TT>login</TT> instruction only if the
-AFS-modified versions of login utilities are also in use in the cell;
-otherwise, refer to <TT>login</TT> in the standard
-<B>inetd.conf</B> instead.
-<P>Note also that some system types use different process names. For
-example, on Sun system types change <TT>rshd</TT> to
-<TT>in.rshd</TT> and <TT>rlogind.afs</TT> to
-<TT>in.rlogind.afs</TT> in the <TT>shell</TT> and
-<TT>login</TT> instructions, respectively.
-<P><LI>Edit the standard <B>inetd.conf</B> file (referenced by the
-standard <B>inetd</B> process): comment out the <TT>shell</TT>
-instruction and, if AFS-modified versions of login utilities are in use in the
-cell, the <TT>login</TT> instruction. The
-<B>inetd.conf.afs</B> file references these processes
-instead. Retain the <TT>login</TT> instruction if AFS-modified
-versions of login utilities are not being used. Alter the
-<TT>ftp</TT> instruction to refer to the AFS version of the <B>ftpd</B>
-process, if it is substituted for the standard version. Do not insert
-the extra fifth column into instructions in the standard
-<B>inetd.conf</B> file if it does not already appear there.
-See the following <B>Examples</B> section for an illustration.
-</UL>
-<P><STRONG>Options</STRONG>
-<P>See the UNIX manual page for the <B>inetd</B> program.
-<P><STRONG>Examples</STRONG>
-<P>The following are sample <B>inetd.conf.afs</B> and
-<B>inetd.conf</B> files, appropriate for use when the
-<B>inetd.afs</B> program is running in parallel with the standard
-<B>inetd</B> and AFS-modified login utilities are being used in the
-cell. Changes to the standard <B>inetd.conf</B> file include
-referencing the AFS version of the <B>ftpd</B> binary and commenting out
-the <TT>shell</TT> and <TT>login</TT> lines. The example
-<B>inetd.conf</B> file does not include the extra fifth
-column. Do not use these examples without modifying them appropriately
-for the local machine type or cell.
-<PRE> # AFS version of Internet server configuration database
- #(EXAMPLE ONLY)
- #
- ta-rauth stream tcp nowait root internal ta-rauth
- shell stream tcp nowait root /usr/etc/rshd rshd
- login stream tcp nowait root /usr/etc/rlogind rlogind
-
- # Standard version of Internet server configuration database
- #(EXAMPLE ONLY)
- #
- ftp stream tcp nowait /etc/ftpd.afs ftpd.afs
- telnet stream tcp nowait /etc/telnetd telnetd
- #shell stream tcp nowait /etc/rshd rshd
- #login stream tcp nowait /etc/rlogind rlogind
- finger stream tcp nowait /usr/etc/fingd fingd
- uucp stream tcp nowait /etc/uucpd uucpd
- exec stream tcp nowait /etc/rexecd rexecd
- comsat dgram udp wait /etc/comsat comsat
- talk dgram udp wait /etc/talkd talkd
- ntalk dgram udp wait /usr/etc/ntalkd talkd
- time dgram udp wait /etc/miscd timed
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>See the UNIX manual page for the <B>inetd</B> program.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf228.htm#HDRRCP">rcp (AFS version)</A>
-<P><A HREF="auarf229.htm#HDRRSH">rsh (AFS version)</A>
-<P>UNIX manual page for <B>inetd</B>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf178.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf180.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf179.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf181.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKADB_CHECK" HREF="auarf002.htm#ToC_194">kadb_check</A></H2>
-<A NAME="IDX5054"></A>
-<A NAME="IDX5055"></A>
-<A NAME="IDX5056"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Checks the integrity of the Authentication Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kadb_check -database</B> <<VAR>kadb_file</VAR>> [<B>-uheader</B>] [<B>-kheader</B>] [<B>-entries</B>]
- [<B>-verbose</B>] [<B>-rebuild</B> <<VAR>out_file</VAR>>] [<B>-help</B>]
-
-<B>kadb_check -d</B> <<VAR>kadb_file</VAR>> [<B>-u</B>] [<B>-k</B>] [<B>-e</B>] [<B>-v</B>] [<B>-r</B> <<VAR>out_file</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kadb_check</B> command checks the integrity of the Protection
-Database, reporting any errors or corruption it finds. If there are
-problems, do not issue any <B>kas</B> commands until the database is
-repaired.
-<P><STRONG>Cautions</STRONG>
-<P>The results can be unpredictable if the Authentication Server makes changes
-to the Authentication Database while this command is running. Use the
-<B>bos shutdown</B> command to shutdown the local <B>kaserver</B>
-process before running this command, or before creating a second copy of the
-<B>kaserver.DB0</B> file (with a different name) on which to run
-the command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-database
-</B><DD>Names the Authentication Database (copy of the
-<B>kaserver.DB0</B> file) to check. If the current working
-directory is not the location of the file, provide a pathname, either full or
-relative to the current working directory.
-<P><DT><B>-uheader
-</B><DD>Displays information which Ubik maintains in the database's
-header.
-<P><DT><B>-kheader
-</B><DD>Displays information which the Authentication Server maintains in the
-database's header.
-<P><DT><B>-entries
-</B><DD>Outputs every entry in the database, providing information similar to that
-returned by the <B>kas examine</B> command.
-<P><DT><B>-verbose
-</B><DD>Reports additional information about the database, including the number of
-free (allocated but unused) entries in the database.
-<P><DT><B>-rebuild
-</B><DD>Names the file in which to record a list of <B>kas</B> commands which,
-if issued in the command shell, recreate the current state of the database
-being verified. Partial pathnames are interpreted relative to the
-current working directory.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If there are errors in the database, the output always reports them on the
-standard error stream. If any options other than <B>-database</B>
-or <B>-help</B> are provided, the output written to the standard output
-stream includes additional information as described for each option in the
-preceding <B>Options</B> section of this reference page. The output
-is intended for debugging purposes and is meaningful to someone familiar with
-the internal structure of the Authentication Database.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf179.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf181.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf180.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf182.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_INTRO" HREF="auarf002.htm#ToC_195">kas</A></H2>
-<A NAME="IDX5057"></A>
-<A NAME="IDX5058"></A>
-<A NAME="IDX5059"></A>
-<A NAME="IDX5060"></A>
-<A NAME="IDX5061"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>kas</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>kas</B> command suite are the administrative
-interface to the Authentication Server, which runs on each database server
-machine in a cell, maintains the Authentication Database, and provides the
-authentication tickets that client applications must present to AFS servers in
-order to obtain access to AFS data and other services.
-<P>There are several categories of commands in the <B>kas</B> command
-suite:
-<UL>
-<P><LI>Commands to create, modify, examine and delete entries in the
-Authentication Database, including passwords: <B>kas create</B>,
-<B>kas delete</B>, <B>kas examine</B>, <B>kas list</B>, <B>kas
-setfields</B>, <B>kas setkey</B>, <B>kas setpassword</B>, and
-<B>kas unlock</B>
-<P><LI>Commands to create, delete, and examine tokens and server tickets:
-<B>kas forgetticket</B>, <B>kas listtickets</B>, <B>kas
-noauthentication</B>, and <B>kas stringtokey</B>
-<P><LI>A command to enter interactive mode: <B>kas interactive</B>
-<P><LI>A command to trace Authentication Server operations: <B>kas
-statistics</B>
-<P><LI>Commands to obtain help: <B>kas apropos</B> and <B>kas
-help</B>
-</UL>
-<P>Because of the sensitivity of information in the Authentication Database,
-the Authentication Server authenticates issuers of <B>kas</B> commands
-directly, rather than accepting the standard token generated by the Ticket
-Granting Service. Any <B>kas</B> command that requires
-administrative privilege prompts the issuer for a password. The
-resulting ticket is valid for six hours unless the maximum ticket lifetime for
-the issuer or the Authentication Server's Ticket Granting Service is
-shorter.
-<A NAME="IDX5062"></A>
-<A NAME="IDX5063"></A>
-<P>To avoid having to provide a password repeatedly when issuing a sequence of
-<B>kas</B> commands, enter <I>interactive mode</I> by issuing the
-<B>kas interactive</B> command, typing <B>kas</B> without any
-operation code, or typing <B>kas</B> followed by a user and cell name,
-separated by an at-sign (<B>@</B>; an example is <B>kas
-smith.admin@abc.com</B>). After prompting once for a
-password, the Authentication Server accepts the resulting token for every
-command issued during the interactive session. See the reference page
-for the <B>kas interactive</B> command for a discussion of when to use
-each method for entering interactive mode and of the effects of entering a
-session.
-<P>The Authentication Server maintains two databases on the local disk of the
-machine where it runs:
-<UL>
-<P><LI>The Authentication Database (<B>/usr/afs/db/kaserver.DB0</B>)
-stores the information used to provide AFS authentication services to users
-and servers, including the password scrambled as an encryption key. The
-reference page for the <B>kas examine</B> command describes the
-information in a database entry.
-<P><LI>An auxiliary file (<B>/usr/afs/local/kaauxdb</B> by default) that
-tracks how often the user has provided an incorrect password to the local
-Authentication Server. The reference page for the <B>kas
-setfields</B> command describes how the Authentication Server uses this file
-to enforce the limit on consecutive authentication failures. To
-designate an alternate directory for the file, use the <B>kaserver</B>
-command's <B>-localfiles</B> argument.
-</UL>
-<P><STRONG>Options</STRONG>
-<P>The following arguments and flags are available on many commands in the
-<B>kas</B> suite. (Some of them are unavailable on commands entered
-in interactive mode, because the information they specify is established when
-entering interactive mode and cannot be changed except by leaving interactive
-mode.) The reference page for each command also lists them, but they
-are described here in greater detail.
-<DL>
-<P><DT><B>
-<A NAME="IDX5064"></A>
-<B>-admin_username</B>
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. If this argument is
-omitted, the <B>kas</B> command interpreter requests authentication for
-the identity under which the issuer is logged onto the local machine.
-Do not combine this argument with the <B>-noauth</B> flag.
-<A NAME="IDX5065"></A>
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P>
-<P>The <B>-cell</B> argument is not available on commands issued in
-interactive mode. The cell defined when the <B>kas</B> command
-interpreter enters interactive mode applies to all commands issued during the
-interactive session.
-<A NAME="IDX5066"></A>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>
-<A NAME="IDX5067"></A>
-<B>-noauth</B>
-</B><DD>Establishes an unauthenticated connection to the Authentication Server, in
-which the Authentication Server treats the issuer as the unprivileged user
-<B>anonymous</B>. It is useful only when authorization checking is
-disabled on the server machine (during the installation of a server machine or
-when the <B>bos setauth</B> command has been used during other unusual
-circumstances). In normal circumstances, the Authentication Server
-allows only privileged users to issue most <B>kas</B> commands, and
-refuses to perform such an action even if the <B>-noauth</B> flag is
-provided. Do not combine this flag with the <B>-admin_username</B>
-and <B>-password_for_admin</B> arguments.
-<P><DT><B>
-<A NAME="IDX5068"></A>
-<B>-password_for_admin</B>
-</B><DD>Specifies the password of the command's issuer. It is best to
-omit this argument, which echoes the password visibly in the command shell,
-instead enter the password at the prompt. Do not combine this argument
-with the <B>-noauth</B> flag.
-<P><DT><B>
-<A NAME="IDX5069"></A>
-<B>-servers</B>
-</B><DD>Establishes a connection with the Authentication Server running on each
-specified database server machine, instead of on each machine listed in the
-local <B>/usr/vice/etc/CellServDB</B> file. In either case, the
-<B>kas</B> command interpreter then chooses one of the machines at random
-to contact for execution of each subsequent command. The issuer can
-abbreviate the machine name to the shortest form that allows the local name
-service to identify it uniquely.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>To issue most <B>kas</B> commands, the issuer must have the
-<TT>ADMIN</TT> flag set in his or her Authentication Database entry (use the
-<B>kas setfields</B> command to turn the flag on).
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<P><A HREF="auarf046.htm#HDRKASERVERAUXDB">kaserverauxdb</A>
-<P><A HREF="auarf182.htm#HDRKAS_APROPOS">kas apropos</A>
-<P><A HREF="auarf183.htm#HDRKAS_CREATE">kas create</A>
-<P><A HREF="auarf184.htm#HDRKAS_DELETE">kas delete</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf186.htm#HDRKAS_FORGETTICKET">kas forgetticket</A>
-<P><A HREF="auarf187.htm#HDRKAS_HELP">kas help</A>
-<P><A HREF="auarf188.htm#HDRKAS_INTERACTIVE">kas interactive</A>
-<P><A HREF="auarf189.htm#HDRKAS_LIST">kas list</A>
-<P><A HREF="auarf190.htm#HDRKAS_LISTTICKETS">kas listtickets</A>
-<P><A HREF="auarf191.htm#HDRKAS_NOAUTH">kas noauthentication</A>
-<P><A HREF="auarf192.htm#HDRKAS_QUIT">kas quit</A>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf195.htm#HDRKAS_STATISTICS">kas statistics</A>
-<P><A HREF="auarf196.htm#HDRKAS_STRINGTOKEY">kas stringtokey</A>
-<P><A HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf180.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf182.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf181.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf183.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_APROPOS" HREF="auarf002.htm#ToC_196">kas apropos</A></H2>
-<A NAME="IDX5070"></A>
-<A NAME="IDX5071"></A>
-<A NAME="IDX5072"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>kas a -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas apropos</B> command displays the first line of the online
-help entry for any <B>kas</B> command that has the string specified by the
-<B>-topic</B> argument in its name or short description.
-<P>To display the syntax for a command, use the <B>kas help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>kas</B> command where the string specified with the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>kas</B> commands that include the
-word <B>key</B> in their names or short descriptions:
-<PRE> %<B> kas apropos key</B>
- setkey: set a user's key
- stringtokey: convert a string to a key
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf187.htm#HDRKAS_HELP">kas help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf181.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf183.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf182.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf184.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_CREATE" HREF="auarf002.htm#ToC_197">kas create</A></H2>
-<A NAME="IDX5073"></A>
-<A NAME="IDX5074"></A>
-<A NAME="IDX5075"></A>
-<A NAME="IDX5076"></A>
-<A NAME="IDX5077"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates an entry in the Authentication Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas create -name</B> <<VAR>name of user</VAR>> [<B>-initial_password</B> <<VAR>initial password</VAR>>]
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas c -na</B> <<VAR>name of user</VAR>> [<B>-i</B> <<VAR>initial password</VAR>>]
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas create</B> command creates an entry in the Authentication
-Database for the user named by the <B>-name</B> argument.
-<P>To avoid having the account's initial password echo visibly at the
-shell prompt, omit the <B>-initial_password</B> argument; the command
-interpreter prompts for the password and does not echo it visibly.
-Whether or not <B>-initial_password</B> is omitted, the Authentication
-Server converts the password into a form suitable for use as an encryption
-key, and records it in the entry's key field.
-<P>To alter settings in an Authentication Database entry, use the <B>kas
-setfields</B> command. To examine an entry, use the <B>kas
-examine</B> command. To list every entry in the database, use the
-<B>kas list</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the new Authentication Database entry. Because it is the name
-under which the user logs in, it must obey the restrictions that many
-operating systems impose on user names (usually, to contain no more than eight
-lowercase letters).
-<P><DT><B>-initial_password
-</B><DD>Sets the user's password; provide a character string that can
-include uppercase and lowercase letters, numerals and punctuation. The
-Authentication Server scrambles the string into an octal string suitable for
-use as an encryption key before placing it in the entry's key
-field. If this argument is omitted, the command interpreter prompts for
-the string and does not echo it visibly.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the prompts that appear when an administrator
-logged in as <B>admin</B> creates an Authentication Database entry for the
-user <B>smith</B>, and does not include either the
-<B>-initial_password</B> or <B>-password_for_admin</B>
-arguments.
-<PRE> % <B>kas create smith</B>
- Password for admin:
- initial_password:
- Verifying, please re-enter initial_password:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf189.htm#HDRKAS_LIST">kas list</A>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf182.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf184.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf183.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf185.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_DELETE" HREF="auarf002.htm#ToC_198">kas delete</A></H2>
-<A NAME="IDX5078"></A>
-<A NAME="IDX5079"></A>
-<A NAME="IDX5080"></A>
-<A NAME="IDX5081"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes an entry from the Authentication Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas delete -name</B> <<VAR>name of user</VAR>>
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas d -na</B> <<VAR>name of user</VAR>> [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-
-<B>kas rm -na</B> <<VAR>name of user</VAR>> [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas delete</B> command removes from the Authentication Database
-the user entry named by the <B>-name</B> argument. The indicated
-user becomes unable to log in, or the indicated server becomes unreachable
-(because the Authentication Server's Ticket Granting Service module no
-longer has a key with which to seal tickets for the server).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the Authentication Database entry to delete.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the administrative user <B>admin</B>
-entering interactive mode to delete three accounts.
-<PRE> % <B>kas</B>
- Password for admin:
- ka> <B>delete smith</B>
- ka><B> delete pat</B>
- ka> <B>delete terry</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf183.htm#HDRKAS_CREATE">kas create</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf183.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf185.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf184.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf186.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_EXAMINE" HREF="auarf002.htm#ToC_199">kas examine</A></H2>
-<A NAME="IDX5082"></A>
-<A NAME="IDX5083"></A>
-<A NAME="IDX5084"></A>
-<A NAME="IDX5085"></A>
-<A NAME="IDX5086"></A>
-<A NAME="IDX5087"></A>
-<A NAME="IDX5088"></A>
-<A NAME="IDX5089"></A>
-<A NAME="IDX5090"></A>
-<A NAME="IDX5091"></A>
-<A NAME="IDX5092"></A>
-<A NAME="IDX5093"></A>
-<A NAME="IDX5094"></A>
-<A NAME="IDX5095"></A>
-<A NAME="IDX5096"></A>
-<A NAME="IDX5097"></A>
-<A NAME="IDX5098"></A>
-<A NAME="IDX5099"></A>
-<A NAME="IDX5100"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays information from an Authentication Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas examine -name</B> <<VAR>name of user</VAR>> [<B>-showkey</B>]
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas e -na</B> <<VAR>name of user</VAR>> [<B>-sh</B>]
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-se</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas examine</B> command formats and displays information from
-the Authentication Database entry of the user named by the <B>-name</B>
-argument.
-<P>To alter the settings displayed with this command, issue the <B>kas
-setfields</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>Displaying actual keys on the standard output stream by including the
-<B>-showkey</B> flag constitutes a security exposure. For most
-purposes, it is sufficient to display a checksum.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the Authentication Database entry from which to display
-information.
-<P><DT><B><B>-showkey</B>
-</B><DD>Displays the octal digits that constitute the key. The issuer must
-have the <TT>ADMIN</TT> flag on his or her Authentication Database
-entry.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes:
-<UL>
-<P><LI>The entry name, following the string <TT>User data for</TT>.
-<P><LI>One or more status flags in parentheses; they appear only if an
-administrator has used the <B>kas setfields</B> command to change them
-from their default values. A plus sign (<TT>+</TT>) separates the
-flags if there is more than one. The nondefault values that can appear,
-and their meanings, are as follows:
-<DL>
-<P><DT><B><TT>ADMIN</TT>
-</B><DD>Enables the user to issue privileged <B>kas</B> commands (default is
-<TT>NOADMIN</TT>)
-<P><DT><B><TT>NOTGS</TT>
-</B><DD>Prevents the user from obtaining tickets from the Authentication
-Server's Ticket Granting Service (default is <TT>TGS</TT>)
-<P><DT><B><TT>NOSEAL</TT>
-</B><DD>Prevents the Ticket Granting Service from using the entry's key field
-as an encryption key (default is <TT>SEAL</TT>)
-<P><DT><B><TT>NOCPW</TT>
-</B><DD>Prevents the user from changing his or her password (default is
-<TT>CPW</TT>)
-</DL>
-<A NAME="IDX5101"></A>
-<A NAME="IDX5102"></A>
-<A NAME="IDX5103"></A>
-<P><LI>The key version number, in parentheses, following the word <TT>key</TT>,
-then one of the following.
-<UL>
-<P><LI>A checksum equivalent of the key, following the string <TT>cksum
-is</TT>, if the <B>-showkey</B> flag is not included. The checksum
-is a decimal number derived by encrypting a constant with the key. In
-the case of the <B><B>afs</B></B> entry, this number must match the
-checksum with the corresponding key version number in the output of the
-<B>bos listkeys</B> command; if not, follow the instructions in the
-<I>IBM AFS Administration Guide</I> for creating a new server encryption
-key.
-<P><LI>The actual key, following a colon, if the <B>-showkey</B> flag is
-included. The key consists of eight octal numbers, each represented as
-a backslash followed by three decimal digits.
-</UL>
-<P><LI>The date the user last changed his or her own password, following the
-string <TT>last cpw</TT> (which stands for "last change of
-password").
-<P><LI>The string <TT>password will never expire</TT> indicates that the
-associated password never expires; the string <TT>password will
-expire</TT> is followed by the password's expiration date. After
-the indicated date, the user cannot authenticate, but has 30 days after it in
-which to use the <B>kpasswd</B> or <B>kas setpassword</B> command to
-set a new password. After 30 days, only an administrator (one whose
-account is marked with the <TT>ADMIN</TT> flag) can change the password by
-using the <B>kas setpassword</B> command. To set the password
-expiration date, use the <B>kas setfields</B> command's
-<B>-pwexpires</B> argument.
-<P><LI>The number of times the user can fail to provide the correct password
-before the account locks, followed by the string <TT>consecutive unsuccessful
-authentications are permitted</TT>, or the string <TT>An unlimited number of
-unsuccessful authentications is permitted</TT> to indicate that there is no
-limit. To set the limit, use the <B>kas setfields</B>
-command's <B>-attempts</B> argument. To unlock a locked
-account, use the <B>kas unlock</B> command. The <B>kas
-setfields</B> reference page discusses how the implementation of the lockout
-feature interacts with this setting.
-<P><LI>The number of minutes for which the Authentication Server refuses the
-user's login attempts after the limit on consecutive unsuccessful
-authentication attempts is exceeded, following the string <TT>The lock time
-for this user is</TT>. Use the <B>kas</B> command's
-<B>-locktime</B> argument to set the lockout time. This line
-appears only if a limit on the number of unsuccessful authentication attempts
-has been set with the the <B>kas setfields</B> command's
-<B>-attempts</B> argument.
-<P><LI>An indication of whether the Authentication Server is currently refusing
-the user's login attempts. The string <TT>User is not
-locked</TT> indicates that authentication can succeed, whereas the string
-<TT>User is locked until</TT> <VAR>time</VAR> indicates that the user cannot
-authenticate until the indicated time. Use the <B>kas unlock</B>
-command to enable a user to attempt authentication. This line appears
-only if a limit on the number of unsuccessful authentication attempts has been
-set with the <B>kas setfields</B> command's <B>-attempts</B>
-argument.
-<P><LI>The date on which the Authentication Server entry expires, or the string
-<TT>entry never expires</TT> to indicate that the entry does not
-expire. A user becomes unable to authenticate when his or her entry
-expires. Use the <B>kas setfields</B> command's
-<B>-expiration</B> argument to set the expiration date.
-<P><LI>The maximum possible lifetime of the tokens that the Authentication Server
-grants the user. This value interacts with several others to determine
-the actual lifetime of the token, as described on the <B>klog</B>
-reference page. Use the <B>kas setfields</B> command's
-<B>-lifetime</B> argument to set this value.
-<P><LI>The date on which the entry was last modified, following the string
-<TT>last mod on</TT> and the user name of the administrator who modified
-it. The date on which a user changed his or her own password is
-recorded on the second line of output as <TT>last cpw</TT> instead.
-<P><LI>An indication of whether the user can reuse one of his or her last twenty
-passwords when issuing the <B>kpasswd</B>, <B>kas setpassword</B>, or
-<B>kas setkey</B> commands. Use the <B>kas setfields</B>
-command's <B>-reuse</B> argument to set this restriction.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command shows the user <B>smith</B> displaying
-her own Authentication Database entry. Note the <TT>ADMIN</TT> flag,
-which shows that <B>smith</B> is privileged.
-<PRE> % <B>kas examine smith</B>
- Password for smith:
- User data for smith (ADMIN)
- key (0) cksum is 3414844392, last cpw: Thu Mar 25 16:05:44 1999
- password will expire: Fri Apr 30 20:44:36 1999
- 5 consecutive unsuccessful authentications are permitted.
- The lock time for this user is 25.5 minutes.
- User is not locked.
- entry never expires. Max ticket lifetime 100.00 hours.
- last mod on Tue Jan 5 08:22:29 1999 by admin
- permit password reuse
-
-</PRE>
-<P>In the following example, the user <B>pat</B> examines his
-Authentication Database entry to determine when the account lockout currently
-in effect will end.
-<PRE> % <B>kas examine pat</B>
- Password for pat:
- User data for pat
- key (0) cksum is 73829292912, last cpw: Wed Apr 7 11:23:01 1999
- password will expire: Fri Jun 11 11:23:01 1999
- 5 consecutive unsuccessful authentications are permitted.
- The lock time for this user is 25.5 minutes.
- User is locked until Tue Sep 21 12:25:07 1999
- entry expires on never. Max ticket lifetime 100.00 hours.
- last mod on Thu Feb 4 08:22:29 1999 by admin
- permit password reuse
-
-</PRE>
-<P>In the following example, an administrator logged in as <B>admin</B>
-uses the <B>-showkey</B> flag to display the octal digits that constitute
-the key in the <B>afs</B> entry.
-<PRE> % <B>kas examine -name afs -showkey</B>
- Password for admin: <VAR>admin_password</VAR>
- User data for afs
- key (12): \357\253\304\352\234\236\253\352, last cpw: no date
- entry never expires. Max ticket lifetime 100.00 hours.
- last mod on Thu Mar 25 14:53:29 1999 by admin
- permit password reuse
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>A user can examine his or her own entry. To examine others'
-entries or to include the <B>-showkey</B> flag, the issuer must have the
-<TT>ADMIN</TT> flag set in his or her Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf107.htm#HDRBOS_LISTKEYS">bos listkeys</A>
-<P><A HREF="auarf115.htm#HDRBOS_SETAUTH">bos setauth</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf202.htm#HDRKPASSWD">kpasswd</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf184.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf186.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf185.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf187.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_FORGETTICKET" HREF="auarf002.htm#ToC_200">kas forgetticket</A></H2>
-<A NAME="IDX5104"></A>
-<A NAME="IDX5105"></A>
-<A NAME="IDX5106"></A>
-<A NAME="IDX5107"></A>
-<A NAME="IDX5108"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Discards all tickets for the issuer
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas forgetticket</B> [<B>-all</B>] [<B>-help</B>]
-
-<B>kas f</B> [<B>-a</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas forgetticket</B> command discards all of the issuer's
-tickets stored in the local machine's kernel memory. This includes
-the AFS server ticket from each cell in which the user has authenticated, and
-any tickets that the user have acquired during the current <B>kas</B>
-session (either when entering the session or by using the <B>kas
-getticket</B> command).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-all
-</B><DD>Discards all tickets. This argument explicitly invokes the
-command's default behavior.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command discards all of the issuer's tickets.
-<PRE> % <B>kas forgetticket</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf185.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf187.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf186.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf188.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_HELP" HREF="auarf002.htm#ToC_201">kas help</A></H2>
-<A NAME="IDX5109"></A>
-<A NAME="IDX5110"></A>
-<A NAME="IDX5111"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of each specified <B>kas</B> command or lists
-functional descriptions of all <B>kas</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas help </B>[<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>kas h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>kas</B> command.
-<P>To list every <B>kas</B> command whose name or short description
-includes a specified keyword, use the <B>kas apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>kas</B> part of the command name, providing only
-the operation code (for example, specify <B>setpassword</B>, not <B>kas
-setpassword</B>). If this argument is omitted, the output briefly
-describes every <B>kas</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>kas</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>kas
-setpassword</B> command:
-<PRE> % <B>kas help setpassword</B>
- kas setpassword: set a user's password
- aliases: sp
- Usage: kas setpassword -name <name of user>
- [-new_password <new password>] [-kvno <key version number>]
- [-admin_username <admin principal to use for authentication>]
- [-password_for_admin <password>] [-cell <cell name>]
- [-servers <explicit list of authentication servers>+] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf182.htm#HDRKAS_APROPOS">kas apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf186.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf188.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf187.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf189.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_INTERACTIVE" HREF="auarf002.htm#ToC_202">kas interactive</A></H2>
-<P><STRONG>Purpose</STRONG>
-<P>Enters interactive mode
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas interactive</B> [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas i</B> [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-n</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas interactive</B> command establishes an interactive session
-for the issuer of the command. By default, the command interpreter
-establishes an authenticated connection for the user logged into the local
-file system with all of the Authentication Servers listed in the local
-<B>/usr/vice/etc/CellServDB</B> file for the cell named in the local
-<B>/usr/vice/etc/ThisCell</B> file. To specify an alternate
-identity, cell name, or list of Authentication Servers, include the
-<B>-admin_username</B>, <B>-cell</B>, or <B>-servers</B> arguments
-respectively. Interactive mode lasts for six hours unless the maximum
-ticket lifetime for the issuer or the Authentication Server's Ticket
-Granting Service is shorter.
-<P>There are two other ways to enter interactive mode, in addition to the
-<B>kas interactive</B> command:
-<OL TYPE=1>
-<P><LI>Type the <B>kas</B> command at the shell prompt without any operation
-code. If appropriate, include one or more of the
-<B>-admin_username</B>, <B>-password_for_admin</B>, <B>-cell</B>,
-and <B>-servers</B> arguments.
-<P><LI>Type the <B>kas</B> command followed by a user name and cell name,
-separated by an <B>@</B> sign (for example: <B>kas
-admin@abc.com</B>), to establish a connection under the specified
-identity with the Authentication Servers listed in the local
-<B>/usr/vice/etc/CellServDB</B> file for the indicated cell. If
-appropriate, provide the <B>-servers</B> argument to specify an alternate
-list of Authentication Server machines that belong to the indicated
-cell.
-</OL>
-<P>There are several consequences of entering interactive mode:
-<UL>
-<P><LI>The <TT>ka></TT> prompt replaces the system (shell) prompt. When
-typing commands at this prompt, provide only the operation code (omit the
-command suite name, <B>kas</B>).
-<P><LI>The command interpreter does not prompt for the issuer's
-password.
-<P>The issuer's identity and password, the relevant cell, and the set of
-Authentication Server machines specified when entering interactive mode apply
-to all commands issued during the session. They cannot be changed
-without leaving the session, except by using the <B>(kas)
-noauthentication</B> command to replace the current authenticated
-connections with unauthenticated ones. The <B>-admin_username</B>,
-<B>-password_for_admin</B>, <B>-cell</B>, and <B>-servers</B>
-arguments are ignored if provided on a command issued during interactive
-mode.
-</UL>
-<P>To establish an unauthenticated connection to the Authentication Server,
-include the <B>-noauth</B> flag or provide an incorrect password.
-Unless authorization checking is disabled on each Authentication Server
-machine involved, however, it is not possible to perform any privileged
-operations within such a session.
-<P>To end the current authenticated connection and establish an
-unauthenticated one, issue the <B>(kas) noauthentication</B>
-command. To leave interactive mode and return to the regular shell
-prompt, issue the <B>(kas) quit</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows a user entering interactive mode as the
-privileged user <B>admin</B>.
-<PRE> % <B>kas interactive admin</B>
- Password for admin: <VAR>admin_password</VAR>
- ka>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf191.htm#HDRKAS_NOAUTH">kas noauthentication</A>
-<P><A HREF="auarf192.htm#HDRKAS_QUIT">kas quit</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf187.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf189.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf188.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf190.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_LIST" HREF="auarf002.htm#ToC_203">kas list</A></H2>
-<A NAME="IDX5112"></A>
-<A NAME="IDX5113"></A>
-<A NAME="IDX5114"></A>
-<A NAME="IDX5115"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays all entries in the Authentication Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas list</B> [<B>-long</B>] [<B>-showadmin</B>] [<B>-showkey</B>]
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas ls</B> [<B>-l</B>] [<B>-showa</B>] [<B>-showk</B>]
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-se</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-n</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas list</B> command either displays all entries from the
-Authentication Database by name, or displays the full database entry for a
-defined set of entries, as determined by the flag provided:
-<UL>
-<P><LI>To display every entry in the Authentication Database in full, include the
-<B>-long</B> flag.
-<P><LI>To display only those entries in full that have the <TT>ADMIN</TT> flag
-set, include the <B>-showadmin</B> flag.
-<P><LI>To list only the name of each Authentication Database entry, omit both the
-<B>-long</B> and <B>-showadmin</B> flags.
-</UL>
-<P>By default, full entries include a checksum for the encryption key, rather
-than the actual octal digits that constitute the key. To display the
-octal digits, include the <B>-showkey</B> flag with the <B>-long</B>
-or <B>-showadmin</B> flag.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-long
-</B><DD>Displays every Authentication Database entry in full. Provide this
-flag or the <B>-showadmin</B> flag, or omit both to display just the name
-of every database entry.
-<P><DT><B>-showadmin
-</B><DD>Displays in full only the Authentication Database entries that have the
-<TT>ADMIN</TT> flag set. Provide this flag or the <B>-long</B>
-flag, or omit both to display just the name of every database entry.
-<P><DT><B>-showkey
-</B><DD>Displays the octal digits that constitute the key in each full
-entry. Provide either the <B>-long</B> or <B>-showadmin</B>
-flag along with this one.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If neither the <B>-long</B> or <B>-showadmin</B> flag is provided,
-the output lists the name of each entry in the Authentication Database on its
-own line.
-<P>If the <B>-long</B> flag is included, the output includes every
-Authentication Database entry in full. If the <B>-showadmin</B>
-flag is included, the output includes in full only the Authentication Database
-entries that have the <TT>ADMIN</TT> flag set. If the
-<B>-showkey</B> is provided along with either one, the output includes the
-octal digits that constitute the encryption key in each entry.
-<P>A full Authentication Database entry includes the same information
-displayed by the <B>kas examine</B> command; for details, see that
-command's reference page.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf188.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf190.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf189.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf191.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_LISTTICKETS" HREF="auarf002.htm#ToC_204">kas listtickets</A></H2>
-<A NAME="IDX5116"></A>
-<A NAME="IDX5117"></A>
-<A NAME="IDX5118"></A>
-<A NAME="IDX5119"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays all of the issuer's tickets (tokens)
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas listtickets</B> [<B>-name</B> <<VAR>name of server</VAR>>] [<B>-long</B>] [<B>-help</B>]
-
-<B>kas listt</B> [<B>-n</B> <<VAR>name of server</VAR>>] [<B>-l</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas listtickets</B> command displays the associated user ID (AFS
-UID), cell name, and expiration date of some or all of the issuer's
-tickets (tokens), depending on which options are provided:
-<UL>
-<P><LI>To display all tokens, provide neither the <B>-name</B> argument nor
-<B>-long</B> flag. The output is similar to that of the
-<B>tokens</B> command.
-<P><LI>To display a single token, provide the <B>-name</B> argument to
-specify name of the Authentication Database entry for the entity that accepts
-the token. All AFS server processes accept tokens sealed with the key
-from the <B>afs</B> entry.
-<P><LI>To display in addition the octal numbers that constitute the token and
-session key, provide the <B>-long</B> flag.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the Authentication Database entry of the entity (usually a server
-process) that accepts the token to display.
-<P><DT><B>-long
-</B><DD>Displays the octal numbers that constitute the session key and
-ticket.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output reports the AFS UID of the user who owns the token, the service
-(usually, <TT>afs</TT>) and cell for which it is valid, and its expiration
-date, using the following format. If the message does not specify a
-cell, the ticket is for the local cell.
-<PRE> User's (AFS ID <VAR>AFS UID</VAR>) tokens for <VAR>service</VAR>[@<VAR>cellname</VAR>] [Expires <VAR>date</VAR>]
-
-</PRE>
-<P>If the <B>-long</B> flag is provided, the output also includes the
-octal numbers making up the session key and token, along with the key version
-number and the number of bytes in the token (if the number of bytes is not 56,
-there is an error).
-<P>If the marker <TT>[>> POSTDATED <]</TT> appears instead of an
-expiration date, the ticket does not become valid until the indicated
-time. (Only internal calls can create a postdated ticket; there is
-no standard interface that allows users to do this.)
-<P><STRONG>Examples</STRONG>
-<P>The following two examples are for a user with AFS UID 1020 in the
-<B>abc.com</B> cell and AFS UID 35 in the
-<B>test.abc.com</B> cell. He is working on a machine
-in the first cell and is authenticated in both cells.
-<PRE> % <B>kas listtickets</B>
- User's (AFS ID 1020) tokens for afs [Expires Wed Mar 31 9:30:54 1999]
- User's (AFS ID 35@test.abc.com) tokens for afs@test.abc.com \
- [Expires Wed Mar 31 13:54:26 1999]
-
- % <B>kas listtickets -name afs -long</B>
- User's (AFS ID 1020) tokens for afs [Expires Wed Mar 31 9:30:54 1999]
- SessionKey: \375\205\351\227\032\310\263\013
- Ticket: (kvno = 0, len = 56): \033\005\221\156\203\278\312\058\016\133 <VAR>(etc.)</VAR>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf189.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf191.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf190.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf192.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_NOAUTH" HREF="auarf002.htm#ToC_205">kas noauthentication</A></H2>
-<A NAME="IDX5120"></A>
-<A NAME="IDX5121"></A>
-<A NAME="IDX5122"></A>
-<A NAME="IDX5123"></A>
-<A NAME="IDX5124"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Discards an authenticated identity in interactive mode
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>noauthentication</B> [<B>-help</B>]
-
-<B>n</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas noauthentication</B> command closes the (presumably
-authenticated) connection that the issuer established with one or more
-Authentication Server processes when entering interactive mode. It
-opens a new unauthenticated connection to each server, assigning the issuer
-the unprivileged identity <B>anonymous</B>. It does not actually
-discard the user's tokens from the Cache Manager's memory (as the
-<B>unlog</B> or <B>kas forgetticket</B> command does). Unless
-authorization checking is disabled on each Authentication Server machine, it
-becomes impossible to perform any privileged operations within the session
-established by this command.
-<P>This command is operative only during interactive mode, so omit the
-<B>kas</B> command suite name from the command line.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command discards the authentication information with
-which the user entered interactive mode.
-<PRE> ka><B> noauthentication</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf186.htm#HDRKAS_FORGETTICKET">kas forgetticket</A>
-<P><A HREF="auarf188.htm#HDRKAS_INTERACTIVE">kas interactive</A>
-<P><A HREF="auarf238.htm#HDRUNLOG">unlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf190.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf192.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf191.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf193.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_QUIT" HREF="auarf002.htm#ToC_206">kas quit</A></H2>
-<A NAME="IDX5125"></A>
-<A NAME="IDX5126"></A>
-<A NAME="IDX5127"></A>
-<A NAME="IDX5128"></A>
-<A NAME="IDX5129"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Leaves interactive mode
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>quit</B> [<B>-help</B>]
-
-<B>q</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas quit</B> command ends interactive mode, severing the
-authenticated connection to one or more Authentication Server processes and
-returning the issuer to the normal shell prompt.
-<P>This command is operative only during interactive mode, so omit the
-<B>kas</B> command suite name from the command line.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example demonstrates how the normal command shell prompt
-returns when the issuer leaves interactive mode.
-<PRE> ka> <B>quit</B>
- %
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf188.htm#HDRKAS_INTERACTIVE">kas interactive</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf191.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf193.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf192.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf194.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_SETFIELDS" HREF="auarf002.htm#ToC_207">kas setfields</A></H2>
-<A NAME="IDX5130"></A>
-<A NAME="IDX5131"></A>
-<A NAME="IDX5132"></A>
-<A NAME="IDX5133"></A>
-<A NAME="IDX5134"></A>
-<A NAME="IDX5135"></A>
-<A NAME="IDX5136"></A>
-<A NAME="IDX5137"></A>
-<A NAME="IDX5138"></A>
-<A NAME="IDX5139"></A>
-<A NAME="IDX5140"></A>
-<A NAME="IDX5141"></A>
-<A NAME="IDX5142"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets optional characteristics in an Authentication Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas setfields -name</B> <<VAR>name of user</VAR>>
- [<B>-flags</B> <<VAR>hex flag value or flag name expression</VAR>>]
- [<B>-expiration</B> <<VAR>date of account expiration</VAR>>]
- [<B>-lifetime</B> <<VAR>maximum ticket lifetime</VAR>>]
- [<B>-pwexpires</B> <<VAR>number days password is valid ([0..254])</VAR>>]
- [<B>-reuse</B> <<VAR>permit password reuse (yes/no)</VAR>>]
- [<B>-attempts</B> <<VAR>maximum successive failed login tries ([0..254])</VAR>>]
- [<B>-locktime</B> <<VAR>failure penalty [hh:mm or minutes]</VAR>>]
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas setf -na</B> <<VAR>name of user</VAR>> [<B>-f</B> <<VAR>hex flag value or flag name expression</VAR>>]
- [<B>-e</B> <<VAR>date of account expiration</VAR>>] [<B>-li</B> <<VAR>maximum ticket lifetime</VAR>>]
- [<B>-pw</B> <<VAR>number days password is valid ([0..254])</VAR>>]
- [<B>-r</B> <<VAR>permit password reuse (yes/no)</VAR>>]
- [<B>-at</B> <<VAR>maximum successive failed login tries ([0..254])</VAR>>]
- [<B>-lo</B> <<VAR>failure penalty [hh:mm or minutes]</VAR>>]
- [<B>-ad</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-pa</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-
-<B>kas sf -na</B> <<VAR>name of user</VAR>> [<B>-f</B> <<VAR>hex flag value or flag name expression</VAR>>]
- [<B>-e</B> <<VAR>date of account expiration</VAR>>] [<B>-li</B> <<VAR>maximum ticket lifetime</VAR>>]
- [<B>-pw</B> <<VAR>number days password is valid ([0..254])</VAR>>]
- [<B>-r</B> <<VAR>permit password reuse (yes/no)</VAR>>]
- [<B>-at</B> <<VAR>maximum successive failed login tries ([0..254])</VAR>>]
- [<B>-lo</B> <<VAR>failure penalty [hh:mm or minutes]</VAR>>]
- [<B>-ad</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-pa</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas setfields</B> command changes the Authentication Database
-entry for the user named by the <B>-name</B> argument in the manner
-specified by the various optional arguments, which can occur singly or in
-combination:
-<UL>
-<P><LI>To set the flags that determine whether the user has administrative
-privileges to the Authentication Server, can obtain a ticket, can change his
-or her password, and so on, include the <B>-flags</B> argument.
-<P><LI>To set when the Authentication Database entry expires, include the
-<B>-expiration</B> argument.
-<P><LI>To set the maximum ticket lifetime associated with the entry, include the
-<B>-lifetime</B> argument. The reference page for the
-<B>klog</B> command explains how this value interacts with others to
-determine the actual lifetime of a token.
-<P><LI>To set when the user's password expires, include the
-<B>-pwexpires</B> argument.
-<P><LI>To set whether the user can reuse any of the previous twenty passwords
-when creating a new one, include the <B>-reuse</B> argument.
-<P><LI>To set the maximum number of times the user can provide an incorrect
-password before the Authentication Server refuses to accept any more attempts
-(locks the issuer out), include the <B>-attempts</B> argument.
-After the sixth failed authentication attempt, the Authentication Server logs
-a message in the UNIX system log file (the <B>syslog</B> file or
-equivalent, for which the standard location varies depending on the operating
-system).
-<P><LI>To set how long the Authentication Server refuses to process
-authentication attempts for a locked-out user, set the <B>-locktime</B>
-argument.
-</UL>
-<P>The <B>kas examine</B> command displays the settings made with this
-command.
-<P><STRONG>Cautions</STRONG>
-<P>The password lifetime set with the <B>-pwexpires</B> argument begins at
-the time the user's password was last changed, rather than when this
-command is issued. It can therefore be retroactive. If, for
-example, a user changed her password 100 days ago and the password lifetime is
-set to 100 days or less, the password effectively expires immediately.
-To avoid retroactive expiration, instruct the user to change the password just
-before setting a password lifetime.
-<P>Administrators whose authentication accounts have the <TT>ADMIN</TT> flag
-enjoy complete access to the sensitive information in the Authentication
-Database. To prevent access by unauthorized users, use the
-<B>-attempts</B> argument to impose a fairly strict limit on the number of
-times that a user obtaining administrative tokens can provide an incorrect
-password. Note, however, that there must be more than one account in
-the cell with the <TT>ADMIN</TT> flag. The <B>kas unlock</B>
-command requires the <TT>ADMIN</TT> privilege, so it is important that the
-locked-out administrator (or a colleague) can access another
-<TT>ADMIN</TT>-privileged account to unlock the current account.
-<P>In certain circumstances, the mechanism used to enforce the number of
-failed authentication attempts can cause a lockout even though the number of
-failed attempts is less than the limit set by the <B>-attempts</B>
-argument. Client-side authentication programs such as <B>klog</B>
-and an AFS-modified login utility normally choose an Authentication Server at
-random for each authentication attempt, and in case of a failure are likely to
-choose a different Authentication Server for the next attempt. The
-Authentication Servers running on the various database server machines do not
-communicate with each other about how many times a user has failed to provide
-the correct password to them. Instead, each Authentication Server
-maintains its own separate copy of the auxiliary database file
-<B>kaserverauxdb</B> (located in the <B>/usr/afs/local</B> directory
-by default), which records the number of consecutive authentication failures
-for each user account and the time of the most recent failure. This
-implementation means that on average each Authentication Server knows about
-only a fraction of the total number of failed attempts. The only way to
-avoid allowing more than the number of attempts set by the
-<B>-attempts</B> argument is to have each Authentication Server allow only
-some fraction of the total. More specifically, if the limit on failed
-attempts is <I>f</I>, and the number of Authentication Servers is
-<I>S</I>, then each Authentication Server can only permit a number of
-attempts equal to <I>f</I> divided by <I>S</I> (the Ubik
-synchronization site for the Authentication Server tracks any remainder,
-<I>fmodS</I>).
-<P>Normally, this implementation does not reduce the number of allowed
-attempts to less than the configured limit (<I>f</I>). If one
-Authentication Server refuses an attempt, the client contacts another instance
-of the server, continuing until either it successfully authenticates or has
-contacted all of the servers. However, if one or more of the
-Authentication Server processes is unavailable, the limit is effectively
-reduced by a percentage equal to the quantity <I>U</I> divided by
-<I>S</I>, where <I>U</I> is the number of unavailable servers and
-<I>S</I> is the number normally available.
-<P>To avoid the undesirable consequences of setting a limit on failed
-authentication attempts, note the following recommendations:
-<UL>
-<P><LI>Do not set the <B>-attempts</B> argument (the limit on failed
-authentication attempts) too low. A limit of nine failed attempts is
-recommended for regular user accounts, to allow three failed attempts per
-Authentication Server in a cell with three database server machines.
-<P><LI>Set fairly short lockout times when including the <B>-locktime</B>
-argument. Although guessing passwords is a common method of attack, it
-is not a very sophisticated one. Setting a lockout time can help
-discourage attackers, but excessively long times are likely to be more of a
-burden to authorized users than to potential attackers. A lockout time
-of 25 minutes is recommended for regular user accounts.
-<P><LI>Do not assign an infinite lockout time on an account (by setting the
-<B>-locktime</B> argument to <B>0</B> [zero]) unless there is a highly
-compelling reason. Such accounts almost inevitably become locked at
-some point, because each Authentication Server never resets the account's
-failure counter in its copy of the <B>kaauxdb</B> file (in contrast, when
-the lockout time is not infinite, the counter resets after the specified
-amount of time has passed since the last failed attempt to that Authentication
-Server). Furthermore, the only way to unlock an account with an
-infinite lockout time is for an administrator to issue the <B>kas
-unlock</B> command. It is especially dangerous to set an infinite
-lockout time on an administrative account; if all administrative accounts
-become locked, the only way to unlock them is to shut down all instances of
-the Authentication Server and remove the <B>kaauxdb</B> file on
-each.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the Authentication Database account for which to change
-settings.
-<P><DT><B>-flags
-</B><DD>Sets one or more of four toggling flags, adding them to any flags
-currently set. Either specify one or more of the following strings, or
-specify a hexidecimal number that combines the indicated values. To
-return all four flags to their defaults, provide a value of <B>0</B>
-(zero). To set more than one flag at once using the strings, connect
-them with plus signs (example: <B>NOTGS+ADMIN+CPW</B>). To
-remove all the current flag settings before setting new ones, precede the list
-with an equal sign (example: <B>=NOTGS+ADMIN+CPW</B>).
-<DL>
-<P><DT><B>ADMIN
-</B><DD>The user is allowed to issue privileged <B>kas</B> commands
-(hexadecimal equivalent is <B>0x004</B>, default is
-<B>NOADMIN</B>).
-<A NAME="IDX5143"></A>
-<P><DT><B>NOTGS
-</B><DD>The Authentication Server's Ticket Granting Service (TGS) refuses to
-issue tickets to the user (hexadecimal equivalent is <B>0x008</B>, default
-is <B>TGS</B>).
-<A NAME="IDX5144"></A>
-<P><DT><B>NOSEAL
-</B><DD>The Ticket Granting Service cannot use the contents of this entry's
-key field as an encryption key (hexadecimal equivalent is <B>0x020</B>,
-default is <B>SEAL</B>).
-<A NAME="IDX5145"></A>
-<P><DT><B>NOCPW
-</B><DD>The user cannot change his or her own password or key (hexadecimal
-equivalent is <B>0x040</B>, default is <B>CPW</B>).
-<A NAME="IDX5146"></A>
-</DL>
-<P><DT><B>-expiration
-</B><DD>Determines when the entry itself expires. When a user entry
-expires, the user becomes unable to log in; when a server entry such as
-<B>afs</B> expires, all server processes that use the associated key
-become inaccessible. Provide one of the three acceptable values:
-<DL>
-<P><DT><B>never
-</B><DD>The account never expires (the default).
-<P><DT><B><VAR>mm/dd/yyyy</VAR>
-</B><DD>Sets the expiration date to 12:00 a.m. on the
-indicated date (month/day/year). Examples: <B>01/23/1999</B>,
-<B>10/07/2000</B>.
-<P><DT><B>"<VAR>mm/dd/yyyy hh:MM</VAR>"
-</B><DD>Sets the expiration date to the indicated time (hours:minutes) on
-the indicated date (month/day/year). Specify the time in 24-hour format
-(for example, <B>20:30</B> is 8:30 p.m.) Date
-format is the same as for a date alone. Surround the entire instance
-with quotes because it contains a space. Examples:
-<B>"01/23/1999 22:30"</B>, <B>"10/07/2000
-3:45"</B>.
-</DL>
-<P>
-<P>Acceptable values for the year range from <B>1970</B> (1 January 1970
-is time 0 in the standard UNIX date representation) through <B>2037</B>
-(2037 is the maximum because the UNIX representation cannot accommodate dates
-later than a value in February 2038).
-<P><DT><B>-lifetime
-</B><DD>Specifies the maximum lifetime that the Authentication Server's
-Ticket Granting Service (TGS) can assign to a ticket. If the account
-belongs to a user, this value is the maximum lifetime of a token issued to the
-user. If the account corresponds to a server such as <B>afs</B>,
-this value is the maximum lifetime of a ticket that the TGS issues to clients
-for presentation to the server during mutual authentication.
-<P>Specify an integer that represents a number of seconds (<B>3600</B>
-equals one hour), or include a colon in the number to indicate a number of
-hours and minutes (<B>10:00</B> equals 10 hours). If this
-argument is omitted, the default setting is 100:00 hours (360000
-seconds).
-<P><DT><B>-pwexpires
-</B><DD>Sets the number of days after the user's password was last changed
-that it remains valid. Provide an integer from the range <B>1</B>
-through <B>254</B> to specify the number of days until expiration, or the
-value <B>0</B> to indicate that the password never expires (the
-default).
-<P>When the password expires, the user is unable to authenticate, but has 30
-days after the expiration date in which to use the <B>kpasswd</B> command
-to change the password (after that, only an administrator can change it by
-using the <B>kas setpassword</B> command). Note that the clock
-starts at the time the password was last changed, not when the <B>kas
-setfields</B> command is issued. To avoid retroactive expiration,
-have the user change the password just before issuing a command that includes
-this argument.
-<P><DT><B>-reuse
-</B><DD>Specifies whether or not the user can reuse any of his or her last 20
-passwords. The acceptable values are <B>yes</B> to allow reuse of
-old passwords (the default) and <B>no</B> to prohibit reuse of a password
-that is similar to one of the previous 20 passwords.
-<P><DT><B>-attempts
-</B><DD>Sets the number of consecutive times the user can provide an incorrect
-password during authentication (using the <B>klog</B> command or a login
-utility that grants AFS tokens). When the user exceeds the limit, the
-Authentication Server rejects further attempts (locks the user out) for the
-amount of time specified by the <B>-locktime</B> argument. Provide
-an integer from the range <B>1</B> through <B>254</B> to specify the
-number of failures allowed, or <B>0</B> to indicate that there is no limit
-on authentication attempts (the default value).
-<P><DT><B>-locktime
-</B><DD>Specifies how long the Authentication Server refuses authentication
-attempts from a user who has exceeded the failure limit set by the
-<B>-attempts</B> argument.
-<P>Specify a number of hours and minutes (<VAR>hh</VAR>:<VAR>mm</VAR>) or
-minutes only (<VAR>mm</VAR>), from the range <B>01</B> (one minute) through
-<B>36:00</B> (36 hours). The <B>kas</B> command
-interpreter automatically reduces any larger value to <B>36:00</B>
-and also rounds up any non-zero value to the next higher multiple of
-8.5 minutes. A value of <B>0</B> (zero) sets an infinite
-lockout time; an administrator must issue the <B>kas unlock</B>
-command to unlock the account.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, an administrator using the <B>admin</B>
-account grants administrative privilege to the user <B>smith</B>, and sets
-the Authentication Database entry to expire at midnight on 31 December
-2000.
-<PRE> %<B> kas setfields -name smith -flags ADMIN -expiration 12/31/2000</B>
- Password for admin:
-
-</PRE>
-<P>In the following example, an administrator using the <B>admin</B>
-account sets the user <B>pat</B>'s password to expire in 60 days from
-when it last changed, and prohibits reuse of passwords.
-<PRE> %<B> kas setfields -name pat -pwexpires 60 -reuse no</B>
- Password for admin:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf046.htm#HDRKASERVERAUXDB">kaserverauxdb</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf202.htm#HDRKPASSWD">kpasswd</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf192.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf194.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf193.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf195.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_SETPASSWORD" HREF="auarf002.htm#ToC_208">kas setpassword</A></H2>
-<A NAME="IDX5147"></A>
-<A NAME="IDX5148"></A>
-<A NAME="IDX5149"></A>
-<A NAME="IDX5150"></A>
-<A NAME="IDX5151"></A>
-<A NAME="IDX5152"></A>
-<A NAME="IDX5153"></A>
-<A NAME="IDX5154"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes the key field in an Authentication Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas setpassword -name</B> <<VAR>name of user</VAR>> [<B>-new_password</B> <<VAR>new password</VAR>>]
- [<B>-kvno</B> <<VAR>key version number</VAR>>]
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas setpasswd -na</B> <<VAR>name of user</VAR>> [<B>-ne</B> <<VAR>new password</VAR>>]
- [<B>-k</B> <<VAR>key version number</VAR>>]
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [-c <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-
-<B>kas setp -na</B> <<VAR>name of user</VAR>> [<B>-ne</B> <<VAR>new password</VAR>>] [<B>-k</B> <<VAR>key version number</VAR>>]
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [-c <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-
-<B>kas sp -na</B> <<VAR>name of user</VAR>> [<B>-ne</B> <<VAR>new password</VAR>>] [<B>-k</B> <<VAR>key version number</VAR>>]
- [<B>-a</B> <<VAR>admin principal to use for authentication </VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas setpassword</B> command accepts a character string of
-unlimited length, scrambles it into a form suitable for use as an encryption
-key, places it in the key field of the Authentication Database entry named by
-the <B>-name</B> argument, and assigns it the key version number specified
-by the <B>-kvno</B> argument.
-<P>To avoid making the password string visible at the shell prompt, omit the
-<B>-new_password</B> argument. Prompts then appear at the shell
-which do not echo the password visibly.
-<P>When changing the <B>afs</B> server key, also issue <B>bos
-addkey</B> command to add the key (with the same key version number) to the
-<B>/usr/afs/etc/KeyFile</B> file. See the <I>IBM AFS
-Administration Guide</I> for instructions.
-<P>The command interpreter checks the password string subject to the following
-conditions:
-<UL>
-<P><LI>If there is a program called <B>kpwvalid</B> in the same directory as
-the <B>kas</B> binary, the command interpreter invokes it to process the
-password. For details, see the <B>kpwvalid</B> reference
-page.
-<P><LI>If the <B>-reuse</B> argument to the <B>kas setfields</B> command
-has been used to prohibit reuse of previous passwords, the command interpreter
-verifies that the password is not too similar too any of the user's
-previous 20 passwords. It generates the following error message at the
-shell:
-<PRE> Password was not changed because it seems like a reused password
-
-</PRE>
-<P>To prevent a user from subverting this restriction by changing the password
-twenty times in quick succession (manually or by running a script), use the
-<B>-minhours</B> argument on the <B>kaserver</B> initialization
-command. The following error message appears if a user attempts to
-change a password before the minimum time has passed:
-<PRE> Password was not changed because you changed it too
- recently; see your systems administrator
-
-</PRE>
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the entry in which to record the new key.
-<P><DT><B>-new_password
-</B><DD>Specifies the character string the user types when authenticating to
-AFS. Omit this argument and type the string at the resulting prompts so
-that the password does not echo visibly. Note that some non-AFS
-programs cannot handle passwords longer than eight characters.
-<P><DT><B>-kvno
-</B><DD>Specifies the key version number associated with the new key.
-Provide an integer in the range from <B>0</B> through
-<B>255</B>. If omitted, the default is 0 (zero), which is probably
-not desirable for server keys.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, an administrator using the <B>admin</B>
-account changes the password for <B>pat</B> (presumably because
-<B>pat</B> forgot the former password or got locked out of his account in
-some other way).
-<PRE> % <B>kas setpassword pat</B>
- Password for admin:
- new_password:
- Verifying, please re-enter new_password:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>Individual users can change their own passwords. To change another
-user's password or the password (server encryption key) for server
-entries such as <B>afs</B>, the issuer must have the <TT>ADMIN</TT> flag
-set in his or her Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf095.htm#HDRBOS_ADDKEY">bos addkey</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf203.htm#HDRKPWVALID">kpwvalid</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf193.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf195.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf194.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf196.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_STATISTICS" HREF="auarf002.htm#ToC_209">kas statistics</A></H2>
-<A NAME="IDX5155"></A>
-<A NAME="IDX5156"></A>
-<A NAME="IDX5157"></A>
-<A NAME="IDX5158"></A>
-<A NAME="IDX5159"></A>
-<A NAME="IDX5160"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays statistics from an Authentication Server process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas statistics</B> [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas sta</B> [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-n</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas statistics</B> command displays statistics from the
-Authentication Server running on one of the cell's database server
-machines. Use the <B>-servers</B> argument to name a specific
-machine, or the command interpreter chooses one at random from all the
-database server machines with which it has established connections.
-<P><STRONG>Cautions</STRONG>
-<P>The <B>-servers</B> argument is not available in interactive mode,
-making it impossible to specify a certain machine.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The information in the output includes:
-<UL>
-<P><LI>The number of allocation and freeing operations the Authentication Server
-has performed, and how many password change requests it has processed.
-<P><LI>An indication of its hash table use.
-<P><LI>The server machine's IP address in hexadecimal and the date when the
-current instance of the Authentication Server started.
-<P><LI>The number of requests and aborted requests for various services:
-authentication, ticket granting, password setting, entry listing, and so
-on.
-<P><LI>The amount of CPU time that the Authentication Server has used to process
-requests since it started. The amount is not accurate on all system
-types, however.
-<P><LI>The number of entries in the Authentication Database that are marked with
-the <TT>ADMIN</TT> flag.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, an administrator using the <B>admin</B>
-account gathers statistics from the Authentication Server running on the
-machine <B>fs1.abc.com</B>.
-<PRE> % <B>kas statistics -servers fs1.abc.com</B>
- 56 allocs, 46 frees, 0 password changes
- Hash table utilization = 0.100000%
- From host bfff21a7 started at Tue Mar 23 12:42:02 1999:
- of 88 requests for Authenticate, 18 were aborted.
- of 14 requests for GetTicket, 0 were aborted.
- of 4 requests for CreateUser, 1 were aborted.
- of 12 requests for SetFields, 4 were aborted.
- of 3 requests for DeleteUser, 0 were aborted.
- of 23 requests for GetEntry, 4 were aborted.
- of 18 requests for ListEntry, 0 were aborted.
- of 2 requests for GetStats, 1 were aborted.
- of 2 requests for GetRandomKey, 0 were aborted.
- Used 6.015 seconds of CPU time.
- 3 admin accounts
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf194.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf196.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf195.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf197.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_STRINGTOKEY" HREF="auarf002.htm#ToC_210">kas stringtokey</A></H2>
-<A NAME="IDX5161"></A>
-<A NAME="IDX5162"></A>
-<A NAME="IDX5163"></A>
-<A NAME="IDX5164"></A>
-<A NAME="IDX5165"></A>
-<A NAME="IDX5166"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Converts a character string into an octal key
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas stringtokey -string</B> <<VAR>password string</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-help</B>]
-
-<B>kas str -s</B> <<VAR>password string</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas stringtokey</B> command converts the character string
-specified with the <B>-string</B> argument into an octal string suitable
-for use as an encryption key.
-<P>The <B>kas</B> command interpreter generates the octal key by using an
-encryption algorithm on the combination of the specified string and the name
-of the local cell (as recorded in the local <B>/usr/vice/etc/ThisCell</B>
-file). Use the <B>-cell</B> argument to convert a string into a key
-appropriate for a cell other than the local one.
-<P><STRONG>Cautions</STRONG>
-<P>This command writes the key to the standard output stream, on which it can
-possibly be intercepted by third parties. It is not very secure to use
-the key in an actual Authentication Database entry.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-string
-</B><DD>Specifies the character string to convert into an octal key.
-<P><DT><B>-cell
-</B><DD>Specifies the complete Internet domain name of the cell to combine with
-the password string while generating the key. If this argument is
-omitted, the <B>kas</B> command interpreter determines the name of the
-local cell by consulting:
-<UL>
-<P><LI>First, the value of the environment variable AFSCELL.
-<P><LI>Second, the cellname in the <B>/usr/vice/etc/ThisCell</B> file on the
-local machine.
-</UL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output is of the following form:
-<PRE> Converting <VAR>password string</VAR> in realm '<VAR>cell_name</VAR>' yields key='<VAR>key</VAR>'.
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the octal key equivalent of the string
-<B>new_pswd</B> in the ABC Corporation cell.
-<PRE> %<B> kas stringtokey new_pswd</B>
- Converting new_pswd in realm 'ABC.COM' yields
- key='\346\307\364\320\263\233\342\354'.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None, and no password is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf032.htm#HDRCLI_THISCELL">ThisCell (client version)</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf195.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf197.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf196.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf198.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKAS_UNLOCK" HREF="auarf002.htm#ToC_211">kas unlock</A></H2>
-<A NAME="IDX5167"></A>
-<A NAME="IDX5168"></A>
-<A NAME="IDX5169"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Unlocks a locked user account
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kas unlock -name</B> <<VAR>authentication ID</VAR>>
- [<B>-admin_username</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-password_for_admin</B> <<VAR>admin password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>]
- [<B>-noauth</B>] [<B>-help</B>]
-
-<B>kas u -na</B> <<VAR>authentication ID</VAR>>
- [<B>-a</B> <<VAR>admin principal to use for authentication</VAR>>]
- [<B>-p</B> <<VAR>admin password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of authentication servers</VAR>><SUP>+</SUP>] [<B>-no</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kas unlock</B> command unlocks the Authentication Database entry
-named by the <B>-name</B> argument. An entry becomes locked when
-the user exceeds the limit on failed authentication attempts, generally by
-providing the wrong password to either an AFS-modified login utility or the
-<B>klog</B> command. Use the <B>kas setfields</B> command to
-set the limit and the lockout time, and the <B>kas examine</B> command to
-examine the settings.
-<P>To unlock all locked user accounts at once, shutdown the
-<B>kaserver</B> process on every database server machine, and remove the
-<B>/usr/afs/local/kaauxdb</B> file from each one. The
-<B>kaserver</B> process recreates the file as it restarts.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Names the Authentication Database entry to unlock.
-<P><DT><B>-admin_username
-</B><DD>Specifies the user identity under which to authenticate with the
-Authentication Server for execution of the command. For more details,
-see the introductory <B>kas</B> reference page.
-<P><DT><B>-password_for_admin
-</B><DD>Specifies the password of the command's issuer. If it is
-omitted (as recommended), the <B>kas</B> command interpreter prompts for
-it and does not echo it visibly. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>kas</B> reference page.
-<P><DT><B>-servers
-</B><DD>Names each machine running an Authentication Server with which to
-establish a connection. For more details, see the introductory
-<B>kas</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>kas</B> reference
-page.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, an administrator using the <B>admin</B>
-account unlocks the entry for <B>jones</B>:
-<PRE> % <B>kas unlock -name jones -admin_username admin</B>
- Administrator's (admin) Password:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <TT>ADMIN</TT> flag set on his or her
-Authentication Database entry.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf196.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf198.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf197.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf199.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKASERVER" HREF="auarf002.htm#ToC_212">kaserver</A></H2>
-<A NAME="IDX5170"></A>
-<A NAME="IDX5171"></A>
-<A NAME="IDX5172"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Authentication Server
-<P><STRONG>Description</STRONG>
-<PRE><B>kaserver</B> [<B>-noAuth</B>] [<B>-fastKeys</B>] [<B>-database</B> <<VAR>dbpath</VAR>>]
- [<B>-localfiles</B> <<VAR>lclpath</VAR>>] [<B>-minhours</B> <<VAR>n</VAR>>]
- [<B>-servers</B> <<VAR>serverlist</VAR>>] [<B>-enable_peer_stats</B>]
- [<B>-enable_process_stats</B>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>kaserver</B> command initializes the Authentication Server,
-which runs on every database server machine. In the conventional
-configuration, its binary file is located in the <B>/usr/afs/bin</B>
-directory on a file server machine.
-<P>The <B>kaserver</B> command is not normally issued at the command shell
-prompt but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a database server machine as the local superuser
-<B>root</B>.
-<P>As it initializes, the Authentication Server process creates the two files
-that constitute the Authentication Database, <B>kaserver.DB0</B>
-and <B>kaserver.DBSYS1</B>, in the <B>/usr/afs/db</B> directory
-if they do not already exist. Use the commands in the <B>kas</B>
-suite to administer the database.
-<P>The Authentication Server is responsible for several aspects of AFS
-security, including:
-<UL>
-<P><LI>Maintenance of all AFS server encryption keys and user passwords in the
-Authentication Database.
-<P><LI>Creation of the tickets and tokens that users and servers use to establish
-secure connections. Its Ticket Granting Service (TGS) component
-performs this function.
-</UL>
-<P>The Authentication Server records a trace of its activity in the
-<B>/usr/afs/logs/AuthLog</B> file. Use the <B>bos getlog</B>
-command to display the contents of the file. Use the <B>kdb</B>
-command to read the protected files associated with the <B>AuthLog</B>
-file, <B>AuthLog.dir</B> and <B>AuthLog.pag</B>.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-noAuth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Thus, it establishes an unauthenticated connection between the
-issuer and the Authentication Server. It is useful only when
-authorization checking is disabled on the database server machine. In
-normal circumstances, the Authentication Server allows only authorized
-(privileged) users to issue commands that affect or contact the Authentication
-Database and will refuse to perform such an action even if the
-<B>-noAuth</B> flag is used.
-<P><DT><B>-fastKeys
-</B><DD>Is a test flag for use by the AFS Development staff; it serves no
-functional purpose.
-<P><DT><B>-database
-</B><DD>Specifies the pathname of an alternate directory in which the
-Authentication Database files reside. Provide the complete pathname,
-ending in the base filename to which the <B>.DB0</B> and
-<B>.DBSYS1</B> extensions are appended. For example, the
-appropriate value for the default database files is
-<B>/usr/afs/db/kaserver</B>.
-<P>Provide the <B>-localfiles</B> argument along with this one;
-otherwise, the <B>-localfiles</B> argument is also set to the value of
-this argument, which is probably inappropriate.
-<P><DT><B>-localfiles
-</B><DD>Specifies the pathname of an alternate directory in which the auxiliary
-Authentication Database file resides. Provide the complete pathname,
-ending in the base filename to which the <B>auxdb</B> suffix is
-appended. For example, the appropriate value for the default auxiliary
-database file is <B>/usr/afs/local/kaserver</B>.
-<P><DT><B>-minhours
-</B><DD>Specifies the minimum number of hours that must pass between password
-changes made by any regular user. System administrators (with the
-<TT>ADMIN</TT> flag in their Authentication Database entry) can change
-passwords as often as desired. Setting a minimum time between password
-changes is not recommended.
-<P><DT><B>-servers
-</B><DD>Names each database server machine running an Authentication Server with
-which the local Authentication Server is to synchronize its copy of the
-Authentication Database , rather than with the machines listed in the local
-<B>/usr/afs/etc/CellServDB</B> file.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates a <B>kaserver</B>
-process on <B>fs3.abc.com</B> (the command appears on two
-lines here only for legibility):
-<PRE> % <B>bos create -server fs3.abc.com -instance kaserver</B> \
- <B>-type simple -cmd /usr/afs/bin/kaserver</B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf012.htm#HDRAUTHLOG">AuthLog</A>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf045.htm#HDRKASERVERDB">kaserver.DB0 and kaserver.DBSYS1</A>
-<P><A HREF="auarf046.htm#HDRKASERVERAUXDB">kaserverauxdb</A>
-<P><A HREF="auarf093.htm#HDRBOS_INTRO">bos</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf181.htm#HDRKAS_INTRO">kas</A>
-<P><A HREF="auarf199.htm#HDRKDB">kdb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf197.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf199.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf198.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf200.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKDB" HREF="auarf002.htm#ToC_213">kdb</A></H2>
-<A NAME="IDX5173"></A>
-<A NAME="IDX5174"></A>
-<A NAME="IDX5175"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays log or privileged actions performed by the Authentication Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kdb</B> [<B>-dbmfile</B> <<VAR>dbmfile to use (default /usr/afs/logs/AuthLog)</VAR>>]
- [<B>-key</B> <<VAR>extract entries that match specified key</VAR>>] [<B>-help</B>]
-
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kdb</B> command displays the contents of the
-<B>AuthLog.dir</B> and <B>AuthLog.pag</B> files
-associated with the <B>AuthLog</B> file that resides on the local disk, by
-default in the <B>/usr/afs/logs</B> directory. The files must exist
-in that directory, which normally implies that the Authentication Server is
-running on the machine. The files contain information on privileged
-actions performed by the Authentication Server.
-<P><STRONG>Cautions</STRONG>
-<P>It is possible that on some operating systems that AFS otherwise supports,
-the Authentication Server cannot create the
-<B>/usr/afs/logs/AuthLog.dir</B> and
-<B>/usr/afs/logs/AuthLog.pag</B> files, making this command
-inoperative. See the <I>IBM AFS Release Notes</I> for
-details.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-dbmfile
-</B><DD>Specifies the pathname of the file to display. Provide either a
-complete pathname, a pathname relative to the <B>/usr/afs/logs</B>
-directory, or a filename only, in which case the file must reside in the
-<B>/usr/afs/logs</B> directory. Omit this argument to display
-information from the <B>AuthLog.dir</B> and
-<B>AuthLog.pag</B> files in the <B>/usr/afs/logs</B>
-directory.
-<P><DT><B>-key
-</B><DD>Specifies each entry to be displayed from the indicated file.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of output indicates the location of the files from which the
-subsequent information is derived:
-<PRE> Printing all entries found in <VAR>file_location</VAR>
-</PRE>
-<P>Each entry then includes the following two fields, separated by a
-colon:
-<DL>
-<P><DT><B><TT>user/server</TT>
-</B><DD>Identifies the user requesting the corresponding service and the server
-that performed that service. In cases where no user is directly
-involved, only the server appears; in cases where no server is directly
-involved, only the user appears.
-<P><DT><B><TT>service</TT>
-</B><DD>Identifies one of the following actions or services performed by the user
-or server process.
-<UL>
-<P><LI><TT>auth</TT>: Obtained a ticket-granting ticket
-<P><LI><TT>chp</TT>: Changed a user password
-<P><LI><TT>cruser</TT>: Created a user entry in the Authentication
-Database
-<P><LI><TT>delu</TT>: Deleted a user entry from the Authentication
-Database
-<P><LI><TT>gtck</TT>: Obtained a ticket other than a ticket-granting
-ticket
-<P><LI><TT>setf</TT>: Set fields in an Authentication Database entry
-<P><LI><TT>unlok</TT>: Unlocked an Authentication Database entry
-</UL>
-</DL>
-<P>The final line of output sums the number of entries.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output of the <B>kdb</B> command in the
-ABC Corporation cell (<B>abc.com</B>):
-<PRE> % <B>kdb</B>
- Printing all entries found in /usr/afs/logs/AuthLog
- admin,krbtgt.ABC.COM:auth
- admin,afs:gtck
- admin:cruser
- admin:delu
- 4 entries were found
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf013.htm#HDRWQ5">AuthLog.dir, AuthLog.pag</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf198.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf200.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf199.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf201.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKLOG" HREF="auarf002.htm#ToC_214">klog</A></H2>
-<A NAME="IDX5176"></A>
-<A NAME="IDX5177"></A>
-<A NAME="IDX5178"></A>
-<A NAME="IDX5179"></A>
-<A NAME="IDX5180"></A>
-<A NAME="IDX5181"></A>
-<A NAME="IDX5182"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Authenticates with the Authentication Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>klog</B> [<B>-x</B>] [<B>-principal</B> <<VAR>user name</VAR>>] [<B>-password</B> <<VAR>user's password</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-servers</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>]
- [<B>-pipe</B>] [<B>-silent</B>] [<B>-lifetime</B> <<VAR>ticket lifetime in hh[:mm[:ss]]</VAR>>]
- [<B>-setpag</B>] [<B>-tmp</B>] [<B>-help</B>]
-
-<B>klog</B> [<B>-x</B>] [<B>-pr</B> <<VAR>user name</VAR>>] [<B>-pa</B> <<VAR>user's password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>] [<B>-pi</B>] [<B>-si</B>]
- [<B>-l</B> <<VAR>ticket lifetime in hh[:mm[:ss]]</VAR>>] [<B>-se</B>] [<B>-t</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>klog</B> command obtains an AFS token from the Authentication
-Server. The Cache Manager on the local machine stores the token in a
-credential structure in kernel memory and uses it when obtaining authenticated
-access to the AFS filespace. This command does not affect the
-issuer's identity (UNIX UID) in the local file system.
-<P>By default, the command interpreter obtains a token for the AFS user name
-that matches the issuer's identity in the local file system. To
-specify an alternate user, include the <B>-principal</B> argument.
-The user named by the <B>-principal</B> argument does not have to appear
-in the local password file (the <B>/etc/passwd</B> file or
-equivalent).
-<P>By default, the command interpreter obtains a token for the local cell, as
-defined by the AFSCELL environment variable set in the command shell or by the
-<B>/usr/vice/etc/ThisCell</B> file on the local machine. To specify
-an alternate cell, include the <B>-cell</B> argument. The command
-interpreter contacts an Authentication Server chosen at random from the
-cell's entry in the local <B>/usr/afs/etc/CellServDB</B> file, unless
-the <B>-servers</B> argument is used to name one or more database server
-machines.
-<P>A user can have tokens in multiple cells simultaneously, but only one token
-per cell per connection to the client machine. If the user's
-credential structure already contains a token for the requested cell, the
-token resulting from this command replaces it.
-<P>Sites that employ standard Kerberos authentication instead of the AFS
-Authentication Server must use the Kerberos version of this command,
-<B>klog.krb</B>, on all client machines. It automatically
-places the issuer's Kerberos tickets in the file named by the KRBTKFILE
-environment variable, which the <B>pagsh.krb</B> command defines
-automatically as <B>/tmp/tktp</B><I>X</I> where <I>X</I> is the
-number of the user's PAG.
-<P>The lifetime of the token resulting from this command is the smallest of
-the following.
-<UL>
-<P><LI>The lifetime specified by the issuer with the <B>-lifetime</B>
-argument. If the issuer does not include this argument, the value
-defaults to 720 hours (30 days).
-<P><LI>The maximum ticket lifetime recorded for the <B>afs</B> entry in the
-Authentication Database. The default is 100 hours.
-<P><LI>The maximum ticket lifetime recorded in the specified user's
-Authentication Database entry. The default is 25 hours for user entries
-created by an Authentication Server running AFS 3.1 or later.
-<P><LI>The maximum ticket lifetime recorded in the
-<B>krbtgt.</B><VAR>CELLNAME</VAR> entry in the Authentication
-Database; this entry corresponds to the ticket-granting ticket used
-internally in generating the token. The default is 720 hours (30
-days).
-</UL>
-<P>The output from the <B>kas examine</B> command displays an
-Authentication Database entry's maximum ticket lifetime as <TT>Max
-ticket lifetime</TT>. Administrators can display any entry, and users
-can display their own entries.
-<P>If none of the defaults have been changed, the token lifetime is 25 hours
-for user accounts created by an Authentication Server running AFS 3.1
-or higher. The maximum lifetime for any token is 720 hours (30 days),
-and the minimum is 5 minutes.
-<P>Between the minimum and maximum values, the Authentication Server uses a
-defined set of values, according to the following rules. Requested
-lifetimes between 5 minutes and 10 hours 40 minutes are granted at 5 minute
-intervals, rounding up. For example, if the issuer requests a lifetime
-of 12 minutes, the token's actual lifetime is 15 minutes.
-<P>For token lifetimes greater than 10 hours 40 minutes, consult the following
-table, which presents all the possible times in units of
-<VAR>hours</VAR><B>:</B><VAR>minutes</VAR><B>:</B><VAR>seconds</VAR>.
-The number in parentheses is an approximation of the corresponding time in
-days and hours (as indicated by the <TT>d</TT> and <TT>h</TT>
-letters). For example, <TT>282:22:17</TT> means 282
-hours, 22 minutes, and 17 seconds, which translates to approximately 11 days
-and 18 hours (<TT>11d 18h</TT>). The Authentication Server rounds up
-a requested lifetime to the next highest possible lifetime.
-<PRE> 11:24:15 (0d 11h) 46:26:01 (1d 22h) 189:03:38 (7d 21h)
- 12:11:34 (0d 12h) 49:38:40 (2d 01h) 202:08:00 (8d 10h)
- 13:02:09 (0d 13h) 53:04:37 (2d 05h) 216:06:35 (9d 00h)
- 13:56:14 (0d 13h) 56:44:49 (2d 08h) 231:03:09 (9d 15h)
- 14:54:03 (0d 14h) 60:40:15 (2d 12h) 247:01:43 (10d 07h)
- 15:55:52 (0d 15h) 64:51:57 (2d 16h) 264:06:34 (11d 00h)
- 17:01:58 (0d 17h) 69:21:04 (2d 21h) 282:22:17 (11d 18h)
- 18:12:38 (0d 18h) 74:08:46 (3d 02h) 301:53:45 (12d 13h)
- 19:28:11 (0d 19h) 79:16:23 (3d 07h) 322:46:13 (13d 10h)
- 20:48:57 (0d 20h) 84:45:16 (3d 12h) 345:05:18 (14d 09h)
- 22:15:19 (0d 22h) 90:36:53 (3d 18h) 368:56:58 (15d 08h)
- 23:47:38 (0d 23h) 96:52:49 (4d 00h) 394:27:37 (16d 10h)
- 25:26:21 (1d 01h) 103:34:45 (4d 07h) 421:44:07 (17d 13h)
- 27:11:54 (1d 03h) 110:44:28 (4d 14h) 450:53:46 (18d 18h)
- 29:04:44 (1d 05h) 118:23:54 (4d 22h) 482:04:24 (20d 02h)
- 31:05:22 (1d 07h) 126:35:05 (5d 06h) 515:24:22 (21d 11h)
- 33:14:21 (1d 09h) 135:20:15 (5d 15h) 551:02:38 (22d 23h)
- 35:32:15 (1d 11h) 144:41:44 (6d 00h) 589:08:45 (24d 13h)
- 37:59:41 (1d 13h) 154:42:01 (6d 10h) 629:52:56 (26d 05h)
- 40:37:19 (1d 16h) 165:23:50 (6d 21h) 673:26:07 (28d 01h)
- 43:25:50 (1d 19h) 176:50:01 (7d 08h)
-
-</PRE>
-<P><STRONG>Cautions</STRONG>
-<P>By default, this command does not create a new process authentication group
-(PAG); see the description of the <B>pagsh</B> command to learn about
-PAGs. If a cell does not use an AFS-modified login utility, users must
-include <B>-setpag</B> option to this command, or issue the
-<B>pagsh</B> command before this one, to have their tokens stored in a
-credential structure that is identified by PAG rather than by local
-UID.
-<P>When a credential structure is identified by local UID, the potential
-security exposure is that the local superuser <B>root</B> can use the UNIX
-<B>su</B> command to assume any other identity and automatically inherit
-the tokens associated with that UID. Identifying the credential
-structure by PAG eliminates this exposure.
-<P>If the <B>-password</B> argument is used, the specified password cannot
-begin with a hyphen, because it is interpreted as another option name.
-Use of the <B>-password</B> argument is not recommended in any
-case.
-<P>By default, it is possible to issue this command on a properly configured
-NFS client machine that is accessing AFS via the NFS/AFS Translator, assuming
-that the NFS client machine is a supported system type. However, if the
-translator machine's administrator has enabled UID checking by including
-the <B>-uidcheck on</B> argument to the <B>fs exportafs</B> command,
-the command fails with an error message similar to the following:
-<PRE>
- Warning: Remote pioctl to <VAR>translator_machine</VAR> has failed (err=8). . .
- Unable to authenticate to AFS because a pioctl failed.
-</PRE>
-<P>Enabling UID checking means that the credential structure in which tokens
-are stored on the translator machine must be identified by a UID that matches
-the local UID of the process that is placing the tokens in the credential
-structure. After the <B>klog</B> command interpreter obtains the
-token on the NFS client, it passes it to the remote executor daemon on the
-translator machine, which makes the system call that stores the token in a
-credential structure on the translator machine. The remote executor
-generally runs as the local superuser <B>root</B>, so in most cases its
-local UID (normally zero) does not match the local UID of the user who issued
-the <B>klog</B> command on the NFS client machine.
-<P>Issuing the <B>klog</B> command on an NFS client machine creates a
-security exposure: the command interpreter passes the token across the
-network to the remote executor daemon in clear text mode.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-x
-</B><DD>Appears only for backwards compatibility. Its former function is
-now the default behavior of this command.
-<P><DT><B>-principal
-</B><DD>Specifies the user name to authenticate. If this argument is
-omitted, the Authentication Server attempts to authenticate the user logged
-into the local file system.
-<P><DT><B>-password
-</B><DD>Specifies the issuer's password (or that of the alternate user
-identified by the <B>-principal</B> argument). Omit this argument
-to have the command interpreter prompt for the password, in which case it does
-not echo visibly in the command shell.
-<P><DT><B>-cell
-</B><DD>Specifies the cell for which to obtain a token. The command is
-directed to that cell's Authentication Servers. During a single
-login session on a given machine, a user can be authenticated in multiple
-cells simultaneously, but can have only one token at a time for each of them
-(that is, can only authenticate under one identity per cell per session on a
-machine). It is acceptable to abbreviate the cell name to the shortest
-form that distinguishes it from the other cells listed in the
-<B>/usr/vice/etc/CellServDB</B> file on the client machine on which the
-command is issued.
-<P>If this argument is omitted, the command is executed in the local cell, as
-defined
-<UL>
-<P><LI>First, by the value of the environment variable AFSCELL
-<P><LI>Second, in the <B>/usr/vice/etc/ThisCell</B> file on the client
-machine on which the command is issued
-</UL>
-<P><DT><B>-servers
-</B><DD>Establishes a connection with the Authentication Server running on each
-specified database server machine. The command interpreter then chooses
-one of these at random to execute the command. It is best to provide
-fully-qualified hostnames, but abbreviated forms are possibly acceptable
-depending on the state of the cell's name server at the time the command
-is issued. This option is useful for testing specific servers if
-problems are encountered.
-<P>If this argument is omitted, the command interpreter establishes a
-connection with each machine listed for the indicated cell in the local copy
-of the <B>/usr/vice/etc/CellServDB</B> file, and then chooses one of them
-at random for command execution.
-<P><DT><B>-pipe
-</B><DD>Suppresses all output to the standard output stream, including prompts and
-error messages. The <B>klog</B> command interpreter expects to
-receive the password from the standard input stream. Do not use this
-argument; it is designed for use by application programs rather than
-human users.
-<P><DT><B>-silent
-</B><DD>Suppresses some of the trace messages that the <B>klog</B> command
-produces on the standard output stream by default. It still reports on
-major problems encountered.
-<P><DT><B>-lifetime
-</B><DD>Requests a specific lifetime for the token. Provide a number of
-hours and optionally minutes and seconds in the format
-<VAR>hh</VAR>[<B>:</B><VAR>mm</VAR>[<B>:</B><VAR>ss</VAR>]].
-The value is used in calculating the token lifetime as described in the
-<B>Description</B> section.
-<P><DT><B>-setpag
-</B><DD>Creates a process authentication group (PAG) prior to requesting
-authentication. The token is associated with the newly created
-PAG.
-<P><DT><B>-tmp
-</B><DD>Creates a Kerberos-style ticket file in the <B>/tmp</B> directory of
-the local machine. The file is called
-<B>tkt.</B><VAR>AFS_UID</VAR> where <VAR>AFS_UID</VAR> is the AFS UID
-of the issuer.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Cautions</STRONG>
-<P><STRONG>Output</STRONG>
-<P>The following message indicates that the limit on consecutive
-authentication failures has been exceeded. An administrator can use the
-<B>kas unlock</B> command to unlock the account, or the issuer can wait
-until the lockout time for the account has passed. (The time is set
-with the <B>-locktime</B> argument to the <B>kas setfields</B> command
-and displayed in the output from the <B>kas examine</B> command).
-<PRE>
- Unable to authenticate to AFS because ID is locked - see your system admin
-
-</PRE>
-<P>If the <B>-tmp</B> flag is included, the following message confirms
-that a Kerberos-style ticket file was created:
-<PRE>
- Wrote ticket file to /tmp
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>Most often, this command is issued without arguments. The
-appropriate password is for the person currently logged into the local file
-system. The ticket's lifetime is calculated as described in the
-<B>Description</B> section (if no defaults have been changed, it is 25
-hours for a user whose Authentication Database entry was created in AFS
-3.1 or later).
-<PRE>
- % <B>klog</B>
- Password:
-
-</PRE>
-<P>The following example authenticates the user as <B>admin</B> in the ABC
-Corporation's test cell:
-<PRE>
- % <B>klog -principal admin -cell test.abc.com</B>
- Password:
-
-</PRE>
-<P>In the following, the issuer requests a ticket lifetime of 104 hours 30
-minutes (4 days 8 hours 30 minutes). Presuming that this lifetime is
-allowed by the maximum ticket lifetimes and other factors described in the
-<B>Description</B> section, the token's lifetime is
-110:44:28, which is the next largest possible value.
-<PRE> % <B>klog -lifetime 104:30</B>
- Password:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf139.htm#HDRFS_EXPORTAFS">fs exportafs</A>
-<P><A HREF="auarf185.htm#HDRKAS_EXAMINE">kas examine</A>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P><A HREF="auarf197.htm#HDRKAS_UNLOCK">kas unlock</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf208.htm#HDRPAGSH">pagsh</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf199.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf201.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf200.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf202.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKNFS" HREF="auarf002.htm#ToC_215">knfs</A></H2>
-<A NAME="IDX5183"></A>
-<A NAME="IDX5184"></A>
-<A NAME="IDX5185"></A>
-<A NAME="IDX5186"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Establishes basis for authenticated access to AFS from a non-supported NFS
-client using the NFS/AFS Translator
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>knfs -host</B> <<VAR>host name</VAR>> [<B>-id</B> <<VAR>user ID (decimal)</VAR>>]
- [<B>-sysname</B> <<VAR>host's '@sys' value</VAR>>] [<B>-unlog</B>] [<B>-tokens</B>] [<B>-help</B>]
-
-<B>knfs -ho</B> <<VAR>host name</VAR>> [<B>-i</B> <<VAR>user ID (decimal)</VAR>>]
- [<B>-s</B> <<VAR>host's '@sys' value</VAR>>] [<B>-u</B>] [<B>-t</B>] [<B>-he</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>knfs</B> command creates an AFS credential structure on the
-local machine, identifying it by a process authentication group (PAG) number
-associated with the NFS client machine named by the <B>-hostname</B>
-argument and by default with a local UID on the NFS client machine that
-matches the issuer's local UID on the local machine. It places in
-the credential structure the AFS tokens that the issuer has previously
-obtained (by logging onto the local machine if an AFS-modified login utility
-is installed, by issuing the <B>klog</B> command, or both). To
-associate the credential structure with an NFS UID that does not match the
-issuer's local UID, use the <B>-id</B> argument.
-<P>Issue this command only on the NFS<SUP>(R)</SUP>/AFS translator machine that is
-serving the NFS client machine, after obtaining AFS tokens on the translator
-machine for every cell to which authenticated access is required. The
-Cache Manager on the translator machine uses the tokens to obtain
-authenticated AFS access for the designated user working on the NFS client
-machine. This command is not effective if issued on an NFS client
-machine.
-<P>To enable the user on the NFS client machine to issue AFS commands, use the
-<B>-sysname</B> argument to specify the NFS client machine's system
-type, which can differ from the translator machine's. The NFS
-client machine must be a system type for which AFS is supported.
-<P>The <B>-unlog</B> flag discards the tokens in the credential structure,
-but does not destroy the credential structure itself. The Cache Manager
-on the translator machine retains the credential structure until the next
-reboot, and uses it each time the issuer accesses AFS through the translator
-machine. The credential structure only has tokens in it if the user
-reissues the <B>knfs</B> command on the translator machine each time the
-user logs into the NFS client machine.
-<P>To display the tokens associated with the designated user on the NFS client
-machine, include the <B>-tokens</B> flag.
-<P>Users working on NFS client machines of system types for which AFS binaries
-are available (and for which the cell has purchased a license) can use the
-<B>klog</B> command rather than the <B>knfs</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>If the translator machine's administrator has enabled UID checking by
-issuing the <B>fs exportafs</B> command with the <B>-uidcheck on</B>
-argument, it is not possible to use the <B>-id</B> argument to assign the
-tokens to an NFS UID that differs from the issuer's local UID. In
-this case, there is no point in including the <B>-id</B> argument, because
-the only acceptable value (the issuer's local UID) is the value used when
-the <B>-id</B> argument is omitted. Requiring matching UIDs is
-effective only when users have the same local UID on the translator machine as
-on NFS client machines. In that case, it guarantees that users assign
-their tokens only to their own NFS sessions.
-<P>This command does not make it possible for users working on non-supported
-system types to issue AFS commands. This is possible only on NFS
-clients of a system type for which AFS is available.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-host
-</B><DD>Names the NFS client machine on which the issuer is to work.
-Providing a fully-qualified hostname is best, but abbreviated forms are
-possibly acceptable depending on the state of the cell's name server at
-the time the command is issued.
-<P><DT><B>-id
-</B><DD>Specifies the local UID on the NFS client to which to assign the
-tokens. The NFS client identifies file requests by the NFS UID, so
-creating the association enables the Cache Manager on the translator machine
-to use the appropriate tokens when filling the requests. If this
-argument is omitted, the command interpreter uses an NFS UID that matches the
-issuer's local UID on the translator machine (as returned by the
-<B>getuid</B> function).
-<P><DT><B>-sysname
-</B><DD>Specifies the value that the local (translator) machine's remote
-executor daemon substitutes for the <B>@sys</B> variable in pathnames when
-executing AFS commands issued on the NFS client machine (which must be a
-supported system type). If the NFS user's PATH environment
-variable uses the <B>@sys</B> variable in the pathnames for directories
-that house AFS binaries (as recommended), then setting this argument enables
-NFS users to issue AFS commands by leading the remote executor daemon to
-access the AFS binaries appropriate to the NFS client machine even if its
-system type differs from the translator machine's.
-<P><DT><B>-unlog
-</B><DD>Discards the tokens stored in the credential structure identified by the
-PAG associated with the <B>-host</B> argument and, optionally, the
-<B>-id</B> argument.
-<P><DT><B>-tokens
-</B><DD>Displays the AFS tokens assigned to the designated user on the indicated
-NFS client machine.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The following error message indicates that UID checking is enabled on the
-translator machine and that the value provided for the <B>-id</B> argument
-differs from the issuer's local UID.
-<PRE>
- knfs: Translator in 'passwd sync' mode; remote uid must be the same as local uid
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example illustrates a typical use of this command. The
-issuer <B>smith</B> is working on the machine
-<B>nfscli1.abc.com</B> and has user ID <B>1020</B> on
-that machine. The translator machine
-<B>tx4.abc.com</B> uses an AFS-modified login utility, so
-<B>smith</B> obtains tokens for the ABC Corporation cell automatically
-upon login via the <B>telnet</B> program. She then issues the
-<B>klog</B> command to obtain tokens as <B>admin</B> in the ABC
-Corporation's test cell, <B>test.abc.com</B>, and the
-<B>knfs</B> command to associate both tokens with the credential structure
-identified by machine name <B>nfs-cli1</B> and user ID
-<B>1020</B>. She breaks the connection to <B>tx4</B> and works
-on <B>nfscli1</B>.
-<PRE> % <B>telnet tx4.abc.com</B>
- . . .
- login: <B>smith</B>
- Password:
- AFS(R) login
-
- % <B>klog admin -cell test.abc.com</B>
- Password:
-
- % <B>knfs nfscli1.abc.com 1020</B>
-
- % <B>exit</B>
-
-</PRE>
-<P>The following example shows user <B>smith</B> again connecting to the
-machine <B>tx4</B> via the <B>telnet</B> program and discarding the
-tokens.
-<PRE> % <B>telnet translator4.abc.com</B>
- . . .
- login: <B>smith</B>
- Password:
- AFS(R) login
-
- % <B>knfs nfscli1.abc.com 1020 -unlog</B>
-
- % <B>exit</B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf208.htm#HDRPAGSH">pagsh</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf200.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf202.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf201.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf203.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKPASSWD" HREF="auarf002.htm#ToC_216">kpasswd</A></H2>
-<A NAME="IDX5187"></A>
-<A NAME="IDX5188"></A>
-<A NAME="IDX5189"></A>
-<A NAME="IDX5190"></A>
-<A NAME="IDX5191"></A>
-<A NAME="IDX5192"></A>
-<A NAME="IDX5193"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes the issuer's password in the Authentication Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>kpasswd</B> [<B>-x</B>] [<B>-principal</B> <<VAR>user name</VAR>>] [<B>-password</B> <<VAR>user's password</VAR>>]
- [<B>-newpassword</B> <<VAR>user's new password</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-servers</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>] [<B>-pipe</B>] [<B>-help</B>]
-
-<B>kpasswd</B> [<B>-x</B>] [<B>-pr</B> <<VAR>user name</VAR>>] [<B>-pa</B> <<VAR>user's password</VAR>>]
- [<B>-n</B> <<VAR>user's new password</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-s</B> <<VAR>explicit list of servers</VAR>><SUP>+</SUP>] [<B>-pi</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>kpasswd</B> command changes the password recorded in an
-Authentication Database entry. By default, the command interpreter
-changes the password for the AFS user name that matches the issuer's
-local identity (UNIX UID). To specify an alternate user, include the
-<B>-principal</B> argument. The user named by the
-<B>-principal</B> argument does not have to appear in the local password
-file (the <B>/etc/passwd</B> file or equivalent).
-<P>By default, the command interpreter sends the password change request to
-the Authentication Server running on one of the database server machines
-listed for the local cell in the <B>/usr/afs/etc/CellServDB</B> file on
-the local disk; it chooses the machine at random. It consults the
-<B>/usr/vice/etc/ThisCell</B> file on the local disk to learn the local
-cell name. To specify an alternate cell, include the <B>-cell</B>
-argument.
-<P>Unlike the UNIX <B>passwd</B> command, the <B>kpasswd</B> command
-does not restrict passwords to eight characters or less; it accepts
-passwords of virtually any length. All AFS commands that require
-passwords (including the <B>klog</B>, <B>kpasswd</B>, and AFS-modified
-login utilities, and the commands in the <B>kas</B> suite) accept
-passwords longer than eight characters, but some other applications and
-operating system utilities do not. Selecting an AFS password of eight
-characters or less enables the user to maintain matching AFS and UNIX
-passwords.
-<P>The command interpreter makes the following checks:
-<UL>
-<P><LI>If the program <B>kpwvalid</B> exists in the same directory as the
-<B>kpasswd</B> command, the command interpreter pass the new password to
-it for verification. For details, see the <B>kpwvalid</B> reference
-page.
-<P><LI>If the <B>-reuse</B> argument to the <B>kas setfields</B> command
-has been used to prohibit reuse of previous passwords, the command interpreter
-verifies that the password is not too similar too any of the user's
-previous 20 passwords. It generates the following error message at the
-shell:
-<PRE> Password was not changed because it seems like a reused password
-
-</PRE>
-<P>To prevent a user from subverting this restriction by changing the password
-twenty times in quick succession (manually or by running a script), use the
-<B>-minhours</B> argument on the <B>kaserver</B> initialization
-command. The following error message appears if a user attempts to
-change a password before the minimum time has passed:
-<PRE> Password was not changed because you changed it too
- recently; see your systems administrator
-</PRE>
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-x
-</B><DD>Appears only for backwards compatibility.
-<P><DT><B>-principal
-</B><DD>Names the Authentication Database entry for which to change the
-password. If this argument is omitted, the database entry with the same
-name as the issuer's local identity (UNIX UID) is changed.
-<P><DT><B>-password
-</B><DD>Specifies the current password. Omit this argument to have the
-command interpreter prompt for the password, which does not echo
-visibly:
-<PRE> Old password: <VAR>current_password</VAR>
-
-</PRE>
-<P><DT><B>-newpassword
-</B><DD>Specifies the new password, which the <B>kpasswd</B> command
-interpreter converts into an encryption key (string of octal numbers) before
-sending it to the Authentication Server for storage in the user's
-Authentication Database entry.
-<P>Omit this argument to have the command interpreter prompt for the password,
-which does not echo visibly:
-<PRE> New password (RETURN to abort): <VAR>new_password</VAR>
- Retype new password: <VAR>new_password</VAR>
-
-</PRE>
-<P><DT><B>-cell
-</B><DD>Specifies the cell in which to change the password, by directing the
-command to that cell's Authentication Servers. The issuer can
-abbreviate the cell name to the shortest form that distinguishes it from the
-other cells listed in the local <B>/usr/vice/etc/CellServDB</B>
-file.
-<P>By default, the command is executed in the local cell, as defined
-<UL>
-<P><LI>First, by the value of the environment variable AFSCELL
-<P><LI>Second, in the <B>/usr/vice/etc/ThisCell</B> file on the client
-machine on which the command is issued
-</UL>
-<P><DT><B>-servers
-</B><DD>Establishes a connection with the Authentication Server running on each
-specified machine, rather than with all of the database server machines listed
-for the relevant cell in the local copy of the
-<B>/usr/vice/etc/CellServDB</B> file. The <B>kpasswd</B>
-command interpreter then sends the password-changing request to one machine
-chosen at random from the set.
-<P><DT><B>-pipe
-</B><DD>Suppresses all output to the standard output stream or standard error
-stream. The <B>kpasswd</B> command interpreter expects to receive
-all necessary arguments, each on a separate line, from the standard input
-stream. Do not use this argument, which is provided for use by
-application programs rather than human users.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows user <B>pat</B> changing her password in
-the ABC Corporation cell.
-<PRE> % <B>kpasswd</B>
- Changing password for 'pat' in cell 'abc.com'.
- Old password:
- New password (RETURN to abort):
- Verifying, please re-enter new_password:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf193.htm#HDRKAS_SETFIELDS">kas setfields</A>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf203.htm#HDRKPWVALID">kpwvalid</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf201.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf203.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf202.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf204.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRKPWVALID" HREF="auarf002.htm#ToC_217">kpwvalid</A></H2>
-<A NAME="IDX5194"></A>
-<A NAME="IDX5195"></A>
-<A NAME="IDX5196"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Checks quality of new password
-<P><STRONG>Description</STRONG>
-<P>The <B>kpwvalid</B> command checks the quality of a new password passed
-to it from the <B>kpasswd</B> or <B>kas setpassword</B>
-command. It is optional. If it exists, it must reside in the
-same AFS directory as the binaries for the <B>kpasswd</B> and
-<B>kas</B> command suites (create a symbolic link from the client
-machine's local disk to this directory). The directory's ACL
-must extend the <B>a</B> (<B>administer</B>) and <B>w</B>
-(<B>write</B>) permissions to the <B>system:administrators</B>
-group only. These requirements prevent unauthorized users from
-substituting a spurious <B>kpwvalid</B> binary.
-<P>The AFS distribution includes an example <B>kpwvalid</B> program that
-checks that the password is at least eight characters long; the code for
-it appears in the following <B>Examples</B> section.
-<P>The script or program must accept a sequence of password strings, one per
-line, on the standard input stream. The first is the current password
-and is ignored. Each subsequent string is a candidate password to be
-checked. The program must write the following to the standard output
-stream for each one:
-<UL>
-<P><LI><TT>0</TT> (zero) and a newline character to indicate that the password
-is acceptable
-<P><LI>A non-zero decimal number and a newline character to indicate that the
-password is not acceptable
-</UL>
-<P>Further, it must write any error messages only to the standard error
-stream, not to the standard output stream.
-<P><STRONG>Examples</STRONG>
-<P>The following example program, included in the AFS distribution, verifies
-that the requested password includes eight or more characters.
-<PRE> #include <stdio.h>
- /* prints 0 if the password is long enough, otherwise non-zero */
- main()
- {
- char oldpassword[512];
- char password[512];
-
- if (fgets(oldpassword, 512, stdin))
- while (fgets(password, 512, stdin)) {
- if (strlen(password) > 8) { /* password includes a newline */
- fputs("0\n",stdout);
- fflush(stdout);
- }
- else {
- fputs("Passwords must contain at least 8 characters.\n",
- stderr);
- fputs("1\n",stdout);
- fflush(stdout);
- }
- return 0;
- }
-
-</PRE>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf194.htm#HDRKAS_SETPASSWORD">kas setpassword</A>
-<P><A HREF="auarf202.htm#HDRKPASSWD">kpasswd</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf202.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf204.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf203.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf205.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPACKAGE" HREF="auarf002.htm#ToC_218">package</A></H2>
-<A NAME="IDX5197"></A>
-<A NAME="IDX5198"></A>
-<A NAME="IDX5199"></A>
-<A NAME="IDX5200"></A>
-<A NAME="IDX5201"></A>
-<A NAME="IDX5202"></A>
-<A NAME="IDX5203"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Configures files and directories on the local disk
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>package</B> [<B>initcmd</B>] [<B>-config</B> <<VAR>base name of configuration file</VAR>>]
- [<B>-fullconfig</B> <<VAR>full name of configuration file, or stdin for standard input</VAR>>]
- [<B>-overwrite</B>] [<B>-noaction</B>] [<B>-verbose</B>] [<B>-silent</B>] [<B>-rebootfiles</B>]
- [<B>-debug</B>] [<B>-help</B>]
-
-<B>package</B> [<B>i</B>] [<B>-c</B> <<VAR>base name of configuration file</VAR>>]
- [<B>-f</B> <<VAR>full name of configuration file, or stdin for standard input</VAR>>]
- [<B>-o</B>] [<B>-n</B>] [<B>-v</B>] [<B>-s</B>] [<B>-r</B>] [<B>-d</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>package</B> command configures the machine's local disk to
-comply with the instructions in the configuration file named by the
-<B>-config</B> or <B>-fullconfig</B> argument.
-<P>By default, the <B>package</B> command alters any existing local disk
-element whose contents or configuration does not match the element defined in
-the configuration file. For example, if a configuration file
-<B>D</B> instruction defines a directory that has the same name as a
-symbolic link on the local disk, the <B>package</B> command replaces the
-symbolic link with the directory. The <B>F</B> and <B>L</B>
-instructions include an optional <VAR>update_code</VAR> field that alters this
-behavior.
-<P>Also by default, the <B>package</B> command takes no action on elements
-on the local disk that are not mentioned in the configuration file. Use
-the <B>D</B> instruction's <B>R</B> update code to remove files
-from the disk directory that are not mentioned in the configuration
-file.
-<P>Before running the <B>package</B> command, the administrator must
-create the template file and other files on the local disk. For
-instructions, see the <I>IBM AFS Administration Guide</I>.
-<P>It is not possible to configure a remote client machine's disk using
-this command.
-<P><STRONG>Cautions</STRONG>
-<P>The <B>package</B> command interpreter exits without executing any
-instruction if there are any syntax errors or incorrect values in the
-configuration file.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-config
-</B><DD>Specifies the pathname of the configuration file to use, ending in the
-file's base name, which omits the suffix that indicates the machine
-type. The <B>package</B> command determines the machine's
-system type name and automatically appends it to the base name. An
-example of the proper value for this argument is <B>staff</B> rather than
-<B>staff.rs_aix42</B>. Partial pathnames are interpreted
-relative to the current working directory.
-<P>Provide this argument or the <B>-fullconfig</B> argument.
-<P><DT><B>-fullconfig
-</B><DD>Specifies the configuration file to use. Two types of values are
-acceptable:
-<UL>
-<P><LI>The full pathname of the configuration file to use, complete with an
-extension indicating the machine type (examples:
-<B>staff.rs_aix42</B>, <B>admin.sun4x_56</B>).
-<P><LI>The string <B>stdin</B> to indicate that the issuer is providing
-configuration information via the standard input stream, either by piping in
-the contents of a file, or by typing configuration lines at the shell.
-In the latter case, type <B><Ctrl-d></B> to conclude the input.
-</UL>
-<P>Provide this argument or the <B>-config</B> argument.
-<P><DT><B>-overwrite
-</B><DD>Overwrites elements on the local disk with the source version indicated in
-the configuration file, even if the owner <B>write</B> (<B>w</B>) mode
-bit is turned on the disk element. Files protected by the <B>I</B>
-update code on an <B>F</B> line in the configuration file are not
-overwritten.
-<P><DT><B>-noaction
-</B><DD>Checks the sequence of operations to be performed when the command
-actually runs and reports any problems that the <B>package</B> command
-interpreter expects to encounter. No elements on the local disk or in
-AFS are changed. If the <B>-verbose</B> flag is also provided, the
-trace includes all actions to be performed as well as anticipated
-errors.
-<P><DT><B>-silent
-</B><DD>Suppresses some of the trace messages sent to the standard output stream
-by default. The output still reports major problems.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-rebootfiles
-</B><DD>Prevents overwriting of any file marked with the <B>Q</B> update code
-on an <B>F</B> line in the configuration file. This effectively
-prevents the machine from rebooting automatically again when the
-<B>package</B> command is invoked in the machine's AFS initialization
-file.
-<P><DT><B>-debug
-</B><DD>Enables debugging output, which is directed to the standard output stream
-by default. By default, no debugging output is produced.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>This command is usually invoked in a client machine's AFS
-initialization file (<B>/etc/rc</B> or equivalent), rather than issued at
-the command shell prompt.
-<P>The following command invokes the version of the <B>staff</B>
-configuration file appropriate for this machine's system type, and
-produces verbose output.
-<PRE> # <B>/etc/package -c staff -v</B>
-
-</PRE>
-<P>The following example uses the configuration file whose basename is defined
-in the <B>/.package</B> file on the local machine. This
-method enables the administrator to use the same <B>package</B> command in
-every machine's AFS initialization file but still customize configuration
-by putting the appropriate basename in the <B>/.package</B>
-file.
-<PRE> # <B>/etc/package -c `cat /.package` -v</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf053.htm#HDRPACKAGECONFIG">package Configuration File</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf203.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf205.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf204.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf206.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPACKAGE_APROPOS" HREF="auarf002.htm#ToC_219">package apropos</A></H2>
-<A NAME="IDX5204"></A>
-<A NAME="IDX5205"></A>
-<A NAME="IDX5206"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>package apropos</B> [<B>-topic</B> <<VAR>help string</VAR>>] [<B>-help</B>]
-
-<B>package a</B> [<B>-t</B> <<VAR>help string</VAR>>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>package apropos</B> command displays the first line of the
-online help entry for any <B>package</B> command that has in its name or
-short description the string specified by the <B>-topic</B>
-argument.
-<P>To display the syntax for a command, use the <B>package help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>package</B> command where the string specified with the
-<B>-topic</B> argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>package</B> commands that include
-the word <B>help</B> in their names or short descriptions:
-<PRE> % <B>package apropos help</B>
- apropos: search by help text
- help: get help on commands
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<P><A HREF="auarf206.htm#HDRPACKAGE_HELP">package help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf204.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf206.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf205.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf207.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPACKAGE_HELP" HREF="auarf002.htm#ToC_220">package help</A></H2>
-<A NAME="IDX5207"></A>
-<A NAME="IDX5208"></A>
-<A NAME="IDX5209"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>package</B> commands or lists
-functional descriptions of all <B>package</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>package help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>package h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>package help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>package</B>
-command.
-<P>To list every <B>package</B> command whose name or short description
-includes a specified keyword, use the <B>package apropos</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>package</B> part of the command name, providing
-only the operation code (for example, specify <B>initcmd</B>, not
-<B>package initcmd</B>). If this argument is omitted, the output
-briefly describes every <B>package</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>package</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>package
-initcmd</B> command:
-<PRE> % <B>package help initcmd</B>
- package initcmd: initialize the program
- Usage: package [initcmd] [-config <base name of configuration file>]
- [-fullconfig <full name of configuration file, or stdin for standard input>]
- [-overwrite] [-noaction] [-verbose] [-silent] [-rebootfiles]
- [-debug] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<P><A HREF="auarf205.htm#HDRPACKAGE_APROPOS">package apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf205.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf207.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf206.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf208.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPACKAGE_TEST" HREF="auarf002.htm#ToC_221">package_test</A></H2>
-<A NAME="IDX5210"></A>
-<A NAME="IDX5211"></A>
-<A NAME="IDX5212"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Tests the validity of a package configuration file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>package_test</B> <<VAR>config file</VAR>>
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>package_test</B> command tests the validity of a
-<B>package</B> configuration file created when a prototype file is
-compiled. The command interpreter prints error messages on the standard
-output stream.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><VAR>config file</VAR>
-</B><DD>Specifies the package configuration file to validate.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example tests the validity of the <B>package</B>
-configuration file <I>staff.sun4x_56</I>.
-<PRE> % <B>package_test staff.sun4x_56</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf053.htm#HDRPACKAGECONFIG">package Configuration File</A>
-<P><A HREF="auarf204.htm#HDRPACKAGE">package</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf206.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf208.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf207.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf209.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPAGSH" HREF="auarf002.htm#ToC_222">pagsh</A></H2>
-<A NAME="IDX5213"></A>
-<A NAME="IDX5214"></A>
-<A NAME="IDX5215"></A>
-<A NAME="IDX5216"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a new PAG
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pagsh</B>
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pagsh</B> command creates a new command shell (owned by the
-issuer of the command) and associates a new <I>process authentication
-group</I> (PAG) with the shell and the user. A PAG is a number
-guaranteed to identify the issuer of commands in the new shell uniquely to the
-local Cache Manager. The PAG is used, instead of the issuer's UNIX
-UID, to identify the issuer in the credential structure that the Cache Manager
-creates to track each user.
-<P>Any tokens acquired subsequently (presumably for other cells) become
-associated with the PAG, rather than with the user's UNIX UID.
-This method for distinguishing users has two advantages.
-<UL>
-<P><LI>It means that processes spawned by the user inherit the PAG and so share
-the token; thus they gain access to AFS as the authenticated user.
-In many environments, for example, printer and other daemons run under
-identities (such as the local superuser <B>root</B>) that the AFS server
-processes recognize only as <B>anonymous</B>. Unless PAGs are used,
-such daemons cannot access files in directories whose access control lists
-(ACLs) do not extend permissions to the <B>system:anyuser</B>
-group.
-<P><LI>It closes a potential security loophole: UNIX allows anyone already
-logged in as the local superuser <B>root</B> on a machine to assume any
-other identity by issuing the UNIX <B>su</B> command. If the
-credential structure is identified by a UNIX UID rather than a PAG, then the
-local superuser <B>root</B> can assume a UNIX UID and use any tokens
-associated with that UID. Use of a PAG as an identifier eliminates that
-possibility.
-</UL>
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">The <B>pagsh.krb</B> version of this command is intended for use
-by sites that employ standard Kerberos authentication for their
-clients. The <B>pagsh.krb</B> command provides all the
-functionality of the <B>pagsh</B> command. In addition, it defines
-the environment variable KRBTKFILE (which specifies the storage location of
-Kerberos tickets) to be the <B>/tmp/tktp</B><VAR>X</VAR> file (where
-<VAR>X</VAR> is the number of the user's PAG). The functionality of
-this command supports the placement of Kerberos tickets by the
-<B>klog.krb</B> command and Kerberized AFS-modified login utilities
-in the file specified by the environment variable KRBTKFILE.
-</TD></TR></TABLE>
-<P><STRONG>Cautions</STRONG>
-<P>Each PAG created uses two of the memory slots that the kernel uses to
-record the UNIX groups associated with a user. If none of these slots
-are available, the <B>pagsh</B> command fails. This is not a
-problem with most operating systems, which make at least 16 slots available
-per user.
-<P>In cells that do not use an AFS-modified login utility, use this command to
-obtain a PAG before issuing the <B>klog</B> command (or include the
-<B>-setpag</B> argument to the <B>klog</B> command). If a PAG
-is not acquired, the Cache Manager stores the token in a credential structure
-identified by local UID rather than PAG. This creates the potential
-security exposure described in the <B>Description</B> section.
-<P>If users of NFS client machines for which AFS is supported are to issue
-this command as part of authenticating with AFS, do not use the <B>fs
-exportafs</B> command's <B>-uidcheck on</B> argument to enable UID
-checking on NFS/AFS Translator machines. Enabling UID checking prevents
-this command from succeeding. See the reference page for the
-<B>klog</B> command.
-<P>If UID checking is not enabled on Translator machines, then by default it
-is possible to issue this command on a properly configured NFS client machine
-that is accessing AFS via the NFS/AFS Translator, assuming that the NFS client
-machine is a supported system type. The <B>pagsh</B> binary
-accessed by the NFS client must be owned by, and grant setuid privilege to,
-the local superuser <B>root</B>. The complete set of mode bits must
-be <B>-rwsr-xr-x</B>. This is not a requirement when the command is
-issued on AFS client machines.
-<P>However, if the translator machine's administrator has enabled UID
-checking by including the <B>-uidcheck on</B> argument to the <B>fs
-exportafs</B> command, the command fails with an error message similar to
-the following:
-<PRE>
- Warning: Remote setpag to <VAR>translator_machine</VAR> has failed (err=8). . .
- setpag: Exec format error
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, the issuer invokes the C shell instead of the
-default Bourne shell:
-<PRE> # <B>pagsh -c /bin/csh</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf139.htm#HDRFS_EXPORTAFS">fs exportafs</A>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf207.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf209.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf208.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf210.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPRDB_CHECK" HREF="auarf002.htm#ToC_223">prdb_check</A></H2>
-<A NAME="IDX5217"></A>
-<A NAME="IDX5218"></A>
-<A NAME="IDX5219"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Checks the integrity of the Protection Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>prdb_check -database</B> <<VAR>ptdb_file</VAR>> [<B>-uheader</B>] [<B>-pheader</B>] [<B>-entries</B>]
- [<B>-verbose</B>] [<B>-help</B>]
-
-<B>prdb_check -d</B> <<VAR>ptdb_file</VAR>> [<B>-u</B>] [<B>-p</B>] [<B>-e</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>prdb_check</B> command checks the integrity of the Protection
-Database, reporting any errors or corruption it finds. If there are
-problems, do not issue any <B>pts</B> commands until the database is
-repaired.
-<P><STRONG>Cautions</STRONG>
-<P>The results can be unpredictable if the Protection Server makes changes to
-the Protection Database while this command is running. Use the <B>bos
-shutdown</B> command to shutdown the local <B>ptserver</B> process
-before running this command, or before creating a second copy of the
-<B>prdb.DB0</B> file (with a different name) on which to run the
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-database
-</B><DD>Names the Protection Database (copy of the <B>prdb.DB0</B>
-file) to check. If the current working directory is not the location of
-the file, provide a pathname, either full or relative to the current working
-directory.
-<P><DT><B>-uheader
-</B><DD>Displays information which Ubik maintains in the database's
-header.
-<P><DT><B>-pheader
-</B><DD>Displays information which the Protection Server maintains in the
-database's header.
-<P><DT><B>-entries
-</B><DD>Outputs every entry in the database. Some of the information is
-similar to that returned by the <B>pts examine</B> command.
-<P><DT><B>-verbose
-</B><DD>Reports additional information about the database, including the number of
-entries in the database and a trace of the internal database structures the
-command is verifying.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If there are errors in the database, the output always reports them on the
-standard error stream. If any options other than <B>-database</B>
-or <B>-help</B> are provided, the output written to the standard output
-stream includes additional information as described for each option in the
-preceding <B>Options</B> section of this reference page. The output
-is intended for debugging purposes and is meaningful to someone familiar with
-the internal structure of the Protection Database.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf047.htm#HDRPRDBDB">prdb.DB0 and prdb.DBSYS1</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf208.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf210.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf209.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf211.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_INTRO" HREF="auarf002.htm#ToC_224">pts</A></H2>
-<A NAME="IDX5220"></A>
-<A NAME="IDX5221"></A>
-<A NAME="IDX5222"></A>
-<A NAME="IDX5223"></A>
-<A NAME="IDX5224"></A>
-<A NAME="IDX5225"></A>
-<A NAME="IDX5226"></A>
-<A NAME="IDX5227"></A>
-<A NAME="IDX5228"></A>
-<A NAME="IDX5229"></A>
-<A NAME="IDX5230"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>pts</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>pts</B> command suite are the administrative
-interface to the Protection Server, which runs on each database server machine
-in a cell and maintains the Protection Database. The database stores
-the information that AFS uses to augment and refine the standard UNIX scheme
-for controlling access to files and directories.
-<P>Instead of relying only on the mode bits that define access rights for
-individual files, AFS associates an access control list (ACL) with each
-directory. The ACL lists users and groups and specifies which of seven
-possible access permissions they have for the directory and the files it
-contains. (It is still possible to set a directory or file's mode
-bits, but AFS interprets them in its own way; see the chapter on
-protection in the <I>IBM AFS Administration Guide</I> for details.)
-<P>AFS enables users to define groups in the Protection Database and place
-them on ACLs to extend a set of rights to multiple users
-simultaneously. Groups simplify administration by making it possible to
-add someone to many ACLs by adding them to a group that already exists on
-those ACLs. Machines can also be members of a group, so that users
-logged into the machine automatically inherit the permissions granted to the
-group.
-<P>There are several categories of commands in the <B>pts</B> command
-suite:
-<UL>
-<P><LI>Commands to create and remove Protection Database entries: <B>pts
-creategroup</B>, <B>pts createuser</B>, and <B>pts delete</B>
-<P><LI>Commands to administer and display group membership: <B>pts
-adduser</B>,
-<P><B>pts listowned</B>, <B>pts membership</B>, and <B>pts
-removeuser</B>
-<P><LI>Commands to administer and display properties of user and group entries
-other than membership: <B>pts chown</B>, <B>pts examine</B>,
-<B>pts listentries</B>, <B>pts rename</B>, and <B>pts
-setfields</B>
-<P><LI>Commands to set and examine the counters used when assigning IDs to users
-and groups: <B>pts listmax</B> and <B>pts setmax</B>
-<P><LI>Commands to obtain help: <B>pts apropos</B> and <B>pts
-help</B>
-</UL>
-<P><STRONG>Options</STRONG>
-<P>The following arguments and flags are available on many commands in the
-<B>pts</B> suite. The reference page for each command also lists
-them, but they are described here in greater detail.
-<DL>
-<A NAME="IDX5231"></A>
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P><DT><B>-force
-</B><DD>
-<A NAME="IDX5232"></A>
-Enables the command to continue executing as far as possible when errors or
-other problems occur, rather than halting execution immediately.
-Without it, the command halts as soon as the first error is
-encountered. In either case, the <B>pts</B> command interpreter
-reports errors at the command shell. This flag is especially useful if
-the issuer provides many values for a command line argument; if one of
-them is invalid, the command interpreter continues on to process the remaining
-arguments.
-<A NAME="IDX5233"></A>
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>-noauth
-</B><DD>
-<A NAME="IDX5234"></A>
-Establishes an unauthenticated connection to the Protection Server, in which
-the server treats the issuer as the unprivileged user
-<B>anonymous</B>. It is useful only when authorization checking is
-disabled on the server machine (during the installation of a file server
-machine or when the <B>bos setauth</B> command has been used during other
-unusual circumstances). In normal circumstances, the Protection Server
-allows only privileged users to issue commands that change the Protection
-Database, and refuses to perform such an action even if the <B>-noauth</B>
-flag is provided.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>Members of the <B>system:administrators</B> group can issue all
-<B>pts</B> commands on any entry in the Protection Database.
-<P>Users who do not belong to the <B>system:administrators</B> group
-can list information about their own entry and any group entries they
-own. The privacy flags set with the <B>pts setfields</B> command
-control access to entries owned by other users.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<P><A HREF="auarf212.htm#HDRPTS_APROPOS">pts apropos</A>
-<P><A HREF="auarf213.htm#HDRPTS_CHOWN">pts chown</A>
-<P><A HREF="auarf214.htm#HDRPTS_CREATEGROUP">pts creategroup</A>
-<P><A HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<P><A HREF="auarf216.htm#HDRPTS_DELETE">pts delete</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf218.htm#HDRPTS_HELP">pts help</A>
-<P><A HREF="auarf219.htm#HDRPTS_LISTENTRIES">pts listentries</A>
-<P><A HREF="auarf220.htm#HDRPTS_LISTMAX">pts listmax</A>
-<P><A HREF="auarf221.htm#HDRPTS_LISTOWNED">pts listowned</A>
-<P><A HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P><A HREF="auarf224.htm#HDRPTS_RENAME">pts rename</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P><A HREF="auarf226.htm#HDRPTS_SETMAX">pts setmax</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf209.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf211.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf210.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf212.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_ADDUSER" HREF="auarf002.htm#ToC_225">pts adduser</A></H2>
-<A NAME="IDX5235"></A>
-<A NAME="IDX5236"></A>
-<A NAME="IDX5237"></A>
-<A NAME="IDX5238"></A>
-<A NAME="IDX5239"></A>
-<A NAME="IDX5240"></A>
-<A NAME="IDX5241"></A>
-<A NAME="IDX5242"></A>
-<A NAME="IDX5243"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a user or machine to a Protection Database group
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts adduser -user</B> <<VAR>user name</VAR>><SUP>+</SUP> <B>-group</B> <<VAR>group name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts ad -u</B> <<VAR>user name</VAR>><SUP>+</SUP> <B>-g</B> <<VAR>group name</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts adduser</B> command adds each user or machine entry named by
-the <B>-user</B> argument as a member of each group named by the
-<B>-group</B> argument.
-<P>To remove members of a group, use the <B>pts removeuser</B>
-command. To list the groups to which a user or machine belongs, or the
-members of a specified group, use the <B>pts membership</B>
-command.
-<P><STRONG>Cautions</STRONG>
-<P>After being added as a group member, a currently authenticated user must
-reauthenticate (for example, by issuing the <B>klog</B> command) to obtain
-permissions granted to the group on an access control list (ACL).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-user
-</B><DD>Specifies the name of each user or machine entry to add to each group
-named by the <B>-group</B> argument. The name of a machine entry
-resembles an IP address and can use the wildcard notation described on the
-<B>pts createuser</B> reference page. The user or machine entry
-must already exist in the Protection Database.
-<P><DT><B>-group
-</B><DD>Specifies the complete name (including the owner prefix if applicable) of
-each group to which to add members. The group entry must already exist
-in the Protection Database.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example adds user <B>smith</B> to the group
-<B>system:administrators</B>.
-<PRE> % <B>pts adduser -user smith -group system:administrators</B>
-
-</PRE>
-<P>The following example adds users <B>jones</B>, <B>terry</B>, and
-<B>pat</B> to the <B>smith:colleagues</B> group.
-<PRE> % <B>pts adduser -user jones terry pat -group smith:colleagues</B>
-
-</PRE>
-<P>The following example adds the machine entries in the ABC Corporation
-subnet to the group <B>bin-prot</B>. Because of the IP address
-range of the ABC Corporation subnet, the system administrator was able to
-group the machines into three machine entries (using the wildcard notation
-discussed on the <B>pts createuser</B> reference page).
-<PRE> % <B>pts adduser -user 138.255.0.0 192.12.105.0 192.12.106.0 -group bin-prot</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The required privilege depends on the setting of the fourth privacy flag in
-the Protection Database entry for each group named by the <B>-group</B>
-argument (use the <B>pts examine</B> command to display the flags):
-<UL>
-<P><LI>If it is the hyphen, only the group's owner and members of the
-<B>system:administrators</B> group can add members.
-<P><LI>If it is lowercase <TT>a</TT>, current members of the group can add new
-members.
-<P><LI>If it is uppercase <TT>A</TT>, anyone who can access the cell's
-database server machines can add new members.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf210.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf212.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf211.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf213.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_APROPOS" HREF="auarf002.htm#ToC_226">pts apropos</A></H2>
-<A NAME="IDX5244"></A>
-<A NAME="IDX5245"></A>
-<A NAME="IDX5246"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>pts ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts apropos</B> command displays the first line of the online
-help entry for any <B>pts</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>pts help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>pts</B> command in which the string specified by the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>pts</B> commands that include the
-word <B>create</B> in their names or short descriptions:
-<PRE> % <B>pts apropos create</B>
- creategroup: create a new group
- createuser: create a new user
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf218.htm#HDRPTS_HELP">pts help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf211.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf213.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf212.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf214.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_CHOWN" HREF="auarf002.htm#ToC_227">pts chown</A></H2>
-<A NAME="IDX5247"></A>
-<A NAME="IDX5248"></A>
-<A NAME="IDX5249"></A>
-<A NAME="IDX5250"></A>
-<A NAME="IDX5251"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes the owner of a Protection Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts chown -name</B> <<VAR>group name</VAR>> <B>-owner</B> <<VAR>new owner</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts cho -na</B> <<VAR>group name</VAR>> <B>-o</B> <<VAR>new owner</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts chown</B> command designates the user or group named by the
-<B>-owner</B> argument as the owner of the group named by the
-<B>-name</B> argument, and records the new owner in the owner field of the
-group's Protection Database entry.
-<P>In the case of regular groups, this command automatically changes the group
-name's owner prefix (the part of the group name before the colon) to
-match the new owner. If the new owner is itself a group, then only its
-owner prefix, not its complete name, becomes the owner prefix in the new
-name. The change to the owner prefix does not propagate to any groups
-owned by the group, however. To make the owner prefix of such
-group-owned groups reflect the new owning group, use the <B>pts rename</B>
-command.
-<P>It is not possible to change a user or machine entry's owner from the
-default set at creation time, the <B>system:administrators</B>
-group.
-<P><STRONG>Cautions</STRONG>
-<P>While designating a machine as a group's owner does not cause an
-error, it is not recommended. The Protection Server does not extend the
-usual privileges of group ownership to users logged onto the machine.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies the current name of the group to which to assign a new
-owner.
-<P><DT><B>-owner
-</B><DD>Names the user or group to become the group's owner.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example changes the owner of the group
-<B>terry:friends</B> from the user <B>terry</B> to the user
-<B>pat</B>. A side effect is that the group name changes to
-<B>pat:friends</B>.
-<PRE> % <B>pts chown -name terry:friends -owner pat</B>
-
-</PRE>
-<P>The following example changes the owner of the group
-<B>terry:friends</B> from the user <B>terry</B> to the group
-<B>pat:buddies</B>. A side effect is that the group name
-changes to <B>pat:friends</B>.
-<PRE> % <B>pts chown -name terry:friends -owner pat:buddies</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B> group
-or currently own the group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf224.htm#HDRPTS_RENAME">pts rename</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf212.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf214.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf213.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf215.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_CREATEGROUP" HREF="auarf002.htm#ToC_228">pts creategroup</A></H2>
-<A NAME="IDX5252"></A>
-<A NAME="IDX5253"></A>
-<A NAME="IDX5254"></A>
-<A NAME="IDX5255"></A>
-<A NAME="IDX5256"></A>
-<A NAME="IDX5257"></A>
-<A NAME="IDX5258"></A>
-<A NAME="IDX5259"></A>
-<A NAME="IDX5260"></A>
-<A NAME="IDX5261"></A>
-<A NAME="IDX5262"></A>
-<A NAME="IDX5263"></A>
-<A NAME="IDX5264"></A>
-<A NAME="IDX5265"></A>
-<A NAME="IDX5266"></A>
-<A NAME="IDX5267"></A>
-<A NAME="IDX5268"></A>
-<A NAME="IDX5269"></A>
-<A NAME="IDX5270"></A>
-<A NAME="IDX5271"></A>
-<A NAME="IDX5272"></A>
-<A NAME="IDX5273"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates an (empty) Protection Database group entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts creategroup -name</B> <<VAR>group name</VAR>><SUP>+</SUP> [<B>-owner</B> <<VAR>owner of the group</VAR>>]
- [<B>-id</B> <<VAR>id (negated) for the group</VAR>><SUP>+</SUP>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts createg -na</B> <<VAR>group name</VAR>><SUP>+</SUP> [<B>-o</B> <<VAR>owner of the group</VAR>>]
- [<B>-i</B> <<VAR>id (negated) for the group</VAR>><SUP>+</SUP>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts cg -na</B> <<VAR>group name</VAR>><SUP>+</SUP> [<B>-o</B> <<VAR>owner of the group</VAR>>]
- [<B>-i</B> <<VAR>id (negated) for the group</VAR>><SUP>+</SUP>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts creategroup</B> command creates an entry in the Protection
-Database for each group specified by the <B>-name</B> argument. The
-entry records the issuer of the command as the group's creator, and as
-the group's owner unless the <B>-owner</B> argument names an
-alternate user or group as the owner.
-<P>There are two types of groups:
-<UL>
-<P><LI><I>regular</I>, the names of which have two parts separated by a
-colon. The part before the colon names the group's owner.
-Any user can create such groups.
-<P><LI><I>prefix-less</I>, which do not have an owner prefix. Only
-members of the <B>system:administrators</B> group can create
-prefix-less groups.
-</UL>
-<P>Creating a group lowers the issuer's group-creation quota by
-one. This is true even if the <B>-owner</B> argument is used to
-assign ownership to an alternate user or group. To display a
-user's group-creation quota, use the <B>pts examine</B> command;
-to set it, use the <B>pts setfields</B> command.
-<P>AFS group ID (AFS GID) numbers are negative integers and by default the
-Protection Server assigns a GID that is one less (more negative) than the
-current value of the <TT>max group id</TT> counter in the Protection
-Database, decrementing the counter by one for each group. Members of
-the <B>system:administrators</B> group can use the <B>-id</B>
-argument to assign specific AFS GID numbers. If any of the specified
-GIDs is lower (more negative) than the current value of the <TT>max group
-id</TT> counter, the counter is reset to that value. It is acceptable
-to specify a GID greater (less negative) than the current value of the
-counter, but the creation operation fails if an existing group already has
-it. To display or set the value of the <TT>max group id</TT> counter,
-use the <B>pts listmax</B> or <B>pts setmax</B> command,
-respectively.
-<P><STRONG>Output</STRONG>
-<P>The command generates the following string to confirm creation of each
-group:
-<PRE> group <VAR>name</VAR> has id <VAR>AFS GID</VAR>
-
-</PRE>
-<P><STRONG>Cautions</STRONG>
-<P>Although using the <B>-owner</B> argument to designate a machine entry
-as a group's owner does not generate an error, it is not
-recommended. The Protection Server does not extend the usual privileges
-of group ownership to users logged onto the machine.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies the name of each group to create. Provide a string of up
-to 63 characters, which can include lowercase (but not uppercase) letters,
-numbers, and punctuation marks. A regular name includes a single colon
-(<B>:</B>) to separate the two parts of the name; the colon
-cannot appear in a prefix-less group name.
-<P>A regular group's name must have the following format:
-<PRE> <VAR>owner_name</VAR><B>:</B><VAR>group_name</VAR>
-
-</PRE>
-<P>and the <VAR>owner_name</VAR> field must reflect the actual owner of the
-group, as follows:
-<UL>
-<P><LI>If the optional <B>-owner</B> argument is not included, the field must
-match the AFS username under which the issuer is currently
-authenticated.
-<P><LI>If the <B>-owner</B> argument names an alternate AFS user, the field
-must match that AFS username.
-<P><LI>If the <B>-owner</B> argument names another regular group, the field
-must match the owning group's owner field (the part of its name before
-the colon). If the <B>-owner</B> argument names a prefix-less
-group, the field must match the owning group's complete name.
-</UL>
-<P><DT><B>-owner
-</B><DD>Specifies a user or group as the owner for each group, rather than the
-issuer of the command. Provide either an AFS username or the name of a
-regular or prefix-less group. An owning group must already have at
-least one member. This requirement prevents assignment of
-self-ownership to a group during its creation; use the <B>pts
-chown</B> command after issuing this command, if desired.
-<P><DT><B>-id
-</B><DD>Specifies a negative integer AFS GID number for each group, rather than
-allowing the Protection Server to assign it. Precede the integer with a
-hyphen (<B>-</B>) to indicate that it is negative.
-<P>If this argument is used and the <B>-name</B> argument names multiple
-new groups, it is best to provide an equivalent number of AFS GIDs. The
-first GID is assigned to the first group, the second to the second group, and
-so on. If there are fewer GIDs than groups, the Protection Server
-assigns GIDs to the unmatched groups based on the <TT>max group id</TT>
-counter. If there are more GIDs than groups, the excess GIDs are
-ignored. If any of the GIDs is lower (more negative) than the current
-value of the <TT>max group id</TT> counter, the counter is reset to that
-value.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>In the following example, the user <B>pat</B> creates groups called
-<B>pat:friends</B> and <B>pat:colleagues</B>.
-<PRE> % <B>pts creategroup -name pat:friends pat:colleagues</B>
-
-</PRE>
-<P>The following example shows a member of the
-<B>system:administrators</B> group creating the prefix-less group
-<B>staff</B> and assigning its ownership to the
-<B>system:administrators</B> group rather than to herself.
-<PRE> % <B>pts creategroup -name staff -owner system:administrators</B>
-
-</PRE>
-<P>In the following example, the user <B>pat</B> creates a group called
-<B>smith:team-members</B>, which is allowed because the
-<B>-owner</B> argument specifies the required value
-(<B>smith</B>).
-<PRE> % <B>pts creategroup -name smith:team-members -owner smith</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B> group
-to create prefix-less groups or include the <B>-id</B> argument.
-<P>To create a regular group, the issuer must
-<UL>
-<P><LI>Be authenticated. The command fails if the <B>-noauth</B> flag
-is provided.
-<P><LI>Have a group-creation quota greater than zero. The <B>pts
-examine</B> command displays this quota.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf220.htm#HDRPTS_LISTMAX">pts listmax</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P><A HREF="auarf226.htm#HDRPTS_SETMAX">pts setmax</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf213.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf215.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf214.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf216.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_CREATEUSER" HREF="auarf002.htm#ToC_229">pts createuser</A></H2>
-<A NAME="IDX5274"></A>
-<A NAME="IDX5275"></A>
-<A NAME="IDX5276"></A>
-<A NAME="IDX5277"></A>
-<A NAME="IDX5278"></A>
-<A NAME="IDX5279"></A>
-<A NAME="IDX5280"></A>
-<A NAME="IDX5281"></A>
-<A NAME="IDX5282"></A>
-<A NAME="IDX5283"></A>
-<A NAME="IDX5284"></A>
-<A NAME="IDX5285"></A>
-<A NAME="IDX5286"></A>
-<A NAME="IDX5287"></A>
-<A NAME="IDX5288"></A>
-<A NAME="IDX5289"></A>
-<A NAME="IDX5290"></A>
-<A NAME="IDX5291"></A>
-<A NAME="IDX5292"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a user or machine entry in the Protection Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts createuser -name</B> <<VAR>user name</VAR>><SUP>+</SUP> [<B>-id</B> <<VAR>user id</VAR>><SUP>+</SUP>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts createu -na</B> <<VAR>user name</VAR>><SUP>+</SUP> [<B>-i</B> <<VAR>user id</VAR>><SUP>+</SUP>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts cu -na</B> <<VAR>user name</VAR>><SUP>+</SUP> [<B>-i</B> <<VAR>user id</VAR>><SUP>+</SUP>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts createuser</B> command creates an entry in the Protection
-Database for each user or machine specified by the <B>-name</B>
-argument. A user entry name becomes the user's AFS username (the
-one to provide when authenticating with the AFS Authentication Server).
-A machine entry's name is the machine's IP address or a wildcard
-notation that represents a range of consecutive IP addresses (a group of
-machines on the same network). It is not possible to authenticate as a
-machine, but a group to which a machine entry belongs can appear on a
-directory's access control list (ACL), thereby granting the indicated
-permissions to any user logged on to the machine.
-<P>AFS user IDs (AFS UIDs) are positive integers and by default the Protection
-Server assigns an AFS UID that is one greater than the current value of the
-<TT>max user id</TT> counter in the Protection Database, incrementing the
-counter by one for each user. To assign a specific AFS UID, use the
-<B>-id</B> argument. If any of the specified AFS UIDs is greater
-than the current value of the <TT>max user id</TT> counter, the counter is
-reset to that value. It is acceptable to specify an AFS UID smaller
-than the current value of the counter, but the creation operation fails if an
-existing user or machine entry already has it. To display or set the
-value of the <TT>max user id</TT> counter, use the <B>pts listmax</B> or
-<B>pts setmax</B> command, respectively.
-<P>The issuer of the <B>pts createuser</B> command is recorded as the
-entry's creator and the group <B>system:administrators</B> as
-its owner.
-<P><STRONG>Cautions</STRONG>
-<P>The Protection Server reserves AFS UID 0 (zero) and returns an error if the
-<B>-id</B> argument has that value.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies either a username for a user entry, or an IP address (complete
-or wildcarded) for a machine entry:
-<UL>
-<P><LI>A username can include up to 63 numbers and lowercase letters, but it is
-best to make it shorter than eight characters, because many application
-programs cannot handle longer names. Also, it is best not to include
-shell metacharacters or other punctuation marks. In particular, the
-colon (<B>:</B>) and at-sign (<B>@</B>) characters are not
-acceptable. The period is generally used only in special administrative
-names, to separate the username and an <I>instance</I>, as in the example
-<B>pat.admin</B>.
-<P><LI>A machine identifier is its IP address in dotted decimal notation (for
-example, 192.12.108.240), or a wildcard notation that
-represents a set of IP addresses (a group of machines on the same
-network). The following are acceptable wildcard formats. The
-letters <B>W</B>, <B>X</B>, <B>Y</B> and <B>Z</B> each
-represent an actual number from the range 1 through 255.
-<UL>
-<P><LI><B>W.X.Y.Z</B> represents a single machine, for
-example <B>192.12.108.240</B>.
-<P><LI><B>W.X.Y.0</B> matches all machines whose IP
-addresses start with the first three numbers. For example,
-<B>192.12.108.0</B> matches both
-<B>192.12.108.119</B> and
-<B>192.12.108.120</B>, but does not match
-<B>192.12.105.144</B>.
-<P><LI><B>W.X.0.0</B> matches all machines whose IP
-addresses start with the first two numbers. For example, the address
-<B>192.12.0.0</B> matches both
-<B>192.12.106.23</B> and
-<B>192.12.108.120</B>, but does not match
-<B>192.5.30.95</B>.
-<P><LI><B>W.0.0.0</B> matches all machines whose IP
-addresses start with the first number in the specified address. For
-example, the address <B>192.0.0.0</B> matches both
-<B>192.5.30.95</B> and
-<B>192.12.108.120</B>, but does not match
-<B>138.255.63.52</B>.
-</UL>
-<P>Do not define a machine entry with the name
-<B>0.0.0.0</B> to match every machine. The
-<B>system:anyuser</B> group is equivalent.
-</UL>
-<P><DT><B>-id
-</B><DD>Specifies an AFS UID for each user or machine entry, rather than allowing
-the Protection Server to assign it. Provide a positive integer.
-<P>If this argument is used and the <B>-name</B> argument names multiple
-new entries, it is best to provide an equivalent number of AFS UIDs.
-The first UID is assigned to the first entry, the second to the second entry,
-and so on. If there are fewer UIDs than entries, the Protection Server
-assigns UIDs to the unmatched entries based on the <TT>max user id</TT>
-counter. If there are more UIDs than entries, the excess UIDs are
-ignored. If any of the UIDs is greater than the current value of the
-<TT>max user id</TT> counter, the counter is reset to that value.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command generates the following string to confirm creation of each
-user:
-<PRE> User <VAR>name</VAR> has id <VAR>id</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example creates a Protection Database entry for the user
-<B>johnson</B>.
-<PRE> % <B>pts createuser -name johnson</B>
-
-</PRE>
-<P>The following example creates three wildcarded machine entries in the ABC
-Corporation cell. The three entries encompass all of the machines on
-the company's networks without including machines on other
-networks:
-<PRE> % <B>pts createuser -name 138.255.0.0 192.12.105.0 192.12.106.0</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B>
-group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf220.htm#HDRPTS_LISTMAX">pts listmax</A>
-<P><A HREF="auarf226.htm#HDRPTS_SETMAX">pts setmax</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf214.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf216.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf215.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf217.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_DELETE" HREF="auarf002.htm#ToC_230">pts delete</A></H2>
-<A NAME="IDX5293"></A>
-<A NAME="IDX5294"></A>
-<A NAME="IDX5295"></A>
-<A NAME="IDX5296"></A>
-<A NAME="IDX5297"></A>
-<A NAME="IDX5298"></A>
-<A NAME="IDX5299"></A>
-<A NAME="IDX5300"></A>
-<A NAME="IDX5301"></A>
-<A NAME="IDX5302"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a Protection Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts delete -nameorid</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts d -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts delete</B> command removes each entry specified by the
-<B>-nameorid</B> argument from the Protection Database. Deleting
-entries affects other parts of the system in various ways:
-<UL>
-<P><LI>Deleted users and groups still appear on access control lists (ACLs), but
-are listed by AFS UID or GID rather than by name, because there is no longer
-an associated name to which to translate the ID. To remove these
-obsolete entries from ACLs, use the <B>fs cleanacl</B> command.
-<P><LI>Deleting a user or machine's entry removes it from the membership
-list of any group to which it belonged.
-<P><LI>Deleting a group entry removes it from the membership list of any user or
-machine entry that belonged to the group, and also increments the
-group-creation quota of the group's creator by one, even if the creator
-no longer owns the group.
-</UL>
-<P>To remove a user or machine from a group without actually deleting the
-entry, use the <B>pts removeuser</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-nameorid
-</B><DD>Specifies the name or AFS UID of each user, the name or AFS GID of each
-group, or the IP address (complete or wildcard-style) or AFS UID of each
-machine entry to delete. It is acceptable to mix users, machines, and
-groups on the same command line, as well as names (IP addresses for machines)
-and IDs. Precede the GID of each group with a hyphen to indicate that
-it is negative.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example deletes the user entries <B>pat</B> and
-<B>terry</B>:
-<PRE> % <B>pts delete pat terry</B>
-
-</PRE>
-<P>The following example deletes the Protection Database entry of the group
-with AFS GID -215.
-<PRE> %<B> pts delete -215</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B> group
-to delete user and machine entries. To delete group entries, the issuer
-must either own the group or belong to the
-<B>system:administrators</B> group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf135.htm#HDRFS_CLEANACL">fs cleanacl</A>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf215.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf217.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf216.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf218.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_EXAMINE" HREF="auarf002.htm#ToC_231">pts examine</A></H2>
-<A NAME="IDX5303"></A>
-<A NAME="IDX5304"></A>
-<A NAME="IDX5305"></A>
-<A NAME="IDX5306"></A>
-<A NAME="IDX5307"></A>
-<A NAME="IDX5308"></A>
-<A NAME="IDX5309"></A>
-<A NAME="IDX5310"></A>
-<A NAME="IDX5311"></A>
-<A NAME="IDX5312"></A>
-<A NAME="IDX5313"></A>
-<A NAME="IDX5314"></A>
-<A NAME="IDX5315"></A>
-<A NAME="IDX5316"></A>
-<A NAME="IDX5317"></A>
-<A NAME="IDX5318"></A>
-<A NAME="IDX5319"></A>
-<A NAME="IDX5320"></A>
-<A NAME="IDX5321"></A>
-<A NAME="IDX5322"></A>
-<A NAME="IDX5323"></A>
-<A NAME="IDX5324"></A>
-<A NAME="IDX5325"></A>
-<A NAME="IDX5326"></A>
-<A NAME="IDX5327"></A>
-<A NAME="IDX5328"></A>
-<A NAME="IDX5329"></A>
-<A NAME="IDX5330"></A>
-<A NAME="IDX5331"></A>
-<A NAME="IDX5332"></A>
-<A NAME="IDX5333"></A>
-<A NAME="IDX5334"></A>
-<A NAME="IDX5335"></A>
-<A NAME="IDX5336"></A>
-<A NAME="IDX5337"></A>
-<A NAME="IDX5338"></A>
-<A NAME="IDX5339"></A>
-<A NAME="IDX5340"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays a Protection Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts examine -nameorid</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts e -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts check -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts che -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts examine</B> command displays information from the Protection
-Database entry of each user, machine or group specified by the
-<B>-nameorid</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-nameorid
-</B><DD>Specifies the name or AFS UID of each user, the name or AFS GID of each
-group, or the IP address (complete or wildcard-style) or AFS UID of each
-machine for which to display the Protection Database entry. It is
-acceptable to mix users, machines, and groups on the same command line, as
-well as names (IP addresses for machines) and IDs. Precede the GID of
-each group with a hyphen to indicate that it is negative.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output for each entry consists of two lines that include the following
-fields:
-<DL>
-<P><DT><B><TT>Name</TT>
-</B><DD>The contents of this field depend on the type of entry:
-<UL>
-<P><LI>For a user entry, it is the username that the user types when
-authenticating with AFS.
-<P><LI>For a machine entry, it is either the IP address of a single machine in
-dotted decimal format, or a wildcard notation that represents a group of
-machines on the same network. See the <B>pts createuser</B>
-reference page for an explanation of the wildcard notation.
-<P><LI>For a group entry, it is one of two types of group name. If the
-name has a colon between the two parts, it represents a regular group and the
-part before the prefix reflects the group's owner. A prefix-less
-group does not have the owner field or the colon. For more details on
-group names, see the <B>pts creategroup</B> reference page.
-</UL>
-<A NAME="IDX5341"></A>
-<A NAME="IDX5342"></A>
-<A NAME="IDX5343"></A>
-<P><DT><B><TT>id</TT>
-</B><DD>A unique number that the AFS server processes use to identify AFS users,
-machines and groups. AFS UIDs for user and machine entries are positive
-integers, and AFS GIDs for group entries are negative integers. AFS
-UIDs and GIDs are similar in function to the UIDs and GIDs used in local file
-systems such as UFS, but apply only to AFS operations.
-<A NAME="IDX5344"></A>
-<A NAME="IDX5345"></A>
-<P><DT><B><TT>owner</TT>
-</B><DD>The user or group that owns the entry and thus can administer it (change
-the values in most of the fields displayed in the output of this command), or
-delete it entirely. The Protection Server automatically records the
-<B>system:administrators</B> group in this field for user and
-machine entries at creation time.
-<A NAME="IDX5346"></A>
-<P><DT><B><TT>creator</TT>
-</B><DD>The user who issued the <B>pts createuser</B> or <B>pts
-creategroup</B> command to create the entry. This field serves as an
-audit trail, and cannot be changed.
-<A NAME="IDX5347"></A>
-<P><DT><B><TT>membership</TT>
-</B><DD>An integer that for users and machines represents the number of groups to
-which the user or machine belongs. For groups, it represents the number
-of group members.
-<P><DT><B><TT>flags</TT>
-</B><DD>A string of five characters, referred to as <I>privacy flags</I>,
-which indicate who can display or administer certain aspects of the
-entry.
-<DL>
-<P><DT><B>s
-</B><DD>Controls who can issue the <B>pts examine</B> command to display the
-entry.
-<P><DT><B>o
-</B><DD>Controls who can issue the <B>pts listowned</B> command to display the
-groups that a user or group owns.
-<P><DT><B>m
-</B><DD>Controls who can issue the <B>pts membership</B> command to display
-the groups a user or machine belongs to, or which users or machines belong to
-a group.
-<P><DT><B>a
-</B><DD>Controls who can issue the <B>pts adduser</B> command to add a user or
-machine to a group. It is meaningful only for groups, but a value must
-always be set for it even on user and machine entries.
-<P><DT><B>r
-</B><DD>Controls who can issue the <B>pts removeuser</B> command to remove a
-user or machine from a group. It is meaningful only for groups, but a
-value must always be set for it even on user and machine entries.
-</DL>
-<P>
-<P>Each flag can take three possible types of values to enable a different set
-of users to issue the corresponding command:
-<UL>
-<P><LI>A hyphen (<B>-</B>) designates the members of the
-<B>system:administrators</B> group and the entry's
-owner. For user entries, it designates the user in addition.
-<P><LI>The lowercase version of the letter applies meaningfully to groups only,
-and designates members of the group in addition to the individuals designated
-by the hyphen.
-<P><LI>The uppercase version of the letter designates everyone.
-</UL>
-<P>
-<P>For example, the flags <TT>SOmar</TT> on a group entry indicate that
-anyone can examine the group's entry and display the groups that it owns,
-and that only the group's members can display, add, or remove its
-members.
-<P>The default privacy flags for user and machine entries are
-<TT>S----</TT>, meaning that anyone can display the entry. The
-ability to perform any other functions is restricted to members of the
-<B>system:administrators</B> group and the entry's owner (as
-well as the user for a user entry).
-<P>The default privacy flags for group entries are <TT>S-M--</TT>, meaning
-that all users can display the entry and the members of the group, but only
-the entry owner and members of the <B>system:administrators</B>
-group can perform other functions.
-<P><DT><B><TT>group quota</TT>
-</B><DD>The number of additional groups the user is allowed to create. The
-<B>pts createuser</B> command sets it to 20 for both users and machines,
-but it has no meaningful interpretation for a machine, because it is not
-possible to authenticate as a machine. Similarly, it has no meaning in
-group entries and the <B>pts creategroup</B> command sets it to 0
-(zero); do not change this value.
-<A NAME="IDX5348"></A>
-<A NAME="IDX5349"></A>
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the user entry for <B>terry</B> and the
-machine entry <B>158.12.105.44</B>.
-<PRE> % <B>pts examine terry 158.12.105.44</B>
- Name: terry, id: 1045, owner: system:administrators, creator: admin,
- membership: 9, flags: S----, group quota: 15.
- Name: 158.12.105.44, id: 5151, owner: system:administrators,
- creator: byu, membership: 1, flags: S----, group quota: 20.
-
-</PRE>
-<P>The following example displays the entries for the AFS groups with GIDs
--673 and -674.
-<PRE> % <B>pts examine -673 -674</B>
- Name: terry:friends, id: -673, owner: terry, creator: terry,
- membership: 5, flags: S-M--, group quota: 0.
- Name: smith:colleagues, id: -674, owner: smith, creator: smith,
- membership: 14, flags: SOM--, group quota: 0.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The required privilege depends on the setting of the first privacy flag in
-the Protection Database entry of each entry specified by the
-<B>-nameorid</B> argument:
-<UL>
-<P><LI>If it is lowercase <TT>s</TT>, members of the
-<B>system:administrators</B> group and the user associated with a
-user entry can examine it, and only members of the
-<B>system:administrators</B> group can examine a machine or group
-entry.
-<P><LI>If it is uppercase <TT>S</TT>, anyone who can access the cell's
-database server machines can examine the entry.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<P><A HREF="auarf213.htm#HDRPTS_CHOWN">pts chown</A>
-<P><A HREF="auarf214.htm#HDRPTS_CREATEGROUP">pts creategroup</A>
-<P><A HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<P><A HREF="auarf221.htm#HDRPTS_LISTOWNED">pts listowned</A>
-<P><A HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P><A HREF="auarf224.htm#HDRPTS_RENAME">pts rename</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf216.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf218.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf217.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf219.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_HELP" HREF="auarf002.htm#ToC_232">pts help</A></H2>
-<A NAME="IDX5350"></A>
-<A NAME="IDX5351"></A>
-<A NAME="IDX5352"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>pts</B> commands or lists
-functional descriptions for all <B>pts</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>pts h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>pts</B> command.
-<P>To list every <B>pts</B> command whose name or short description
-includes a specified keyword, use the <B>pts apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>pts</B> part of the command name, providing only
-the operation code (for example, specify <B>membership</B>, not <B>pts
-membership</B>). If this argument is omitted, the output briefly
-describes every <B>pts</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>pts</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>pts
-membership</B> command:
-<PRE> % <B>pts help membership</B>
- pts membership: list membership of a user or group
- aliases: groups
- Usage: pts membership -nameorid <user or group name or id>+
- [-cell <cell name>] [-noauth] [-force] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf212.htm#HDRPTS_APROPOS">pts apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf217.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf219.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf218.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf220.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_LISTENTRIES" HREF="auarf002.htm#ToC_233">pts listentries</A></H2>
-<A NAME="IDX5353"></A>
-<A NAME="IDX5354"></A>
-<A NAME="IDX5355"></A>
-<A NAME="IDX5356"></A>
-<A NAME="IDX5357"></A>
-<A NAME="IDX5358"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays all user or group entries in the Protection Database
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts listentries</B> [<B>-users</B>] [<B>-groups</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts liste</B> [<B>-u</B>] [<B>-g</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts listentries</B> command displays the name and AFS ID of all
-Protection Database entries of the indicated type. It also displays the
-AFS ID of each entry's owner and creator.
-<P>To display all user and machine entries, either include the
-<B>-users</B> flag or omit both it and the <B>-groups</B> flag.
-To display all group entries, include the <B>-groups</B> flag. To
-display all entries, provide both flags.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-users
-</B><DD>Displays user and machine entries.
-<P><DT><B>-groups
-</B><DD>Displays group entries.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output includes a line for each entry, with information in four columns
-that have the following headers:
-<DL>
-<P><DT><B><TT>Name</TT>
-</B><DD>The entry's name
-<P><DT><B><TT>ID</TT>
-</B><DD>The entry's AFS ID (AFS UID for a user or machine, negative AFS GID
-for a group)
-<P><DT><B><TT>Owner</TT>
-</B><DD>The AFS ID of the user or group that owns the entry
-<P><DT><B><TT>Creator</TT>
-</B><DD>The AFS ID of the user who created the entry (the
-<B>system:administrators</B> group is listed as the creator of the
-entry for <B>anonymous</B> and the system groups, but it is not otherwise
-possible for a group to create groups)
-</DL>
-<P>In general, the entries appear in the order in which they were
-created.
-<P><STRONG>Examples</STRONG>
-<P>The following example displays both user and group entries.
-<PRE> % <B>pts listentries -users -groups</B>
- Name ID Owner Creator
- system:administrators -204 -204 -204
- system:anyuser -101 -204 -204
- system:authuser -102 -204 -204
- anonymous 32766 -204 -204
- admin 1 -204 32766
- pat 100 -204 1
- smith 101 -204 1
- pat:friends -206 100 100
- staff -207 -204 1
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B>
-group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf214.htm#HDRPTS_CREATEGROUP">pts creategroup</A>
-<P><A HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf218.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf220.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf219.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf221.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_LISTMAX" HREF="auarf002.htm#ToC_234">pts listmax</A></H2>
-<A NAME="IDX5359"></A>
-<A NAME="IDX5360"></A>
-<A NAME="IDX5361"></A>
-<A NAME="IDX5362"></A>
-<A NAME="IDX5363"></A>
-<A NAME="IDX5364"></A>
-<A NAME="IDX5365"></A>
-<A NAME="IDX5366"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the <TT>max user id</TT> and <TT>max group id</TT> counters
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts listmax</B> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts listm</B> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts listmax</B> command displays the values of the <TT>max user
-id</TT> and <TT>max group id</TT> counters, which the Protection Server
-uses to track the AFS user IDs (AFS UIDs) it allocates to new users or
-machines, and the AFS group IDs (AFS GIDs) it allocates to new groups,
-respectively. When an administrator next issues the <B>pts
-createuser</B> command and does not include the <B>-id</B> argument, the
-new user or machine receives an AFS UID one greater than the <TT>max user
-id</TT> counter, and when a user issues the <B>pts creategroup</B>
-command and does not include the <B>-id</B> argument, the new group
-receives an AFS UID one less (more negative) than the <TT>max group id</TT>
-counter.
-<P>To reset one or both counters, members of the
-<B>system:administrators</B> group can issue the <B>pts
-setmax</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command displays the counters in the following format:
-<PRE> Max user id is <VAR>user_counter</VAR> and max group id is <VAR>group_counter</VAR>.
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example displays the output of this command:
-<PRE> %<B> pts listmax</B>
- Max user name is 1271 and max group id is -382.
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf226.htm#HDRPTS_SETMAX">pts setmax</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf219.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf221.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf220.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf222.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_LISTOWNED" HREF="auarf002.htm#ToC_235">pts listowned</A></H2>
-<A NAME="IDX5367"></A>
-<A NAME="IDX5368"></A>
-<A NAME="IDX5369"></A>
-<A NAME="IDX5370"></A>
-<A NAME="IDX5371"></A>
-<A NAME="IDX5372"></A>
-<A NAME="IDX5373"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the Protection Database groups owned by a user or group
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts listowned -nameorid</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts listo -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts listowned</B> command lists the groups owned by each user or
-group specified by the <B>-nameorid</B> argument.
-<P>To list any <I>orphaned group</I>s, whose owners have themselves been
-deleted from the Protection Database, provide a value of <B>0</B> (zero)
-for the <B>-nameorid</B> argument. To change the owner to a user or
-group that still exists, use the <B>pts chown</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-nameorid
-</B><DD>Specifies the name or AFS UID of each user, or the name or AFS GID of each
-group, for which to display the list of owned groups. It is acceptable
-to mix users and groups on the same command line, as well as names and
-IDs. Precede the GID of each group with a hyphen to indicate that it is
-negative.
-<P>A value of <B>0</B> (zero) lists group entries for groups whose owners
-no longer have entries in the Protection Database.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of the output indicates the name and AFS UID or AFS GID of
-each user or group for which ownership information is requested, in the
-following format:
-<PRE> Groups owned by <VAR>name</VAR> (id: <VAR>ID</VAR>) are:
-
-</PRE>
-<P>A list of groups follows. The list does not include groups owned by
-groups that the user or group owns, or to which the user or group
-belongs. If the user or group does not own any groups, only the header
-line appears.
-<P>The following error message appears if the issuer is not privileged to view
-ownership information. By default, for both user and group entries the
-second privacy flag is the hyphen, which denies permission to anyone other
-than the user (for a user entry) and the members of the
-<B>system:administrators</B> group.
-<PRE> pts: Permission denied so failed to get owner list for <VAR>name</VAR> (id: <VAR>ID</VAR>)
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example lists the groups owned by user <B>terry</B> and
-shows that the group <B>terry:friends</B> does not own any
-groups:
-<PRE> % <B>pts listowned terry terry:friends</B>
- Groups owned by terry (id: 1045) are:
- terry:friends
- terry:project1
- terry:project2
- Groups owned by terry:friends (id: -673) are:
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The required privilege depends on the setting of the second privacy flag in
-the Protection Database entry of each user or group indicated by the
-<B>-nameorid</B> argument (use the <B>pts examine</B> command to
-display the flags):
-<UL>
-<P><LI>If it is the hyphen and the <B>-nameorid</B> argument specifies a
-group, only the members of the <B>system:administrators</B> group
-and the owner of a group can list the groups it owns.
-<P><LI>If it is the hyphen and the <B>-nameorid</B> argument specifies a
-user, only the members of the <B>system:administrators</B> group and
-the associated user can list the groups he or she owns.
-<P><LI>If it is uppercase letter <TT>O</TT>, anyone who can access the
-cell's database server machines can list the groups owned by this user or
-group.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf213.htm#HDRPTS_CHOWN">pts chown</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf220.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf222.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf221.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf223.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_MEMBERSHIP" HREF="auarf002.htm#ToC_236">pts membership</A></H2>
-<A NAME="IDX5374"></A>
-<A NAME="IDX5375"></A>
-<A NAME="IDX5376"></A>
-<A NAME="IDX5377"></A>
-<A NAME="IDX5378"></A>
-<A NAME="IDX5379"></A>
-<A NAME="IDX5380"></A>
-<A NAME="IDX5381"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the membership list for a user or group
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts membership -nameorid</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts m -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts groups -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-
-<B>pts g -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts membership</B> command lists the groups to which each user
-or machine specified by the <B>-nameorid</B> argument belongs, or lists
-the users and machines that belong to each group specified by the
-<B>-nameorid</B> argument.
-<P>It is not possible to list the members of the
-<B>system:anyuser</B> or <B>system:authuser</B> groups,
-and they do not appear in the list of groups to which a user belongs.
-<P>To add users or machine to groups, use the <B>pts adduser</B>
-command; to remove them, use the <B>pts removeuser</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-nameorid
-</B><DD>Specifies the name or AFS UID of each user entry, the IP address (complete
-or wildcard-style) or AFS UID of each machine entry, or the name or AFS GID of
-each group, for which to list group membership. It is acceptable to mix
-users, machines, and groups on the same command line, as well as names and
-IDs. Precede the GID of each group with a hyphen to indicate that it is
-negative.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>For each user and machine, the output begins with the following header
-line, followed by a list of the groups to which the user or machine
-belongs:
-<PRE> Groups <VAR>name</VAR> (id: <VAR>AFS UID</VAR>) is a member of:
-
-</PRE>
-<P>For each group, the output begins with the following header line, followed
-by a list of the users and machines who belong to the group:
-<PRE> Members of <VAR>group_name</VAR> (id: <VAR>AFS GID</VAR>) are:
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example lists the groups to which the user <B>pat</B>
-belongs and the members of the group <B>smith:friends</B>.
-Note that third privacy flag for the <B>pat</B> entry was changed from the
-default hyphen to enable a non-administrative user to obtain this
-listing.
-<PRE> % <B>pts membership pat smith:friends</B>
- Groups pat (id: 1144) is a member of:
- smith:friends
- staff
- johnson:project-team
- Members of smith:friends (id: -562) are:
- pat
- terry
- jones
- richard
- thompson
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The required privilege depends on the setting of the third privacy flag in
-the Protection Database entry of each user or group indicated by the
-<B>-nameorid</B> argument (use the <B>pts examine</B> command to
-display the flags):
-<UL>
-<P><LI>If it is the hyphen and the <B>-nameorid</B> argument specifies a
-user, only the associated user and members of the
-<B>system:administrators</B> group can list the groups to which the
-user belongs.
-<P><LI>If it is the hyphen and the <B>-nameorid</B> argument specifies a
-machine, only the members of the <B>system:administrators</B> group
-can list the groups to which the machine belongs.
-<P><LI>If it is the hyphen and the <B>-nameorid</B> argument specifies a
-group, only the owner of the group and members of the
-<B>system:administrators</B> group can list the members of the
-group.
-<P><LI>If it is lowercase <TT>m</TT> and the <B>-nameorid</B> argument
-specifies a user or machine entry, the meaning is equivalent to the
-hyphen.
-<P><LI>If it is lowercase <TT>m</TT> and the <B>-nameorid</B> argument
-specifies a group, members of the group can also list the other
-members.
-<P><LI>If it is uppercase <TT>M</TT>, anyone who can access the cell's
-database server machines can list group memberships.
-</UL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf221.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf223.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf222.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf224.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_REMOVEUSER" HREF="auarf002.htm#ToC_237">pts removeuser</A></H2>
-<A NAME="IDX5382"></A>
-<A NAME="IDX5383"></A>
-<A NAME="IDX5384"></A>
-<A NAME="IDX5385"></A>
-<A NAME="IDX5386"></A>
-<A NAME="IDX5387"></A>
-<A NAME="IDX5388"></A>
-<A NAME="IDX5389"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a user from a Protection Database group
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts removeuser -user</B> <<VAR>user name</VAR>><SUP>+</SUP> <B>-group</B> <<VAR>group name</VAR>><SUP>+</SUP>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts rem -u</B> <<VAR>user name</VAR>><SUP>+</SUP> <B>-g</B> <<VAR>group name</VAR>><SUP>+</SUP> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts removeuser</B> command removes each user or machine named by
-the <B>-user</B> argument from each group named by the <B>-group</B>
-argument.
-<P>To add users to a group, use the <B>pts adduser</B> command. To
-list group membership, use the <B>pts membership</B> command. To
-remove users from a group and delete the group's entry completely in a
-single step, use the <B>pts delete</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>AFS compiles each user's group membership as he or she
-authenticates. Any users who have valid tokens when they are removed
-from a group retain the privileges extended to that group's members until
-they discard their tokens or reauthenticate.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies the name of each user entry or the IP address (complete or
-wildcard-style) of each machine entry to remove.
-<P><DT><B>-group
-</B><DD>Names each group from which to remove members.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example removes user <B>smith</B> from the groups
-<B>staff</B> and <B>staff:finance</B>. Note that no
-switch names are necessary because only a single instance is provided for the
-first argument (the username).
-<PRE> % <B>pts removeuser smith staff staff:finance</B>
-
-</PRE>
-<P>The following example removes three machine entries, which represent all
-machines in the ABC Corporation network, from the group
-<B>bin-prot</B>:
-<PRE> % <B>pts removeuser -user 138.255.0.0 192.12.105.0 192.12.106.0 -group bin-prot</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The required privilege depends on the setting of the fifth privacy flag in
-the Protection Database for the group named by the <B>-group</B> argument
-(use the <B>pts examine</B> command to display the flags):
-<UL>
-<P><LI>If it is the hyphen, only the group's owner and members of the
-<B>system:administrators</B> group can remove members.
-<P><LI>If it is lowercase <TT>r</TT>, members of the group can also remove
-other members.
-</UL>
-<P>(It is not possible to set the fifth flag to uppercase
-<TT>R</TT>.)
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<P><A HREF="auarf225.htm#HDRPTS_SETFIELDS">pts setfields</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf222.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf224.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf223.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf225.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_RENAME" HREF="auarf002.htm#ToC_238">pts rename</A></H2>
-<A NAME="IDX5390"></A>
-<A NAME="IDX5391"></A>
-<A NAME="IDX5392"></A>
-<A NAME="IDX5393"></A>
-<A NAME="IDX5394"></A>
-<A NAME="IDX5395"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes the name of a Protection Database entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts rename -oldname</B> <<VAR>old name</VAR>> <B>-newname</B> <<VAR>new name</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts ren -o</B> <<VAR>old name</VAR>> <B>-ne</B> <<VAR>new name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts rename</B> command changes the name of the user, machine, or
-group entry specified by the <B>-oldname</B> argument to the name
-specified by the <B>-newname</B> argument. It is not possible to
-change a user or machine entry's name to look like a regular group
-entry's name (have a colon in it).
-<P>Members of the <B>system:administrators</B> group can change a
-regular group name into a prefix-less name and vice versa. When
-changing a prefix-less group name into a regular group name or a regular group
-name to another regular group name, the owner field of the new name (the part
-before the colon) must correctly reflect the group's owner.
-<P>Changing a regular group's owner with the <B>pts chown</B> command
-automatically changes the owner field (the part before the colon) of the
-group's name, but does not change the owner field of any groups owned by
-the group. Use this command to rename those groups to a form that
-accurately reflects their ownership.
-<P><STRONG>Cautions</STRONG>
-<P>By convention, many aspects of an AFS user account have the same name as
-the user's Protection Database entry, including the Authentication
-Database entry, volume, and mount point. When using this command to
-change a user name, also change the names of all related entities to maintain
-consistency. For instructions, see the chapter on user accounts in the
-<I>IBM AFS Administration Guide</I>.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-oldname
-</B><DD>Specifies the current full name of the entry.
-<P><DT><B>-newname
-</B><DD>Specifies the new full name for the entry. For regular groups, the
-owner field (the part before the colon) of the new name must reflect the
-actual ownership of the group.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example changes the name of the group <B>staff</B>, owned
-by the privileged user <B>admin</B>, to
-<B>admin:staff</B>:
-<PRE> % <B>pts rename -oldname staff -newname admin:staff</B>
-
-</PRE>
-<P>The following example changes the name of the group
-<B>admin:finance</B> to the group <B>finance</B>. The
-issuer must belong to the <B>system:administrators</B> group.
-<PRE> % <B>pts rename -oldname admin:finance -newname finance</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To change a regular group name to a prefix-less name or vice versa, or to
-change a user or machine entry's name, the issuer must belong to the
-<B>system:administrators</B> group.
-<P>To change a group name to a new name of the same type (regular or
-prefix-less), the issuer must own the group or belong to the
-<B>system:administrators</B> group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf213.htm#HDRPTS_CHOWN">pts chown</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf223.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf225.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf224.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf226.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_SETFIELDS" HREF="auarf002.htm#ToC_239">pts setfields</A></H2>
-<A NAME="IDX5396"></A>
-<A NAME="IDX5397"></A>
-<A NAME="IDX5398"></A>
-<A NAME="IDX5399"></A>
-<A NAME="IDX5400"></A>
-<A NAME="IDX5401"></A>
-<A NAME="IDX5402"></A>
-<A NAME="IDX5403"></A>
-<A NAME="IDX5404"></A>
-<A NAME="IDX5405"></A>
-<A NAME="IDX5406"></A>
-<A NAME="IDX5407"></A>
-<A NAME="IDX5408"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets privacy flags or the group-creation quota for a Protection Database
-entry.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts setfields -nameorid</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP>
- [<B>-access</B> <<VAR>set privacy flags</VAR>>]
- [<B>-groupquota</B> <<VAR>set limit on group creation</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts setf -na</B> <<VAR>user or group name or id</VAR>><SUP>+</SUP> [<B>-a</B> <<VAR>set privacy flags</VAR>>]
- [<B>-g</B> <<VAR>set limit on group creation</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts setfields</B> command sets the group-creation quota, the
-privacy flags, or both, associated with each user, machine, or group entry
-specified by the <B>-nameorid</B> argument.
-<P>To examine the current quota and privacy flags, use the <B>pts
-examine</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>Changing a machine or group's group-creation quota is allowed, but not
-recommended. The concept is meaningless for machines and groups,
-because it is impossible to authenticate as a group or machine.
-<P>Similarly, some privacy flag settings do not have a sensible
-interpretation. The <B>Arguments</B> section specifies the
-appropriate settings.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-nameorid
-</B><DD>Specifies the name or AFS UID of each user, the IP address (complete or
-wildcard-style) of each machine, or the name or AFS GID of each machine for
-which to set privacy flags or group-creation quota. It is acceptable to
-mix users, machines, and groups on the same command line, as well as names (IP
-addresses for machines) and IDs. Precede the GID of each group with a
-hyphen to indicate that it is negative.
-<P><DT><B>-access
-</B><DD>Specifies the privacy flags to apply to each entry. Provide a
-string of five characters, one for each of the permissions. If this
-option is omitted, the current setting remains unchanged.
-<P>Set each flag to achieve the desired combination of permissions. If
-the following list does not mention a certain setting, it is not
-acceptable. For further discussion of the privacy flags, see the
-<B>pts examine</B> reference page.
-<UL>
-<P><LI>The first flag determines who can use the <B>pts examine</B> command
-to display information from a user, machine or group's Protection
-Database entry.
-<UL>
-<P><LI>Set it to lowercase <B>s</B> to permit the members of the
-<B>system:administrators</B> group to display a user, machine, or
-group entry, and the associated user to display a user entry.
-<P><LI>Set it to uppercase <B>S</B> to permit anyone who can access the
-cell's database server machines to display a user, machine, or group
-entry.
-</UL>
-<P><LI>The second flag determines who can use the <B>pts listowned</B>
-command to list the groups that a user or group owns.
-<UL>
-<P><LI>Set it to the hyphen (<B>-</B>) to permit the members of the
-<B>system:administrators</B> group and a user to list the groups he
-or she owns, or to permit the members of the
-<B>system:administrators</B> group and a group's owner to list
-the groups that a group owns.
-<P><LI>Set it to uppercase letter <B>O</B> to permit anyone who can access
-the cell's database server machines to list the groups owned by a machine
-or group entry.
-</UL>
-<P><LI>The third flag determines who can use the <B>pts membership</B>
-command to list the groups to which a user or machine belongs, or the users
-and machines that belong to a group.
-<UL>
-<P><LI>Set it to the hyphen (<B>-</B>) to permit the members of the
-<B>system:administrators</B> group and a user to list the groups he
-or she belongs to, to permit the members of the
-<B>system:administrators</B> group to list the groups a machine
-belongs to, or to permit the members of the
-<B>system:administrators</B> group and a group's owner to list
-the users and machines that belong to it.
-<P><LI>Set it to lowercase <B>m</B> to permit members of a group to list the
-other members. (For user and machine entries, this setting is
-equivalent to the hyphen.)
-<P><LI>Set it to uppercase <B>M</B> to permit anyone who can access the
-cell's database server machines to list membership information for a
-user, machine or group.
-</UL>
-<P><LI>The fourth flag determines who can use the <B>pts adduser</B> command
-to add users and machines as members of a group. This flag has no
-sensible interpretation for user and machine entries, but must be set
-nonetheless, preferably to the hyphen.
-<UL>
-<P><LI>Set it to the hyphen (<B>-</B>) to permit the members of the
-<B>system:administrators</B> group and the owner of the group to add
-members.
-<P><LI>Set it to lowercase <B>a</B> to permit members of a group to add other
-members.
-<P><LI>Set it to uppercase <B>A</B> to permit anyone who can access the
-cell's database server machines to add members to a group.
-</UL>
-<P><LI>The fifth flag determines who can use the <B>pts removeuser</B>
-command to remove users and machines from membership in a group. This
-flag has no sensible interpretation for user and machine entries, but must be
-set nonetheless, preferably to the hyphen.
-<UL>
-<P><LI>Set it to the hyphen (<B>-</B>) to permit the members of the
-<B>system:administrators</B> group and the owner of the group to
-remove members.
-<P><LI>Set it to lowercase <B>r</B> to permit members of a group to remove
-other members.
-</UL>
-</UL>
-<P><DT><B>-groupquota
-</B><DD>Specifies the number of additional groups a user can create (it does not
-matter how many he or she has created already). Do not include this
-argument for a group or machine entry.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example changes the privacy flags on the group
-<B>operators</B>, retaining the default values of the first, second and
-third flags, but setting the fourth and fifth flags to enable the group's
-members to add and remove other members.
-<PRE> % <B>pts setfields -nameorid operators -access S-Mar</B>
-
-</PRE>
-<P>The following example changes the privacy flags and sets group quota on the
-user entry <B>admin</B>. It retains the default values of the
-first, fourth, and fifth flags, but sets the second and third flags, to enable
-anyone to list the groups that <B>admin</B> owns and belongs to.
-Users authenticated as <B>admin</B> can create an additional 50
-groups.
-<PRE> % <B>pts setfields -nameorid admin -access SOM-- -groupquota 50</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To edit group entries or set the privacy flags on any type of entry, the
-issuer must own the entry or belong to the
-<B>system:administrators</B> group. To set group-creation
-quota on a user entry, the issuer must belong to the
-<B>system:administrators</B> group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf211.htm#HDRPTS_ADDUSER">pts adduser</A>
-<P><A HREF="auarf217.htm#HDRPTS_EXAMINE">pts examine</A>
-<P><A HREF="auarf221.htm#HDRPTS_LISTOWNED">pts listowned</A>
-<P><A HREF="auarf222.htm#HDRPTS_MEMBERSHIP">pts membership</A>
-<P><A HREF="auarf223.htm#HDRPTS_REMOVEUSER">pts removeuser</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf224.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf226.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf225.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf227.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTS_SETMAX" HREF="auarf002.htm#ToC_240">pts setmax</A></H2>
-<A NAME="IDX5409"></A>
-<A NAME="IDX5410"></A>
-<A NAME="IDX5411"></A>
-<A NAME="IDX5412"></A>
-<A NAME="IDX5413"></A>
-<A NAME="IDX5414"></A>
-<A NAME="IDX5415"></A>
-<A NAME="IDX5416"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Sets the value of the <TT>max group id</TT> or <TT>max user id</TT>
-counter
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>pts setmax</B> [<B>-group</B> <<VAR>group max</VAR>>] [<B>-user</B> <<VAR>user max</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-force</B>] [<B>-help</B>]
-
-<B>pts setm</B> [<B>-g</B> <VAR>group max</VAR>>] [<B>-u</B> <<VAR>user max</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-f</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>pts setmax</B> command sets the value of one or both counters
-that track the IDs the Protection Server allocates to new users, machines, or
-groups: the <TT>max user id</TT> counter for the AFS user IDs (AFS
-UIDs) assigned to users and machines, and the <TT>max group id</TT> counter
-for the AFS group IDs (AFS GIDs) assigned to groups.
-<P>Use the <B>pts listmax</B> command to display the current value of both
-counters.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-group
-</B><DD>Sets the <TT>max group id</TT> counter. Precede the value with a
-hyphen to indicate that it is negative. When an administrator next uses
-the <B>pts creategroup</B> command to create a group entry and does not
-include that command's <B>-id</B> argument, the Protection Server
-assigns the group an AFS GID one less (more negative) than this value.
-<P><DT><B>-user
-</B><DD>Sets the <TT>max user id</TT> counter. When an administrator next
-uses the <B>pts createuser</B> command to create a user or machine entry
-and does not include that command's <B>-id</B> argument, the
-Protection Server assigns the group an AFS UID one greater than this
-value.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. For more details, see
-the introductory <B>pts</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. For more details, see the introductory <B>pts</B> reference
-page.
-<P><DT><B>-force
-</B><DD>Enables the command to continue executing as far as possible when errors
-or other problems occur, rather than halting execution at the first
-error.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command sets the <TT>max group id</TT> counter to -500 and
-the <TT>max user id</TT> counter to 1000.
-<PRE> % <B>pts setmax -group -500 -user 1000</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must belong to the <B>system:administrators</B>
-group.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P><A HREF="auarf214.htm#HDRPTS_CREATEGROUP">pts creategroup</A>
-<P><A HREF="auarf215.htm#HDRPTS_CREATEUSER">pts createuser</A>
-<P><A HREF="auarf220.htm#HDRPTS_LISTMAX">pts listmax</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf225.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf227.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf226.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf228.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRPTSERVER" HREF="auarf002.htm#ToC_241">ptserver</A></H2>
-<A NAME="IDX5417"></A>
-<A NAME="IDX5418"></A>
-<A NAME="IDX5419"></A>
-<A NAME="IDX5420"></A>
-<A NAME="IDX5421"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Protection Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>ptserver</B> [<B>-database</B> <<VAR>db path</VAR>>] [<B>-p</B> <<VAR>number of processes</VAR>>] [<B>-rebuildDB</B>]
- [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>ptserver</B> command initializes the Protection Server, which
-must run on every database server machine. In the conventional
-configuration, its binary file is located in the <B>/usr/afs/bin</B>
-directory on a file server machine.
-<P>The <B>ptserver</B> command is not normally issued at the command shell
-prompt, but rather placed into a database server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a file server machine as the local superuser
-<B>root</B>.
-<P>The Protection Server performs the following tasks:
-<UL>
-<P><LI>Maintains the Protection Database, which contains entries for every user
-and group in the cell. Use the <B>pts</B> commands to administer
-the database.
-<P><LI>Allocates AFS IDs for new user, machine and group entries and maps each ID
-to the corresponding name.
-<P><LI>Generates a current protection subgroup (CPS) at the File Server's
-request. The CPS lists all groups to which a user or machine
-belongs.
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-database
-</B><DD>Specifies the pathname of an alternate directory in which the Protection
-Database files reside. Provide the complete pathname, ending in the
-base filename to which the <B>.DB0</B> and
-<B>.DBSYS1</B> extensions are appended. For example, the
-appropriate value for the default database files is
-<B>/usr/afs/db/prdb</B>.
-<P><DT><B>-p
-</B><DD>Sets the number of server lightweight processes (LWPs) to run.
-Provide a positive integer from the range <B>3</B> to
-<B>16</B>. The default value is 3.
-<P><DT><B>-rebuildDB
-</B><DD>Rebuilds the Protection Database at the beginning of Protection Server
-initialization. Use this argument only in consultation with AFS
-Development or Product Support.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates a <B>ptserver</B>
-process on the machine <B>fs3.abc.com</B>. The
-command appears here on multiple lines only for legibility.
-<PRE> % <B>bos create -server fs3.abc.com -instance ptserver</B> \
- <B>-type simple -cmd /usr/afs/bin/ptserver</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf047.htm#HDRPRDBDB">prdb.DB0 and prdb.DBSYS1</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf210.htm#HDRPTS_INTRO">pts</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf226.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf228.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf227.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf229.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRRCP" HREF="auarf002.htm#ToC_242">rcp (AFS version)</A></H2>
-<A NAME="IDX5422"></A>
-<A NAME="IDX5423"></A>
-<A NAME="IDX5424"></A>
-<A NAME="IDX5425"></A>
-<A NAME="IDX5426"></A>
-<A NAME="IDX5427"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Copies a file on a remote machine
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>rcp</B> [<B>-p</B>] <<VAR>file1</VAR>> <<VAR>file2</VAR>>
-
-<B>rcp</B> [<B>-r</B>] [<B>-p</B>] <<VAR>file</VAR>><SUP>+</SUP> <<VAR>directory</VAR>>
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The AFS-modified <B>rcp</B> program functions like the standard UNIX
-<B>rcp</B> program, but also passes the issuer's AFS token to the
-remote machine's Cache Manager, to enable authenticated access to the AFS
-filespace via that machine.
-<P>Token passing is most effective if both the remote machine and local
-machine belong to the same cell, because the <B>rcp</B> command can pass
-only one token even if the user has several tokens--it passes the token
-listed first in the output from the <B>tokens</B> command. If the
-remote and local machine do not belong to the same cell, the possibilities are
-as follows:
-<UL>
-<P><LI>The passed token is for the remote machine's cell. The issuer
-accesses the remote cell's AFS file tree as an authenticated AFS user,
-but is considered <B>anonymous</B> in the local cell and so can exercise
-only the access rights granted to the <B>system:anyuser</B> group
-there. For example, to copy a file into a local AFS directory from the
-remote cell, the directory's ACL must grant the <B>l</B>
-(<B>lookup</B>) and <B>i</B> (<B>insert</B>) permissions to the
-<B>system:anyuser</B> group.
-<P><LI>The passed token is for the local machine's cell. The issuer
-accesses the remote cell's AFS file tree as <B>anonymous</B>, and so
-can only exercise the access rights granted to the
-<B>system:anyuser</B> group.
-</UL>
-<P>In addition to running the AFS version of the <B>rcp</B> binary on the
-machine where the <B>rcp</B> command is issued, other configuration
-changes are necessary for token passing to work properly. See the
-<B>Cautions</B> section for a list.
-<P>The AFS version of the <B>rcp</B> command is compatible with the
-standard <B>inetd</B> command, but token passing works only if both
-programs are modified to handle AFS tokens. If only one of them is
-modified, the issuer accesses the AFS filespace through the remote machine as
-the <B>anonymous</B> user.
-<P><STRONG>Cautions</STRONG>
-<P>The AFS distribution does not include an AFS-modified version of this
-command for every system type, in some cases because the operating system
-vendor has already modified the standard version in the required way.
-For details, see the <I>IBM AFS Release Notes</I>.
-<P>The AFS <B>rcp</B> command does not allow third party copies, in which
-neither the source file nor the target file is stored on the machine where the
-command is issued. The standard UNIX <B>rcp</B> command claims to
-provide this functionality.
-<P>For security's sake, use the AFS version of the <B>rcp</B> command
-only in conjunction with PAGs, either by using an AFS-modified login utility,
-issuing the <B>pagsh</B> command before obtaining tokens, or including the
-<B>-setpag</B> flag to the <B>klog</B> command.
-<P>Several configuration requirements and restrictions are necessary for token
-passing to work correctly with an AFS-modified version of the <B>rcp</B>
-command. Some of these are also necessary with the standard UNIX
-version, but are included here because the issuer accustomed to AFS
-protections is possibly unlikely to consider them. There are possibly
-other UNIX-based requirements and restrictions not mentioned here;
-consult the UNIX manual page. (One important one is that no
-<TT>stty</TT> commands can appear in the issuer's shell initialization
-file, such as the <B>.cshrc</B> file.)
-<P>The requirements and restrictions for token passing include the
-following.
-<UL>
-<P><LI>The local machine must be running the AFS version of the <B>rcp</B>
-command, with the <B>rcp</B> binary file locally installed to grant setuid
-privilege to the owner, the local superuser <B>root</B>.
-<P><LI>The remote machine must be running the AFS version of the <B>inetd</B>
-program.
-<P><LI>If the <B>rcp</B> command is to consult a <B>.rhosts</B>
-file on the remote machine, the file must have UNIX protections no more
-liberal than <B>-rw-r--r--</B>. If the <B>.rhosts</B>
-file resides in a user home directory in AFS, the home directory must also
-grant the <B>lookup</B> (<B>l</B>) and <B>read</B> (<B>r</B>)
-permissions to the <B>system:anyuser</B> group.
-</UL>
-<P><STRONG>Options</STRONG>
-<P>Consult the UNIX manual page for the <B>rcp</B> command.
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf179.htm#HDRINETD">inetd (AFS version)</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>UNIX manual page for <B>rcp</B>
-<P><I>IBM AFS Release Notes</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf227.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf229.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf228.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf230.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRRSH" HREF="auarf002.htm#ToC_243">rsh (AFS version)</A></H2>
-<A NAME="IDX5428"></A>
-<A NAME="IDX5429"></A>
-<A NAME="IDX5430"></A>
-<A NAME="IDX5431"></A>
-<A NAME="IDX5432"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Opens a shell on a remote machine
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>rsh</B> <VAR>host</VAR> [<B>-n</B>] [<B>-l</B> <<VAR>username</VAR>>] <<VAR>command</VAR>>
-
-<VAR>host</VAR> [<B>-n</B>] [<B>-l</B> <<VAR>username</VAR>>] <<VAR>command</VAR>>
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The AFS-modified <B>rsh</B> program functions like the standard UNIX
-<B>rsh</B> program, but also passes the issuer's AFS token to the
-remote machine's Cache Manager, to enable authenticated access to the AFS
-filespace via that machine.
-<P>Token passing is most effective if both the remote machine and local
-machine belong to the same cell, because the <B>rsh</B> program can pass
-only one token even if the user has several tokens--it passes the token
-listed first in the output from the <B>tokens</B> command. If the
-remote and local machine do not belong to the same cell, the first token must
-be valid for the remote machine's cell, in order for the remote
-cell's server processes to recognize the issuer as authenticated.
-<P>In addition to running the AFS version of the <B>rsh</B> binary on the
-machine where the <B>rsh</B> command is issued, other configuration
-changes are necessary for token passing to work properly. See the
-<B>Cautions</B> section for a list.
-<P>The AFS version of the <B>rsh</B> command is compatible with the
-standard UNIX <B>inetd</B> command, but token passing works only if both
-programs are modified to handle AFS tokens. If only one of them is
-modified, the issuer accesses the AFS filespace through the remote machine as
-the user <B>anonymous</B>.
-<P><STRONG>Cautions</STRONG>
-<P>Some operating systems assign an alternate name to this program, such as
-<B>remsh</B>. The version included in the AFS distribution uses the
-same name as the operating system.
-<P>The AFS distribution does not include an AFS-modified version of this
-command for every system type, in some cases because the operating system
-vendor has already modified the standard version in the required way.
-For details, see the <I>IBM AFS Release Notes</I>.
-<P>For security's sake, use the AFS version of the <B>rsh</B> command
-only in conjunction with PAGs, either by using an AFS-modified login utility,
-issuing the <B>pagsh</B> command before obtaining tokens, or including the
-<B>-setpag</B> flag to the <B>klog</B> command.
-<P>Several configuration requirements and restrictions are necessary for token
-passing to work correctly with the AFS version of the <B>rsh</B>
-command. Some of these are also necessary with the standard UNIX
-version, but are included here because the issuer used to AFS protections is
-possibly unlikely to think of them. There are possibly other UNIX-based
-requirements or restrictions not mentioned here; consult the UNIX manual
-page for the <B>rsh</B> command. (One important one is that no
-<TT>stty</TT> commands can appear in the issuer's shell initialization
-file, such as the <B>.cshrc</B> file.)
-<P>The requirements and restrictions for token passing include the
-following.
-<UL>
-<P><LI>The local machine must be running the AFS version of the <B>rsh</B>
-command, with the binary file locally installed to grant setuid privilege to
-the owner, the local superuser <B>root</B>.
-<P><LI>The remote machine must be running the AFS version of the <B>inetd</B>
-program.
-<P><LI>If the <B>rsh</B> command is to consult an <B>.rhosts</B>
-file on the remote machine, the file must have UNIX mode bits no more liberal
-than <B>-rw-r--r--</B>. If the <B>.rhosts</B> file
-resides in a user home directory in AFS, the home directory must also grant
-the <B>l</B> (<B>lookup</B>) and <B>r</B> (<B>read</B>)
-permissions to the <B>system:anyuser</B> group.
-</UL>
-<P><STRONG>Options</STRONG>
-<P>Consult the UNIX manual page for the <B>rsh</B> command.
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf179.htm#HDRINETD">inetd (AFS version)</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>UNIX manual page for <B>rsh</B> or <B>remsh</B>
-<P><I>IBM AFS Release Notes</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf228.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf230.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf229.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf231.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRRUNNTP" HREF="auarf002.htm#ToC_244">runntp</A></H2>
-<A NAME="IDX5433"></A>
-<A NAME="IDX5434"></A>
-<A NAME="IDX5435"></A>
-<A NAME="IDX5436"></A>
-<A NAME="IDX5437"></A>
-<A NAME="IDX5438"></A>
-<A NAME="IDX5439"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Network Time Protocol Daemon
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>runntp</B> [<B>-localclock</B>] [<B>-precision</B> <<VAR>small negative integer</VAR>>]
- [<B>-logfile</B> <<VAR>filename for ntpd's stdout/stderr</VAR>>]
- [<B>-ntpdpath</B> <<VAR>pathname of ntpd executable (/usr/afs/bin/ntpd)</VAR>>]
- [<<VAR>host</VAR>><SUP>+</SUP>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>runntp</B> command initializes the Network Time Protocol Daemon
-(NTPD) and related programs on the local machine and constructs an
-<B>ntp.conf</B> configuration file. The intended use is on
-AFS file server machines as a convenient interface to the standard
-<B>ntpd</B> program.
-<P>In the conventional configuration, the binary file for the command is
-located in the <B>/usr/afs/bin</B> directory on a file server
-machine. The command is not normally issued at the command shell
-prompt, but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a server machine as the local superuser
-<B>root</B>.
-<P><STRONG>Cautions</STRONG>
-<P>Do not run the <B>runntp</B> program if NTPD or another time protocol
-is already in use in the cell. Running two time-synchronization
-protocols can cause errors.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-localclock
-</B><DD>Designates the local machine's internal clock as a possible time
-source if a network partition separates the machine from the other source
-machines listed on the command line. In cells that are not connected to
-an exterior network or are behind a firewall, include this flag on every
-machine that runs the <B>runntp</B> process. In cells that
-frequently lose access to exterior networks (voluntarily or not), include it
-only on the <B>runntp</B> process running on the system control
-machine. Do not include the flag if the cell is reliably connected to
-exterior networks.
-<P><DT><B>-precision
-</B><DD>Specifies the precision of the local clock. This argument is not
-normally provided. As the <B>ntpd</B> process initializes, it
-determines the precision of the local clock on its own. If provided, it
-is a small integer preceded by a hyphen to show that it is negative.
-The value is used as an exponent on the number 2, and the result interpreted
-as the frequency, in fractions of a second, at which the local clock ticks
-(advances).
-<P>For example, a value of <B>-6</B>, which translates to
-<B>2<SUP>-6</SUP></B> or 1/64, means that the local clock ticks once every
-1/64th of a second, or has a precision of about 60 ticks per second. A
-value of <B>-7</B> translates to about 100 ticks per second. A
-value of <B>-10</B> translates to about 1000 ticks per second (a
-millisecond clock).
-<P><DT><B>-logfile
-</B><DD>Specifies the local disk pathname for the NTP daemon's log file, such
-as <B>/usr/afs/logs/ntp.log</B>. The log records which
-machines are serving as time sources and peers, what adjustments have been
-made to reduce drift, and so on. Use the <B>ntpd</B> process's
-debugging mechanism to control the amount of information produced. If
-this argument is omitted, the information is discarded.
-<P><DT><B>-ntpdpath
-</B><DD>Specifies the local disk pathname of the binary for the <B>ntpd</B>
-program. If this argument is omitted, the default is
-<B>/usr/afs/bin/ntpd</B>.
-<P><DT><B><VAR>host</VAR>
-</B><DD>Is the fully qualified hostname of each machine to consult as a time
-source. By convention, the machines are outside the cell if exterior
-networks are accessible.
-<P>In general, this argument is necessary only on the system control
-machine. If the issuer omits it, then the local machine consults the
-local database server machines listed in its copy of the
-<B>/usr/afs/etc/CellServDB</B> file.
-<P>For advice on selecting appropriate time sources, see the <I>IBM AFS
-Quick Beginnings</I> or ask AFS Product Support.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P>UNIX manual page for <B>ntp</B>
-<P>UNIX manual page for <B>ntpd</B>
-<P>UNIX manual page for <B>ntpdc</B>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf229.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf231.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf230.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf232.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRRXDEBUG" HREF="auarf002.htm#ToC_245">rxdebug</A></H2>
-<A NAME="IDX5440"></A>
-<A NAME="IDX5441"></A>
-<A NAME="IDX5442"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Provides debugging trace of Rx activity
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>rxdebug -servers</B> <<VAR>server machine</VAR>> [<B>-port</B> <<VAR>IP port</VAR>>] [<B>-nodally</B>]
- [<B>-allconnections</B>] [<B>-rxstats</B>] [<B>-onlyserver</B>] [<B>-onlyclient</B>]
- [<B>-onlyport</B> <<VAR>show only <port></VAR>>] [<B>-onlyhost</B> <<VAR>show only <host></VAR>>]
- [<B>-onlyauth</B> <<VAR>show only <auth level></VAR>>] [<B>-version</B>] [<B>-noconns</B>]
- [<B>-peers</B>] [<B>-help</B>]
-
-<B>rxdebug -s</B> <<VAR>server machine</VAR>> [<B>-po</B> <<VAR>IP port</VAR>>] [<B>-nod</B>] [<B>-a</B>] [<B>-r</B>]
- [<B>-onlys</B>] [<B>-onlyc</B>] [<B>-onlyp</B> <<VAR>show only <port></VAR>>]
- [<B>-onlyh</B> <<VAR>show only <host></VAR>>] [<B>-onlya</B> <<VAR>show only <auth level></VAR>>]
- [<B>-v</B>] [<B>-noc</B>] [<B>-pe</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>rxdebug</B> command provides a trace of Rx activity for the
-server or client machine named by the <B>-servers</B> argument. Rx
-is AFS's proprietary remote procedure call (RPC) protocol, so this
-command enables the issuer to check the status of communication between the
-Cache Manager or an AFS server process (as specified with the <B>-port</B>
-argument) on the machine and one or more processes on other machines.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-servers
-</B><DD>Specifies the machine that is running the Cache Manager or server process
-for which to trace Rx activity. Provide the machine's IP address
-in dotted decimal format, its fully qualified host name (for example,
-<B>fs1.abc.com</B>), or the shortest abbreviated form of its
-host name that distinguishes it from other machines. Successful use of
-an abbreviated form depends on the availability of a name resolution service
-(such as the Domain Name Service or a local host table) at the time the
-command is issued.
-<P><DT><B>-port
-</B><DD>Specifies the process for which to trace Rx activity. Omit this
-argument to specify the File Server (<B>fileserver</B> process), or
-provide one of the following values:
-<DL>
-<DD><P><B>7000</B> for the File Server (<B>fileserver</B> process)
-<DD><P><B>7001</B> for the Cache Manager (specifically, its callback
-interface)
-<DD><P><B>7002</B> for the Protection Server (<B>ptserver</B> process)
-<DD><P><B>7003</B> for the Volume Location (VL) Server (<B>vlserver</B>
-process)
-<DD><P><B>7004</B> for the Authentication Server (<B>kaserver</B>
-process)
-<DD><P><B>7005</B> for the Volume Server (<B>volserver</B> process)
-<DD><P><B>7007</B> for the BOS Server (<B>bosserver</B> process)
-<DD><P><B>7008</B> for the Update Server (<B>upserver</B> process)
-<DD><P><B>7009</B> for the NFS/AFS Translator's <B>rmtsysd</B>
-daemon
-<DD><P><B>7021</B> for the Backup Server (<B>buserver</B> process)
-<DD><P><B>7025</B> through <B>65535</B> for the Backup Tape Coordinator
-(<B>butc</B> process) that has the port offset number derived by
-subtracting 7025 from this value
-</DL>
-<P><DT><B>-nodally
-</B><DD>Produces output only for connections that are not in dally mode.
-<P><DT><B>-allconnections
-</B><DD>Produces output for all connections, even inactive ones. By
-default, the output includes information only for connections that are active
-or in dally mode when the <B>rxdebug</B> command is issued.
-<P><DT><B>-rxstats
-</B><DD>Produces detailed statistics about Rx history and performance (for
-example, counts of the number of packets of various types the process has read
-and sent, calculations of average and minimum roundtrip time, and so
-on).
-<P><DT><B>-onlyserver
-</B><DD>Produces output only for connections in which the process designated by
-the <B>-port</B> argument is acting as the server.
-<P><DT><B>-onlyclient
-</B><DD>Produces output only for connections in which the process designated by
-the <B>-port</B> argument is acting as the client.
-<P><DT><B>-onlyport
-</B><DD>Produces output only for connections between the process designated by the
-<B>-port</B> argument and the specified port on any another
-machine. Use the same port identifiers as for the <B>-port</B>
-argument.
-<P><DT><B>-onlyhost
-</B><DD>Produces output only for connections between the process designated by the
-<B>-port</B> argument and any process on the specified machine. To
-identify the machine, use the same notation as for the <B>-servers</B>
-argument.
-<P><DT><B>-onlyauth
-</B><DD>Produces output only for connections that are using the specified
-authentication level. Provide one of the following values:
-<UL>
-<P><LI><B>auth</B> for connections at authentication level
-<B>rxkad_auth</B>
-<P><LI><B>clear</B> for connections at authentication level
-<B>rxkad_clear</B>
-<P><LI><B>crypt</B> for connections at authentication level
-<B>rxkad_crypt</B>
-<P><LI><B>none</B> for unauthenticated connections (equivalents are
-<B>null</B>, <B>noauth</B>, and <B>unauth</B>)
-</UL>
-<P><DT><B>-version
-</B><DD>Reports the AFS build level of the binary file for the process designated
-by the <B>-port</B> argument (or of the kernel extensions file for port
-7001, the Cache Manager's callback interface). Any other options
-combined with this one are ignored.
-<P><DT><B>-noconns
-</B><DD>Produces only the standard statistics that begin the output produced by
-every option (other than <B>-version</B>), without reporting on any
-connections. Any other options combined with this one are
-ignored.
-<P><DT><B>-peers
-</B><DD>Outputs information from the <I>peer structure</I> maintained for each
-port on another machine to which the process designated by the
-<B>-port</B> argument has a connection. There is information about
-roundtrip time and numbers of packets sent and received, for example.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If any options other than <B>-version</B> or <B>-help</B> are
-provided, the output written to the standard output stream begins with basic
-statistics about packet usage and availability, how many calls are waiting for
-a thread, how many threads are free, and so on (this is the only information
-provided by the <B>-noconns</B> flag). Adding other options
-produces additional information as described in the preceding
-<B>Options</B> section of this reference page. The output is
-intended for debugging purposes and is meaningful to someone familiar with the
-implementation of Rx.
-<P><STRONG>Privilege Required</STRONG>
-<P>None.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf058.htm#HDRAFSD">afsd</A>
-<P><A HREF="auarf124.htm#HDRBOSSERVER">bosserver</A>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P><A HREF="auarf126.htm#HDRBUTC">butc</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf230.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf232.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf231.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf233.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSALVAGER" HREF="auarf002.htm#ToC_246">salvager</A></H2>
-<A NAME="IDX5443"></A>
-<A NAME="IDX5444"></A>
-<A NAME="IDX5445"></A>
-<A NAME="IDX5446"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Salvager component of the <B>fs</B> process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>salvager</B> [<B>initcmd</B>] [<B>-partition</B> <<VAR>Name of partition to salvage</VAR>>]
- [<B>-volumeid</B> <<VAR>Volume Id to salvage</VAR>>] [<B>-debug</B>]
- [<B>-nowrite</B>] [<B>-inodes</B>] [<B>-force</B>] [<B>-oktozap</B>]
- [<B>-rootinodes</B>] [<B>-salvagedirs</B>] [<B>-blockreads</B>]
- [<B>-parallel</B> <<VAR># of max parallel partition salvaging</VAR>>]
- [<B>-tmpdir</B> <<VAR>Name of dir to place tmp files</VAR>>]
- [<B>-showlog</B>] [<B>-showsuid</B>] [<B>-showmounts</B>]
- [<B>-orphans</B> <<B>ignore</B> | <B>remove</B> | <B>attach</B>>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>salvager</B> command initializes the Salvager component of the
-<B>fs</B> process. In the conventional configuration, its binary
-file is located in the <B>/usr/afs/bin</B> directory on a file server
-machine.
-<P>The Salvager restores internal consistency to corrupted read/write volumes
-on the local file server machine where possible. For read-only or
-backup volumes, it inspects only the volume header:
-<UL>
-<P><LI>If the volume header is corrupted, the Salvager removes the volume
-completely and records the removal in its log file,
-<B>/usr/afs/logs/SalvageLog</B>. Issue the <B>vos release</B>
-or <B>vos backup</B> command to create the read-only or backup volume
-again.
-<P><LI>If the volume header is intact, the Salvager skips the volume (does not
-check for corruption in the contents). However, if the File Server
-notices corruption as it initializes, it sometimes refuses to attach the
-volume or bring it online. In this case, it is simplest to remove the
-volume by issuing the <B>vos remove</B> or <B>vos zap</B>
-command. Then issue the <B>vos release</B> or <B>vos backup</B>
-command to create it again.
-</UL>
-<P>Unlike other server process initialization commands, the
-<B>salvager</B> command is designed to be issued at the command shell
-prompt, as well as being placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. It is also possible to invoke the Salvager remotely by issuing
-the <B>bos salvage</B> command.
-<P>Combine the command's options as indicated to salvage different
-numbers of read/write volumes:
-<UL>
-<P><LI>To salvage all volumes on the file server machine, provide no
-arguments. No volumes on the machine are accessible to Cache Managers
-during the salvage, because the BOS Server stops the File Server and Volume
-Server processes while the Salvager runs.
-<P><LI>To salvage all of the volumes on one partition, provide the
-<B>-partition</B> argument. As for a salvage of all volumes on the
-machine, no volumes on the machine are accessible to Cache Managers during the
-salvage operation.
-<P><LI>To salvage only one volume, combine the <B>-partition</B> and
-<B>-volumeid</B> arguments. Only that volume is inaccessible to
-Cache Managers, because the BOS Server does not shutdown the File Server and
-Volume Server processes.
-</UL>
-<P>The Salvager normally salvages only those read/write volumes that are
-marked as having been active when a crash occurred. To have it salvage
-all relevant read/write volumes, add the <B>-force</B> flag.
-<P>The Salvager normally creates new inodes as it repairs damage. If
-the partition is so full that there is no room for new inodes, use the
-<B>-nowrite</B> argument to bringing undamaged volumes online without
-attempting to salvage damaged volumes. Then use the <B>vos move</B>
-command to move one or more of the undamaged volumes to other partitions,
-freeing up the space that the Salvager needs to create new inodes.
-<P>By default, multiple Salvager subprocesses run in parallel: one for
-each partition up to four, and four subprocesses for four or more
-partitions. To increase or decrease the number of subprocesses running
-in parallel, provide a positive integer value for the <B>-parallel</B>
-argument.
-<P>If there is more than one server partition on a physical disk, the Salvager
-by default salvages them serially to avoid the inefficiency of constantly
-moving the disk head from one partition to another. However, this
-strategy is often not ideal if the partitions are configured as logical
-volumes that span multiple disks. To force the Salvager to salvage
-logical volumes in parallel, provide the string <B>all</B> as the value
-for the <B>-parallel</B> argument. Provide a positive integer to
-specify the number of subprocesses to run in parallel (for example,
-<B>-parallel 5all</B> for five subprocesses), or omit the integer to run
-up to four subprocesses, depending on the number of logical volumes being
-salvaged.
-<P>The Salvager creates temporary files as it runs, by default writing them to
-the partition it is salvaging. The number of files can be quite large,
-and if the partition is too full to accommodate them, the Salvager terminates
-without completing the salvage operation (it always removes the temporary
-files before exiting). Other Salvager subprocesses running at the same
-time continue until they finish salvaging all other partitions where there is
-enough disk space for temporary files. To complete the interrupted
-salvage, reissue the command against the appropriate partitions, adding the
-<B>-tmpdir</B> argument to redirect the temporary files to a local disk
-directory that has enough space.
-<P>The <B>-orphans</B> argument controls how the Salvager handles orphaned
-files and directories that it finds on server partitions it is
-salvaging. An <I>orphaned</I> element is completely inaccessible
-because it is not referenced by the vnode of any directory that can act as its
-parent (is higher in the filespace). Orphaned objects occupy space on
-the server partition, but do not count against the volume's quota.
-<P>To generate a list of all mount points that reside in one or more volumes,
-rather than actually salvaging them, include the <B>-showmounts</B>
-flag.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-partition
-</B><DD>Specifies the name of the partition to salvage. Specify the full
-partition name using the form <B>/vicep</B><VAR>x</VAR> or
-<B>/vicep</B><VAR>xx</VAR>. Omit this argument to salvage every
-partition on the file server machine.
-<P><DT><B>-volumeid
-</B><DD>Specifies the volume ID of a specific read/write volume to salvage.
-The <B>-partition</B> argument must be provided along with this one and
-specify the volume's actual site.
-<P><DT><B>-debug
-</B><DD>Allows only one Salvager subprocess to run at a time, regardless of the
-setting of the <B>-parallel</B> option. Include it when running the
-Salvager in a debugger to make the trace easier to interpret.
-<P><DT><B>-nowrite
-</B><DD>Brings all undamaged volumes online without attempting to salvage any
-damaged volumes.
-<P><DT><B>-inodes
-</B><DD>Records in the <B>/usr/afs/logs/SalvageLog</B> file a list of all AFS
-inodes that the Salvager modified.
-<P><DT><B>-force
-</B><DD>Inspects all volumes for corruption, not just those that are marked as
-having been active when a crash occurred.
-<P><DT><B>-oktozap
-</B><DD>Removes a volume that is so damaged that even issuing the <B>vos
-zap</B> command with the <B>-force</B> flag is ineffective. Use
-this argument only in consultation with AFS Development or Product
-Support. Combine it with the <B>-partition</B> and
-<B>-volumeid</B> arguments to identify the volume to remove.
-<P><DT><B>-rootinodes
-</B><DD>Records in the <B>/usr/afs/logs/SalvageLog</B> file a list of all AFS
-inodes owned by the local superuser <B>root</B>.
-<P><DT><B>-salvagedirs
-</B><DD>Salvages entire directory structures, even if they do not appear to be
-damaged. By default, the Salvager salvages a directory only if it is
-flagged as corrupted.
-<P><DT><B>-blockreads
-</B><DD>Forces the Salvager to read a partition one disk block (512 bytes) at a
-time and to skip any blocks that are too badly damaged to be salvaged.
-This allows it to salvage as many volumes as possible. By default, the
-Salvager reads large disk blocks, which can cause it to exit prematurely if it
-encounters disk errors. Use this flag if the partition to be salvaged
-has disk errors.
-<P><DT><B>-parallel
-</B><DD>Specifies the maximum number of Salvager subprocesses to run in
-parallel. Provide one of three values:
-<UL>
-<P><LI>An integer from the range <B>1</B> to <B>32</B>. A value of
-<B>1</B> means that a single Salvager process salvages the partitions
-sequentially.
-<P><LI>The string <B>all</B> to run up to four Salvager subprocesses in
-parallel on partitions formatted as logical volumes that span multiple
-physical disks. Use this value only with such logical volumes.
-<P><LI>The string <B>all</B> followed immediately (with no intervening space)
-by an integer from the range <B>1</B> to <B>32</B>, to run the
-specified number of Salvager subprocesses in parallel on partitions formatted
-as logical volumes. Use this value only with such logical
-volumes.
-</UL>
-<P>The BOS Server never starts more Salvager subprocesses than there are
-partitions, and always starts only one process to salvage a single
-volume. If this argument is omitted, up to four Salvager subprocesses
-run in parallel.
-<P><DT><B>-tmpdir
-</B><DD>Names a local disk directory in which the Salvager places the temporary
-files it creates during a salvage operation, instead of writing them to the
-partition being salvaged (the default). If the Salvager cannot write to
-the specified directory, it attempts to write to the partition being
-salvaged.
-<P><DT><B>-showlog
-</B><DD>Displays on the standard output stream all log data that is being written
-to the <B>/usr/afs/logs/SalvageLog</B> file.
-<P><DT><B>-showsuid
-</B><DD>Displays a list of the pathnames for all files that have the setuid or
-setgid mode bit set.
-<P><DT><B>-showmounts
-</B><DD>Records in the <B>/usr/afs/logs/SalvageLog</B> file all mount points
-found in each volume. The Salvager does not repair corruption in the
-volumes, if any exists.
-<P><DT><B>-orphans
-</B><DD>Controls how the Salvager handles orphaned files and directories.
-Choose one of the following three values:
-<DL>
-<P><DT><B>ignore
-</B><DD>Leaves the orphaned objects on the disk, but prints a message to the
-<B>/usr/afs/logs/SalvageLog</B> file reporting how many orphans were found
-and the approximate number of kilobytes they are consuming. This is the
-default if the <B>-orphans</B> argument is omitted.
-<P><DT><B>remove
-</B><DD>Removes the orphaned objects, and prints a message to the
-<B>/usr/afs/logs/SalvageLog</B> file reporting how many orphans were
-removed and the approximate number of kilobytes they were consuming.
-<P><DT><B>attach
-</B><DD>Attaches the orphaned objects by creating a reference to them in the vnode
-of the volume's root directory. Since each object's actual
-name is now lost, the Salvager assigns each one a name of the following
-form:
-<DL>
-<DD><P><B>_ _ORPHANFILE_ _.</B><VAR>index</VAR> for files
-<DD><P><B>_ _ORPHANDIR_ _.</B><VAR>index</VAR> for directories
-</DL>
-<P>
-<P>where <VAR>index</VAR> is a two-digit number that uniquely identifies each
-object. The orphans are charged against the volume's quota and
-appear in the output of the <B>ls</B> command issued against the
-volume's root directory.
-</DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command instructs the Salvager to attempt to salvage the
-volume with volume ID 258347486 on <B>/vicepg</B> on the local
-machine.
-<PRE> % <B>/usr/afs/bin/salvager -partition /vicepg -volumeid 258347486</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>To issue the command at the shell prompt, the issuer must be logged in as
-the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf030.htm#HDRSALVAGELOG">SalvageLog</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf268.htm#HDRVOS_MOVE">vos move</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf231.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf233.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf232.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf234.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSCOUT" HREF="auarf002.htm#ToC_247">scout</A></H2>
-<A NAME="IDX5447"></A>
-<A NAME="IDX5448"></A>
-<A NAME="IDX5449"></A>
-<A NAME="IDX5450"></A>
-<A NAME="IDX5451"></A>
-<A NAME="IDX5452"></A>
-<A NAME="IDX5453"></A>
-<A NAME="IDX5454"></A>
-<A NAME="IDX5455"></A>
-<A NAME="IDX5456"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Monitors the File Server process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>scout</B> [<B>initcmd</B>] <B>-server</B> <<VAR>FileServer name(s) to monitor</VAR>><SUP>+</SUP>
- [<B>-basename</B> <<VAR>base server name</VAR>>]
- [<B>-frequency</B> <<VAR>poll frequency, in seconds</VAR>>] [<B>-host</B>]
- [<B>-attention</B> <<VAR>specify attention (highlighting) level</VAR>><SUP>+</SUP>]
- [<B>-debug</B> <<VAR>turn debugging output on to the named file</VAR>>] [<B>-help</B>]
-
-<B>scout</B> [<B>i</B>] <B>-s</B> <<VAR>FileServer name(s) to monitor</VAR>><SUP>+</SUP>
- [<B>-b</B> <<VAR>base server name</VAR>>] [<B>-f</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-ho</B>] [<B>-a</B> <<VAR>specify attention (highlighting) level</VAR>><SUP>+</SUP>]
- [<B>-d</B> <<VAR>turn debugging output on to the named file</VAR>>] [<B>-he</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>scout</B> command displays statistics gathered from the File
-Server process running on each machine specified with the <B>-server</B>
-argument. The <B>Output</B> section explains the meaning of the
-statistics and describes how they appear in the command shell, which is
-preferably a window managed by a window manager program.
-<P><STRONG>Cautions</STRONG>
-<P>The <B>scout</B> program must be able to access the <B>curses</B>
-graphics package, which it uses to display statistics. Most UNIX
-distributions include <B>curses</B> as a standard utility.
-<P>Both dumb terminals and windowing systems that emulate terminals can
-display the <B>scout</B> program's statistics. The display
-makes use of reverse video and cursor addressing, so the display environment
-must support those features for it to look its best (most windowing systems
-do, most dumb terminals do not). Also, set the TERM environment
-variable to the correct terminal type, or one with characteristics similar to
-the actual ones. For machines running the AIX operating system, the
-recommended setting for TERM is <B>vt100</B>, as long as the terminal is
-similar to that. For other operating systems, the wider range of
-acceptable values includes <B>xterm</B>, <B>xterms</B>,
-<B>vt100</B>, <B>vt200</B>, and <B>wyse85</B>.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-server
-</B><DD>Specifies each file server machine running a File Server process to
-monitor. Provide each machine's fully qualified hostname unless
-the <B>-basename</B> argument is used. In that case, specify only
-the unique initial part of each machine name, omitting the domain name suffix
-(the basename) common to all the names. It is also acceptable to use
-the shortest abbreviated form of a host name that distinguishes it from other
-machines, but successful resolution depends on the availability of a name
-resolution service (such as the Domain Name Service or a local host table) at
-the time the command is issued.
-<P><DT><B>-basename
-</B><DD>Specifies the basename (domain name) suffix common to all of the file
-server machine names specified with the <B>-server</B> argument, and is
-automatically appended to them. This argument is normally the name of
-the cell to which the machines belong. Do not include the period that
-separates this suffix from the distinguishing part of each file server machine
-name, but do include any periods that occur within the suffix itself.
-For example, in the ABC Corporation cell, the proper value is
-<B>abc.com</B> rather than
-<B>.abc.com</B>.
-<P><DT><B>-frequency
-</B><DD>Indicates how often to probe the File Server processes. Specify a
-number of seconds greater than <B>0</B> (zero). The default is 60
-seconds.
-<P><DT><B>-host
-</B><DD>Displays the name of the machine that is running the <B>scout</B>
-program, in the banner line of the display screen.
-<P><DT><B>-attention
-</B><DD>Defines a list of entries, each of which pairs a statistic and a threshold
-value. When the value of the statistic exceeds the indicated threshold
-value, it is highlighted (in reverse video) in the display. List the
-pairs in any order. The acceptable values are the following:
-<UL>
-<P><LI><B>conn</B> <VAR>connections</VAR>. Indicates the number of open
-connections to client processes at which to highlight the statistic.
-The statistic returns to regular display when the value goes back below the
-threshold. There is no default threshold.
-<P>An example of an acceptable value is <B>conn 300</B>.
-<P><LI><B>disk</B>, which takes one of two types of values:
-<UL>
-<P><LI><B>disk</B> <VAR>blocks_free</VAR>. Indicates the number of
-remaining free kilobyte blocks at which to highlight the statistic. The
-statistic returns to regular display when the value again exceeds the
-threshold. There is no default threshold.
-<P>An example of an acceptable value is <B>disk 5000</B>.
-<P><LI><B>disk</B> <VAR>percent_full</VAR><B>%</B>. Indicates the
-percentage of disk usage at which to highlight the statistic. The
-statistic returns to regular display when the value goes back below the
-threshold. The default threshold is 95%. Acceptable values are
-the integers in the range from <B>0</B> to <B>99</B>, followed by the
-percent sign (<B>%</B>) to distinguish this type of value from the one
-described just previously.
-<P>An example is <B>disk 90%</B>.
-</UL>
-<P><LI><B>fetch</B> <VAR>fetch_RPCs</VAR>. Indicates the cumulative
-number of fetch RPCs from client processes at which to highlight the
-statistic. The statistic does not return to regular display until the
-File Server process restarts, at which time the value returns to zero.
-There is no default threshold.
-<P>Example of a legal value: <B>fetch 6000000</B>
-<P><LI><B>store</B> <VAR>store_RPCs</VAR>. Indicates the cumulative
-number of store RPCs from client processes at which to highlight the
-statistic. The statistic does not return to regular display until the
-File Server process restarts, at which time the value returns to zero.
-There is no default threshold.
-<P>Example of an acceptable value: <B>store 200000</B>
-<P><LI><B>ws</B> <VAR>active_client_machines</VAR>. Indicates the number
-of client machines with active open connections at which to highlight the
-statistic. An active connection is defined as one over which the File
-Server and client have communicated in the last 15 minutes. The
-statistic returns to regular display when the value goes back below the
-threshold. There is no default threshold.
-<P>Example of an acceptable value: <B>ws 65</B>
-</UL>
-<P><DT><B>-debug
-</B><DD>Specifies the pathname of the file into which to write a debugging
-trace. Partial pathnames are interpreted relative to the current
-working directory.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The <B>scout</B> program can display statistics either in a dedicated
-window or on a plain screen if a windowing environment is not
-available. For best results, the window or screen needs the ability to
-print in reverse video.
-<P>The <B>scout</B> screen has three main parts: the banner line,
-the statistics display region and the message/probe line.
-<P><B><I>The Banner Line</I></B>
-<P>By default, the string <TT>Scout</TT> appears in the banner line at the
-top of the window or screen. Two optional arguments place additional
-information in the banner line:
-<UL>
-<P><LI>The <B>-host</B> flag displays the name of the machine where the
-<B>scout</B> program is running. As mentioned previously, this is
-useful when running the <B>scout</B> program on several machines but
-displaying the results on a single machine.
-<P>For example, when the <B>-host</B> flag is included and the
-<B>scout</B> program is running on the machine
-<B>client1.abc.com</B>, the banner line reads as
-follows:
-<PRE> [client1.abc.com] Scout
-
-</PRE>
-<P><LI>The <B>-basename</B> argument displays the indicated basename on the
-banner line. For example, including the argument <B>-basename
-abc.com</B> argument results in the following banner line:
-<PRE> Scout for abc.com
-
-</PRE>
-</UL>
-<P><B><I>The Statistics Display Region</I></B>
-<P>In this region, which occupies the majority of the window, the
-<B>scout</B> process displays the statistics gathered for each File Server
-process. Each process appears on its own line.
-<P>The region is divided into six columns, labeled as indicated and displaying
-the following information:
-<A NAME="IDX5457"></A>
-<A NAME="IDX5458"></A>
-<UL>
-<P><LI><TT>Conn</TT>: The first column displays the number of RPC
-connections open between the File Server process and client machines.
-This number equals or exceeds the number in the <TT>Ws</TT> column (see the
-fourth entry below), because each user on the machine can have several
-separate connections open at once, and one client machine can handle several
-users.
-<A NAME="IDX5459"></A>
-<P><LI><TT>Fetch</TT>: The second column displays the number of
-fetch-type RPCs (fetch data, fetch access list, and fetch status) that client
-machines have made to the File Server process since the latter started.
-This number is reset to zero each time the File Server process
-restarts.
-<A NAME="IDX5460"></A>
-<P><LI><TT>Store</TT>: The third column displays the number of store-type
-RPCs (store data, store access list, and store status) that client machines
-have made to the File Server process since the latter started. This
-number is reset to zero each time the File Server process restarts.
-<A NAME="IDX5461"></A>
-<P><LI><TT>Ws</TT>: The fourth column displays the number of client
-machines (<TT>Ws</TT> stands for workstations) that have communicated with
-the File Server process within the last 15 minutes. Such machines are
-termed <I>active</I>). This number is likely to be smaller than the
-number in the first (<TT>Conn</TT>) column because a single client machine
-can have several connections open to one File Server.
-<A NAME="IDX5462"></A>
-<A NAME="IDX5463"></A>
-<A NAME="IDX5464"></A>
-<P><LI>The fifth, unlabeled, column displays the name of the file server machine
-on which the File Server process is running. Names of 12 characters or
-less are displayed in full; longer names are truncated and an asterisk
-(<TT>*</TT>) appears as the last character in the name. Using the
-<B>-basename</B> argument is a good way to avoid truncation, but only if
-all machine names end in a common string.
-<P><LI><TT>Disk attn</TT>: The sixth column displays the number of
-available kilobyte blocks on each AFS disk partition on the file server
-machine.
-<A NAME="IDX5465"></A>
-<A NAME="IDX5466"></A>
-<A NAME="IDX5467"></A>
- The display for each partition has the following form:
-<PRE> x:<VAR>free_blocks</VAR>
-
-</PRE>
-<P>where <TT>x</TT> indicates the partition name. For example,
-<TT><B>a:8949</B></TT> specifies that the <B>/vicepa</B>
-partition has 8,949 1-KB blocks free. Available space can be displayed
-for up to 26 partitions. If the window is not wide enough for all
-partition entries to appear on a single line, the <B>scout</B> process
-automatically creates multiple lines, stacking the partition entries into
-sub-columns within the sixth column.
-<P>The label on the <TT>Disk</TT> <TT>attn</TT> column indicates the
-threshold value at which entries in the column become highlighted. By
-default, the label is
-<PRE> Disk attn: > 95% used
-
-</PRE>
-<P>because by default the <B>scout</B> program highlights the entry for
-any partition that is over 95% full.
-</UL>
-<P>For all columns except the fifth (file server machine name), the optional
-<B>-attention</B> argument sets the value at which entries in the column
-are highlighted to indicate that a certain value has been exceeded.
-Only values in the fifth and <TT>Disk attn</TT> columns ever become
-highlighted by default.
-<P>If the <B>scout</B> program is unable to access or otherwise obtain
-information about a partition, it generates a message similar to the following
-example:
-<PRE> Could not get information on server fs1.abc.com partition /vicepa
-
-</PRE>
-<P><B><I>The Message/Probe Line</I></B>
-<P>The bottom line of the <B>scout</B> screen indicates how many times the
-<B>scout</B> program has probed the File Server processes for
-statistics. The statistics gathered in the latest probe appear in the
-statistics display region. The <B>-frequency</B> argument overrides
-the default probe frequency of 60 seconds.
-<P><STRONG>Examples</STRONG>
-<P>See the chapter on monitoring tools in the <I>IBM AFS Administration
-Guide</I>, which illustrates the displays that result from different
-combinations of options.
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf059.htm#HDRAFSMONITOR">afsmonitor</A>
-<P><A HREF="auarf169.htm#HDRFSTRACE_INTRO">fstrace</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf232.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf234.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf233.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf235.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRSYS" HREF="auarf002.htm#ToC_248">fs sysname</A></H2>
-<P><STRONG>Purpose</STRONG>
-<A NAME="IDX5468"></A>
-<A NAME="IDX5469"></A>
-<A NAME="IDX5470"></A>
-<A NAME="IDX5471"></A>
-<A NAME="IDX5472"></A>
-<A NAME="IDX5473"></A>
-<A NAME="IDX5474"></A>
-<P>Reports the CPU/operating system type
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>sys</B>
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>fs sysname</B> command displays the string stored in kernel memory that
-indicates the local machine's CPU/operating system (OS) type. The
-Cache Manager substitutes the string for the <VAR>@sys</VAR> variable which can
-occur in AFS pathnames; the <I>IBM AFS Quick Beginnings</I> and
-<I>IBM AFS Administration Guide</I> explain how using <VAR>@sys</VAR> can
-simplify cell configuration.
-<P>The command always reports the value for the local machine only. To
-set a new value in kernel memory, use the <B>fs sysname</B> command, which
-like this command can also be used to display the current value.
-<P><STRONG>Output</STRONG>
-<P>The machine's system type appears as a text string:
-<PRE> <VAR>system_type</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output produced on a Sun SPARCStation
-running Solaris 5.7:
-<PRE> % <B>fs sysname</B>
- sun4x_57
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf165.htm#HDRFS_SYSNAME">fs sysname</A>
-<P><I>IBM AFS Quick Beginnings</I>
-<P><I>IBM AFS Administration Guide</I>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf233.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf235.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf234.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf236.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRTOKENS" HREF="auarf002.htm#ToC_249">tokens</A></H2>
-<A NAME="IDX5475"></A>
-<A NAME="IDX5476"></A>
-<A NAME="IDX5477"></A>
-<A NAME="IDX5478"></A>
-<A NAME="IDX5479"></A>
-<A NAME="IDX5480"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the issuer's tokens
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>tokens</B> [<B>-help</B>]
-
-<B>tokens</B> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>tokens</B> command displays all tokens (tickets) cached on the
-local machine for the issuer. AFS server processes require that their
-clients present a token as evidence that they have authenticated in the
-server's local cell.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">The <B>tokens.krb</B> version of this command is intended for use
-by sites that employ standard Kerberos authentication for their
-clients. The <B>tokens.krb</B> command provides all of the
-functionality of the <B>tokens</B> command. In addition, it
-provides information on the Kerberos tickets stored in the file specified by
-the KRBTKFILE environment variable (the <B>/tmp/tkt</B><VAR>X</VAR> file,
-where <VAR>X</VAR> is the number of the user's PAG).
-</TD></TR></TABLE>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output lists one token for each cell in which the user is
-authenticated. The output indicates the
-<UL>
-<P><LI>User's AFS UID, if it is available for display.
-<P><LI>Server for which the token is valid (normally, <B>afs</B>).
-This includes a cell specification.
-<P><LI>Day and time the token expires.
-</UL>
-<P>The output of the Kerberos version of this command,
-<B>tokens.krb</B>, also reports the following about the Kerberos
-ticket-granting ticket: the ticket owner, which Kerberos ticket-granting
-service that issued the ticket (for example,
-<B>krbtgt.ABC.COM</B>), and ticket's expiration
-date.
-<P>The string <TT>--End of list--</TT> appears at the end of the
-output. If the user is not authenticated in any cell, this line is all
-that appears.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output when the issuer is not authenticated
-in any cell.
-<PRE> % <B>tokens</B>
- Tokens held by the Cache Manager:
-
- --End of list--
-
-</PRE>
-<P>The following example shows the output when the issuer is authenticated in
-ABC Corporation cell, where he or she has AFS UID 1000.
-<PRE> % <B>tokens</B>
- Tokens held by the Cache Manager:
-
- User's (AFS ID 1000) tokens for afs@abc.com [Expires Jan 2 10:00]
- --End of list--
-
-</PRE>
-<P>The following example shows the output when the issuer is authenticated in
-the ABC Corporation cell, the State University cell, and the XYZ Company
-cell. The user has different AFS UIDs in the three cells. Tokens
-for last cell are expired:
-<PRE> % <B>tokens</B>
- Tokens held by the Cache Manager:
-
- User's (AFS ID 1000) tokens for afs@abc.com [Expires Jan 3 10:00]
- User's (AFS ID 4286) tokens for afs@stateu.edu [Expires Jan 3 1:34]
- User's (AFS ID 22) tokens for afs@xyz.com [>>Expired<]
- --End of list--
-
-</PRE>
-<P>The following example shows the output when the issuer uses the
-<B>tokens.krb</B> version of the command after authenticating in
-the ABC Corporation cell using the <B>klog.krb</B> command.
-<PRE> % <B>tokens.krb</B>
- Tokens held by the Cache Manager:
-
- User's (AFS ID 1000) tokens for afs@abc.com [Expires Jan 31 00:09]
- User smiths tokens for krbtgt.ABC.COM@abc.com [Expires Jan 31 00:09]
- --End of list--
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf238.htm#HDRUNLOG">unlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf234.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf236.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf235.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf237.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRTRANSLATE_ET" HREF="auarf002.htm#ToC_250">translate_et</A></H2>
-<A NAME="IDX5481"></A>
-<A NAME="IDX5482"></A>
-<A NAME="IDX5483"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Translates numbered error codes into text messages
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>translate_et</B> <<VAR>error number</VAR>><SUP>+</SUP>
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>translate_et</B> command translates each specified error number
-into a text message.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><VAR>error number</VAR>
-</B><DD>Specifies each error number to translate.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command translates the error numbers 1 and 4:
-<PRE> % <B>translate_et 1 4</B>
- 1 ().1 = Not owner
- 4 ().4 = Interrupted system call
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf235.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf237.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf236.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf238.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUDEBUG" HREF="auarf002.htm#ToC_251">udebug</A></H2>
-<A NAME="IDX5484"></A>
-<A NAME="IDX5485"></A>
-<A NAME="IDX5486"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports status of Ubik process associated with a database server process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>udebug -servers</B> <<VAR>server machine</VAR>> [<B>-port</B> <<VAR>IP port</VAR>>] [<B>-long</B>] [<B>-help</B>]
-
-<B>udebug -s</B> <<VAR>server machine</VAR>> [<B>-p</B> <<VAR>IP port</VAR>>] [<B>-l</B>] [<B>-h</B>]
-
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>udebug</B> command displays the status of the lightweight Ubik
-process for the database server process identified by the <B>-port</B>
-argument that is running on the database server machine named by the
-<B>-servers</B> argument. The output identifies the machines where
-peer database server processes are running, which of them is the
-synchronization site (Ubik coordinator), and the status of the connections
-between them.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-servers
-</B><DD>Names the database server machine that is running the process for which to
-display status information. Provide the machine's IP address in
-dotted decimal format, its fully qualified host name (for example,
-<B>fs1.abc.com</B>), or the shortest abbreviated form of its
-host name that distinguishes it from other machines. Successful use of
-an abbreviated form depends on the availability of a name resolution service
-(such as the Domain Name Service or a local host table) at the time the
-command is issued.
-<P><DT><B>-port
-</B><DD>Identifies the database server process for which to display status
-information, either by its process name or port number. Provide one of
-the following values.
-<DL>
-<DD><P><B>buserver</B> or <B>7021</B> for the Backup Server
-<DD><P><B>kaserver</B> or <B>7004</B> for the Authentication Server
-<DD><P><B>ptserver</B> or <B>7002</B> for the Protection Server
-<DD><P><B>vlserver</B> or <B>7003</B> for the Volume Location Server
-</DL>
-<P><DT><B>-long
-</B><DD>Reports additional information about each peer of the machine named by the
-<B>-servers</B> argument. The information appears by default if
-that machine is the synchronization site.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>Several of the messages in the output provide basic status information
-about the Ubik process on the machine specified by the <B>-servers</B>
-argument, and the remaining messages are useful mostly for debugging
-purposes.
-<P>To check basic Ubik status, issue the command for each database server
-machine in turn. In the output for each, one of the following messages
-appears in the top third of the output.
-<PRE> I am sync site . . . (<VAR>#_sites</VAR> servers)
-
- I am not sync site
-</PRE>
-<P>For the synchronization site, the following message indicates that all
-sites have the same version of the database, which implies that Ubik is
-functioning correctly. See the following for a description of values
-other than <TT>1f</TT>.
-<PRE> Recovery state 1f
-</PRE>
-<P>For correct Ubik operation, the database server machine clocks must agree
-on the time. The following messages, which are the second and third
-lines in the output, report the current date and time according to the
-database server machine's clock and the clock on the machine where the
-<B>udebug</B> command is issued.
-<PRE> Host's <VAR>IP_addr</VAR> time is <VAR>dbserver_date/time</VAR>
- Local time is <VAR>local_date/time</VAR> (time differential <VAR>skew</VAR> secs)
-</PRE>
-<P>The <VAR>skew</VAR> is the difference between the database server machine
-clock and the local clock. Its absolute value is not vital for Ubik
-functioning, but a difference of more than a few seconds between the
-<VAR>skew</VAR> values for the database server machines indicates that their
-clocks are not synchronized and Ubik performance is possibly hampered.
-<P>Following is a description of all messages in the output. As noted,
-it is useful mostly for debugging and most meaningful to someone who
-understands Ubik's implementation.
-<P>The output begins with the following messages. The first message
-reports the IP addresses that are configured with the operating system on the
-machine specified by the <B>-servers</B> argument. As previously
-noted, the second and third messages report the current date and time
-according to the clocks on the database server machine and the machine where
-the <B>udebug</B> command is issued, respectively. All subsequent
-timestamps in the output are expressed in terms of the local clock rather than
-the database server machine clock.
-<PRE> Host's addresses are: <VAR>list_of_IP_addrs</VAR>
- Host's <VAR>IP_addr</VAR> time is <VAR>dbserver_date/time</VAR>
- Local time is <VAR>local_date/time</VAR> (time differential <VAR>skew</VAR> secs)
-</PRE>
-<P>If the <VAR>skew</VAR> is more than about 10 seconds, the following message
-appears. As noted, it does not necessarily indicate Ubik
-malfunction: it denotes clock skew between the database server machine
-and the local machine, rather than among the database server machines.
-<PRE> ****clock may be bad
-</PRE>
-<P>If the <B>udebug</B> command is issued during the coordinator election
-process and voting has not yet begun, the following message appears
-next.
-<PRE> Last yes vote not cast yet
-</PRE>
-<P>Otherwise, the output continues with the following messages.
-<PRE> Last yes vote for <VAR>sync_IP_addr</VAR> was <VAR>last_vote</VAR> secs ago (sync site);
- Last vote started <VAR>vote_start</VAR> secs ago (at <VAR>date/time</VAR>)
- Local db version is <VAR>db_version</VAR>
-</PRE>
-<P>The first indicates which peer this Ubik process last voted for as
-coordinator (it can vote for itself) and how long ago it sent the vote.
-The second message indicates how long ago the Ubik coordinator requested
-confirming votes from the secondary sites. Usually, the
-<VAR>last_vote</VAR> and <VAR>vote_start</VAR> values are the same; a
-difference between them can indicate clock skew or a slow network connection
-between the two database server machines. A small difference is not
-harmful. The third message reports the current version number
-<VAR>db_version</VAR> of the database maintained by this Ubik process. It
-has two fields separated by a period. The field before the period is
-based on a timestamp that reflects when the database first changed after the
-most recent coordinator election, and the field after the period indicates the
-number of changes since the election.
-<P>The output continues with messages that differ depending on whether the
-Ubik process is the coordinator or not.
-<UL>
-<P><LI>If there is only one database server machine, it is always the coordinator
-(synchronization site), as indicated by the following message.
-<PRE> I am sync site forever (1 server)
-</PRE>
-<P><LI>If there are multiple database sites, and the <B>-servers</B> argument
-names the coordinator (synchronization site), the output continues with the
-following two messages.
-<PRE> I am sync site until <VAR>expiration</VAR> secs from now (at <VAR>date/time</VAR>) (<VAR>#_sites</VAR> servers)
- Recovery state <VAR>flags</VAR>
-</PRE>
-<P>The first message reports how much longer the site remains coordinator even
-if the next attempt to maintain quorum fails, and how many sites are
-participating in the quorum. The <VAR>flags</VAR> field in the second
-message is a hexadecimal number that indicates the current state of the
-quorum. A value of <TT>1f</TT> indicates complete database
-synchronization, whereas a value of <TT>f</TT> means that the coordinator
-has the correct database but cannot contact all secondary sites to determine
-if they also have it. Lesser values are acceptable if the
-<B>udebug</B> command is issued during coordinator election, but they
-denote a problem if they persist. The individual flags have the
-following meanings:
-<DL>
-<P><DT><B><TT>0x1</TT>
-</B><DD>This machine is the coordinator
-<P><DT><B><TT>0x2</TT>
-</B><DD>The coordinator has determined which site has the database with the
-highest version number
-<P><DT><B><TT>0x4</TT>
-</B><DD>The coordinator has a copy of the database with the highest version number
-<P><DT><B><TT>0x8</TT>
-</B><DD>The database's version number has been updated correctly
-<P><DT><B><TT>0x10</TT>
-</B><DD>All sites have the database with the highest version number
-</DL>
-<P>If the <B>udebug</B> command is issued while the coordinator is writing
-a change into the database, the following additional message appears.
-<PRE> I am currently managing write transaction <VAR>identifier</VAR>
-</PRE>
-<P><LI>If the <B>-servers</B> argument names a secondary site, the output
-continues with the following messages.
-<PRE> I am not sync site
- Lowest host <VAR>lowest_IP_addr</VAR> was set <VAR>low_time</VAR> secs ago
- Sync host <VAR>sync_IP_addr</VAR> was set <VAR>sync_time</VAR> secs ago
-</PRE>
-<P>The <VAR>lowest_IP_addr</VAR> is the lowest IP address of any peer from which
-the Ubik process has received a message recently, whereas the
-<VAR>sync_IP_addr</VAR> is the IP address of the current coordinator. If
-they differ, the machine with the lowest IP address is not currently the
-coordinator. The Ubik process continues voting for the current
-coordinator as long as they remain in contact, which provides for maximum
-stability. However, in the event of another coordinator election, this
-Ubik process votes for the <VAR>lowest_IP_addr</VAR> site instead (assuming they
-are in contact), because it has a bias to vote in elections for the site with
-the lowest IP address.
-</UL>
-<P>For both the synchronization and secondary sites, the output continues with
-the following messages. The first message reports the version number of
-the database at the synchronization site, which needs to match the
-<VAR>db_version</VAR> reported by the preceding <TT>Local db version</TT>
-message. The second message indicates how many VLDB records are
-currently locked for any operation or for writing in particular. The
-values are nonzero if the <B>udebug</B> command is issued while an
-operation is in progress.
-<PRE> Sync site's db version is <VAR>db_version</VAR>
- <VAR>locked</VAR> locked pages, <VAR>writes</VAR> of them for write
-</PRE>
-<P>The following messages appear next only if there are any read or write
-locks on database records:
-<PRE> There are read locks held
- There are write locks held
-</PRE>
-<P>Similarly, one or more of the following messages appear next only if there
-are any read or write transactions in progress when the <B>udebug</B>
-command is issued:
-<PRE> There is an active write transaction
- There is at least one active read transaction
- Transaction tid is <VAR>tid</VAR>
-</PRE>
-<P>If the machine named by the <B>-servers</B> argument is the
-coordinator, the next message reports when the current coordinator last
-updated the database.
-<PRE> Last time a new db version was labelled was:
- <VAR>last_restart</VAR> secs ago (at <VAR>date/time</VAR>)
-</PRE>
-<P>If the machine named by the <B>-servers</B> argument is the
-coordinator, the output concludes with an entry for each secondary site that
-is participating in the quorum, in the following format.
-<PRE> Server( <VAR>IP_address</VAR> ): (db <VAR>db_version</VAR>)
- last vote rcvd <VAR>last_vote</VAR> secs ago (at <VAR>date/time</VAR>),
- last beacon sent <VAR>last_beacon</VAR> secs ago (at <VAR>date/time</VAR>), last vote was { yes | no }
- dbcurrent={ 0 | 1 }, up={ 0 | 1 } beaconSince={ 0 | 1 }
-</PRE>
-<P>The first line reports the site's IP address and the version number of
-the database it is maintaining. The <VAR>last_vote</VAR> field reports
-how long ago the coordinator received a vote message from the Ubik process at
-the site, and the <VAR>last_beacon</VAR> field how long ago the coordinator last
-requested a vote message. If the <B>udebug</B> command is issued
-during the coordinator election process and voting has not yet begun, the
-following messages appear instead.
-<PRE> Last vote never rcvd
- Last beacon never sent
-</PRE>
-<P>On the final line of each entry, the fields have the following
-meaning:
-<UL>
-<P><LI><TT>dbcurrent</TT> is <TT>1</TT> if the site has the database with the
-highest version number, <TT>0</TT> if it does not
-<P><LI><TT>up</TT> is <TT>1</TT> if the Ubik process at the site is
-functioning correctly, <TT>0</TT> if it is not
-<P><LI><TT>beaconSince</TT> is <TT>1</TT> if the site has responded to the
-coordinator's last request for votes, <TT>0</TT> if it has not
-</UL>
-<P>Including the <B>-long</B> flag produces peer entries even when the
-<B>-servers</B> argument names a secondary site, but in that case only the
-<VAR>IP_address</VAR> field is guaranteed to be accurate. For example,
-the value in the <VAR>db_version</VAR> field is usually <TT>0.0</TT>,
-because secondary sites do not poll their peers for this information.
-The values in the <VAR>last_vote</VAR> and <VAR>last_beacon</VAR> fields indicate
-when this site last received or requested a vote as coordinator; they
-generally indicate the time of the last coordinator election.
-<P><STRONG>Examples</STRONG>
-<P>This example checks the status of the Ubik process for the Volume Location
-Server on the machine <B>afs1</B>, which is the synchronization
-site.
-<PRE> % <B>udebug afs1 vlserver</B>
- Host's addresses are: 192.12.107.33
- Host's 192.12.107.33 time is Wed Oct 27 09:49:50 1999
- Local time is Wed Oct 27 09:49:52 1999 (time differential 2 secs)
- Last yes vote for 192.12.107.33 was 1 secs ago (sync site);
- Last vote started 1 secs ago (at Wed Oct 27 09:49:51 1999)
- Local db version is 940902602.674
- I am sync site until 58 secs from now (at Wed Oct 27 09:50:50 1999) (3 servers)
- Recovery state 1f
- Sync site's db version is 940902602.674
- 0 locked pages, 0 of them for write
- Last time a new db version was labelled was:
- 129588 secs ago (at Mon Oct 25 21:50:04 1999)
-
- Server( 192.12.107.35 ): (db 940902602.674)
- last vote rcvd 2 secs ago (at Wed Oct 27 09:49:50 1999),
- last beacon sent 1 secs ago (at Wed Oct 27 09:49:51 1999), last vote was yes
- dbcurrent=1, up=1 beaconSince=1
-
- Server( 192.12.107.34 ): (db 940902602.674)
- last vote rcvd 2 secs ago (at Wed Oct 27 09:49:50 1999),
- last beacon sent 1 secs ago (at Wed Oct 27 09:49:51 1999), last vote was yes
- dbcurrent=1, up=1 beaconSince=1
-</PRE>
-<P>This example checks the status of the Authentication Server on the machine
-with IP address 192.12.107.34, which is a secondary
-site. The local clock is about 4 minutes behind the database server
-machine's clock.
-<PRE> % <B>udebug 192.12.107.34 7004</B>
- Host's addresses are: 192.12.107.34
- Host's 192.12.107.34 time is Wed Oct 27 09:54:15 1999
- Local time is Wed Oct 27 09:50:08 1999 (time differential -247 secs)
- ****clock may be bad
- Last yes vote for 192.12.107.33 was 6 secs ago (sync site);
- Last vote started 6 secs ago (at Wed Oct 27 09:50:02 1999)
- Local db version is 940906574.25
- I am not sync site
- Lowest host 192.12.107.33 was set 6 secs ago
- Sync host 192.12.107.33 was set 6 secs ago
- Sync site's db version is 940906574.25
- 0 locked pages, 0 of them for write
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf125.htm#HDRBUSERVER">buserver</A>
-<P><A HREF="auarf198.htm#HDRKASERVER">kaserver</A>
-<P><A HREF="auarf227.htm#HDRPTSERVER">ptserver</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf236.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf238.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf237.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf239.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUNLOG" HREF="auarf002.htm#ToC_252">unlog</A></H2>
-<A NAME="IDX5487"></A>
-<A NAME="IDX5488"></A>
-<A NAME="IDX5489"></A>
-<A NAME="IDX5490"></A>
-<A NAME="IDX5491"></A>
-<A NAME="IDX5492"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Discards all of the issuer's tokens
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>unlog</B> [<B>-cell</B> <<VAR>cell name</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>unlog</B> [<B>-c </B><<VAR>cell name</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>unlog</B> command by default discards all tokens that the issuer
-currently holds. To discard tokens for certain cells only, name them
-with the <B>-cell</B> argument.
-<P>Since a token pertains to one client machine only, destroying tokens on one
-machine has no effect on tokens on another machine.
-<P><STRONG>Cautions</STRONG>
-<P>Specifying one or more cell names can cause a brief authentication outage
-during which the issuer has no valid tokens in any cell. This is
-because the command actually discards all tokens and then restores the ones
-for cells not named by the <B>-cell</B> argument. The outage can
-sometimes interrupt the operation of jobs that require authentication.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Specifies each cell for to discard the token. If this argument is
-omitted, the Cache Manager discards all tokens. Provide the fully
-qualified domain name, or a shortened form, in which case successful
-resolution depends on the availability of a name resolution service (such as
-the Domain Name Service or a local host table) at the time the command is
-issued.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command discards all tokens.
-<PRE> % <B>unlog</B>
-
-</PRE>
-<P>The following command discards only the tokens for the
-<B>abc.com</B> and <B>stateu.edu</B> cells.
-<PRE> % <B>unlog -cell abc.com stateu</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf200.htm#HDRKLOG">klog</A>
-<P><A HREF="auarf235.htm#HDRTOKENS">tokens</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf237.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf239.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf238.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf240.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUP" HREF="auarf002.htm#ToC_253">up</A></H2>
-<A NAME="IDX5493"></A>
-<A NAME="IDX5494"></A>
-<A NAME="IDX5495"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Recursively copies the contents of a source directory to a destination
-directory.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>up</B> [<B>-v</B>] [<B>-1</B>] [<B>-f</B>] [<B>-r</B>] [<B>-x</B>] <<VAR>source directory</VAR>> <<VAR>destination directory</VAR>>
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>up</B> command recursively copies the files and subdirectories
-in a specified source directory to a specified destination directory.
-The command interpreter changes the destination directory and the files and
-subdirectories in it in the following ways:
-<UL>
-<P><LI>It copies the source directory's access control list (ACL) to the
-destination directory and its subdirectories, overwriting any existing
-ACLs.
-<P><LI>If the issuer is logged on as the local superuser <B>root</B> and has
-AFS tokens as a member of the group <B>system:administrators</B>,
-then the source directory's owner (as reported by the <B>ls -ld</B>
-command) becomes the owner of the destination directory and all files and
-subdirectories in it. Otherwise, the issuer's user name is
-recorded as the owner.
-<P><LI>If a file or directory exists in both the source and destination
-directories, the source version overwrites the destination version. The
-overwrite operation fails if the first (user) <B>w</B> (<B>write</B>)
-mode bit is turned off on the version in the destination directory, unless the
-<B>-f</B> flag is provided.
-<P><LI>The modification timestamp on a file (as displayed by the <B>ls -l</B>
-command) in the source directory overwrites the timestamp on a file of the
-same name in the destination directory, but the timestamp on an existing
-subdirectory in the destination directory remains unchanged. If the
-command creates a new subdirectory in the destination directory, the new
-subdirectory's timestamp is set to the time of the copy operation, rather
-than to the timestamp that the subdirectory has in the source
-directory.
-</UL>
-<P>The <B>up</B> command is idempotent, meaning that if its execution is
-interrupted by a network, server machine, or process outage, then a subsequent
-reissue of the same command continues from the interruption point, rather than
-starting over at the beginning. This saves time and reduces network
-traffic in comparison to the UNIX commands that provide similar
-functionality.
-<P>The <B>up</B> command returns a status code of <B>0</B> (zero) only
-if it succeeds. Otherwise, it returns a status code of <B>1</B>
-(one).
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-v
-</B><DD>Prints a detailed trace to the standard output stream as the command
-runs.
-<P><DT><B>-1
-</B><DD>Copies only the files in the top level source directory to the destination
-directory, rather than copying recursively through subdirectories. The
-source directory's ACL still overwrites the destination
-directory's. (This is the number one, not the letter
-<B>l</B>.)
-<P><DT><B>-f
-</B><DD>Overwrites existing directories, subdirectories, and files even if the
-first (user) <B>w</B> (<B>write</B>) mode bit is turned off on the
-version in the destination directory.
-<P><DT><B>-r
-</B><DD>Creates a backup copy of all files overwritten in the destination
-directory and its subdirectories, by adding a <B>.old</B> extension
-to each filename.
-<P><DT><B>-x
-</B><DD>Sets the modification timestamp on each file to the time of the copying
-operation.
-<P><DT><B><VAR>source directory</VAR>
-</B><DD>Names the directory to copy recursively.
-<P><DT><B><VAR>destination directory</VAR>
-</B><DD>Names the directory to which to copy. It does not have to exist
-already.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command copies the contents of the directory <VAR>dir1</VAR> to
-directory <VAR>dir2</VAR>:
-<PRE> % <B>up dir1 dir2</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must have the <B>a</B> (<B>administer</B>) permission on
-the ACL of both the source and destination directories.
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf238.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf240.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf239.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf241.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUPCLIENT" HREF="auarf002.htm#ToC_254">upclient</A></H2>
-<A NAME="IDX5496"></A>
-<A NAME="IDX5497"></A>
-<A NAME="IDX5498"></A>
-<A NAME="IDX5499"></A>
-<A NAME="IDX5500"></A>
-<A NAME="IDX5501"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the client portion of the Update Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>upclient</B> <<VAR>hostname</VAR>> [<B>-crypt</B>] [<B>-clear</B>] [<B>-t </B><<VAR>retry time</VAR>>]
- [<B>-verbose</B>]<SUP>*</SUP> <<VAR>dir</VAR>><SUP>+</SUP> [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>upclient</B> command initializes the client portion of the
-Update Server. In the conventional configuration, its binary file is
-located in the <B>/usr/afs/bin</B> directory on a file server
-machine.
-<P>The <B>upclient</B> command is not normally issued at the command shell
-prompt but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a database server machine as the local superuser
-<B>root</B>.
-<P>The <B>upclient</B> process periodically checks that all files in each
-local directory named by the <VAR>dir</VAR> argument match the files in the
-corresponding directory on the source machine named by the
-<VAR>hostname</VAR>argument. If a file does not match, the
-<B>upclient</B> process requests the source copy from the
-<B>upserver</B> process running on the source machine.
-<P>By default, the <B>upclient</B> process in the United States edition of
-AFS requests that the <B>upserver</B> process encrypt the data before
-transferring it, whereas in the international edition it requests unencrypted
-transfer. If using the United States edition, use the <B>-clear</B>
-flag to request unencrypted transfer if appropriate. (The
-<B>-crypt</B> flag explicitly sets the default in the United States
-edition, and is not available in the international edition.)
-<P>In the conventional configuration, separate instances of the
-<B>upclient</B> process request data from the <B>/usr/afs/bin</B> and
-<B>/usr/afs/etc</B> directories, except on machines for which the system
-control machine is also the binary distribution machine for the machine's
-system type. The conventional names for the separate instances are
-<B>upclientbin</B> and <B>upclientetc</B> respectively.
-<P>The <B>upclient</B> and <B>upserver</B> processes always mutually
-authenticate, whether or not the data they pass is encrypted; they use
-the key with the highest key version number in the
-<B>/usr/afs/etc/KeyFile</B> file to construct a server ticket for mutual
-authentication.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use the Update Server to distribute the contents of the
-<B>/usr/afs/etc</B> directory if using the international edition of
-AFS. The contents of this directory are sensitive and the international
-edition of AFS does not include the encryption routines necessary for
-encrypting files before transfer across the network.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><VAR>hostname</VAR>
-</B><DD>Names either the cell's system control machine (if the requested
-directory is <B>/usr/afs/etc</B>), or the binary distribution machine for
-the local machine's CPU and operating system type (if the requested
-directory is <B>/usr/afs/bin</B>).
-<P><DT><B>-crypt
-</B><DD>Requests the transfer of data from the <B>upserver</B> process in
-encrypted form. With the United States edition of AFS, use this flag to
-set the default explicitly. Provide this flag or the <B>-crypt</B>
-flag, but not both.
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">This flag is not available in the international edition of AFS.
-</TD></TR></TABLE>
-<P><DT><B>-clear
-</B><DD>Requests transfer of data from the <B>upserver</B> process in
-unencrypted form. Use this flag to change from the default for the
-United States edition of AFS. Provide this flag or the
-<B>-crypt</B> flag, but not both.
-<P><DT><B>-t
-</B><DD>Specifies how often to check for changes in each specified directory, as a
-number of seconds. If this argument is omitted, the default is 300 (5
-minutes). This argument determines the maximum amount of time it takes
-for a change made on the source machine to propagate to this machine.
-<P><DT><B>-verbose
-</B><DD>Writes a trace of the <B>upclient</B> process's operations on the
-standard output stream, which usually corresponds to the machine
-console. Provide one, two, or three instances of the flag; each
-additional instance generates increasingly numerous and detailed
-messages.
-<P><DT><B><VAR>dir</VAR>
-</B><DD>Names each directory to check for modified files. The conventional
-choices are the following:
-<UL>
-<P><LI><B>/usr/afs/bin</B>, in which case the recommended name for the
-process (assigned with the <B>-instance</B> argument to the <B>bos
-create</B> command) is <B>upclientbin</B>. The <VAR>hostname</VAR>
-is the binary distribution machine for the local machine's system
-type. Use the <B>-clear</B> flag be used for the
-<B>/usr/afs/bin</B> directory, since binaries are not particularly
-sensitive and encrypting them can take a long time.
-<P><LI><B>/usr/afs/etc</B>, in which case the recommended name for the
-process (assigned with the <B>-instance</B> argument to the <B>bos
-create</B> command) is <B>upclientetc</B>. The <VAR>hostname</VAR>
-is the cell's system control machine. Use the <B>-crypt</B>
-flag for the <B>/usr/afs/etc</B> directory, since it contains the
-<B>KeyFile</B> file and other data vital to cell security.
-<P>As a reminder, do not use the Update Server to transfer the contents of the
-<B>/usr/afs/etc</B> directory if using the international edition of
-AFS.
-</UL>
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates an
-<B>upclientbin</B> process on the machine
-<B>fs4.abc.com</B> that refers to the machine
-<B>fs1.abc.com</B> as the source for the
-<B>/usr/afs/bin</B> directory (thus <B>fs1.abc.com</B>
-is the binary distribution machine for machines of
-<B>fs4.abc.com</B>'s type). The files in the
-<B>/usr/afs/bin</B> directory are distributed every 120 seconds.
-The command requests transfer in unencrypted form.
-<PRE> % <B>bos create -server fs4.abc.com -instance upclientbin -type simple</B> \
- <B>-cmd "/usr/afs/bin/upclient fs1.abc.com -clear</B> \
- <B>-t 120 /usr/afs/bin"</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf241.htm#HDRUPSERVER">upserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf239.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf241.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf240.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf242.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUPSERVER" HREF="auarf002.htm#ToC_255">upserver</A></H2>
-<A NAME="IDX5502"></A>
-<A NAME="IDX5503"></A>
-<A NAME="IDX5504"></A>
-<A NAME="IDX5505"></A>
-<A NAME="IDX5506"></A>
-<A NAME="IDX5507"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the server portion of the Update Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>upserver</B> [<<VAR>directory</VAR>><SUP>+</SUP>] [<B>-crypt</B> <<VAR>directory</VAR>><SUP>+</SUP>] [<B>-clear</B> <<VAR>directory</VAR>><SUP>+</SUP>]
- [<B>-auth</B> <<VAR>directory</VAR>><SUP>+</SUP>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>upserver</B> command initializes the server portion of the
-Update Server (the <B>upserver</B> process). In the conventional
-configuration, its binary file is located in the <B>/usr/afs/bin</B>
-directory on a file server machine.
-<P>The <B>upserver</B> command is not normally issued at the command shell
-prompt but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a database server machine as the local superuser
-<B>root</B>.
-<P>The <B>upserver</B> command specifies which of the directories on the
-local disk are eligible for distribution in response to requests from the
-client portion of the Update Server (the <B>upclient</B> process) running
-on other machines. If no directories are specified, the
-<B>upserver</B> process distributes the contents of any directory on its
-local disk.
-<P>The <B>upserver</B> process can distribute a directory's contents
-in encrypted or unencrypted form. By default, it does not use
-encryption unless an <B>upclient</B> process requests it (this default is
-equivalent to setting the <B>-clear</B> flag). When the
-<B>-crypt</B> flag is provided, the <B>upserver</B> process only
-fulfills requests for encrypted transfer.
-<P>For the United States edition of AFS, using the <B>-crypt</B> flag
-guarantees that the <B>upserver</B> process transfers a directory's
-contents only in encrypted form. For the international edition, using
-the <B>-crypt</B> flag completely blocks data transfer, because the
-international edition of the <B>upclient</B> process cannot request
-encrypted transfer (the <B>upclient</B> initialization command does not
-include the <B>-crypt</B> flag).
-<P>The <B>upclient</B> and <B>upserver</B> processes always mutually
-authenticate, whether or not the data they pass is encrypted; they use
-the key with the highest key version number in the
-<B>/usr/afs/etc/KeyFile</B> file to construct a server ticket for mutual
-authentication.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use the Update Server to distribute the contents of the
-<B>/usr/afs/etc</B> directory if using the international edition of
-AFS. The contents of this directory are sensitive and the international
-edition of AFS does not include the encryption routines necessary for
-encrypting files before transfer across the network.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><VAR>directory</VAR>
-</B><DD>Names each directory to distribute in unencrypted form (because they
-appear before the first <B>-crypt</B> or <B>-clear</B> flag on the
-command line). If this argument is omitted, all directories on the
-machine's local disk are eligible for distribution.
-<P><DT><B>-crypt
-</B><DD>Precedes a list of one or more directories that the <B>upserver</B>
-process distributes only in encrypted form.
-<P><DT><B>-clear
-</B><DD>Precedes a list of one or more directories that the <B>upserver</B>
-process distributes in unencrypted form unless the <B>upclient</B> process
-requests them in encrypted form. Use this argument only if a list of
-directories headed by the <B>-crypt</B> flag precedes it on the command
-line.
-<P><DT><B>-auth
-</B><DD>Precedes a list of one or more directories which the <B>upserver</B>
-process distributes using a form of encryption that is intermediate in
-complexity and security between the unencrypted and encrypted levels set by
-the <B>-clear</B> and <B>-crypt</B> arguments. Do not use this
-argument, because the <B>upclient</B> process does not have a
-corresponding argument that it can use to request data transfer at this
-level.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example <B>bos create</B> command defines and starts an
-<B>upserver</B> process on the host machine
-<B>fs1.abc.com</B>. The last parameter (enclosed in
-quotes) instructs the <B>upserver</B> process to distribute the contents
-of the <B>/usr/afs/bin</B> directory in unencrypted form and the contents
-of the <B>/usr/afs/etc</B> directory in encrypted form.
-<PRE> % <B>bos create -server fs1.abc.com -instance upserver -type simple</B> \
- <B>-cmd "/usr/afs/bin/upserver /usr/afs/bin -crypt /usr/afs/etc"</B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf240.htm#HDRUPCLIENT">upclient</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf240.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf242.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf241.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf243.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_INTRO" HREF="auarf002.htm#ToC_256">uss</A></H2>
-<A NAME="IDX5508"></A>
-<A NAME="IDX5509"></A>
-<A NAME="IDX5510"></A>
-<A NAME="IDX5511"></A>
-<A NAME="IDX5512"></A>
-<A NAME="IDX5513"></A>
-<A NAME="IDX5514"></A>
-<A NAME="IDX5515"></A>
-<A NAME="IDX5516"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>uss</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>uss</B> command suite help administrators to
-create AFS user accounts more easily and efficiently. If <B>uss</B>
-commands are not used, creating an account requires issuing at least six
-separate commands to five different AFS servers.
-<P>There are three main commands in the suite:
-<UL>
-<P><LI>The <B>uss add</B> command creates a single complete user account,
-based on command line arguments and instructions in a template file.
-<P><LI>The <B>uss bulk</B> command creates multiple complete accounts at
-once, based on command line arguments, instructions in a template file and a
-bulk input file.
-<P><LI>the <B>uss delete</B> command removes most parts of a user
-account.
-</UL>
-<P>To obtain help, issue the <B>uss apropos</B> and <B>uss help</B>
-commands.
-<P><STRONG>Options</STRONG>
-<P>The following arguments and flags are available on many commands in the
-<B>uss</B> suite. The reference page for each command also lists
-them, but they are described here in greater detail.
-<DL>
-<P><DT><B>-admin <<VAR>administrator to authenticate</VAR>>
-</B><DD>Specifies the AFS user name under which to establish a connection to the
-AFS server processes that administer the various parts of a user
-account. If it is omitted, the connection is established under the
-issuer's effective user ID (his or her identity in the local file
-system). Even when this argument is included, UNIX commands that run
-during the <B>uss</B> operation (for instance, the UNIX
-<B>/etc/chown</B> command) run under the effective user ID.
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P><DT><B>-dryrun
-</B><DD>Reports actions that the command interpreter needs to perform when
-executing the <B>uss</B> operation, without actually performing
-them. Include this flag to verify that the command produces the desired
-account configuration. Combine it with the <B>-verbose</B> flag to
-yield even more detailed information. Note that the output does not
-necessarily reveal all possible problems that can prevent successful execution
-of the command, especially those that result from transient server or network
-outages.
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>-skipauth
-</B><DD>Bypasses mutual authentication with the AFS Authentication Server,
-allowing a site that uses Kerberos instead of the AFS Authentication Server to
-substitute that form of authentication.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer of a <B>uss</B> command must have all the rights required
-for performing the equivalent actions individually. See each
-<B>uss</B> command's reference page.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>
-<P><A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-<P><A HREF="auarf243.htm#HDRUSS_ADD">uss add</A>
-<P><A HREF="auarf244.htm#HDRUSS_APROPOS">uss apropos</A>
-<P><A HREF="auarf245.htm#HDRUSS_BULK">uss bulk</A>
-<P><A HREF="auarf246.htm#HDRUSS_DELETE">uss delete</A>
-<P><A HREF="auarf247.htm#HDRUSS_HELP">uss help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf241.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf243.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf242.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf244.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_ADD" HREF="auarf002.htm#ToC_257">uss add</A></H2>
-<A NAME="IDX5517"></A>
-<A NAME="IDX5518"></A>
-<A NAME="IDX5519"></A>
-<A NAME="IDX5520"></A>
-<A NAME="IDX5521"></A>
-<A NAME="IDX5522"></A>
-<A NAME="IDX5523"></A>
-<A NAME="IDX5524"></A>
-<A NAME="IDX5525"></A>
-<A NAME="IDX5526"></A>
-<A NAME="IDX5527"></A>
-<A NAME="IDX5528"></A>
-<A NAME="IDX5529"></A>
-<A NAME="IDX5530"></A>
-<A NAME="IDX5531"></A>
-<A NAME="IDX5532"></A>
-<A NAME="IDX5533"></A>
-<A NAME="IDX5534"></A>
-<A NAME="IDX5535"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a user account
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>uss add -user</B> <<VAR>login name</VAR>> [<B>-realname</B> <<VAR>full name in quotes</VAR>>]
- [<B>-pass</B> <<VAR>initial password</VAR>>]
- [<B>-pwexpires</B> <<VAR>password expires in [0..254] days (0 => never)</VAR>>]
- [<B>-server</B> <<VAR>FileServer for home volume</VAR>>]
- [<B>-partition</B> <<VAR>FileServer's disk partition for home volume</VAR>>]
- [<B>-mount</B> <<VAR>home directory mount point</VAR>>]
- [<B>-uid</B> <<VAR>uid to assign the user</VAR>>]
- [<B>-template</B> <<VAR>pathname of template file</VAR>>]
- [<B>-verbose</B>] [<B>-var</B> <<VAR>auxiliary argument pairs (Num val)</VAR>><SUP>+</SUP>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-admin</B> <<VAR>administrator to authenticate</VAR>>]
- [<B>-dryrun</B>] [<B>-skipauth</B>] [<B>-overwrite</B>] [<B>-help</B>]
-
-<B>uss ad -us</B> <<VAR>login name</VAR>> [<B>-r</B> <<VAR>full name in quotes</VAR>>]
- [<B>-pas</B> <<VAR>initial password</VAR>>]
- [<B>-pw</B> <<VAR>password expires in [0..254] days (0 => never)</VAR>>]
- [<B>-se</B> <<VAR>FileServer for home volume</VAR>>]
- [<B>-par</B> <<VAR>FileServer's disk partition for home volume</VAR>>]
- [<B>-m</B> <<VAR>home directory mount point</VAR>>] [<B>-ui</B> <<VAR>uid to assign the user</VAR>>]
- [<B>-t</B> <<VAR>pathname of template file</VAR>>] [<B>-ve</B>]
- [<B>-va</B> <<VAR>auxiliary argument pairs (Num val)</VAR>><SUP>+</SUP>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-a</B> <<VAR>administrator to authenticate</VAR>>] [<B>-d</B>] [<B>-sk</B>] [<B>-o</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>uss add</B> command creates entries in the Protection Database
-and Authentication Database for the user name specified by the
-<B>-user</B> argument. By default, the Protection Server
-automatically allocates an AFS user ID (UID) for the new user; to specify
-an alternate AFS UID, include the <B>-uid</B> argument. If a
-password is provided with the <B>-pass</B> argument, it is stored as the
-user's password in the Authentication Database after conversion into a
-form suitable for use as an encryption key. Otherwise, the string
-<B>changeme</B> is assigned as the user's initial password.
-<P>The other results of the command depend on which instructions and which of
-a defined set of variables appear in the template file specified with the
-<B>-template</B> argument. Many of the command's arguments
-supply a value for one of the defined variables, and failure to provide an
-argument when the corresponding variable appears in the template file halts
-the account creation process at the point where the command interpreter first
-encounters the variable in the template file.
-<P>To create multiple accounts with a single command, use the <B>uss
-bulk</B> command. To delete accounts with a single command, use the
-<B>uss delete</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-user
-</B><DD>Names the user's Authentication Database and Protection Database
-entries. It can include up to eight alphanumeric characters, but not
-any of the following characters: <B>:</B> (colon),
-<B>@</B> (at-sign), <B>.</B> (period), space, or
-newline. Because it becomes the username (the name under which a user
-logs in), it is best not to include shell metacharacters and to obey the
-restrictions that many operating systems impose on usernames (usually, to
-contain no more than eight lowercase letters).
-<P>Corresponding variable in the template file: $USER.
-<P><DT><B>-realname
-</B><DD>Specifies the user's full name. If it contains spaces or
-punctuation, surround it with double quotes. If not provided, it
-defaults to the user name provided with the <B>-user</B> argument.
-<P>Corresponding variable in the template file: $NAME. Many
-operating systems include a field for the full name in a user's entry in
-the local password file (<B>/etc/passwd</B> or equivalent), and this
-variable can be used to pass a value to be used in that field.
-<P><DT><B>-pass
-</B><DD>Specifies the user's initial password. Although the AFS
-commands that handle passwords accept strings of virtually unlimited length,
-it is best to use a password of eight characters or less, which is the maximum
-length that many applications and utilities accept. If not provided,
-this argument defaults to the string <B>changeme</B>.
-<P>Corresponding variable in the template file: none.
-<P><DT><B>-pwexpires
-</B><DD>Sets the number of days after a user's password is changed that it
-remains valid. Provide an integer from the range <B>1</B> through
-<B>254</B> to specify the number of days until expiration, or the value
-<B>0</B> to indicate that the password never expires (the default).
-<P>When the password becomes invalid (expires), the user is unable to
-authenticate, but has 30 more days in which to issue the <B>kpasswd</B>
-command to change the password (after that, only an administrator can change
-it).
-<P>Corresponding variable in the template file: $PWEXPIRES.
-<P><DT><B>-server
-</B><DD>Names the file server machine on which to create the new user's
-volume. It is best to provide a fully qualified hostname (for example,
-<B>fs1.abc.com</B>), but an abbreviated form is acceptable
-provided that the cell's naming service is available to resolve it at the
-time the volume is created.
-<P>Corresponding variable in the template file: $SERVER.
-<P><DT><B>-partition
-</B><DD>Specifies the partition on which to create the user's volume; it
-must be on the file server machine named by the <B>-server</B>
-argument. Provide the complete partition name (for example
-<B>/vicepa</B>) or one of the following abbreviated forms:
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P>
-<P>Corresponding variable in the template file: $PART.
-<P><DT><B>-mount
-</B><DD>Specifies the pathname for the user's home directory. Partial
-pathnames are interpreted relative to the current working directory.
-<P>Specify the read/write path to the directory, to avoid the failure that
-results from attempting to create a new mount point in a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P>Corresponding variable in template: $MTPT, but in the template
-file's <B>V</B> instruction only. Occurrences of the $MTPT
-variable in template instructions that follow the <B>V</B> instruction
-take their value from the <B>V</B> instruction's
-<B>mount_point</B> field. Thus the value of this command line
-argument becomes the value for the $MTPT variable in instructions that follow
-the <B>V</B> instruction only if the string $MTPT appears alone in the
-<B>V</B> instruction's <B>mount_point</B> field.
-<P><DT><B>-uid
-</B><DD>Specifies a positive integer other than 0 (zero) to assign as the
-user's AFS UID. If this argument is omitted, the Protection Server
-assigns an AFS UID that is one greater than the current value of the
-<TT>max</TT> <TT>user</TT> <TT>id</TT> counter (use the <B>pts
-listmax</B> command to display the counter). If including this
-argument, it is best first to use the <B>pts examine</B> command to verify
-that no existing account already has the desired AFS UID; it one does,
-the account creation process terminates with an error.
-<P>Corresponding variable in the template file: $UID.
-<P><DT><B>-template
-</B><DD>Specifies the pathname of the template file. If this argument is
-omitted, the command interpreter searches the following directories in the
-indicated order for a file called <B>uss.template</B>:
-<OL TYPE=1>
-<P><LI>The current working directory
-<P><LI><B>/afs/</B><VAR>cellname</VAR><B>/common/uss</B>, where
-<VAR>cellname</VAR> names the local cell
-<P><LI><B>/etc</B>
-</OL>
-<P>
-<P>If the issuer provides a filename other than <B>uss.template</B>
-but without a pathname, the command interpreter searches for it in the
-indicated directories. If the issuer provides a full or partial
-pathname, the command interpreter consults the specified file only; it
-interprets partial pathnames relative to the current working directory.
-<P>
-<P>If the specified template file is empty (zero-length), the command creates
-Protection and Authentication Database entries only.
-<P>The <B>uss Template File</B> reference page details the file's
-format.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-var
-</B><DD>Specifies values for each of the number variables $1 through $9 that can
-appear in the template file. Use the number variables to assign values
-to variables in the <B>uss</B> template file that are not part of the
-standard set.
-<P>Corresponding variables in the template file: $1 through $9.
-<P>For each instance of this argument, provide two parts in the indicated
-order, separated by a space:
-<UL>
-<P><LI>The integer from the range <B>1</B> through <B>9</B> that matches
-the variable in the template file. Do not precede it with a dollar
-sign.
-<P><LI>A string of alphanumeric characters to assign as the value of the
-variable.
-</UL>
-<P>See the chapter on <B>uss</B> in the <I>IBM AFS Administration
-Guide</I> for further explanation.
-<P><DT><B>-cell
-</B><DD>Specifies the cell in which to run the command. For more details,
-see the introductory <B>uss</B> reference page.
-<P><DT><B>-admin
-</B><DD>Specifies the AFS user name under which to establish authenticated
-connections to the AFS server processes that maintain the various components
-of a user account. For more details, see the introductory
-<B>uss</B> reference page.
-<P><DT><B>-dryrun
-</B><DD>Reports actions that the command interpreter needs to perform while
-executing the command, without actually performing them. For more
-details, see the introductory <B>uss</B> reference page.
-<P><DT><B>-skipauth
-</B><DD>Prevents authentication with the AFS Authentication Server, allowing a
-site using Kerberos to substitute that form of authentication.
-<P><DT><B>-overwrite
-</B><DD>Overwrites any directories, files and links that exist in the file system
-and for which there are definitions in <B>D</B>, <B>E</B>,
-<B>F</B>, <B>L</B>, or <B>S</B> instructions in the template file
-named by the <B>-template</B> argument. If this flag is omitted,
-the command interpreter prompts once for confirmation that it is to overwrite
-all such elements.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The combination of the following example <B>uss add</B> command and
-<B>V</B> instruction in a template file called <B>uss.tpl</B>
-creates Protection and Authentication Database entries named <B>smith</B>,
-and a volume called <TT>user.smith</TT> with a quota of 2500 kilobyte
-blocks, mounted at the pathname
-<B>/afs/abc.com/usr/smith</B>. The access control list (ACL)
-on the mount point grants <B>smith</B> all rights.
-<P>The issuer of the <B>uss add</B> command provides only the template
-file's name, not its complete pathname, because it resides in the current
-working directory. The command and <B>V</B> instruction appear here
-on two lines only for legibility; there are no line breaks in the actual
-instruction or command.
-<PRE> V user.$USER $SERVER.abc.com /vice$PART $1 \
- /afs/abc.com/usr/$USER $UID $USER all
-
- % <B>uss add -user smith -realname "John Smith" -pass js_pswd -server fs2</B> \
- <B>-partition b -template uss.tpl -var 1 2500</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer (or the user named by the <B>-admin</B> argument) must
-belong to the <B>system:administrators</B> group in the Protection
-Database and must have the <TT>ADMIN</TT> flag turned on in his or her
-Authentication Database entry.
-<P>If the template contains a <B>V</B> instruction, the issuer must be
-listed in the <B>/usr/afs/etc/UserList</B> file and must have at least
-<B>a</B> (<B>administer</B>) and <B>i</B> (<B>insert</B>)
-permissions on the ACL of the directory that houses the new mount
-point. If the template file includes instructions for creating other
-types of objects (directories, files or links), the issuer must have each
-privilege necessary to create them.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<P><A HREF="auarf245.htm#HDRUSS_BULK">uss bulk</A>
-<P><A HREF="auarf246.htm#HDRUSS_DELETE">uss delete</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf242.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf244.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf243.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf245.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_APROPOS" HREF="auarf002.htm#ToC_258">uss apropos</A></H2>
-<A NAME="IDX5536"></A>
-<A NAME="IDX5537"></A>
-<A NAME="IDX5538"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>uss apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>uss ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>uss apropos</B> command displays the first line of the online
-help entry for any <B>uss</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>uss help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-topic</B>
-</B><DD>Specifies the keyword string to match, in lowercase letters only.
-If the string is more than a single word, surround it with double quotes ("")
-or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>uss</B> command where the string specified by the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command lists all <B>uss</B> commands that include the
-word <B>create</B> in their names or short descriptions:
-<PRE> % <B>uss apropos create</B>
- add: create a new user
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<P><A HREF="auarf247.htm#HDRUSS_HELP">uss help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf243.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf245.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf244.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf246.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_BULK" HREF="auarf002.htm#ToC_259">uss bulk</A></H2>
-<A NAME="IDX5539"></A>
-<A NAME="IDX5540"></A>
-<A NAME="IDX5541"></A>
-<A NAME="IDX5542"></A>
-<A NAME="IDX5543"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Executes multiple <B>uss</B> commands listed in a file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>uss bulk -file</B> <<VAR>bulk input file</VAR>> [<B>-template</B> <<VAR>pathname of template file</VAR>>]
- [<B>-verbose</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-admin</B> <<VAR>administrator to authenticate</VAR>>] [<B>-dryrun</B>]
- [<B>-skipauth</B>] [<B>-overwrite</B>]
- [<B>-pwexpires</B> <<VAR>password expires in [0..254] days (0 => never)</VAR>>]
- [<B>-pipe</B>] [<B>-help</B>]
-
-<B>uss b -f</B> <<VAR>bulk input file</VAR>> [<B>-t</B> <<VAR>pathname of template file</VAR>>] [<B>-v</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-a</B> <<VAR>administrator to authenticate</VAR>>] [<B>-d</B>] [<B>-s</B>]
- [<B>-o</B>] [<B>-pw</B> <<VAR>password expires in [0..254] days (0 => never)</VAR>>]
- [<B>-pi</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>uss bulk</B> command executes the <B>uss</B> commands listed
-in the <B>bulk input file</B> specified with the <B>-file</B>
-argument. If the bulk input file includes <B>add</B> instructions
-that reference a template file, then the <B>-template</B> argument is
-required.
-<P>To create a single account, use the <B>uss add</B> command. To
-delete one or more accounts, use the <B>uss delete</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-file
-</B><DD>Specifies the pathname of the bulk input file. Partial pathnames
-are interpreted relative to the current working directory. For details
-on the file's format, see <A HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>.
-<P><DT><B>-template
-</B><DD>Specifies the pathname of the template file for any <B>uss add</B>
-commands that appear in the bulk input file. Partial pathnames are
-interpreted relative to the current working directory. For details on
-the file's format, see <A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-cell
-</B><DD>Specifies the cell in which to run the command. For more details,
-see the introductory <B>uss</B> reference page.
-<P><DT><B>-admin
-</B><DD>Specifies the AFS user name under which to establish authenticated
-connections to the AFS server processes that maintain the various components
-of a user account. For more details, see the introductory
-<B>uss</B> reference page.
-<P><DT><B>-dryrun
-</B><DD>Reports actions that the command interpreter needs to perform while
-executing the command, without actually performing them. For more
-details, see the introductory <B>uss</B> reference page.
-<P><DT><B>-skipauth
-</B><DD>Prevents authentication with the AFS Authentication Server, allowing a
-site using Kerberos to substitute that form of authentication.
-<P><DT><B>-overwrite
-</B><DD>Overwrites any directories, files and links that exist in the file system
-and for which there are also <B>D</B>, <B>E</B>, <B>F</B>,
-<B>L</B>, or <B>S</B> instructions in a template file referenced by an
-<B>add</B> instruction in the bulk input file. If this flag is
-omitted, the command interpreter prompts, once for each <B>add</B>
-instruction in the bulk input file, for confirmation that it should overwrite
-such elements. Do not include this flag if the bulk input file does not
-contain <B>add</B> instructions.
-<P><DT><B>-pwexpires
-</B><DD>Sets the number of days after a user's password is changed that it
-remains valid, for each user named by an <B>add</B> instruction in the
-bulk input file. Provide an integer from the range <B>1</B> through
-<B>254</B> to specify the number of days until expiration, or the value
-<B>0</B> to indicate that the password never expires (the default).
-<P>When the password becomes invalid (expires), the user is unable to
-authenticate, but has 30 more days in which to issue the <B>kpasswd</B>
-command to change the password (after that, only an administrator can change
-it).
-<P><DT><B>-pipe
-</B><DD>Suppresses the Authentication Server's prompt for the password of the
-issuer or the user named by the <B>-admin</B> argument (the Authentication
-Server always separately authenticates the creator of an entry in the
-Authentication Database). Instead, the command interpreter accepts the
-password via the standard input stream, as piped in from another
-program. This enables the <B>uss bulk</B> command to run as part of
-unattended batch jobs.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command executes the instructions in the bulk input
-file called <B>new_students</B>, which includes <B>add</B>
-instructions that refer to the template file
-<B>student.template</B>. Both files reside in the current
-working directory.
-<PRE> % <B>uss bulk new_students student.template</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer (or the user named by the <B>-admin</B> argument) must have
-the privileges necessary to run the commands that correspond to instructions
-in the bulk input file.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf054.htm#HDRUSSBULKINPUT">uss Bulk Input File</A>
-<P><A HREF="auarf055.htm#HDRUSSFILE">uss Template File</A>
-<P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<P><A HREF="auarf243.htm#HDRUSS_ADD">uss add</A>
-<P><A HREF="auarf246.htm#HDRUSS_DELETE">uss delete</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf244.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf246.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf245.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf247.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_DELETE" HREF="auarf002.htm#ToC_260">uss delete</A></H2>
-<A NAME="IDX5544"></A>
-<A NAME="IDX5545"></A>
-<A NAME="IDX5546"></A>
-<A NAME="IDX5547"></A>
-<A NAME="IDX5548"></A>
-<A NAME="IDX5549"></A>
-<A NAME="IDX5550"></A>
-<A NAME="IDX5551"></A>
-<A NAME="IDX5552"></A>
-<A NAME="IDX5553"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Deletes a user account
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>uss delete -user</B> <<VAR>login name</VAR>> [<B>-mountpoint</B> <<VAR>mountpoint for user's volume</VAR>>]
- [<B>-savevolume</B>] [<B>-verbose</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-admin</B> <<VAR>administrator to authenticate</VAR>>] [<B>-dryrun</B>]
- [<B>-skipauth</B>] [<B>-help</B>]
-
-<B>uss d -u</B> <<VAR>login name</VAR>> [<B>-m</B> <<VAR>mountpoint for user's volume</VAR>>] [<B>-sa</B>] [<B>-v</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] <B>-a</B> <<VAR>administrator to authenticate</VAR>>]
- [<B>-d</B>] [<B>-sk</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>uss delete</B> command removes the Authentication Database and
-Protection Database entries for the user named by <B>-user</B>
-argument. In addition, it can remove the user's home volume and
-associated VLDB entry, a mount point for the volume or both, depending on
-whether the <B>-mountpoint</B> and <B>-savevolume</B> options are
-provided.
-<UL>
-<P><LI>To remove both the volume and mount point, use the <B>-mountpoint</B>
-argument to name the user's home directory. It is best to create a
-tape backup of a volume before deleting it. Note that other mount
-points for the volume are not removed, if they exist.
-<P><LI>To remove the mount point only, provide both the <B>-mountpoint</B>
-and <B>-savevolume</B> options.
-<P><LI>To preserve both the volume and mount point, omit the
-<B>-mountpoint</B> argument (or both it and the <B>-savevolume</B>
-flag).
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-user
-</B><DD>Names the entry to delete from the Protection and Authentication
-Databases.
-<P><DT><B>-mountpoint
-</B><DD>Specifies the pathname to the user's home directory, which is deleted
-from the filespace. By default, the volume referenced by the mount
-point is also removed from the file server machine that houses it, along with
-its Volume Location Database (VLDB) entry. To retain the volume and
-VLDB entry, include the <B>-savevolume</B> flag. Partial pathnames
-are interpreted relative to the current working directory.
-<P>Specify the read/write path to the mount point, to avoid the failure that
-results from attempting to remove a mount point from a read-only
-volume. By convention, the read/write path is indicated by placing a
-period before the cell name at the pathname's second level (for example,
-<B>/afs/.abc.com</B>). For further discussion of the
-concept of read/write and read-only paths through the filespace, see the
-<B>fs mkmount</B> reference page.
-<P><DT><B>-savevolume
-</B><DD>Preserves the user's volume and VLDB entry.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-cell
-</B><DD>Specifies the cell in which to run the command. For more details,
-see the introductory <B>uss</B> reference page.
-<P><DT><B>-admin
-</B><DD>Specifies the AFS user name under which to establish authenticated
-connections to the AFS server processes that maintain the various components
-of a user account. For more details, see the introductory
-<B>uss</B> reference page.
-<P><DT><B>-dryrun
-</B><DD>Reports actions that the command interpreter needs to perform while
-executing the command, without actually performing them. For more
-details, see the introductory <B>uss</B> reference page.
-<P><DT><B>-skipauth
-</B><DD>Prevents authentication with the AFS Authentication Server, allowing a
-site using Kerberos to substitute that form of authentication.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes <B>smith</B>'s user account from the
-<B>abc.com</B> cell. The <B>-savevolume</B> argument
-retains the <TT>user.smith</TT> volume on its file server
-machine.
-<PRE> % <B>uss delete smith -mountpoint /afs/abc.com/usr/smith -savevolume</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer (or the user named by <B>-admin</B> argument) must belong to
-the <B>system:administrators</B> group in the Protection Database,
-must have the <TT>ADMIN</TT> flag turned on in his or her Authentication
-Database entry, and must have at least <B>a</B> (<B>administer</B>)
-and <B>d</B> (<B>delete</B>) permissions on the access control list
-(ACL) of the mount point's parent directory. If the
-<B>-savevolume</B> flag is not included, the issuer must also be listed in
-the <B>/usr/afs/etc/UserList</B> file.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf153.htm#HDRFS_MKMOUNT">fs mkmount</A>
-<P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf245.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf247.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf246.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf248.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRUSS_HELP" HREF="auarf002.htm#ToC_261">uss help</A></H2>
-<A NAME="IDX5554"></A>
-<A NAME="IDX5555"></A>
-<A NAME="IDX5556"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>uss</B> commands or lists
-functional descriptions of all <B>uss</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>uss help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>uss h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>uss help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>uss</B> command.
-<P>To list every <B>uss</B> command whose name or short description
-includes a specified keyword, use the <B>uss apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Indicates each command for which to display the complete online help
-entry. Omit the <B>uss</B> part of the command name, providing only
-the operation code (for example, specify <B>bulk</B>, not <B>uss
-bulk</B>). If this argument is omitted, the output briefly describes
-every <B>uss</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>uss</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>uss
-bulk</B> command:
-<PRE> % <B>uss help bulk</B>
- uss bulk: bulk input mode
- Usage: uss bulk -file <bulk input file> [-template <pathname
- of template file>] [-verbose] [-cell <cell name>] [-admin
- <administrator to authenticate>] [-dryrun] [-skipauth] [-overwrite]
- [-pwexpires <password expires in [0..254] days (0 => never)>] [-pipe]
- [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf242.htm#HDRUSS_INTRO">uss</A>
-<P><A HREF="auarf244.htm#HDRUSS_APROPOS">uss apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf246.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf248.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf247.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf249.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVLDB_CHECK" HREF="auarf002.htm#ToC_262">vldb_check</A></H2>
-<A NAME="IDX5557"></A>
-<A NAME="IDX5558"></A>
-<A NAME="IDX5559"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Checks the integrity of the VLDB
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vldb_check -database</B> <<VAR>vldb_file</VAR>> [<B>-uheader</B>] [<B>-vheader</B>] [<B>-servers</B>]
- [<B>-entries</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vldb_check -d</B> <<VAR>vldb_file</VAR>> [<B>-u</B>] [<B>-vh</B>] [<B>-s</B>] [<B>-e</B>] [<B>-ve</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vldb_check</B> command checks the integrity of the Volume
-Location Database (VLDB), reporting any errors or corruption it finds.
-If there are problems, do not issue any <B>vos</B> commands until the
-database is repaired.
-<P><STRONG>Cautions</STRONG>
-<P>The results can be unpredictable if the Volume Location (VL) Server makes
-changes to the VLDB while this command is running. Use the <B>bos
-shutdown</B> command to shutdown the local <B>vlserver</B> process
-before running this command, or before creating a second copy of the
-<B>vldb.DB0</B> file (with a different name) on which to run the
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-database
-</B><DD>Names the VLDB (copy of the <B>vldb.DB0</B> file) to
-check. If the current working directory is not the location of the
-file, provide a pathname, either full or relative to the current working
-directory.
-<P><DT><B>-uheader
-</B><DD>Displays information which Ubik maintains in the database's
-header.
-<P><DT><B>-pheader
-</B><DD>Displays information which the VL Server maintains in the database's
-header.
-<P><DT><B>-servers
-</B><DD>Outputs the server entries from the VLDB, which list the IP addresses
-registered for each file server machine in the cell.
-<P><DT><B>-entries
-</B><DD>Outputs every volume entry in the database. The information
-includes the volume's name and the volume ID number for each of its
-versions.
-<P><DT><B>-verbose
-</B><DD>Reports additional information about the database, including the number of
-entries for each type of volume.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If there are errors in the database, the output always reports them on the
-standard error stream. If any options other than <B>-database</B>
-or <B>-help</B> are provided, the output written to the standard output
-stream includes additional information as described for each option in the
-preceding <B>Options</B> section of this reference page. The output
-is intended for debugging purposes and is meaningful to someone familiar with
-the internal structure of the VLDB.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf118.htm#HDRBOS_SHUTDOWN">bos shutdown</A>
-<P><A HREF="auarf249.htm#HDRVLSERVER">vlserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf247.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf249.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf248.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf250.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVLSERVER" HREF="auarf002.htm#ToC_263">vlserver</A></H2>
-<A NAME="IDX5560"></A>
-<A NAME="IDX5561"></A>
-<A NAME="IDX5562"></A>
-<A NAME="IDX5563"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Volume Location Server
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vlserver</B> [<B>-p</B> <<VAR>lwp processes</VAR>>] [<B>-nojumbo</B>]
- [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>vlserver</B> command initializes the Volume Location (VL)
-Server, which runs on every database server machine. In the
-conventional configuration, its binary file is located in the
-<B>/usr/afs/bin</B> directory on a file server machine.
-<P>The <B>vlserver</B> command is not normally issued at the command shell
-prompt but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a database server machine as the local superuser
-<B>root</B>.
-<P>As it initializes, the VL Server process creates the two files that
-constitute the Volume Location Database (VLDB), <B>vldb.DB0</B> and
-<B>vldb.DBSYS1</B>, in the <B>/usr/afs/db</B> directory if they
-do not already exist. Use the commands in the <B>vos</B> suite to
-administer the database.
-<P>The VL Server maintains the record of volume locations in the Volume
-Location Database (VLDB). When the Cache Manager fills a file request
-from an application program, it first contacts the VL Server to learn which
-file server machine currently houses the volume that contains the file.
-The Cache Manager then requests the file from the File Server process running
-on that file server machine.
-<P>The VL Server records a trace of its activity in the
-<B>/usr/afs/logs/VLLog</B> file. Use the <B>bos getlog</B>
-command to display the contents of the file. By default, it records on
-a minimal number of messages. For instructions on increasing the amount
-of logging, see the <B>VLLog</B> reference page.
-<P>By default, the VL Server runs nine lightweight processes (LWPs). To
-change the number, use the <B>-p</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-p
-</B><DD>Sets the number of server lightweight processes (LWPs) to run.
-Provide an integer between <B>4</B> and <B>16</B>. The default
-is 9.
-<P><DT><B>-nojumbo
-</B><DD>Prohibits the server from sending or receiving jumbograms. A
-jumbogram is a large-size packet composed of 2 to 4 normal Rx data packets
-that share the same header. The VL Server uses jumbograms by default,
-but some routers are not capable of properly breaking the jumbogram into
-smaller packets and reassembling them.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates a <B>vlserver</B>
-process on the machine <B>fs2.abc.com</B> that uses six
-lightweight processes. Type the command on a single line:
-<PRE> % <B>bos create -server fs2.abc.com -instance vlserver -type simple</B> \
- <B>-cmd "/usr/afs/bin/vlserver -p 6"</B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf038.htm#HDRVLLOG">VLLog</A>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf248.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf250.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf249.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf251.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOLINFO" HREF="auarf002.htm#ToC_264">volinfo</A></H2>
-<A NAME="IDX5564"></A>
-<A NAME="IDX5565"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Produces detailed statistics about one or more volume headers and the
-partition that houses them
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>volinfo</B> [<B>-online</B>] [<B>-vnode</B>] [<B>-date</B>] [<B>-inode</B>] [<B>-itime</B>]
- [<B>-part</B> <<VAR>AFS partition name (default current partition)</VAR>><SUP>+</SUP>]
- [<B>-volumeid</B> <<VAR>Volume id</VAR>><SUP>+</SUP>] [<B>-header</B>] [<B>-sizeOnly</B>] [<B>-fixheader</B>]
- [<B>-saveinodes</B>] [<B>-orphaned</B>] [<B>-help</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>volinfo</B> command displays detailed statistics about one or
-more volume headers and the partition that houses them. The command
-must be issued on a file server machine and by default produces output for
-every volume on every AFS server partition on the machine. To display
-output for the volumes on one partition only, include the <B>-part</B>
-argument. To display output for one volume only, include the
-<B>-volumeid</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-online
-</B><DD>Is nonoperational.
-<P><DT><B>-vnode
-</B><DD>Displays a table for each volume which lists the large (directory) and
-small (file) vnodes in it, in addition to the default output.
-<P><DT><B>-date
-</B><DD>When combined with the <B>-vnode</B> flag, adds the
-<TT>ServerModTime</TT> field to each vnode entry in the large vnode and
-small vnode tables, reporting its most recent modification time.
-<P><DT><B>-inode
-</B><DD>When combined with the <B>-vnode</B> flag, adds the <TT>inode</TT>
-field to each vnode entry in the large vnode and small vnode tables, reporting
-the associated inode number.
-<P><DT><B>-itime
-</B><DD>When combined with the <B>-vnode</B> flag, displays a change,
-modification, and access timestamp for each of the large vnode and small vnode
-tables.
-<P><DT><B>-part
-</B><DD>Specifies the partition that houses each volume for which to produce
-output. Use the format <B>/vicep</B><VAR>xx</VAR>, where <VAR>xx</VAR>
-is one or two lowercase letters. This argument can be omitted if the
-current working directory is the mount location for an AFS server
-partition; it is not the mount location for an AFS server partition, the
-command produces output for every volume on all local AFS server
-partitions.
-<P><DT><B>-volumeid
-</B><DD>Specifies the ID number of one volume for which to produce output.
-The <B>-part</B> argument must be provided along with this one unless the
-current working directory is the mount location for the AFS server partition
-that houses the volume.
-<P><DT><B>-header
-</B><DD>Displays statistics about the volume header of each volume, in addition to
-the default output.
-<P><DT><B>-sizeOnly
-</B><DD>Displays a single line of output for each volume, reporting the size of
-various structures associated with it. The default output is suppressed
-and any flags that modify it (such as <B>-vnode</B>) are ignored.
-<P><DT><B>-fixheader
-</B><DD>Repairs damaged inodes in each volume if possible. If there are
-any, it reports the action it is taking to repair them. Otherwise, it
-produces no output in addition to the default output.
-<P><DT><B>-saveinodes
-</B><DD>Creates a file in the current working directory for each inode in each
-volume. Each file is called
-<B>TmpInode.</B><VAR>vnode_number</VAR> and contains the inode's
-contents. The default output is suppressed and any flags that modify it
-(such as <B>-vnode</B>) are ignored.
-<P><DT><B>-orphaned
-</B><DD>Displays a large vnode and small vnode table for each volume, which lists
-only orphaned vnodes (vnodes that have no parent). If there are none,
-the tables are empty (only the headers appear).
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>By default, the command produces several line of statistics for each
-volume. Adding other options produces or substitutes additional
-information as described in the preceding <B>Options</B> section of this
-reference page. The output is intended for debugging purposes and is
-meaningful to someone familiar with the internal structure of volume
-headers.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf051.htm#HDRVLDBDB">vldb.DB0 and vldb.DBSYS1</A>
-<P><A HREF="auarf251.htm#HDRVOLSERVER">volserver</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf249.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf251.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf250.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf252.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOLSERVER" HREF="auarf002.htm#ToC_265">volserver</A></H2>
-<A NAME="IDX5566"></A>
-<A NAME="IDX5567"></A>
-<A NAME="IDX5568"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Initializes the Volume Server component of the <B>fs</B> process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>volserver</B> [<B>-log</B>] [<B>-p</B> <<VAR>number of processes</VAR>>]
- [<B>-udpsize</B> <<VAR>size of socket buffer in bytes</VAR>>]
- [<B>-enable_peer_stats</B>] [<B>-enable_process_stats</B>] [<B>-help</B>]
-</PRE>
-<P>This command does not use the syntax conventions of the AFS command
-suites. Provide the command name and all option names in full.
-<P><STRONG>Description</STRONG>
-<P>The <B>volserver</B> command initializes the Volume Server component of
-the <B>fs</B> process. In the conventional configuration, its
-binary file is located in the <B>/usr/afs/bin</B> directory on a file
-server machine.
-<P>The <B>volserver</B> command is not normally issued at the command
-shell prompt but rather placed into a file server machine's
-<B>/usr/afs/local/BosConfig</B> file with the <B>bos create</B>
-command. If it is ever issued at the command shell prompt, the issuer
-must be logged onto a database server machine as the local superuser
-<B>root</B>.
-<P>The Volume Server records a trace of its activity in the
-<B>/usr/afs/logs/VolserLog</B> file. Use the <B>bos getlog</B>
-command to display the contents of the file.
-<P>The Volume Server processes the <B>vos</B> commands that administrators
-use to create, delete, move, and replicate volumes, as well as prepare them
-for archiving to tape or other media.
-<P>By default, the VL Server runs nine lightweight processes (LWPs). To
-change the number, use the <B>-p</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-log
-</B><DD>Records in the <B>/usr/afs/logs/VolserLog</B> file the names of all
-users who successfully initiate a <B>vos</B> command. The Volume
-Server also records any file removals that result from issuing the <B>vos
-release</B> command with the <B>-f</B> flag.
-<P><DT><B>-p
-</B><DD>Sets the number of server lightweight processes (LWPs) to run.
-Provide an integer between <B>4</B> and <B>16</B>. The default
-is 9.
-<P><DT><B>-udpsize
-</B><DD>Sets the size of the UDP buffer, which is 64 KB by default. Provide
-a positive integer, preferably larger than the default.
-<P><DT><B>-enable_peer_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. For each connection with a specific UDP port on another
-machine, a separate record is kept for each type of RPC (FetchFile, GetStatus,
-and so on) sent or received. To display or otherwise access the
-records, use the Rx Monitoring API.
-<P><DT><B>-enable_process_stats
-</B><DD>Activates the collection of Rx statistics and allocates memory for their
-storage. A separate record is kept for each type of RPC (FetchFile,
-GetStatus, and so on) sent or received, aggregated over all connections to
-other machines. To display or otherwise access the records, use the Rx
-Monitoring API.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following <B>bos create</B> command creates a <B>volserver</B>
-process on the machine <B>fs2.abc.com</B>:
-<PRE> % <B>bos create -server fs2.abc.com -instance volserver -type simple</B> \
- <B>-cmd /usr/afs/bin/volserver </B>
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the superuser <B>root</B> on a file
-server machine to issue the command at a command shell prompt. It is
-conventional instead to create and start the process by issuing the <B>bos
-create</B> command.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf016.htm#HDRBOSCONFIG">BosConfig</A>
-<P><A HREF="auarf039.htm#HDRVOLSERLOG">VolserLog</A>
-<P><A HREF="auarf098.htm#HDRBOS_CREATE">bos create</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf250.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf252.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf251.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf253.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_INTRO" HREF="auarf002.htm#ToC_266">vos</A></H2>
-<A NAME="IDX5569"></A>
-<A NAME="IDX5570"></A>
-<A NAME="IDX5571"></A>
-<A NAME="IDX5572"></A>
-<A NAME="IDX5573"></A>
-<A NAME="IDX5574"></A>
-<A NAME="IDX5575"></A>
-<A NAME="IDX5576"></A>
-<A NAME="IDX5577"></A>
-<A NAME="IDX5578"></A>
-<A NAME="IDX5579"></A>
-<A NAME="IDX5580"></A>
-<A NAME="IDX5581"></A>
-<A NAME="IDX5582"></A>
-<A NAME="IDX5583"></A>
-<A NAME="IDX5584"></A>
-<A NAME="IDX5585"></A>
-<A NAME="IDX5586"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Introduction to the <B>vos</B> command suite
-<P><STRONG>Description</STRONG>
-<P>The commands in the <B>vos</B> command suite are the administrative
-interface to the Volume Server and Volume Location (VL) Server. System
-administrators use <B>vos</B> commands to create, move, delete, replicate,
-back up and examine volumes, among other operations. The VL Server
-automatically records in the Volume Location Database (VLDB) changes in volume
-status and location that result from <B>vos</B> commands.
-<P>The operations invoked by most <B>vos</B> commands are idempotent,
-meaning that if an operation is interrupted by a network, server machine, or
-process outage, then a subsequent attempt at the same operation continues from
-the interruption point, rather than starting over at the beginning of the
-operation. Before executing a command, the Volume and VL Servers check
-the current state of the volumes and VLDB records to be altered by the
-command. If they are already in the desired end state (or a consistent
-intermediate state), there is no need to repeat the internal steps that
-brought them there. Idempotency does not apply if the command issuer
-explicitly interrupts the operation with the <<B>Ctrl-c</B>> command or
-another interrupt signal. In that case, the volume is left locked and
-the administrator must use the <B>vos unlock</B> command to unlock it
-before proceeding.
-<P>It is important that the VLDB accurately indicate the status of the volumes
-on file server machines at all times. The reference pages for the files
-<B>vldb.DB0</B> and
-<B>V</B><VAR>vol_ID</VAR><B>.vol</B> describe the information
-recorded in the VLDB and volume headers, respectively. If a
-<B>vos</B> command changes volume status, it automatically records the
-change in the corresponding VLDB entry. The most common cause of
-discrepancies between the VLDB and volume status on file server machines is
-interrupted operations; to restore consistency, use the <B>vos
-syncserv</B> and <B>vos syncvldb</B> commands.
-<P>There are several categories of commands in the <B>vos</B> command
-suite:
-<UL>
-<P><LI>Commands to create, move, and rename volumes: <B>vos backup</B>,
-<B>vos backupsys</B>, <B>vos create</B>, <B>vos move</B>, and
-<B>vos rename</B>
-<P><LI>Commands to remove VLDB volume records or volumes or both: <B>vos
-delentry</B>, <B>vos remove</B>, and <B>vos zap</B>
-<P><LI>Commands to edit or display VLDB server entries: <B>vos
-changeaddr</B> and <B>vos listaddrs</B>
-<P><LI>Commands to create and restore dump files: <B>vos dump</B> and
-<B>vos restore</B>
-<P><LI>Commands to administer replicated volumes: <B>vos addsite</B>,
-<B>vos release</B>, and <B>vos remsite</B>
-<P><LI>Commands to display VLDB records, volume headers, or both: <B>vos
-examine</B>, <B>vos listvldb</B>, and <B>vos listvol</B>
-<P><LI>Commands to display information about partitions that house volumes:
-<B>vos listpart</B> and <B>vos partinfo</B>
-<P><LI>Commands to restore consistency between the VLDB and volume headers:
-<B>vos syncserv</B> and <B>vos syncvldb</B>
-<P><LI>Commands to lock and unlock VLDB entries: <B>vos lock</B>,
-<B>vos unlock</B>, and <B>vos unlockvldb</B>
-<P><LI>A command to report Volume Server status: <B>vos status</B>
-<P><LI>Commands to obtain help: <B>vos apropos</B> and <B>vos
-help</B>
-</UL>
-<P><STRONG>Options</STRONG>
-<P>The following arguments and flags are available on many commands in the
-<B>bos</B> suite. The reference page for each command also lists
-them, but they are described here in greater detail.
-<DL>
-<P><DT><B>-cell <<VAR>cell name</VAR>>
-</B><DD>Names the cell in which to run the command. It is acceptable to
-abbreviate the cell name to the shortest form that distinguishes it from the
-other entries in the <B>/usr/vice/etc/CellServDB</B> file on the local
-machine. If the <B>-cell</B> argument is omitted, the command
-interpreter determines the name of the local cell by reading the following in
-order:
-<OL TYPE=1>
-<P><LI>The value of the AFSCELL environment variable
-<P><LI>The local <B>/usr/vice/etc/ThisCell</B> file
-</OL>
-<P>
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell.
-<P><DT><B>-help
-</B><DD>Prints a command's online help message on the standard output
-stream. Do not combine this flag with any of the command's other
-options; when it is provided, the command interpreter ignores all other
-options, and only prints the help message.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using the server encryption key with the
-highest key version number in the local <B>/usr/afs/etc/KeyFile</B>
-file. The <B>vos</B> command interpreter presents the ticket, which
-never expires, to the Volume Server and VL Server during mutual
-authentication.
-<P>Use this flag only when issuing a command on a server machine; client
-machines do not usually have a <B>/usr/afs/etc/KeyFile</B> file.
-The issuer of a command that includes this flag must be logged on to the
-server machine as the local superuser <B>root</B>. The flag is
-useful for commands invoked by an unattended application program, such as a
-process controlled by the UNIX <B>cron</B> utility or by a cron entry in
-the machine's <B>/usr/afs/local/BosConfig</B> file. It is also
-useful if an administrator is unable to authenticate to AFS but is logged in
-as the local superuser <B>root</B>.
-<P>Do not combine the <B>-cell</B> and <B>-localauth</B>
-options. A command on which the <B>-localauth</B> flag is included
-always runs in the local cell (as defined in the server machine's local
-<B>/usr/afs/etc/ThisCell</B> file), whereas a command on which the
-<B>-cell</B> argument is included runs in the specified foreign
-cell. Also, do not combine the <B>-localauth</B> and
-<B>-noauth</B> flags.
-<P><DT><B>-noauth
-</B><DD>Establishes an unauthenticated connection to the Volume Server and VL
-Server, in which the servers treat the issuer as the unprivileged user
-<B>anonymous</B>. It is useful only when authorization checking is
-disabled on the server machine (during the installation of a file server
-machine or when the <B>bos setauth</B> command has been used during other
-unusual circumstances). In normal circumstances, the servers allow only
-privileged users to issue commands that change the status of a volume or VLDB
-record, and refuses to perform such an action even if the <B>-noauth</B>
-flag is provided. Do not combine the <B>-noauth</B> and
-<B>-localauth</B> flags.
-<P><DT><B>-partition <<VAR>partition name</VAR>>
-</B><DD>Identifies the AFS server partition on a file server machine that houses,
-or is to house, the volumes of interest, or about which to list
-information. The <B>vos</B> command interpreter accepts any of the
-following four name formats:
-<PRE> <B>/vicepa</B> = <B>vicepa</B> = <B>a</B> = <B>0</B>
- <B>/vicepb</B> = <B>vicepb</B> = <B>b</B> = <B>1</B>
-
-</PRE>
-<P>
-<P>After <B>/vicepz</B> (for which the index is 25) comes
-<PRE> <B>/vicepaa</B> = <B>vicepaa</B> = <B>aa</B> = <B>26</B>
- <B>/vicepab</B> = <B>vicepab</B> = <B>ab</B> = <B>27</B>
-
-</PRE>
-<P>and so on through
-<PRE> <B>/vicepiv</B> = <B>vicepiv</B> = <B>iv</B> = <B>255</B>
-
-</PRE>
-<P>The <B>-frompartition</B> and <B>-topartition</B> arguments to the
-<B>vos move</B> command also accept this notation.
-<P><DT><B>-server <<VAR>machine name</VAR>>
-</B><DD>Identifies the file server machine that houses, or is to house, the
-volumes or AFS server partitions of interest. Provide the
-machine's IP address in dotted decimal format, its fully qualified host
-name (for example, <B>fs1.abc.com</B>), or the shortest
-abbreviated form of its host name that distinguishes it from other
-machines. Successful use of an abbreviated form depends on the
-availability of a name resolution service (such as the Domain Name Service or
-a local host table) at the time the command is issued.
-<P>The <B>-fromserver</B> and <B>-toserver</B> arguments to the
-<B>vos move</B> command also accept these name formats.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-</DL>
-<P><STRONG>Privilege Required</STRONG>
-<P>To issue most <B>vos</B> commands, the issuer must be listed in the
-<B>/usr/afs/etc/UserList</B> file on each server machine that houses or is
-to house an affected volume, and on each database server machine. The
-most predictable performance results if all database server and file server
-machines in the cell share a common <B>UserList</B> file.
-Alternatively, if the <B>-localauth</B> flag is included, the issuer must
-be logged on to a server machine as the local superuser
-<B>root</B>.
-<P>To issue a <B>vos</B> command that only displays information, no
-privilege is required.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf253.htm#HDRVOS_ADDSITE">vos addsite</A>
-<P><A HREF="auarf254.htm#HDRVOS_APROPOS">vos apropos</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P><A HREF="auarf256.htm#HDRVOS_BACKUPSYS">vos backupsys</A>
-<P><A HREF="auarf257.htm#HDRVOS_CHANGEADDR">vos changeaddr</A>
-<P><A HREF="auarf258.htm#HDRVOS_CREATE">vos create</A>
-<P><A HREF="auarf259.htm#HDRVOS_DELENTRY">vos delentry</A>
-<P><A HREF="auarf260.htm#HDRVOS_DUMP">vos dump</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf262.htm#HDRVOS_HELP">vos help</A>
-<P><A HREF="auarf263.htm#HDRVOS_LISTADDRS">vos listaddrs</A>
-<P><A HREF="auarf264.htm#HDRVOS_LISTPART">vos listpart</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P><A HREF="auarf267.htm#HDRVOS_LOCK">vos lock</A>
-<P><A HREF="auarf268.htm#HDRVOS_MOVE">vos move</A>
-<P><A HREF="auarf269.htm#HDRVOS_PARTINFO">vos partinfo</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P><A HREF="auarf272.htm#HDRVOS_REMSITE">vos remsite</A>
-<P><A HREF="auarf273.htm#HDRVOS_RENAME">vos rename</A>
-<P><A HREF="auarf274.htm#HDRVOS_RESTORE">vos restore</A>
-<P><A HREF="auarf275.htm#HDRVOS_STATUS">vos status</A>
-<P><A HREF="auarf276.htm#HDRVOS_SYNCSERV">vos syncserv</A>
-<P><A HREF="auarf277.htm#HDRVOS_SYNCVLDB">vos syncvldb</A>
-<P><A HREF="auarf278.htm#HDRVOS_UNLOCK">vos unlock</A>
-<P><A HREF="auarf279.htm#HDRVOS_UNLOCKVLDB">vos unlockvldb</A>
-<P><A HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf251.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf253.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf252.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf254.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_ADDSITE" HREF="auarf002.htm#ToC_267">vos addsite</A></H2>
-<A NAME="IDX5587"></A>
-<A NAME="IDX5588"></A>
-<A NAME="IDX5589"></A>
-<A NAME="IDX5590"></A>
-<A NAME="IDX5591"></A>
-<A NAME="IDX5592"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Adds a read-only site definition to a volume's VLDB entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos addsite -server</B> <<VAR>machine name for new site</VAR>>
- <B>-partition</B> <<VAR>partition name for new site</VAR>>
- <B>-id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos ad -s</B> <<VAR>machine name for new site</VAR>> <B>-p</B> <<VAR>partition name for new site</VAR>>
- <B>-i</B> <<VAR>volume name or ID</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos addsite</B> command defines a new read-only site (partition
-on a file server machine, specified by the <B>-server</B> and
-<B>-partition</B> arguments) in the Volume Location Database (VLDB) entry
-of the read/write volume named by the <B>-id</B> argument. When the
-<B>vos release</B> command is next issued against the read/write volume, a
-read-only copy of it is distributed to all of the read-only sites, including
-the newly defined one.
-<P><STRONG>Cautions</STRONG>
-<P>A volume's VLDB entry accommodates a maximum number of site
-definitions, as defined in the <I>IBM AFS Release Notes</I>. The
-site housing the read/write and backup versions of the volume counts as one
-site, and each read-only site counts as an additional site (even the read-only
-site defined on the same file server machine and partition as the read/write
-site counts as a separate site). The limit in the VLDB entry
-effectively determines the maximum number of copies of the volume that are
-available to AFS clients.
-<P>Attempts to create additional sites by using this command fail with an
-error.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine where the read-only volume is to
-reside. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition where the read-only volume is to reside, on the
-file server machine named by the <B>-server</B> argument. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of the read/write
-source volume.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example, appropriate in the State University cell, defines a
-read-only site for the cell's <B>root.afs</B> volume.
-<PRE> % <B>vos addsite -server sv7.stateu.edu -partition /vicepb -id root.afs</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf252.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf254.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf253.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf255.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_APROPOS" HREF="auarf002.htm#ToC_268">vos apropos</A></H2>
-<A NAME="IDX5593"></A>
-<A NAME="IDX5594"></A>
-<A NAME="IDX5595"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays each help entry containing a keyword string
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos apropos -topic</B> <<VAR>help string</VAR>> [<B>-help</B>]
-
-<B>vos ap -t</B> <<VAR>help string</VAR>> [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos apropos</B> command displays the first line of the online
-help entry for any <B>vos</B> command that has in its name or short
-description the string specified by the <B>-topic</B> argument.
-<P>To display the syntax for a command, use the <B>vos help</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Specifies the keyword string to match. Use lowercase letters only,
-except for the acronym <B>VLDB</B>. If the string is more than a
-single word, surround it with double quotes ("") or other delimiters.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first line of a command's online help entry names it and briefly
-describes its function. This command displays the first line for any
-<B>vos</B> command where the string specified with the <B>-topic</B>
-argument is part of the command name or first line.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays all <B>vos</B> commands that include the
-word <B>lock</B> in their names or short descriptions:
-<PRE> % <B>vos apropos lock</B>
- lock: lock VLDB entry for a volume
- unlock: release lock on VLDB entry for a volume
- unlockvldb: unlock all the locked entries in the VLDB
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf262.htm#HDRVOS_HELP">vos help</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf253.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf255.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf254.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf256.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_BACKUP" HREF="auarf002.htm#ToC_269">vos backup</A></H2>
-<A NAME="IDX5596"></A>
-<A NAME="IDX5597"></A>
-<A NAME="IDX5598"></A>
-<A NAME="IDX5599"></A>
-<A NAME="IDX5600"></A>
-<A NAME="IDX5601"></A>
-<A NAME="IDX5602"></A>
-<A NAME="IDX5603"></A>
-<A NAME="IDX5604"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a backup volume for a single read/write volume
-<P><STRONG>Synopsis</STRONG>
-<PRE>
-<B>vos backup -id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos backup -i</B> <<VAR>volume name or ID</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos backup</B> command clones the indicated read/write volume to
-create a backup version, placing it at the same site as the read/write
-version. The backup volume's name is the same as the read/write
-source's with the addition of the <B>.backup</B>
-extension. Its volume ID number is the one allocated for it in the
-Volume Location Database (VLDB) when the read/write source was created with
-the <B>vos create</B> command. If a backup version already exists,
-the new clone replaces it.
-<P>To create a backup version of multiple volumes, use the <B>vos
-backupsys</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of the read/write
-source volume.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The following message confirms that the command succeeded:
-<PRE> Created backup volume for <VAR>volume name</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example creates a backup version of the volume
-<B>user.smith</B>.
-<PRE> % <B>vos backup user.smith</B>
- Created backup volume for user.smith
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf256.htm#HDRVOS_BACKUPSYS">vos backupsys</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf254.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf256.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf255.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf257.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_BACKUPSYS" HREF="auarf002.htm#ToC_270">vos backupsys</A></H2>
-<A NAME="IDX5605"></A>
-<A NAME="IDX5606"></A>
-<A NAME="IDX5607"></A>
-<A NAME="IDX5608"></A>
-<A NAME="IDX5609"></A>
-<A NAME="IDX5610"></A>
-<A NAME="IDX5611"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a backup volume for several read/write volumes
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos backupsys</B> [<B>-prefix</B> <<VAR>common prefix on volume(s)</VAR>><SUP>+</SUP>]
- [<B>-server</B> <<VAR>machine name</VAR>>] [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-exclude</B>] [<B>-xprefix</B> <<VAR>negative prefix on volume(s)</VAR>><SUP>+</SUP>]
- [<B>-dryrun</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>]
- [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos backups</B> [<B>-pr</B> <<VAR>common prefix on volume(s)</VAR>><SUP>+</SUP>] [<B>-s</B> <<VAR>machine name</VAR>>]
- [<B>-pa</B> <<VAR>partition name</VAR>>] [<B>-e</B>] [<B>-x</B> <<VAR>negative prefix on volume(s)</VAR>><SUP>+</SUP>]
- [<B>-d</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos backupsys</B> command clones each indicated read/write
-volume to create a backup version, placing each clone at the same site as its
-read/write source version. It assigns each clone the same name as the
-read/write source, adding a <B>.backup</B> extension. It
-assigns the volume ID number already allocated for the backup version in the
-Volume Location Database (VLDB). If a backup version already exists for
-a given volume, the new clone replaces it.
-<P>To clone every read/write volume listed in the VLDB, omit all of the
-command's options. Otherwise, combine the command's options
-to clone various groups of volumes. The options use one of two basic
-criteria to select volumes: location (the <B>-server</B> and
-<B>-partition</B> arguments) or presence in the volume name of one of a
-set of specified character strings (the <B>-prefix</B>,
-<B>-exclude</B>, and <B>-xprefix</B> options).
-<P>To clone only volumes that reside on one file server machine, include the
-<B>-server</B> argument. To clone only volumes that reside on one
-partition, combine the <B>-server</B> and <B>-partition</B>
-arguments. The <B>-partition</B> argument can also be used alone to
-clone volumes that reside on the indicated partition on every file server
-machine. These arguments can be combined with those that select volumes
-based on their names.
-<P>Combine the <B>-prefix</B>, <B>-exclude</B>, and
-<B>-xprefix</B> options (with or without the <B>-server</B> and
-<B>-partition</B> arguments) in the indicated ways to select volumes based
-on character strings contained in their names:
-<UL>
-<P><LI>To clone every read/write volume at the specified location whose name
-includes one of a set of specified character strings (for example, begins with
-<B>user.</B> or includes the string <B>afs</B>), use the
-<B>-prefix</B> argument or combine the <B>-xprefix</B> and
-<B>-exclude</B> options.
-<P><LI>To clone every read/write volume at the specified location except those
-whose name includes one of a set of specified character strings, use the
-<B>-xprefix</B> argument or combine the <B>-prefix</B> and
-<B>-exclude</B> options.
-<P><LI>To clone every read/write volume at the specified location whose name
-includes one of one of a set of specified character strings, except those
-whose names include one of a different set of specified character strings,
-combine the <B>-prefix</B> and <B>-xprefix</B> arguments. The
-command creates a list of all volumes that match the <B>-prefix</B>
-argument and then removes from the list the volumes that match the
-<B>-xprefix</B> argument. For effective results, the strings
-specified by the <B>-xprefix</B> argument must designate a subset of the
-volumes specified by the <B>-prefix</B> argument.
-<P>If the <B>-exclude</B> flag is combined with the <B>-prefix</B> and
-<B>-xprefix</B> arguments, the command creates a list of all volumes that
-do not match the <B>-prefix</B> argument and then adds to the list any
-volumes that match the <B>-xprefix</B> argument. As when the
-<B>-exclude</B> flag is not used, the result is effective only if the
-strings specified by the <B>-xprefix</B> argument designate a subset of
-the volumes specified by the <B>-prefix</B> argument.
-</UL>
-<P>The <B>-prefix</B> and <B>-xprefix</B> arguments both accept
-multiple values, which can be used to define disjoint groups of
-volumes. Each value can be one of two types:
-<OL TYPE=1>
-<P><LI>A simple character string, which matches volumes whose name begin with the
-string. All characters are interpreted literally (that is, characters
-that potentially have special meaning to the command shell, such as the
-period, have only their literal meaning).
-<P><LI>A regular expression, which matches volumes whose names contain the
-expressions. Place a caret ( <B>^</B> ) at the
-beginning of the expression, and enclose the entire string in single quotes
-(<B>'</B> <B>'</B>). Explaining regular
-expressions is outside the scope of this reference page; see the UNIX
-manual page for <B>regexp(5)</B> or (for a brief introduction) the
-<B>backup addvolentry</B> reference page in this document. As an
-example, the following expression matches volumes that have the string
-<B>aix</B> anywhere in their names:
-<PRE> <B>-prefix '^.*aix'</B>
-</PRE>
-</OL>
-<P>To display a list of the volumes to be cloned, without actually cloning
-them, include the <B>-dryrun</B> flag. To display a statement that
-summarizes the criteria being used to select volume, include the
-<B>-verbose</B> flag.
-<P>This command can be used to clone a single read/write volume; specify
-its complete name as the <B>-prefix</B> argument. However, it is
-more efficient to use the <B>vos backup</B> command, which employs a more
-streamlined technique for finding a single volume.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-prefix
-</B><DD>Specifies one or more simple character strings or regular expressions of
-any length; a volume whose name includes the string is placed on the set
-of volumes to be cloned. Include field separators (such as periods) if
-appropriate. This argument can be combined with any combination of the
-<B>-server</B>, <B>-partition</B>, <B>-exclude</B>, and
-<B>-xprefix</B> options.
-<P><DT><B>-server
-</B><DD>Identifies the file server machine where each read/write source volume
-resides. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P>This argument can be combined with any combination of the
-<B>-prefix</B>, <B>-partition</B>, <B>-exclude</B>, and
-<B>-xprefix</B> options.
-<P><DT><B><B>-partition</B>
-</B><DD>Identifies the partition where each read/write source volume
-resides. Provide the partition's complete name with preceding
-slash (for example, <B>/vicepa</B>) or use one of the three acceptable
-abbreviated forms. For details, see the introductory reference page for
-the <B>vos</B> command suite.
-<P>This argument can be combined with any combination of the
-<B>-prefix</B>, <B>-server</B>, <B>-exclude</B>, and
-<B>-xprefix</B> options.
-<P><DT><B>-exclude
-</B><DD>Reverses the meaning of the <B>-prefix</B> or <B>-xprefix</B>
-argument. This flag can be combined with any combination of the
-<B>-prefix</B>, <B>-server</B>, <B>-partition</B>, and
-<B>-xprefix</B> options.
-<P><DT><B>-xprefix
-</B><DD>Specifies a simple character string or regular expression of any
-length; a volume whose name includes the string is removed from the set
-of volumes to be cloned. Include field separators (such as periods) if
-appropriate. This argument can be combined with any combination of the
-<B>-prefix</B>, <B>-server</B>, <B>-partition</B>, and
-<B>-exclude</B> options.
-<P><DT><B>-dryrun
-</B><DD>Displays on the standard output stream a list of the volumes to be cloned,
-without actually cloning them.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The command generates the following messages on the standard output stream
-to confirm that the operation was successful:
-<PRE> done
- Total volumes backed up: <VAR>number_cloned</VAR>; failed to backup: <VAR>failures</VAR>
-</PRE>
-<P>If the <B>-dryrun</B> flag is included, a list of the volumes to be
-backed up precedes the standard confirmation messages.
-<P>If the <B>-verbose</B> flag is included but not the <B>-dryrun</B>
-flag, the following messages appear for each volume. The output
-concludes with the standard confirmation messages.
-<PRE> Creating backup volume for <VAR>volume_name</VAR> on <VAR>date/time</VAR>
- {Recloning backup volume | Creating a new backup clone} <VAR>backup_volumeID</VAR> . . .done
-</PRE>
-<P>If both the <B>-dryrun</B> and <B>-verbose</B> flags are included,
-the output begins with a statement summarizing the criteria being used to
-select the volumes, followed by a list of the volumes and the standard
-confirmation messages. The format of the criteria summary statement
-depends on which other options are provided:
-<UL>
-<P><LI>If only the <B>-prefix</B> argument is provided, or the
-<B>-xprefix</B> and <B>-exclude</B> options are combined:
-<PRE> Would have backed up volumes which are prefixed with <VAR>string</VAR> [or<VAR>string</VAR>] . .
-</PRE>
-<P><LI>If only the <B>-xprefix</B> argument is provided, or the
-<B>-prefix</B> and <B>-exclude</B> options are combined:
-<PRE> Would have backed up volumes which are not prefixed with <VAR>string</VAR> [nor<VAR>string</VAR>] . .
-</PRE>
-<P><LI>If the <B>-prefix</B> and <B>-xprefix</B> arguments are
-combined:
-<PRE> Would have backed up volumes which are prefixed with <VAR>string</VAR> [or<VAR>string</VAR>] \
- removing those which are prefixed with <VAR>x_string</VAR> [or<VAR>x_string</VAR>] . .
-</PRE>
-<P><LI>If the <B>-prefix</B>, <B>-xprefix</B>, and <B>-exclude</B>
-options are provided:
-<PRE> Would have backed up volumes which are not prefixed with <VAR>string</VAR> [nor<VAR>string</VAR>] \
- adding those which are prefixed with <VAR>x_string</VAR> [or<VAR>x_string</VAR>] . .
-</PRE>
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example creates a backup version of every read/write volume
-listed in the cell's VLDB whose name begins with the string
-<B>user</B>.
-<PRE> % <B>vos backupsys -prefix user</B>
-
-</PRE>
-<P>The following example, appropriate in the ABC Corporation cell, creates a
-backup version of every read/write volume on the file server machine
-<B>fs3.abc.com</B>.
-<PRE> % <B>vos backupsys -server fs3.abc.com</B>
-
-</PRE>
-<P>The following example, appropriate in the State University cell, creates a
-backup version of every read/write volume on the file server machine
-<B>db1.stateu.edu</B> except those whose name includes the
-string <B>temp</B>.
-<PRE> % <B>vos backupsys -server db1.stateu.edu -prefix '^.*temp'</B>
-
-</PRE>
-<P>The following example creates a backup version of every volume listed in
-the cell's VLDB, excluding those whose names contain the string
-<B>source</B>, but including those whose names contain the string
-<B>source.current</B>.
-<PRE> % <B>vos backupsys -prefix '^.*source' -exclude -xprefix '^.*source\.current'</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf063.htm#HDRBK_ADDVOLENTRY">backup addvolentry</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P>UNIX manual page for <B>regexp(5)</B>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf255.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf257.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf256.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf258.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_CHANGEADDR" HREF="auarf002.htm#ToC_271">vos changeaddr</A></H2>
-<A NAME="IDX5612"></A>
-<A NAME="IDX5613"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Changes or removes a file server machine's entry in the VLDB
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos changeaddr -oldaddr</B> <<VAR>original IP address</VAR>> [<B>-newaddr</B> <<VAR>new IP address</VAR>>]
- [<B>-remove</B>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>]
- [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos ch -o</B> <<VAR>original IP address</VAR>> [<B>-ne</B> <<VAR>new IP address</VAR>>] [<B>-r</B>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos changeaddr</B> command removes a server entry from the
-Volume Location Database (VLDB) when the <B>-remove</B> flag is combined
-with the <B>-oldaddr</B> argument. There must be no VLDB entries
-that list the machine as a site for any version of a volume (if necessary, use
-the <B>vos move</B> or <B>vos remove</B> command to more or remove
-volumes). It is appropriate to remove a VLDB server entry when removing
-the corresponding file server machine from service; this is the only
-recommended use of the command.
-<P>To display all VLDB server entries, use the <B>vos listaddrs</B>
-command.
-<P><STRONG>Cautions</STRONG>
-<P>Combining the command's <B>-oldaddr</B> and <B>-newaddr</B>
-arguments is no longer the appropriate way to change the IP address registered
-for a file server machine. Furthermore, if a machine is multihomed and
-its server entry includes several addresses, then the address specified with
-the <B>-newaddr</B> argument replaces all of the addresses currently
-listed in the server entry that includes the address specified by the
-<B>-oldaddr</B> argument. This effectively makes the machine
-single-homed with respect to AFS operations, which is probably not the desired
-result.
-<P>The recommended method for changing the IP addresses in a server entry is
-instead to restart the <B>fs</B> process group (which includes the File
-Server) after using the utilities provided by the operating system to
-reconfigure the machine's network interfaces. For a description of
-how the File Server constructs and registers a list of its network interfaces
-in the VLDB, see the reference page for the <B>sysid</B> file.
-<P>If, counter to recommended usage, the command is used to change the IP
-address in a server entry, it does not also change the names of machine
-entries in the Protection Database. Operations fail when they refer to
-a protection group that has an obsolete IP address in it. Use the
-<B>pts rename</B> command to change the names of machine entries that
-correspond to the addresses changed with this command. Changing the
-address of a database server machine also requires updating the client and
-server versions of the <B>CellServDB</B> file on every machine.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-oldaddr
-</B><DD>Specifies the IP address currently registered for the file server machine
-in the VLDB server entry. If there are multiple addresses registered
-for a multihomed machine, use any of them to identify the server entry.
-<P><DT><B>-newaddr
-</B><DD>Specifies the new IP address that replaces all currently registered
-addresses.
-<P><DT><B>-remove
-</B><DD>Removes from the VLDB the server entry that includes the address specified
-by the <B>-oldaddr</B> argument.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the VLDB server entry that includes the IP
-address <B>192.12.107.214</B>.
-<PRE> % <B>vos changeaddr -oldaddr 192.12.107.214 -remove</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>Issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on the
-machine specified with the <B>-oldaddr</B> argument and on each database
-server machine.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf019.htm#HDRCLI_CSDB">CellServDB (client version)</A>
-<P><A HREF="auarf020.htm#HDRSV_CSDB">CellServDB (server version)</A>
-<P><A HREF="auarf035.htm#HDRUSERLIST">UserList</A>
-<P><A HREF="auarf049.htm#HDRSYSID">sysid</A>
-<P><A HREF="auarf129.htm#HDRFILESERVER">fileserver</A>
-<P><A HREF="auarf224.htm#HDRPTS_RENAME">pts rename</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf263.htm#HDRVOS_LISTADDRS">vos listaddrs</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf256.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf258.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf257.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf259.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_CREATE" HREF="auarf002.htm#ToC_272">vos create</A></H2>
-<A NAME="IDX5614"></A>
-<A NAME="IDX5615"></A>
-<A NAME="IDX5616"></A>
-<A NAME="IDX5617"></A>
-<A NAME="IDX5618"></A>
-<A NAME="IDX5619"></A>
-<A NAME="IDX5620"></A>
-<A NAME="IDX5621"></A>
-<A NAME="IDX5622"></A>
-<A NAME="IDX5623"></A>
-<A NAME="IDX5624"></A>
-<A NAME="IDX5625"></A>
-<A NAME="IDX5626"></A>
-<A NAME="IDX5627"></A>
-<A NAME="IDX5628"></A>
-<A NAME="IDX5629"></A>
-<A NAME="IDX5630"></A>
-<A NAME="IDX5631"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Creates a read/write volume and associated VLDB entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos create -server</B> <<VAR>machine name</VAR>> <B>-partition</B> <<VAR>partition name</VAR>>
- <B>-name</B> <<VAR>volume name</VAR>> [<B>-maxquota</B> <<VAR>initial quota (KB)</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos cr -s</B> <<VAR>machine name</VAR>> <B>-p</B> <<VAR>partition name</VAR>> <B>-na</B> <<VAR>volume name</VAR>>
- [<B>-m</B> <<VAR>initial quota (KB)</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-no</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos create</B> command creates a read/write volume with the name
-specified by the <B>-name</B> argument at the site specified by the
-<B>-server</B> and <B>-partition</B> arguments. In addition,
-the command allocates or sets the following:
-<UL>
-<P><LI>Volume ID numbers for the read/write volume and its associated read-only
-and backup volumes (this command does not actually create the latter two types
-of volume). A volume ID number is an identification number guaranteed
-to be unique within a cell.
-<A NAME="IDX5632"></A>
-<A NAME="IDX5633"></A>
-<A NAME="IDX5634"></A>
-<A NAME="IDX5635"></A>
-<A NAME="IDX5636"></A>
-<A NAME="IDX5637"></A>
-<P><LI>An access control list (ACL) associated with the volume's root
-directory, which takes the same name as volume's mount point when the
-volume is mounted with the <B>fs mkmount</B> command. An entry that
-grants all seven permissions to the members of the
-<B>system:administrators</B> group is automatically placed on the
-ACL. (In addition, the File Server by default always implicitly grants
-the <B>l</B> (<B>lookup</B>) and <B>a</B> (<B>administer</B>)
-permissions on every ACL to members of the
-<B>system:administrators</B> group, even when the group does not
-appear on an ACL; use the <B>-implicit</B> argument to the
-<B>fileserver</B> initialization command to alter the set of rights on a
-server-by-server basis if desired.)
-<P><LI>The volume's space quota, set to 5000 kilobyte blocks by
-default. Use the <B>-maxquota</B> argument to specify a different
-quota, or use the <B>fs setquota</B> command to change the volume's
-quota after mounting the volume with the <B>fs mkmount</B> command.
-</UL>
-<P>The volume is empty when created. To access it via the Cache
-Manager, mount it in the file space by using the <B>fs mkmount</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine on which to create the read/write
-volume. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition on which to create the read/write volume, on the
-file server machine specified by the <B>-server</B> argument.
-Provide the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-name
-</B><DD>Specifies a name for the read/write volume. The maximum length is
-22 characters, which can include any alphanumeric or punctuation
-character. By convention, periods separate the fields in a name.
-Do not apply the <B>.backup</B> or <B>.readonly</B>
-extension to a read/write volume name; they are reserved for the Volume
-Server to add to the read/write name when creating those backup and read-only
-volumes respectively.
-<P><DT><B>-maxquota
-</B><DD>Specifies the maximum amount of disk space the volume can use, as a number
-of kilobyte blocks (a value of <B>1024</B> is one megabyte). The
-value <B>0</B> (zero) grants an unlimited quota, but the size of the disk
-partition that houses the volume places an absolute limit on its size.
-If this argument is omitted, the default value is <B>5000</B>.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The Volume Server produces the following message to confirm that it created
-the volume:
-<PRE> Volume <VAR>volume_ID</VAR> created on partition <VAR>partition_name</VAR> of <VAR>machine_name</VAR>
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command creates the read/write volume
-<B>user.pat</B> on the <B>/vicepf</B> partition of the file
-server machine <B>fs4.abc.com</B>.
-<PRE> % <B>vos create -server fs4.abc.com -partition /vicepf -name user.pat</B>
- Volume user.pat created on partition /vicepf of fs4.abc.com
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf257.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf259.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf258.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf260.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_DELENTRY" HREF="auarf002.htm#ToC_273">vos delentry</A></H2>
-<A NAME="IDX5638"></A>
-<A NAME="IDX5639"></A>
-<A NAME="IDX5640"></A>
-<A NAME="IDX5641"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a volume entry from the VLDB.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos delentry</B> [<B>-id</B> <<VAR>volume name or ID</VAR>><SUP>+</SUP>]
- [<B>-prefix</B> <<VAR>prefix of volume whose VLDB entry is to be deleted</VAR>>]
- [<B>-server</B> <<VAR>machine name</VAR>>] [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos de</B> [<B>-i</B> <<VAR>volume name or ID</VAR>><SUP>+</SUP>]
- [<B>-pr</B> <<VAR>prefix of volume whose VLDB entry is to be deleted</VAR>>]
- [<B>-s</B> <<VAR>machine name</VAR>>] [<B>-pa</B> <<VAR>partition name</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos delentry</B> command removes the Volume Location Database
-(VLDB) entry for each specified volume. A specified volume can be any
-of the three types (read/write, read-only, or backup), but the entire entry is
-removed no matter which type is provided. The command has no effect on
-the actual volumes on file server machines, if they exist.
-<P>This command is useful if a volume removal operation did not update the
-VLDB (perhaps because the <B>vos zap</B> command was used), but the system
-administrator does not feel it is necessary to use the <B>vos syncserv</B>
-and <B>vos syncvldb</B> commands to synchronize an entire file server
-machine.
-<P>To remove the VLDB entry for a single volume, use the <B> -id</B>
-argument. To remove groups of volumes, combine the <B> -prefix</B>,
-<B>-server</B>, and <B>-partition</B> arguments. The following
-list describes how to remove the VLDB entry for the indicated group of
-volumes:
-<UL>
-<P><LI>For every volume whose name begins with a certain character string (for
-example, <B>sys.</B> or <B>user.</B>): use the
-<B>-prefix</B> argument.
-<P><LI>Every volume for which the VLDB lists a site on a certain file server
-machine: specify the file server name with the <B>-server</B>
-argument.
-<P><LI>Every volume for which the VLDB lists a site on a partition of the same
-name (for instance, on the <B>/vicepa</B> partition on any file server
-machine): specify the partition name with the <B> -partition</B>
-argument.
-<P><LI>Every volume for which the VLDB lists a site one a specific partition of a
-file server machine: specify both the <B>-server</B> and
-<B>-partition</B> arguments.
-<P><LI>Every volume whose name begins with a certain prefix and for which the
-VLDB lists a site on a file server machine: combine the
-<B>-prefix</B> and <B>-server</B> arguments. Combine the
-<B>-prefix</B> argument with the <B>-partition</B> argument, or both
-the <B>-server</B> and <B>-partition</B> arguments, to remove a more
-specific group of volumes.
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command to remove a volume in normal circumstances; it
-does not remove a volume from the file server machine, and so is likely to
-make the VLDB inconsistent with state of the volumes on server
-machines. Use the <B>vos remove</B> command to remove both the
-volume and its VLDB entry.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies the complete name or the volume ID number of each volume for
-which to remove the VLDB entry. The entire entry is removed, regardless
-of whether the read/write, read-only, or backup version is indicated.
-Provide this argument or some combination of the <B>-prefix</B>,
-<B>-server</B>, and <B>-partition</B> arguments.
-<P><DT><B>-prefix
-</B><DD>Specifies a character string of any length; the VLDB entry for a
-volume whose name begins with the string is removed. Include field
-separators (such as periods) if appropriate. Combine this argument with
-the <B>-server</B> argument, <B>-partition</B> argument, or
-both.
-<P><DT><B>-server
-</B><DD>Identifies a file server machine; if a volume's VLDB entry lists
-a site on the machine, the entry is removed. Provide the machine's
-IP address or its host name (either fully qualified or using an unambiguous
-abbreviation). For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P>Combine this argument with the <B>-prefix</B> argument, the
-<B>-partition</B> argument, or both.
-<P><DT><B>-partition
-</B><DD>Identifies a partition; if a volume's VLDB entry lists a site on
-the partition, the entry is removed. Provide the partition's
-complete name with preceding slash (for example, <B>/vicepa</B>) or use
-one of the three acceptable abbreviated forms. For details, see the
-introductory reference page for the <B>vos</B> command suite.
-<P>Combine this argument with the <B>-prefix</B> argument, the
-<B>-server</B> argument, or both.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The following message confirms the success of the command by indicating how
-many VLDB entries were removed.
-<PRE> Deleted <VAR>number</VAR> VLDB entries
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the VLDB entry for the volume
-<B>user.temp</B>.
-<PRE> % <B>vos delentry user.temp</B>
-
-</PRE>
-<P>The following command removes the VLDB entry for every volume whose name
-begins with the string <B>test</B> and for which the VLDB lists a site on
-the file server machine <B>fs3.abc.com</B>.
-<PRE> % <B>vos delentry -prefix test -server fs3.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P><A HREF="auarf276.htm#HDRVOS_SYNCSERV">vos syncserv</A>
-<P><A HREF="auarf277.htm#HDRVOS_SYNCVLDB">vos syncvldb</A>
-<P><A HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf258.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf260.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf259.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf261.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_DUMP" HREF="auarf002.htm#ToC_274">vos dump</A></H2>
-<A NAME="IDX5642"></A>
-<A NAME="IDX5643"></A>
-<A NAME="IDX5644"></A>
-<A NAME="IDX5645"></A>
-<A NAME="IDX5646"></A>
-<A NAME="IDX5647"></A>
-<A NAME="IDX5648"></A>
-<A NAME="IDX5649"></A>
-<A NAME="IDX5650"></A>
-<A NAME="IDX5651"></A>
-<A NAME="IDX5652"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Converts a volume into ASCII format and writes it to a file
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos dump -id</B> <<VAR>volume name or ID</VAR>> [<B>-time</B> <<VAR>dump from time</VAR>>] [<B>-file</B> <<VAR>dump file</VAR>>]
- [<B>-server</B> <<VAR>server</VAR>>] [<B>-partition</B> <<VAR>partition</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos du -i</B> <<VAR>volume name or ID</VAR>> [<B>-t</B> <<VAR>dump from time</VAR>>] [<B>-f</B> <<VAR>dump file</VAR>>]
- [<B>-s</B> <<VAR>server</VAR>>] [<B>-p</B> <<VAR>partition</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos dump</B> command converts the contents of the indicated
-volume, which can be read/write, read-only or backup, into ASCII
-format. The Volume Server writes the converted contents to the file
-named by the <B>-file</B> argument, or to the standard output
-stream. In the latter case, the output can be directed to a named pipe,
-which enables interoperation with third-party backup utilities.
-<P>To dump the complete contents of a volume (create a <I>full dump</I>),
-omit the <B>-time</B> argument or specify the value <B>0</B> (zero)
-for it. To create an <I>incremental dump</I>, which includes only
-the files and directories in the volume that have modification timestamps
-later than a certain time, specify a date and time as the value for the
-<B>-time</B> argument.
-<P>By default, the <B>vos</B> command interpreter consults the Volume
-Location Database (VLDB) to learn the volume's location, so the
-<B>-server</B> and <B>-partition</B> arguments are not
-required. If the <B>-id</B> argument identifies a read-only volume
-that resides at multiple sites, the command dumps the version from just one of
-them (normally, the one listed first in the volume's VLDB entry as
-reported by the <B>vos examine</B> or <B>vos listvldb</B>
-command). To dump the read-only volume from a particular site, use the
-<B>-server</B> and <B>-partition</B> arguments to specify the
-site. To bypass the VLDB lookup entirely, provide a volume ID number
-(rather than a volume name) as the value for the <B>-id</B> argument,
-together with the <B>-server</B> and <B>-partition</B>
-arguments. This makes it possible to dump a volume for which there is
-no VLDB entry.
-<P>During the dump operation, the volume is inaccessible both to Cache
-Managers and to other volume operations. Dumping a volume does not
-otherwise affect its status on the partition or its VLDB entry.
-<P>To restore a dumped volume back into AFS, use the <B>vos restore</B>
-command.
-<P><STRONG>Cautions</STRONG>
-<P>Support for incremental dumps is provided to facilitate interoperation with
-third-party backup utilities. The <B>vos dump</B> command does not
-provide any of the administrative facilities of an actual backup system, so
-the administrator must keep manual records of dump times and the relationship
-between full and incremental dumps of a volume. For a volume's
-contents to be consistent after restoration of incremental dumps, there must
-be no gap between the time at which a prior dump of the volume was created and
-the value of the <B>-time</B> argument to the <B>vos dump</B> command
-that creates the incremental dump. More specifically, for a read/write
-volume, the <B>-time</B> argument must specify the time that the prior
-dump was performed, and for a read-only or backup volume it must specify the
-time that the volume was last released (using the <B>vos release</B>
-command) or cloned (using the <B>vos backup</B> or <B>vos
-backupsys</B> command) prior to dumping it. The parent dump can be
-either a full dump or another incremental dump.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of the read/write,
-read-only, or backup volume to dump.
-<P><DT><B>-time
-</B><DD>Specifies whether the dump is full or incremental. Omit this
-argument to create a full dump, or provide one of three acceptable
-values:
-<UL>
-<P><LI>The value <B>0</B> (zero) to create a full dump.
-<P><LI>A date in the format
-<VAR>mm</VAR><B>/</B><VAR>dd</VAR><B>/</B><VAR>yyyy</VAR> (month, day and
-year) to create an incremental dump that includes only files and directories
-with modification timestamps later than midnight (12:00
-a.m.) on the indicated date. Valid values for the year
-range from <B>1970</B> to <B>2037</B>; higher values are not
-valid because the latest possible date in the standard UNIX representation is
-in 2038. The command interpreter automatically reduces later dates to
-the maximum value. An example is <B>01/13/1999</B>.
-<P><LI>A date and time in the format
-<B>"</B><VAR>mm</VAR><B>/</B><VAR>dd</VAR><B>/</B><VAR>yyyy</VAR>
-<VAR>hh</VAR><B>:</B><VAR>MM</VAR><B>"</B> to create an incremental
-dump that includes only files and directories with modification timestamps
-later than the specified date and time. The date format is the same as
-for a date alone. Express the time as hours and minutes
-(<VAR>hh</VAR>:<VAR>MM</VAR>) in 24-hour format (for example,
-<B>20:30</B> is 8:30 p.m.). Surround the
-entire expression with double quotes (" ") because it contains a space.
-An example is <B>"01/13/1999 22:30"</B>.
-</UL>
-<P><DT><B>-file
-</B><DD>Specifies the pathname of the file to which to write the dump. The
-file can be in AFS, but not in the volume being dumped. A partial
-pathname is interpreted relative to the current working directory. If
-this argument is omitted, the dump is directed to the standard output
-stream.
-<P><DT><B>-server
-</B><DD>Specifies the file server machine on which the volume resides.
-Provide the <B>-partition</B> argument along with this one.
-<P><DT><B>-partition
-</B><DD>Specifies the partition on which the volume resides. Provide the
-<B>-server</B> argument along with this one.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command writes a full dump of the volume
-<B>user.terry</B> to the file
-<B>/afs/abc.com/common/dumps/terry.dump</B>.
-<PRE> % <B>vos dump -id user.terry -time 0 -file /afs/abc.com/common/dumps/terry.dump</B>
-
-</PRE>
-<P>The following command writes an incremental dump of the volume
-<B>user.smith</B> to the file
-<B>smith.990131.dump</B> in the current working
-directory. Only those files in the volume with modification time stamps
-later than 6:00 p.m. on 31 January 1999 are included in
-the dump.
-<PRE> % <B>vos dump -id user.smith -time "01/31/1999 18:00" -file smith.990131.dump</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P>If the <B>-file</B> argument is included, the issuer must also have
-permission to insert and write in the directory that houses the file.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P><A HREF="auarf274.htm#HDRVOS_RESTORE">vos restore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf259.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf261.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf260.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf262.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_EXAMINE" HREF="auarf002.htm#ToC_275">vos examine</A></H2>
-<A NAME="IDX5653"></A>
-<A NAME="IDX5654"></A>
-<A NAME="IDX5655"></A>
-<A NAME="IDX5656"></A>
-<A NAME="IDX5657"></A>
-<A NAME="IDX5658"></A>
-<A NAME="IDX5659"></A>
-<A NAME="IDX5660"></A>
-<A NAME="IDX5661"></A>
-<A NAME="IDX5662"></A>
-<A NAME="IDX5663"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays information from the volume header and VLDB entry for a
-volume.
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos examine -id</B> <<VAR>volume name or ID</VAR>> [<B>-extended</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos e -i</B> <<VAR>volume name or ID</VAR>> [<B>-e</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-
-<B>vos volinfo -i</B> <<VAR>volume name or ID</VAR>> [<B>-e</B>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-
-<B>vos v -i</B> <<VAR>volume name or ID</VAR>> [<B>-e</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos examine</B> command formats and displays information from
-the Volume Location Database (VLDB) entry and the volume header of the volume
-specified by the <B>-id</B> argument.
-<P>To display the volume header only, use the <B>vos listvol</B>
-command. To display information from the VLDB only, use the <B>vos
-listvldb</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of the volume,
-which can be read/write, read-only, or backup.
-<P><DT><B>-extended
-</B><DD>Display statistics about read and write operations on files and
-directories in the volume.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The first seven lines of the output show information from the volume header
-and the remaining lines come from the VLDB. Each item in the following
-list corresponds to a line of output derived from the volume header.
-<UL>
-<P><LI>Basic information about the specified volume (displayed on a single
-line):
-<UL>
-<P><LI>Name
-<P><LI>Volume ID number
-<A NAME="IDX5664"></A>
-<P><LI>Type (the flag is <TT>RW</TT> for read/write, <TT>RO</TT> for
-read-only, <TT>BK</TT> for backup)
-<P><LI>Size in kilobytes (<TT>1024</TT> equals a megabyte)
-<P><LI>Number of files in the volume, if the <B>-extended</B> flag is
-provided
-<A NAME="IDX5665"></A>
-<P><LI>Status on the file server machine, which is one of the following:
-<DL>
-<A NAME="IDX5666"></A>
-<P><DT><B><TT>On-line</TT>
-</B><DD>The volume is completely accessible to Cache Managers.
-<A NAME="IDX5667"></A>
-<P><DT><B><TT>Off-line</TT>
-</B><DD>The volume is not accessible to Cache Managers, but does not seem to be
-corrupted. This status appears while a volume is being dumped, for
-example.
-<A NAME="IDX5668"></A>
-<P><DT><B><TT>Off-line**needs salvage**</TT>
-</B><DD>The volume is not accessible to Cache Managers, because it seems to be
-corrupted. Use the <B>bos salvage</B> or <B>salvager</B>
-command to repair the corruption.
-</DL>
-</UL>
-<P><LI>The file server machine and partition that house the volume, as determined
-by the command interpreter as the command runs, rather than derived from the
-VLDB or the volume header.
-<A NAME="IDX5669"></A>
-<A NAME="IDX5670"></A>
-<A NAME="IDX5671"></A>
-<A NAME="IDX5672"></A>
-<A NAME="IDX5673"></A>
-<A NAME="IDX5674"></A>
-<A NAME="IDX5675"></A>
-<A NAME="IDX5676"></A>
-<P><LI>The volume ID numbers associated with the various versions of the
-volume: read/write (<TT>RWrite</TT>), read-only (<TT>ROnly</TT>),
-backup (<TT>Backup</TT>), and ReleaseClone (<TT>RClone</TT>). One
-of them matches the volume ID number that appears on the first line of the
-volume's output. If the value in the <TT>RWrite</TT>,
-<TT>ROnly</TT>, or <TT>Backup</TT> field is <TT>0</TT> (zero), there is
-no volume of that type. If there is currently no ReleaseClone, the
-<TT>RClone</TT> field does not appear at all.
-<A NAME="IDX5677"></A>
-<A NAME="IDX5678"></A>
-<P><LI>The maximum space quota allotted to the read/write copy of the volume,
-expressed in kilobyte blocks in the <TT>MaxQuota</TT> field.
-<A NAME="IDX5679"></A>
-<A NAME="IDX5680"></A>
-<P><LI>The date and time the volume was created, in the <TT>Creation</TT>
-field. If the volume has been restored with the <B>backup
-diskrestore</B>, <B>backup volrestore</B>, or <B>vos restore</B>
-command, this is the restore time.
-<A NAME="IDX5681"></A>
-<A NAME="IDX5682"></A>
-<P><LI>The date and time when the contents of the volume last changed, in the
-<TT>Last Update</TT> field. For read-only and backup volumes, it
-matches the timestamp in the <TT>Creation</TT> field.
-<A NAME="IDX5683"></A>
-<A NAME="IDX5684"></A>
-<P><LI>The number of times the volume has been accessed for a fetch or store
-operation since the later of the two following times:
-<UL>
-<P><LI>12:00 a.m. on the day the command is issued
-<P><LI>The last time the volume changed location
-</UL>
-</UL>
-<P>When the <B>-extended</B> flag is included, two tables appear
-next:
-<UL>
-<P><LI>The table labeled <TT>Raw Read/Write Stats</TT> contains information on
-the number of reads (fetches) and writes (stores) made on the specified
-volume.
-<P><LI>The table labeled <TT>Writes Affecting Authorship</TT> contains
-information on writes made to files and directories in the specified
-volume.
-</UL>
-<P>If the following message appears instead of the previously listed
-information, it indicates that a volume is not accessible to Cache Managers or
-the <B>vos</B> command interpreter, for example because a clone is being
-created.
-<PRE> **** Volume <VAR>volume_ID</VAR> is busy ****
-</PRE>
-<P>If the following message appears instead of the previously listed
-information, it indicates that the File Server is unable to attach the volume,
-perhaps because it is seriously corrupted. The <B>FileLog</B> and
-<B>VolserLog</B> log files in the <B>/usr/afs/logs</B> directory on
-the file server machine possibly provide additional information; use the
-<B>bos getlog</B> command to display them.
-<PRE> **** Could not attach volume <VAR>volume_ID</VAR> ****
-</PRE>
-<P>Following a blank line, information from the VLDB entry appears.
-Each item in this list corresponds to a separate line in the output:
-<UL>
-<P><LI>The base (read/write) volume name. The read-only and backup
-versions have the same name with a <B>.readonly</B> and
-<B>.backup</B> extension, respectively.
-<P><LI>The volume ID numbers allocated to the versions of the volume that
-actually exist, in fields labeled <TT>RWrite</TT> for the read/write,
-<TT>ROnly</TT> for the read-only, <TT>Backup</TT> for the backup, and
-<TT>RClone</TT> for the ReleaseClone. (If a field does not appear,
-the corresponding version of the volume does not exist.) The appearance
-of the <TT>RClone</TT> field normally indicates that a release operation did
-not complete successfully; the <TT>Old release</TT> and <TT>New
-release</TT> flags often also appear on one or more of the site definition
-lines described just following.
-<A NAME="IDX5685"></A>
-<A NAME="IDX5686"></A>
-<P><LI>The number of sites that house a read/write or read-only copy of the
-volume, following the string <TT>number of sites -></TT>.
-<A NAME="IDX5687"></A>
-<A NAME="IDX5688"></A>
-<A NAME="IDX5689"></A>
-<A NAME="IDX5690"></A>
-<A NAME="IDX5691"></A>
-<P><LI>A line for each site that houses a read/write or read-only copy of the
-volume, specifying the file server machine, partition, and type of volume
-(<TT>RW</TT> for read/write or <TT>RO</TT> for read-only). If a
-backup version exists, it is understood to share the read/write site.
-Several flags can appear with a site definition:
-<DL>
-<A NAME="IDX5692"></A>
-<P><DT><B><TT>Not released</TT>
-</B><DD>Indicates that the <B>vos release</B> command has not been issued
-since the <B>vos addsite</B> command was used to define the read-only
-site.
-<A NAME="IDX5693"></A>
-<P><DT><B><TT>Old release</TT>
-</B><DD>Indicates that a <B>vos release</B> command did not complete
-successfully, leaving the previous, obsolete version of the volume at this
-site.
-<A NAME="IDX5694"></A>
-<P><DT><B><TT>New release</TT>
-</B><DD>Indicates that a <B>vos release</B> command did not complete
-successfully, but that this site did receive the correct new version of the
-volume.
-</DL>
-<P><LI>If the VLDB entry is locked, the string <TT>Volume is currently
-LOCKED</TT>.
-</UL>
-<P>For further discussion of the <TT>New release</TT> and <TT>Old
-release</TT> flags, see the reference page for the <B>vos release</B>
-command.
-<P><STRONG>Examples</STRONG>
-<P>The following example shows output for the ABC Corporation volume called
-<B>usr</B> with two read-only replication sites (this volume is mounted at
-the <B>/afs/abc.com/usr</B> directory). For the sake of
-illustration, the output shows the volume as locked.
-<PRE> % <B>vos examine usr</B>
- usr 536870981 RW 3459 K On-line
- fs2.abc.com /vicepb
- RWrite 5360870981 ROnly 536870982 Backup 536870983
- MaxQuota 40000 K
- Creation Mon Jun 12 15:22:06 1989
- Last Update Fri Jun 16 09:34:35 1989
- 5719 accesses in the past day (i.e., vnode references)
- RWrite: 5360870981 ROnly: 536870982 Backup: 536870983
- number of sites -> 3
- server fs1.abc.com partition /vicepa RO Site
- server fs3.abc.com partition /vicepa RO Site
- server fs2.abc.com partition /vicepb RW Site
- Volume is currently LOCKED
-
-</PRE>
-<P>The following example shows the output for the volume
-<B>user.terry</B> using the <B>-extended</B> flag. The
-volume has no read-only replication sites.
-<PRE> %<B> vos examine -id user.terry -extended</B>
- user.terry 354287190 RW 2302 K used 119 files On-line
- fs4.abc.com /vicepc
- RWrite 354287190 ROnly 0 Backup 354287192
- MaxQuota 5000 K
- Creation Wed Nov 25 17:38:57 1992
- Last Update Tue Dec 15 10:46:20 1992
- 598 accesses in the past day (i.e., vnode references)
- Raw Read/Write Stats
- |-------------------------------------------|
- | Same Network | Diff Network |
- |----------|----------|----------|----------|
- | Total | Auth | Total | Auth |
- |----------|----------|----------|----------|
- Reads | 55 | 55 | 38 | 38 |
- Writes | 95 | 95 | 0 | 0 |
- |-------------------------------------------|
- Writes Affecting Authorship
- |-------------------------------------------|
- | File Authorship | Directory Authorship|
- |----------|----------|----------|----------|
- | Same | Diff | Same | Diff |
- |----------|----------|----------|----------|
- 0-60 sec | 38 | 0 | 21 | 1 |
- 1-10 min | 2 | 0 | 7 | 0 |
- 10min-1hr | 0 | 0 | 1 | 0 |
- 1hr-1day | 1 | 0 | 5 | 1 |
- 1day-1wk | 0 | 0 | 0 | 0 |
- > 1wk | 0 | 0 | 0 | 0 |
- |-------------------------------------------|
- RWrite: 354287190 Backup: 354287192
- number of sites -> 1
- server fs4.abc.com partition /vicepc RW Site
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P><A HREF="auarf274.htm#HDRVOS_RESTORE">vos restore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf260.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf262.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf261.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf263.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_HELP" HREF="auarf002.htm#ToC_276">vos help</A></H2>
-<A NAME="IDX5695"></A>
-<A NAME="IDX5696"></A>
-<A NAME="IDX5697"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays the syntax of specified <B>vos</B> commands or functional
-descriptions for all <B>vos</B> commands
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos help</B> [<B>-topic</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-help</B>]
-
-<B>vos h</B> [<B>-t</B> <<VAR>help string</VAR>><SUP>+</SUP>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos help</B> command displays the complete online help entry
-(short description and syntax statement) for each command operation code
-specified by the <B>-topic</B> argument. If the <B>-topic</B>
-argument is omitted, the output includes the first line (name and short
-description) of the online help entry for every <B>vos</B> command.
-<P>To list every <B>vos</B> command whose name or short description
-includes a specified keyword, use the <B>vos apropos</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-topic
-</B><DD>Identifies each command for which to display the complete online help
-entry. Omit the <B>vos</B> part of the command name, providing only
-the operation code (for example, specify <B>create</B>, not <B>vos
-create</B>). If this argument is omitted, the output briefly
-describes every <B>vos</B> command.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The online help entry for each <B>vos</B> command consists of the
-following two or three lines:
-<UL>
-<P><LI>The first line names the command and briefly describes its
-function.
-<P><LI>The second line lists aliases for the command, if any.
-<P><LI>The final line, which begins with the string <TT>Usage</TT>, lists the
-command's options in the prescribed order. Online help entries use
-the same symbols (for example, brackets) as the reference pages in this
-document.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the online help entry for the <B>vos
-create</B> command:
-<PRE> % <B>vos help create</B>
- vos create: create a new volume
- Usage: vos create -server <machine name> -partition <partition name>
- -name <volume name> [-cell <cell name>] [-noauth] [-localauth]
- [-verbose] [-help]
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf254.htm#HDRVOS_APROPOS">vos apropos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf261.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf263.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf262.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf264.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_LISTADDRS" HREF="auarf002.htm#ToC_277">vos listaddrs</A></H2>
-<A NAME="IDX5698"></A>
-<A NAME="IDX5699"></A>
-<A NAME="IDX5700"></A>
-<A NAME="IDX5701"></A>
-<A NAME="IDX5702"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays all VLDB server entries
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos listaddrs</B> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos lista</B> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos listaddrs</B> command displays all of the server entries
-from the Volume Location Database (VLDB). An entry is created as the
-File Server initializes and registers the contents of its
-<B>/usr/afs/local/sysid</B> file in the VLDB.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output displays all server entries from the VLDB, each on its own
-line. If a file server machine is multihomed, all of its registered
-addresses appear on the line. The first one is the one reported as a
-volume's site in the output from the <B>vos examine</B> and <B>vos
-listvldb</B> commands.
-<P>The VLDB records IP addresses, and the command interpreter has the local
-name service (either a process like the Domain Name Service or a local host
-table) translate them to hostnames before displaying them. If an IP
-address appears in the output, it is not possible to translate it.
-<P>The existence of an entry does not necessarily indicate that the machine
-that is still an active file server machine. To remove obsolete server
-entries, use the <B>vos changeaddr</B> command with the <B>-remove</B>
-argument.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the VLDB server entries in the ABC
-Corporation cell:
-<PRE> % <B>vos listaddrs </B>
- sv5.abc.com
- sv1.abc.com
- sv2.abc.com afs2.abc.com
- sv6.abc.com
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf049.htm#HDRSYSID">sysid</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf257.htm#HDRVOS_CHANGEADDR">vos changeaddr</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf262.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf264.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf263.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf265.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_LISTPART" HREF="auarf002.htm#ToC_278">vos listpart</A></H2>
-<A NAME="IDX5703"></A>
-<A NAME="IDX5704"></A>
-<A NAME="IDX5705"></A>
-<A NAME="IDX5706"></A>
-<A NAME="IDX5707"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays all AFS partitions on a file server machine
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos listpart -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos listp -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos listpart</B> command displays all of the valid AFS
-partitions on the indicated file server machine, without consulting the Volume
-Location Database (VLDB). The <B>vos partinfo</B> command reports
-the size of a partition and the available space on that partition.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine for which to list the
-partitions. Provide the machine's IP address or its host name
-(either fully qualified or using an unambiguous abbreviation). For
-details, see the introductory reference page for the <B>vos</B> command
-suite.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output consists of a list of partition names of the form
-<B>/vicep</B><VAR>xx</VAR>, following the header:
-<PRE> The partitions on the server are:
-
-</PRE>
-<P>The last line of the output reports the total number of partitions.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays the partitions on
-<B>fs1.abc.com</B>:
-<PRE> % <B>vos listpart fs1.abc.com</B>
- The partitions on the server are:
- /vicepa /vicepb /vicepc /vicepd
- Total: 4
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf269.htm#HDRVOS_PARTINFO">vos partinfo</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf263.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf265.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf264.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf266.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_LISTVLDB" HREF="auarf002.htm#ToC_279">vos listvldb</A></H2>
-<A NAME="IDX5708"></A>
-<A NAME="IDX5709"></A>
-<A NAME="IDX5710"></A>
-<A NAME="IDX5711"></A>
-<A NAME="IDX5712"></A>
-<A NAME="IDX5713"></A>
-<A NAME="IDX5714"></A>
-<A NAME="IDX5715"></A>
-<A NAME="IDX5716"></A>
-<A NAME="IDX5717"></A>
-<A NAME="IDX5718"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays a volume's VLDB entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos listvldb</B> [<B>-name</B> <<VAR>volume name or ID</VAR>>] [<B>-server</B> <<VAR>machine name</VAR>>]
- [<B>-partition</B> <<VAR>partition name</VAR>>] [<B>-locked</B>] [<B>-quiet</B>] [<B>-nosort</B>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos listvl</B> [<B>-na</B> <<VAR>volume name or ID</VAR>>] [<B>-s</B> <<VAR>machine name</VAR>>]
- [<B>-p</B> <<VAR>partition name</VAR>>] [<B>-lock</B>] [<B>-q</B>] [<B>-nos</B>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-noa</B>] [<B>-loca</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos listvldb</B> command formats and displays information from
-the Volume Location Database (VLDB) entry for each volume specified.
-The output depends on the combination of options supplied on the command
-line. Combine options as indicated to display the desired type of VLDB
-entries:
-<UL>
-<P><LI>Every entry in the VLDB: provide no options
-<P><LI>Every VLDB entry that mentions a certain file server machine as the site
-for a volume: specify the machine's name as the <B>-server</B>
-argument
-<P><LI>Every VLDB entry that mentions a certain partition on any file server
-machine as the site for a volume: specify the partition name as the
-<B>-partition</B> argument
-<P><LI>Every VLDB entry that mentions a certain partition on a certain file
-server machine as the site for a volume: combine the <B>-server</B>
-and <B>-partition</B> arguments
-<P><LI>A single VLDB entry: specify a volume name or ID number with the
-<B>-name</B> argument
-<P><LI>The VLDB entry only for the volumes with locked VLDB entries found at a
-certain site: combine the <B>-locked</B> flag with any of arguments
-that define sites
-</UL>
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-name
-</B><DD>Specifies either the complete name or volume ID number of a volume of any
-of the three types.
-<P><DT><B>-server
-</B><DD>Identifies the file server machine listed as a site in each VLDB entry to
-display. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P>This argument can be combined with the <B>-partition</B> argument, the
-<B>-locked</B> flag, or both.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) listed as a site in each VLDB entry to
-display. Provide the partition's complete name with preceding
-slash (for example, <B>/vicepa</B>) or use one of the three acceptable
-abbreviated forms. For details, see the introductory reference page for
-the <B>vos</B> command suite.
-<P>This argument can be combined with the <B>-server</B> argument, the
-<B>-locked</B> flag, or both.
-<P><DT><B>-locked
-</B><DD>Displays only locked VLDB entries. This flag can be combined with
-the <B>-server</B> argument, the <B>-partition</B> argument, or
-both.
-<P><DT><B>-quiet
-</B><DD>Suppresses the lines that summarize the number of volumes listed and their
-status, which otherwise appear at the beginning and end of the output when the
-output includes more than one volume.
-<P><DT><B>-nosort
-</B><DD>Suppresses the default sorting of volume entries alphabetically by volume
-name.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>If the output includes more than one VLDB entry, by default the first line
-reports which file server machine, partition, or both, houses the
-volumes. The final line of output reports the total number of entries
-displayed. Including the <B>-quiet</B> flag suppresses these
-lines.
-<P>By default, volumes are sorted alphabetically by volume name.
-Including the <B>-nosort</B> flag skips the sorting step, which can speed
-up the production of output if there are a large number of entries.
-<P>The VLDB entry for each volume includes the following information:
-<UL>
-<P><LI>The base (read/write) volume name. The read-only and backup
-versions have the same name with a <B>.readonly</B> and
-<B>.backup</B> extension, respectively.
-<P><LI>The volume ID numbers allocated to the versions of the volume that
-actually exist, in fields labeled <TT>RWrite</TT> for the read/write,
-<TT>ROnly</TT> for the read-only, <TT>Backup</TT> for the backup, and
-<TT>RClone</TT> for the ReleaseClone. (If a field does not appear,
-the corresponding version of the volume does not exist.) The appearance
-of the <TT>RClone</TT> field normally indicates that a release operation did
-not complete successfully; the <TT>Old release</TT> and <TT>New
-release</TT> flags often also appear on one or more of the site definition
-lines described just following.
-<A NAME="IDX5719"></A>
-<A NAME="IDX5720"></A>
-<P><LI>The number of sites that house a read/write or read-only copy of the
-volume, following the string <TT>number of sites -></TT>.
-<A NAME="IDX5721"></A>
-<A NAME="IDX5722"></A>
-<A NAME="IDX5723"></A>
-<A NAME="IDX5724"></A>
-<A NAME="IDX5725"></A>
-<P><LI>A line for each site that houses a read/write or read-only copy of the
-volume, specifying the file server machine, partition, and type of volume
-(<TT>RW</TT> for read/write or <TT>RO</TT> for read-only). If a
-backup version exists, it is understood to share the read/write site.
-Several flags can appear with a site definition:
-<DL>
-<A NAME="IDX5726"></A>
-<P><DT><B><TT>Not released</TT>
-</B><DD>Indicates that the <B>vos release</B> command has not been issued
-since the <B>vos addsite</B> command was used to define the read-only
-site.
-<A NAME="IDX5727"></A>
-<P><DT><B><TT>Old release</TT>
-</B><DD>Indicates that a <B>vos release</B> command did not complete
-successfully, leaving the previous, obsolete version of the volume at this
-site.
-<A NAME="IDX5728"></A>
-<P><DT><B><TT>New release</TT>
-</B><DD>Indicates that a <B>vos release</B> command did not complete
-successfully, but that this site did receive the correct new version of the
-volume.
-</DL>
-<P><LI>If the VLDB entry is locked, the string <TT>Volume is currently
-LOCKED</TT>.
-</UL>
-<P>For further discussion of the <TT>New release</TT> and <TT>Old
-release</TT> flags, see the reference page for the <B>vos release</B>
-command.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays VLDB information for the ABC Corporation
-volume called <B>usr</B>, which has two read-only replication sites:
-<PRE> % <B>vos listvldb -name usr</B>
- usr
- RWrite: 5360870981 ROnly: 536870982 Backup: 536870983
- number of sites -> 3
- server fs1.abc.com partition /vicepa RO Site
- server fs3.abc.com partition /vicepa RO Site
- server fs2.abc.com partition /vicepb RW Site
-
-</PRE>
-<P>The following example shows entries for two of the volumes that reside on
-the file server machine <B>fs4.abc.com</B>. The first
-VLDB entry is currently locked. There are 508 entries that mention the
-machine as a volume site.
-<PRE> % <B>vos listvldb -server fs4.abc.com</B>
- VLDB entries for server fs4.abc.com
- . . . .
- . . . .
- user.smith
- RWrite: 278541326 ROnly: 278541327 Backup: 278542328
- number of sites -> 1
- server fs4.abc.com partition /vicepg RW Site
- Volume is currently LOCKED
- user.terry
- RWrite 354287190 ROnly 354287191 Backup 354287192
- number of sites -> 1
- server fs4.abc.com partition /vicepc RW Site
- . . . .
- . . . .
- Total entries: 508
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P><A HREF="auarf267.htm#HDRVOS_LOCK">vos lock</A>
-<P><A HREF="auarf278.htm#HDRVOS_UNLOCK">vos unlock</A>
-<P><A HREF="auarf279.htm#HDRVOS_UNLOCKVLDB">vos unlockvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf264.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf266.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf265.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf267.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_LISTVOL" HREF="auarf002.htm#ToC_280">vos listvol</A></H2>
-<A NAME="IDX5729"></A>
-<A NAME="IDX5730"></A>
-<A NAME="IDX5731"></A>
-<A NAME="IDX5732"></A>
-<A NAME="IDX5733"></A>
-<A NAME="IDX5734"></A>
-<A NAME="IDX5735"></A>
-<A NAME="IDX5736"></A>
-<A NAME="IDX5737"></A>
-<A NAME="IDX5738"></A>
-<A NAME="IDX5739"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays information from a volume header
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos listvol -server</B> <<VAR>machine name</VAR>> [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-fast</B>] [<B>-long</B>] [<B>-quiet</B>] [<B>-extended</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos listvo -s</B> <<VAR>machine name</VAR>> [<B>-p</B> <<VAR>partition name</VAR>>] [<B>-f</B>] [<B>-lon</B>]
- [<B>-q</B>] [<B>-e</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-loc</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos listvol</B> command formats and displays the following
-information from the volume header of each specified volume: volume
-name, volume ID, volume type, size, and status at the server. The
-actual information displayed depends on the combination of arguments supplied
-when the command is issued. To display volume header information for
-various numbers of volumes, combine the command's arguments as
-indicated:
-<UL>
-<P><LI>For every volume on a file server machine, specify the machine's name
-with the <B>-server</B> argument.
-<P><LI>For every volume at a particular site, combine the <B>-server</B>
-argument with the <B>-partition</B> argument.
-</UL>
-<P>To display the Volume Location Database (VLDB) entry for one or more
-volumes, use the <B>vos listvldb</B> command. To display both the
-VLDB entry and the volume header for a single volume, use the <B>vos
-examine</B> command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine that houses volumes for which to
-display the header. Provide the machine's IP address or its host
-name (either fully qualified or using an unambiguous abbreviation). For
-details, see the introductory reference page for the <B>vos</B> command
-suite.
-<P>This argument can be combined with the <B>-partition</B> argument, as
-well as the <B>-fast</B>, <B>-long</B>, or <B>-extended</B>
-flag.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) that houses volumes for which to display the
-header. Provide the partition's complete name with preceding slash
-(for example, <B>/vicepa</B>) or use one of the three acceptable
-abbreviated forms. For details, see the introductory reference page for
-the <B>vos</B> command suite.
-<P><DT><B>-fast
-</B><DD>Displays only the volume ID numbers of volumes stored at the site
-specified by the <B>-server</B>, and optionally <B>-partition</B>,
-argument. Do not combine this flag with the <B>-extended</B>
-flag.
-<P><DT><B>-long
-</B><DD>Displays more detailed information about each volume stored at the site
-specified by the <B>-server</B>, and optionally <B>-partition</B>,
-argument. The information includes the volume IDs of all three volume
-types associated with the volume, and the read/write volume's quota,
-creation date and update date.
-<P><DT><B>-quiet
-</B><DD>Suppresses the lines that summarize the number of volumes listed and their
-status, which otherwise appear at the beginning and end of the output when the
-output includes more than one volume.
-<P><DT><B>-extended
-</B><DD>Displays extensive statistics about access patterns for each volume stored
-at the site specified by the <B>-server</B>, and optionally
-<B>-partition</B>, argument. The statistics include the number of
-reads and writes to files in the volume, and how recently files and
-directories have been updated by their owners or other users. Do not
-combine this flag with the <B>-fast</B> flag.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The output is ordered alphabetically by volume name and by default provides
-the following information on a single line for each volume:
-<UL>
-<P><LI>Name
-<P><LI>Volume ID number
-<A NAME="IDX5740"></A>
-<P><LI>Type (the flag is <TT>RW</TT> for read/write, <TT>RO</TT> for
-read-only, <TT>BK</TT> for backup)
-<P><LI>Size in kilobytes (<TT>1024</TT> equals a megabyte)
-<P><LI>Number of files in the volume, if the <B>-extended</B> flag is
-provided
-<A NAME="IDX5741"></A>
-<P><LI>Status on the file server machine, which is one of the following:
-<DL>
-<A NAME="IDX5742"></A>
-<P><DT><B><TT>On-line</TT>
-</B><DD>The volume is completely accessible to Cache Managers.
-<A NAME="IDX5743"></A>
-<P><DT><B><TT>Off-line</TT>
-</B><DD>The volume is not accessible to Cache Managers, but does not seem to be
-corrupted. This status appears while a volume is being dumped, for
-example.
-<A NAME="IDX5744"></A>
-<P><DT><B><TT>Off-line**needs salvage**</TT>
-</B><DD>The volume is not accessible to Cache Managers, because it seems to be
-corrupted. Use the <B>bos salvage</B> or <B>salvager</B>
-command to repair the corruption.
-</DL>
-</UL>
-<P>If the following message appears instead of the previously listed
-information, it indicates that a volume is not accessible to Cache Managers or
-the <B>vos</B> command interpreter, for example because a clone is being
-created.
-<PRE> **** Volume <VAR>volume_ID</VAR> is busy ****
-</PRE>
-<P>If the following message appears instead of the previously listed
-information, it indicates that the File Server is unable to attach the volume,
-perhaps because it is seriously corrupted. The <B>FileLog</B> and
-<B>VolserLog</B> log files in the <B>/usr/afs/logs</B> directory on
-the file server machine possibly provide additional information; use the
-<B>bos getlog</B> command to display them.
-<PRE> **** Could not attach volume <VAR>volume_ID</VAR> ****
-</PRE>
-<P>The information about individual volumes is bracketed by summary
-lines. The first line of output specifies the number of volumes in the
-listing. The last line of output summarizes the number of volumes that
-are online, offline, and busy. These lines do not appear if the
-<B>-quiet</B> flag is used.
-<P>If the <B>-fast</B> flag is added, the output displays only the volume
-ID number of each volume, arranged in increasing numerical order. The
-final line (which summarizes the number of online, offline, and busy volumes)
-is omitted.
-<P>If the <B>-long</B> flag is included, the output for each volume
-includes all of the information in the default listing plus the
-following. Each item in this list corresponds to a separate line of
-output:
-<UL>
-<P><LI>The file server machine and partition that house the volume, as determined
-by the command interpreter as the command runs, rather than derived from the
-VLDB or the volume header.
-<A NAME="IDX5745"></A>
-<A NAME="IDX5746"></A>
-<A NAME="IDX5747"></A>
-<A NAME="IDX5748"></A>
-<A NAME="IDX5749"></A>
-<A NAME="IDX5750"></A>
-<A NAME="IDX5751"></A>
-<A NAME="IDX5752"></A>
-<P><LI>The volume ID numbers associated with the various versions of the
-volume: read/write (<TT>RWrite</TT>), read-only (<TT>ROnly</TT>),
-backup (<TT>Backup</TT>), and ReleaseClone (<TT>RClone</TT>). One
-of them matches the volume ID number that appears on the first line of the
-volume's output. If the value in the <TT>RWrite</TT>,
-<TT>ROnly</TT>, or <TT>Backup</TT> field is <TT>0</TT> (zero), there is
-no volume of that type. If there is currently no ReleaseClone, the
-<TT>RClone</TT> field does not appear at all.
-<A NAME="IDX5753"></A>
-<A NAME="IDX5754"></A>
-<P><LI>The maximum space quota allotted to the read/write copy of the volume,
-expressed in kilobyte blocks in the <TT>MaxQuota</TT> field.
-<A NAME="IDX5755"></A>
-<A NAME="IDX5756"></A>
-<P><LI>The date and time the volume was created, in the <TT>Creation</TT>
-field. If the volume has been restored with the <B>backup
-diskrestore</B>, <B>backup volrestore</B>, or <B>vos restore</B>
-command, this is the restore time.
-<A NAME="IDX5757"></A>
-<A NAME="IDX5758"></A>
-<P><LI>The date and time when the contents of the volume last changed, in the
-<TT>Last Update</TT> field. For read-only and backup volumes, it
-matches the timestamp in the <TT>Creation</TT> field.
-<A NAME="IDX5759"></A>
-<A NAME="IDX5760"></A>
-<P><LI>The number of times the volume has been accessed for a fetch or store
-operation since the later of the two following times:
-<UL>
-<P><LI>12:00 a.m. on the day the command is issued
-<P><LI>The last time the volume changed location
-</UL>
-</UL>
-<P>If the <B>-extended</B> flag is included, the output for each volume
-includes all of the information reported with the <B>-long</B> flag, plus
-two tables of statistics:
-<UL>
-<P><LI>The table labeled <TT>Raw Read/Write Stats</TT> table summarizes the
-number of times the volume has been accessed for reading or writing.
-<P><LI>The table labeled <TT>Writes Affecting Authorship</TT> table contains
-information on writes made to files and directories in the specified
-volume.
-</UL>
-<P><STRONG>Examples</STRONG>
-<P>The following example shows the output for the <B>/vicepb</B> partition
-on the file server machine <B>fs2.abc.com</B> when no flags
-are provided:
-<PRE> % <B>vos listvol -server fs2.abc.com -partition b</B>
- Total number of volumes on server fs2.abc.com \
- partition /vicepb : 66
- sys 1969534847 RW 1582 K On-line
- sys.backup 1969535105 BK 1582 K On-line
- . . . . . .
- . . . . . .
- user.pat 1969534536 RW 17518 K On-line
- user.pat.backup 1969534538 BK 17537 K On-line
- Total volumes onLine 66 ; Total volumes offLine 0 ; Total busy 0
-
-</PRE>
-<P>The following example shows the output when the <B>-fast</B> flag is
-added:
-<PRE> % <B>vos listvol -server fs2.abc.com -partition b -fast</B>
- Total number of volumes on server fs2.abc.com \
- partition /vicepb : 66
- 1969516782
- 1969516784
- .
- .
- 1969535796
-
-</PRE>
-<P>The following example shows two volumes from the output that appears when
-the <B>-long</B> flag is added:
-<PRE> % <B>vos listvol -server fs2.abc.com -partition b -long</B>
- Total number of volumes on server fs2.abc.com \
- partition /vicepb: 66
- . . . . . .
- . . . . . .
- user.pat 1969534536 RW 17518 K On-line
- fs2.abc.com /vicepb
- RWrite 1969534536 ROnly 0 Backup 1969534538
- MaxQuota 20000 K
- Creation Mon Jun 12 09:02:25 1989
- Last Update Thu May 20 17:39:34 1999
- 1573 accesses in the past day (i.e., vnode references)
- user.pat.backup 1969534538 BK 17537 K On-line
- fs2.abc.com /vicepb
- RWrite 1969534536 ROnly 0 Backup 1969534538
- MaxQuota 20000 K
- Creation Tue Jun 13 04:37:59 1989
- Last Update Wed May 19 06:37:59 1999
- 0 accesses in the past day (i.e., vnode references)
- . . . . . .
- . . . . . .
- Total volumes onLine 66 ; Total volumes offLine 0 ; \
- Total busy 0
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf072.htm#HDRBK_DISKRESTORE">backup diskrestore</A>
-<P><A HREF="auarf091.htm#HDRBK_VOLRESTORE">backup volrestore</A>
-<P><A HREF="auarf102.htm#HDRBOS_GETLOG">bos getlog</A>
-<P><A HREF="auarf114.htm#HDRBOS_SALVAGE">bos salvage</A>
-<P><A HREF="auarf232.htm#HDRSALVAGER">salvager</A>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P><A HREF="auarf274.htm#HDRVOS_RESTORE">vos restore</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf265.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf267.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf266.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf268.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_LOCK" HREF="auarf002.htm#ToC_281">vos lock</A></H2>
-<A NAME="IDX5761"></A>
-<A NAME="IDX5762"></A>
-<A NAME="IDX5763"></A>
-<A NAME="IDX5764"></A>
-<A NAME="IDX5765"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Locks a VLDB volume entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos lock -id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos lo -i</B> <<VAR>volume name or ID</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos lock</B> command locks the Volume Location Database (VLDB)
-entry for the indicated volume, blocking any operation that requires a write
-to that entry. The lock applies to all of the volume versions
-associated with the entry, not just the one specified with the <B>-id</B>
-argument.
-<P>To unlock a single VLDB entry, use the <B>vos unlock</B>
-command. To unlock several entries, or all locked entries in the VLDB,
-use the <B>vos unlockvldb</B> command.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command in normal circumstances. It is useful for
-guaranteeing that the volume stays unchanged when there is reason to believe
-that volume operations cannot properly lock VLDB volume entries as they
-normally do to synchronize with one another.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of a volume of the
-any of the three types.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command locks the VLDB entry for
-<B>user.terry</B>.
-<PRE> % <B>vos lock user.terry</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf278.htm#HDRVOS_UNLOCK">vos unlock</A>
-<P><A HREF="auarf279.htm#HDRVOS_UNLOCKVLDB">vos unlockvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf266.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf268.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf267.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf269.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_MOVE" HREF="auarf002.htm#ToC_282">vos move</A></H2>
-<A NAME="IDX5766"></A>
-<A NAME="IDX5767"></A>
-<A NAME="IDX5768"></A>
-<A NAME="IDX5769"></A>
-<A NAME="IDX5770"></A>
-<A NAME="IDX5771"></A>
-<A NAME="IDX5772"></A>
-<A NAME="IDX5773"></A>
-<A NAME="IDX5774"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Moves a read/write volume to another site
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos move -id</B> <<VAR>volume name or ID</VAR>> <B>-fromserver</B> <<VAR>machine name on source</VAR>>
- <B>-frompartition</B> <<VAR>partition name on source</VAR>>
- <B>-toserver</B> <<VAR>machine name on destination</VAR>>
- <B>-topartition</B> <<VAR>partition name on destination</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos m -i</B> <<VAR>volume name or ID</VAR>> <B>-froms</B> <<VAR>machine name on source</VAR>>
- <B>-fromp</B> <<VAR>partition name on source</VAR>> <B>-tos</B> <<VAR>machine name on destination</VAR>>
- <B>-top</B> <<VAR>partition name on destination</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos move</B> command moves the indicated read/write volume from
-its current site (specified with the <B>-fromserver</B> and
-<B>-frompartition</B> arguments) to the destination site (specified with
-the <B>-toserver</B> and <B>-topartition</B> arguments). This
-command automatically removes the backup copy from the current site, if it
-exists. To create a new backup volume at the destination site, use the
-<B>vos backup</B> command.
-<P>This command works on read/write volumes only. To move a read-only
-volume, use the <B>vos addsite</B> and <B>vos release</B> commands to
-define a new read-only site and release the volume contents to it, and then
-use the <B>vos remove</B> command to remove the previous read-only
-volume's definition from the Volume Location Database (VLDB) and data
-from the partition. To move a backup volume, use this command to move
-its read/write source and then issue the <B>vos backup</B> command.
-<P>Before executing this command, the <B>vos</B> command interpreter
-initiates a check that the destination partition contains enough space to
-house the volume being moved. If there is not enough space, the move
-operation is not attempted and the following message appears:
-<PRE> vos: no space on target partition <VAR>dest_part</VAR> to move volume <VAR>volume</VAR>
-
-</PRE>
-<P><STRONG>Cautions</STRONG>
-<P>Unless there is a compelling reason, do not interrupt a <B>vos move</B>
-command in progress. Interrupting a move can result in one or more of
-the following inconsistent states:
-<UL>
-<P><LI>There are two versions of the volume, one at the source site and one at
-the destination site. (If this happens, retain the version identified
-by the VLDB and use the <B>vos zap</B> command to remove the other
-version.)
-<P><LI>The backup version of the volume is stranded at the old site. (If
-this happens, use the <B>vos zap</B> command to remove it.)
-<P><LI>The volume is off-line. (If this happens, run the <B>bos
-salvage</B> command to bring it back on line.)
-</UL>
-<P>If the <<B>Ctrl-c</B>> interrupt signal is pressed while a <B>vos
-move</B> operation is executing, the following message warns of the
-consequences and requests confirmation of the kill signal:
-<PRE> SIGINT handler: vos move operation in progress
- WARNING: may leave AFS storage and metadata in indeterminate state
- enter second control-c to exit
-
-</PRE>
-<P>To confirm termination of the operation, press <<B>Ctrl-c</B>> a
-second time; press any other key to continue the operation.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of a read/write
-volume.
-<P><DT><B>-fromserver
-</B><DD>Identifies the file server machine where the volume currently
-resides. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-frompartition
-</B><DD>Names the partition where the volume currently resides. Provide the
-full partition name (for, example, <B>/vicepa</B>) or one of the
-abbreviated forms described on the introductory <B>vos</B> reference
-page.
-<P><DT><B>-toserver
-</B><DD>Identifies the file server machine to which to move the volume.
-Provide the machine's IP address or its host name (either fully qualified
-or using an unambiguous abbreviation). For details, see the
-introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-topartition
-</B><DD>Names the partition to which to move the volume. Provide the full
-partition name (for, example, <B>/vicepa</B>) or one of the abbreviated
-forms described on the introductory <B>vos</B> reference page.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example moves the volume <B>user.smith</B> from
-the <B>/vicepb</B> partition on the file server machine
-<B>fs3.abc.com</B> to the <B>/vicepg</B> partition on
-the file server machine <B>fs7.abc.com</B>.
-<PRE> % <B>vos move -id user.smith -fromserver fs3.abc.com -frompartition b</B> \
- <B>-toserver fs7.abc.com -topartition g</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machines specified with the <B>-toserver</B> and
-<B>-fromserver</B> arguments and on each database server machine.
-If the <B>-localauth</B> flag is included, the issuer must instead be
-logged on to a server machine as the local superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf253.htm#HDRVOS_ADDSITE">vos addsite</A>
-<P><A HREF="auarf255.htm#HDRVOS_BACKUP">vos backup</A>
-<P><A HREF="auarf270.htm#HDRVOS_RELEASE">vos release</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf267.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf269.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf268.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf270.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_PARTINFO" HREF="auarf002.htm#ToC_283">vos partinfo</A></H2>
-<A NAME="IDX5775"></A>
-<A NAME="IDX5776"></A>
-<A NAME="IDX5777"></A>
-<A NAME="IDX5778"></A>
-<A NAME="IDX5779"></A>
-<A NAME="IDX5780"></A>
-<A NAME="IDX5781"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports the available and total space on a partition
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos partinfo -server</B> <<VAR>machine name</VAR>> [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos p -s</B> <<VAR>machine name</VAR>> [<B>-p</B> <<VAR>partition name</VAR>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos partinfo</B> command reports the amount of space available
-and total size on <B>either</B> all of the partitions on the indicated
-file server machine (if the <B>-partition</B> argument is omitted)
-<B>or</B> the specified partition on that file server machine. The
-Volume Location Database (VLDB) is not consulted.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine for which to display partition
-information. Provide the machine's IP address or its host name
-(either fully qualified or using an unambiguous abbreviation). For
-details, see the introductory reference page for the <B>vos</B> command
-suite.
-<P><DT><B>-partition
-</B><DD>Identifies which partition on the file server machine specified by the
-<B>-server</B> argument for which to display information. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Cautions</STRONG>
-<P>The partition-related statistics in this command's output do not
-always agree with the corresponding values in the output of the standard UNIX
-<B>df</B> command. The statistics reported by this command can be
-up to five minutes old, because the Cache Manager polls the File Server for
-partition information at that frequency. Also, on some operating
-systems, the <B>df</B> command's report of partition size includes
-reserved space not included in this command's calculation, and so is
-likely to be about 10% larger.
-<P><STRONG>Output</STRONG>
-<P>The output reports the amount of space available and total space for each
-specified partition.
-<P><STRONG>Examples</STRONG>
-<P>The following command displays all partitions on the file server machine
-<B>fs2.abc.com</B>.
-<PRE> % <B>vos partinfo fs2.abc.com</B>
- Free space on partition /vicepa: 27301 K blocks out of total 549197
- Free space on partition /vicepb: 13646 K blocks out of total 69194
- Free space on partition /vicepc: 31798 K blocks out of total 320315
- Free space on partition /vicepd: 33302 K blocks out of total 494954
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf264.htm#HDRVOS_LISTPART">vos listpart</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf268.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf270.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf269.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf271.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_RELEASE" HREF="auarf002.htm#ToC_284">vos release</A></H2>
-<A NAME="IDX5782"></A>
-<A NAME="IDX5783"></A>
-<A NAME="IDX5784"></A>
-<A NAME="IDX5785"></A>
-<A NAME="IDX5786"></A>
-<A NAME="IDX5787"></A>
-<A NAME="IDX5788"></A>
-<A NAME="IDX5789"></A>
-<A NAME="IDX5790"></A>
-<A NAME="IDX5791"></A>
-<A NAME="IDX5792"></A>
-<A NAME="IDX5793"></A>
-<A NAME="IDX5794"></A>
-<A NAME="IDX5795"></A>
-<A NAME="IDX5796"></A>
-<A NAME="IDX5797"></A>
-<A NAME="IDX5798"></A>
-<A NAME="IDX5799"></A>
-<A NAME="IDX5800"></A>
-<A NAME="IDX5801"></A>
-<A NAME="IDX5802"></A>
-<A NAME="IDX5803"></A>
-<A NAME="IDX5804"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Updates the contents of read-only volumes to match their read/write source
-volume
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos release -id</B> <<VAR>volume name or ID</VAR>> [<B>-f</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos rel -i</B> <<VAR>volume name or ID</VAR>> [<B>-f</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos release</B> command copies the contents of the indicated
-read/write source volume to each read-only site defined in the source
-volume's Volume Location Database (VLDB) entry. (Use the <B>vos
-addsite</B> command to define sites as necessary before issuing this
-command). Each read-only copy has the same name as read/write source
-with the addition of a <B>.readonly</B> extension.
-<P>For users to have a consistent view of the file system, the release of the
-new volume version must be atomic: either all read-only sites receive
-the new version, or all sites keep the version they currently have. The
-<B>vos release</B> command is designed to ensure that all copies of the
-volume's read-only version match both the read/write source and each
-other. In cases where problems such as machine or server process
-outages prevent successful completion of the release operation, AFS uses two
-mechanisms to alert the administrator.
-<P>First, the command interpreter generates an error message on the standard
-error stream naming each read-only site that did not receive the new volume
-version. Second, during the release operation the Volume Location (VL)
-Server marks site definitions in the VLDB entry with flags (<TT>New
-release</TT> and <TT>Old release</TT>) that indicate whether or not the
-site has the new volume version. If any flags remain after the
-operation completes, it was not successful. The Cache Manager refuses
-to access a read-only site marked with the <TT>Old release</TT> flag, which
-potentially imposes a greater load on the sites marked with the <TT>New
-release</TT> flag. It is important to investigate and eliminate the
-cause of the failure and then to issue the <B>vos release</B> command as
-many times as necessary to complete the release without errors.
-<P>The pattern of site flags remaining in the volume's VLDB entry after a
-failed release operation can help determine the point at which the operation
-failed. Use the <B>vos examine</B> or <B>vos listvldb</B>
-command to display the VLDB entry. The VL Server sets the flags in
-concert with the Volume Server's operations, as follows:
-<OL TYPE=1>
-<P><LI>Before the operation begins, the VL Server sets the <TT>New release</TT>
-flag on the read/write site definition in the VLDB entry and the <TT>Old
-release</TT> flag on read-only site definitions (unless the read-only site
-has been defined since the last release operation and has no actual volume, in
-which case its site flag remains <TT>Not released</TT>).
-<P><LI>If necessary, the Volume Server creates a temporary copy (a
-<I>clone</I>) of the read/write source called the ReleaseClone (see the
-following discussion of when the Volume Server does or does not create a new
-ReleaseClone.) It assigns the ReleaseClone its own volume ID number,
-which the VL Server records in the <TT>RClone</TT> field of the source
-volume's VLDB entry.
-<P><LI>The Volume Server distributes a copy of the ReleaseClone to each read-only
-site defined in the VLDB entry. As the site successfully receives the
-new clone, the VL Server sets the site's flag in the VLDB entry to
-<TT>New release</TT>.
-<P><LI>When all the read-only copies are successfully released, the VL Server
-clears all the <TT>New release</TT> site flags. The ReleaseClone is
-no longer needed, so the Volume Server deletes it and the VL Server erases its
-ID from the VLDB entry.
-</OL>
-<P>By default, the Volume Server determines automatically whether or not it
-needs to create a new ReleaseClone:
-<UL>
-<P><LI>If there are no flags (<TT>New release</TT>, <TT>Old release</TT>, or
-<TT>Not released</TT>) on site definitions in the VLDB entry, the previous
-<B>vos release</B> command completed successfully and all read-only sites
-currently have the same volume. The Volume Server infers that the
-current <B>vos release</B> command was issued because the read/write
-volume has changed. The Volume Server creates a new ReleaseClone and
-distributes it to all of the read-only sites.
-<P><LI>If any site definition in the VLDB entry is marked with a flag, either the
-previous release operation did not complete successfully or a new read-only
-site was defined since the last release. The Volume Server does not
-create a new ReleaseClone, instead distributing the existing ReleaseClone to
-sites marked with the <TT>Old release</TT> or <TT>Not released</TT>
-flag. As previously noted, the VL Server marks each VLDB site
-definition with the <TT>New release</TT> flag as the site receives the
-ReleaseClone, and clears all flags after all sites successfully receive
-it.
-</UL>
-<P>To override the default behavior, forcing the Volume Server to create and
-release a new ReleaseClone to the read-only sites, include the <B>-f</B>
-flag. This is appropriate if, for example, the data at the read/write
-site has changed since the existing ReleaseClone was created during the
-previous release operation.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of a read/write
-volume.
-<P><DT><B>-f
-</B><DD>Creates a new ReleaseClone and distributes it all read-only sites
-regardless of whether or not any site definitions in the VLDB entry are marked
-with a flag.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command clones the read/write volume <B>usr</B> and
-releases it to the read-only sites defined in its VLDB entry.
-<PRE> % <B>vos release usr</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf253.htm#HDRVOS_ADDSITE">vos addsite</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf265.htm#HDRVOS_LISTVLDB">vos listvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf269.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf271.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf270.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf272.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_REMOVE" HREF="auarf002.htm#ToC_285">vos remove</A></H2>
-<A NAME="IDX5805"></A>
-<A NAME="IDX5806"></A>
-<A NAME="IDX5807"></A>
-<A NAME="IDX5808"></A>
-<A NAME="IDX5809"></A>
-<A NAME="IDX5810"></A>
-<A NAME="IDX5811"></A>
-<A NAME="IDX5812"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a volume from a site
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos remove</B> [<B>-server</B> <<VAR>machine name</VAR>>] [<B>-partition</B> <<VAR>partition name</VAR>>]
- <B>-id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos remo</B> [<B>-s</B> <<VAR>machine name</VAR>>] [<B>-p</B> <<VAR>partition name</VAR>>] <B>-i</B> <<VAR>volume name or ID</VAR>>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos remove</B> command removes the indicated volume from the
-partition on which it resides. The Volume Location Database (VLDB)
-record is altered appropriately, as described in the following
-paragraphs. Use this command to remove any of the three types of
-volumes; the effect depends on the type.
-<UL>
-<P><LI>If the <B>-id</B> argument names the read/write volume (that is,
-specifies the volume's base name), both it and the associated backup
-volume are removed from the partition that houses them. The
-<B>-server</B> and <B>-partition</B> arguments are optional, because
-there can be only one read/write site. When the volume is removed, the
-site information is also removed from the VLDB entry. The read/write
-and backup volume ID numbers no longer appear in the output from the <B>vos
-listvldb</B> or <B>vos examine</B> commands, but they are preserved
-internally. Read-only sites, if any, are not affected, but cannot be
-changed unless a read/write site is again defined. The site count
-reported by the <B>vos examine</B> and <B>vos listvldb</B> commands as
-<TT>number of sites</TT> decrements by one. The entire VLDB entry is
-removed if there are no read-only sites.
-<P><LI>If the <B>-id</B> argument names a read-only volume, it is removed
-from the partition that houses it, and the corresponding site information is
-removed from the VLDB entry. The site count reported by the <B>vos
-examine</B> and <B>vos listvldb</B> commands as <TT>number of
-sites</TT> decrements by one for each volume you remove. If there is
-more than one read-only site, the <B>-server</B> argument (and optionally
-<B>-partition</B> argument) must be used to specify the site from which to
-remove the volume. If there is only one read-only site, the
-<B>-id</B> argument is sufficient; if there is also no read/write
-volume in this case, the entire VLDB entry is removed.
-<P><LI>If the <B>-id</B> argument names a backup volume, it is removed from
-the partition that houses it. The <B>-server</B> and
-<B>-partition</B> arguments are optional, because there can be only one
-backup site. The backup volume ID number no longer appears in the
-output from the <B>vos listvldb</B> command or in the corresponding
-portion of the output from the <B>vos examine</B> command, but is
-preserved internally.
-</UL>
-<P>This command is the most appropriate one for removing volumes in almost all
-cases. Other commands that remove only volumes or only VLDB entries
-(such as the <B>vos delentry</B>, <B>vos remsite</B> and <B>vos
-zap</B> commands) by definition can put the volumes and VLDB out of
-sync. Use them only in the special circumstances mentioned on their
-reference pages. Like the <B>vos delentry</B> command, this command
-can remove a VLDB entry when no corresponding volumes exist on the file server
-machine. Like the <B>vos zap</B> command, this command can remove a
-volume that does not have a VLDB entry, as long as the volume is online,
-<B>-server</B> and <B>-partition</B> arguments are provided, and the
-<B>-id</B> argument specifies the volume's ID number.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine that houses the volume to
-remove. It is necessary only when the <B>-id</B> argument names a
-read-only volume that exists at multiple sites. Provide the
-machine's IP address or its host name (either fully qualified or using an
-unambiguous abbreviation). For details, see the introductory reference
-page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) that houses the volume to remove. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P>Including this argument is necessary only when the <B>-id</B> argument
-names a read-only volume that exists at multiple sites. Provide the
-<B>-server</B> argument along with this one.
-<P><DT><B>-id
-</B><DD>Identifies the volume to remove, either by its complete name or volume ID
-number. If identifying a read-only or backup volume by name, include
-the appropriate extension (<B>.readonly</B> or
-<B>.backup</B>).
-<TABLE><TR><TD ALIGN="LEFT" VALIGN="TOP"><B>Note:</B></TD><TD ALIGN="LEFT" VALIGN="TOP">If the <B>-server</B> and <B>-partition</B> arguments are omitted,
-the <B>-id</B> switch must be provided.
-</TD></TR></TABLE>
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example removes the read/write volume
-<B>user.terry</B> and its backup version, if any.
-<PRE> % <B>vos remove -id user.terry</B>
-
-</PRE>
-<P>The following example removes the read-only volume
-<B>root.afs.readonly</B> from one of its sites, the
-<B>/vicepa</B> partition on the file server machine
-<B>fs1.abc.com</B>.
-<PRE> % <B>vos remove fs1.abc.com a root.afs.readonly</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf259.htm#HDRVOS_DELENTRY">vos delentry</A>
-<P><A HREF="auarf272.htm#HDRVOS_REMSITE">vos remsite</A>
-<P><A HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf270.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf272.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf271.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf273.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_REMSITE" HREF="auarf002.htm#ToC_286">vos remsite</A></H2>
-<A NAME="IDX5813"></A>
-<A NAME="IDX5814"></A>
-<A NAME="IDX5815"></A>
-<A NAME="IDX5816"></A>
-<A NAME="IDX5817"></A>
-<A NAME="IDX5818"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a read-only site definition from a VLDB entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos remsite -server</B> <<VAR>machine name</VAR>> <B>-partition</B> <<VAR>partition name</VAR>>
- <B>-id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos rems -s</B> <<VAR>machine name</VAR>> <B>-p</B> <<VAR>partition name</VAR>> <B>-i</B> <<VAR>volume name or ID</VAR>>
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos remsite</B> command removes the read-only replication site
-specified by the <B>-machine</B> and <B>-partition</B> arguments from
-the Volume Location Database (VLDB) entry for the indicated volume, which is
-read/write.
-<P>This command is useful for removing read-only sites that were mistakenly
-created with the <B>vos addsite</B> command, before the <B>vos
-release</B> command actually releases them. If a read-only copy
-already exists at the site, it is not affected. However, if this
-read-only site was the last site housing any version of the volume, then the
-entire VLDB entry is removed, even if a copy of the read-only version still
-actually exists at the site. The VL Server does not correct the
-discrepancy until the <B>vos syncserv</B> and <B>vos syncvldb</B>
-commands are run.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command as the standard way to remove a read-only volume,
-because it can create a discrepancy between the VLDB and the volumes on file
-server machines. Use the <B>vos remove</B> command instead.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Specifies the file server machine portion of the site definition to
-remove. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Specifies the partition name portion of the site definition to
-remove. Provide the partition's complete name with preceding slash
-(for example, <B>/vicepa</B>) or use one of the three acceptable
-abbreviated forms. For details, see the introductory reference page for
-the <B>vos</B> command suite.
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of the read/write
-volume to remove.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command removes the mistakenly defined read-only site
-<B>/viceph</B> on the file server machine
-<B>fs5.abc.com</B> from the VLDB entry for the volume
-<B>root.cell</B>.
-<PRE> % <B>vos remsite -server fs5.abc.com -partition h -id root.cell</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf259.htm#HDRVOS_DELENTRY">vos delentry</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P><A HREF="auarf280.htm#HDRVOS_ZAP">vos zap</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf271.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf273.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf272.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf274.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_RENAME" HREF="auarf002.htm#ToC_287">vos rename</A></H2>
-<A NAME="IDX5819"></A>
-<A NAME="IDX5820"></A>
-<A NAME="IDX5821"></A>
-<A NAME="IDX5822"></A>
-<A NAME="IDX5823"></A>
-<A NAME="IDX5824"></A>
-<A NAME="IDX5825"></A>
-<A NAME="IDX5826"></A>
-<A NAME="IDX5827"></A>
-<A NAME="IDX5828"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Renames a volume
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos rename -oldname</B> <<VAR>old volume name</VAR>> <B>-newname</B> <<VAR>new volume name</VAR>>
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos ren -o</B> <<VAR>old volume name</VAR>> <B>-ne</B> <<VAR>new volume name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos rename</B> command changes the name of the read/write volume
-specified with the <B>-oldname</B> argument to the name specified with the
-<B>-newname</B> argument. The names of the read/write's
-read-only copies and backup copy, if any, change automatically to
-match.
-<P>After issuing this command, remember to correct any mount points that refer
-to the old volume name, by removing the old mount point with the <B>fs
-rmmount</B> command and creating a new one with the <B>fs mkmount</B>
-command.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-oldname
-</B><DD>Is the current name of the read/write volume.
-<P><DT><B>-newname
-</B><DD>Is the desired new name for the volume.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>The <B>vos rename</B> command produces no output if the command
-succeeds.
-<P>If the volume named by the <B>-oldname</B> argument does not exist, the
-following message appears:
-<PRE> vos: Could not find entry for volume <VAR>old volume name</VAR>.
-
-</PRE>
-<P><STRONG>Examples</STRONG>
-<P>The following example changes the mistaken volume name
-<B>sun4x_56.afsws</B> to the correct alternative
-<TT>sun4x_56.usr.afsws</TT>.
-<PRE> % <B>vos rename -oldname sun4x_56.afsws -newname sun4x_56.usr.afsws</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf272.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf274.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf273.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf275.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_RESTORE" HREF="auarf002.htm#ToC_288">vos restore</A></H2>
-<A NAME="IDX5829"></A>
-<A NAME="IDX5830"></A>
-<A NAME="IDX5831"></A>
-<A NAME="IDX5832"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Converts an ASCII file into proper volume format and writes it to the file
-system
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos restore -server</B> <<VAR>machine name</VAR>> <B>-partition</B> <<VAR>partition name</VAR>>
- <B>-name</B> <<VAR>name of volume to be restored</VAR>> [<B>-file</B> <<VAR>dump file</VAR>>]
- [<B>-id</B> <<VAR>volume ID</VAR>>] [<B>-overwrite</B> <<B>abort</B> | <B>full</B> | <B>incremental</B>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>]
- [<B>-help</B>]
-
-<B>vos res -s</B> <<VAR>machine name</VAR>> <B>-p</B> <<VAR>partition name</VAR>>
- <B>-na</B> <<VAR>name of volume to be restored</VAR>> [<B>-f</B> <<VAR>dump file</VAR>>]
- [<B>-i</B> <<VAR>volume ID</VAR>>] [<B>-o</B> <<B>a</B> | <B>f</B> | <B>inc</B>>] [<B>-c</B> <<VAR>cell name</VAR>>]
- [<B>-no</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos restore</B> command converts a volume dump file previously
-created with the <B>vos dump</B> command from ASCII into the volume format
-appropriate for the machine type indicated by the <B>-server</B> argument,
-and restores it as a read/write volume to the partition named by the
-<B>-partition</B> argument on that machine. The Volume Server
-assigns the volume name indicated with the <B>-name</B> argument, and
-resets the volume's creation timestamp to the time at which the restore
-operation begins (the creation timestamp is stored in the volume header and
-reported in the <TT>Creation</TT> field in the output from the <B>vos
-examine</B> and <B>vos listvol</B> commands.)
-<P>Use the <B>-file</B> argument to name the dump file, or omit the
-argument to provide the file via the standard input stream, presumably through
-a pipe. The pipe can be named, which enables interoperation with
-third-party backup utilities.
-<P>As described in the following list, the command can create a completely new
-volume or overwrite an existing volume. In all cases, the full dump of
-the volume must be restored before any incremental dumps. If there are
-multiple incremental dump files, they must be restored in the order they were
-created.
-<UL>
-<P><LI>To create a new read/write volume, use the <B>-name</B> argument to
-specify a volume name that does not already exist in the Volume Location
-Database (VLDB), and the <B>-server</B> and <B>-partition</B>
-arguments to specify the new volume's site. It is best to omit the
-<B>-id</B> argument so that the Volume Location (VL) Server allocates a
-volume ID automatically. Do not include the <B>-overwrite</B>
-argument, because there is no existing volume to overwrite.
-<P><LI>To overwrite an existing volume at its current site, specify its name and
-site with the <B>-name</B>, <B>-server</B>, and <B>-partition</B>
-arguments. The volume retains its current volume ID number unless the
-<B>-id</B> argument is provided. Specify the value <B>f</B> or
-<B>i</B> for the <B>-overwrite</B> argument to indicate whether the
-dump file is full or incremental, respectively.
-<P><LI>To overwrite an existing volume and move it to a new site, specify its
-name and the new site with the <B>-name</B>, <B>-server</B>, and
-<B>-partition</B> arguments. The volume retains its current volume
-ID number unless the <B>-id</B> argument is provided. The volume is
-removed from its original site. Specify the value <B>f</B> for the
-<B>-overwrite</B> argument to indicate that the dump file is a full dump
-(it is not possible to restore an incremental dump and move the volume at the
-same time).
-</UL>
-<P>If the volume named by the <B>-name</B> argument already exists and the
-<B>-overwrite</B> argument is omitted, the command interpreter produces
-the following prompt:
-<P>
-<PRE> Do you want to do a full/incremental restore or abort? [fia](a):
-
-</PRE>
-<P>Respond by entering one of the following values:
-<UL>
-<P><LI><B>f</B> if restoring a full dump file
-<P><LI><B>i</B> if restoring an incremental dump file
-<P><LI><B>a</B> or <<B>Return</B>> to cancel the restore operation
-</UL>
-<P><STRONG>Cautions</STRONG>
-<P>If the <B>-file</B> argument is omitted, the issuer must provide all
-other necessary arguments, because the standard input stream is unavailable
-for responding to the command interpreter's prompts for missing
-information. In particular, the issuer must provide the
-<B>-overwrite</B> argument if overwriting an existing volume.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine onto which to restore the
-volume. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) onto which to restore the volume. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-name
-</B><DD>Specifies the name under which to restore the volume. It can be up
-to 22 characters long, but cannot end with a <B>.readonly</B> or
-<B>.backup</B> extension. If the volume already exists, it
-is overwritten subject to the value of the <B>-overwrite</B>
-argument.
-<P><DT><B>-file
-</B><DD>Names the dump file to restore. Incomplete pathnames are
-interpreted relative to the current working directory. Omit this
-argument to provide the dump file via the standard input stream.
-<P><DT><B>-id
-</B><DD>Specifies the volume ID number to assign to the restored volume.
-<P><DT><B>-overwrite
-</B><DD>Specifies which type of dump file is being restored when overwriting an
-existing volume. Provide one of the following values:
-<UL>
-<P><LI><B>a</B> to terminate the restore operation.
-<P><LI><B>f</B> if restoring a full dump file.
-<P><LI><B>i</B> if restoring an incremental dump file. This value is
-not acceptable if the <B>-server</B> and <B>-partition</B> arguments
-do not indicate the volume's current site.
-</UL>
-<P>
-<P>This argument is mandatory if the <B>-file</B> argument is not
-provided.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command restores the contents of the dump file
-<B>/afs/abc.com/common/dumps/terry.dump</B> to the
-<B>/vicepc</B> partition on the file server machine
-<B>fs3.abc.com</B>. The restored volume is named
-<B>user.terry</B>.
-<PRE> % <B>cd /afs/abc.com/common/dumps</B>
-
- % <B>vos restore -file terry.dump -server fs3.abc.com -partition c</B> \
- <B>-name user.terry</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf260.htm#HDRVOS_DUMP">vos dump</A>
-<P><A HREF="auarf261.htm#HDRVOS_EXAMINE">vos examine</A>
-<P><A HREF="auarf266.htm#HDRVOS_LISTVOL">vos listvol</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf273.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf275.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf274.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf276.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_STATUS" HREF="auarf002.htm#ToC_289">vos status</A></H2>
-<A NAME="IDX5833"></A>
-<A NAME="IDX5834"></A>
-<A NAME="IDX5835"></A>
-<A NAME="IDX5836"></A>
-<A NAME="IDX5837"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Reports a Volume Server's status
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos status -server</B> <<VAR>machine name</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos st -s</B> <<VAR>machine name</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos status</B> command reports on what the Volume Server on a
-certain file server machine is doing at the moment the command is
-issued. If there is no activity, the following message appears:
-<PRE> No active transactions on <VAR>machine_name</VAR>
-
-</PRE>
-<P>This command is useful mainly if there is concern that the Volume Server is
-not performing requested actions.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B><B>-server</B>
-</B><DD>Identifies the file server machine running the Volume Server for which to
-display status information. Provide the machine's IP address or
-its host name (either fully qualified or using an unambiguous
-abbreviation). For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Output</STRONG>
-<P>There are two possible types of output.
-<P>The following message indicates that the Volume Server is not currently
-performing any actions.
-<PRE> No active transactions on <VAR>machine name</VAR>
-
-</PRE>
-<P>The other possible output is a set of information which is probably more
-useful to programmers than to system administrators. A full
-understanding of all the fields requires familiarity with the code for the
-Volume Server, as many of the fields report ID numbers and flag values that
-the Volume Server sets for internal use.
-<P>Among the fields of possible interest to an administrator are:
-<UL>
-<P><LI><TT>created</TT> on the first line, which indicates the time at which
-this transaction started
-<P><LI><TT>attachFlags</TT> on the second line, where a value of
-<TT>offline</TT> indicates that the volume is not available for other read
-or write operations during this transaction
-<P><LI><TT>volume</TT> on the third line, which specifies the affected
-volume's ID number
-<P><LI><TT>partition</TT> on the third line, which indicates where the affected
-volume resides (at the beginning of the transaction if this is a move)
-<P><LI><TT>procedure</TT> on the third line, which indicates the internal
-subprocedure being executed
-</UL>
-<P>A fourth line can appear during certain transactions, and includes the
-following fields:
-<UL>
-<P><LI><TT>packetRead</TT> tracks whether information is being read into the
-volume. Its absolute value is not informative, but the way it changes
-shows whether the <B>vos restore</B> command is executing properly.
-As the <B>vos status</B> command is issued repeatedly during a restore,
-<TT>readNext</TT> increases monotonically to indicate that information is
-being read into the volume.
-<P><LI><TT>packetSend</TT> tracks whether information is being sent out of the
-volume. Its absolute value is not informative, but the way it changes
-shows whether the <B>vos dump</B> command is executing properly. As
-the <B>vos status</B> command is issued repeatedly during a dump,
-<TT>transmitNext</TT> increases monotonically to indicate that information
-is being transferred from the volume into the dump file.
-</UL>
-<P>The <TT>lastReceiveTime</TT> and <TT>lastSendTime</TT> are for internal
-use.
-<P><STRONG>Examples</STRONG>
-<P>The following example illustrates the kind of output that sometimes appears
-when the Volume Server on <B>fs1.abc.com</B> is executing a
-dump at the time this command is issued.
-<PRE> % <B>vos status fs1.abc.com</B>
- --------------------------------------------
- transaction: 575 created: Tue Jan 2 8:34:56 1990
- attachFlags: offline
- volume: 536871080 partition: /vicepb procedure: Dump
- packetRead: 2 lastReceiveTime: 113313 packetSend: 24588
- lastSendTime: 113317
- --------------------------------------------
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>None
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf274.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf276.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf275.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf277.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_SYNCSERV" HREF="auarf002.htm#ToC_290">vos syncserv</A></H2>
-<A NAME="IDX5838"></A>
-<A NAME="IDX5839"></A>
-<A NAME="IDX5840"></A>
-<A NAME="IDX5841"></A>
-<A NAME="IDX5842"></A>
-<A NAME="IDX5843"></A>
-<A NAME="IDX5844"></A>
-<A NAME="IDX5845"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Verifies VLDB entries that mention a specified site
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos syncserv -server</B> <<VAR>machine name</VAR>> [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>]
- [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos syncs -s</B> <<VAR>machine name</VAR>> [<B>-p</B> <<VAR>partition name</VAR>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos syncserv</B> command verifies that each volume mentioned in
-a VLDB entry actually exists at the site indicated in the entry. It
-checks all VLDB entries that mention a read/write, read-only, or backup site
-either on any partition on the file server machine specified by the
-<B>-server</B> argument, or on the one partition specified by the
-<B>-server</B> and <B>-partition</B> arguments. Note that the
-command can end up inspecting sites other than those specified by the
-<B>-server</B> and <B>-partition</B> arguments, if there are versions
-of the volume at sites other than the one specified.
-<P>The command alters any incorrect information in the VLDB, unless there is
-an irreconcilable conflict with other VLDB entries. In that case, it
-writes a message to the standard error stream instead. The command
-never removes volumes from file server machines.
-<P>To achieve complete VLDB consistency, first run the <B>vos syncvldb</B>
-command on all file server machines in the cell, then run this command on all
-file server machines in the cell.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine mentioned in each VLDB entry to
-check. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition mentioned in each VLDB entry to check.
-Provide the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example verifies the VLDB entries in which a site definition
-mentions the file server machine <B>fs3.abc.com</B>.
-<PRE> % <B>vos syncserv -server fs3.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf277.htm#HDRVOS_SYNCVLDB">vos syncvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf275.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf277.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf276.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf278.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_SYNCVLDB" HREF="auarf002.htm#ToC_291">vos syncvldb</A></H2>
-<A NAME="IDX5846"></A>
-<A NAME="IDX5847"></A>
-<A NAME="IDX5848"></A>
-<A NAME="IDX5849"></A>
-<A NAME="IDX5850"></A>
-<A NAME="IDX5851"></A>
-<A NAME="IDX5852"></A>
-<A NAME="IDX5853"></A>
-<A NAME="IDX5854"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Verifies VLDB entries for volumes residing at specified site
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos syncvldb</B> [<B>-server</B> <<VAR>machine name</VAR>>] [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-volume</B> <<VAR>volume name or ID</VAR>>] [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos syncv</B> [<B>-s</B> <<VAR>machine name</VAR>>] [<B>-p</B> <<VAR>partition name</VAR>>] [<B>-vo</B> <<VAR>volume name or ID</VAR>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-ve</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos syncvldb</B> command verifies that the status of the volumes
-housed either on all partitions on the file server machine specified by the
-<B>-server</B> argument, or on the single partition specified by the
-<B>-server</B> and <B>-partition</B> arguments, is recorded correctly
-in the VLDB. If the <B>-volume</B> argument is included to indicate
-a single volume, the command compares only its status on the file server
-machine with its VLDB entry.
-<P>If the <B>-volume</B> argument is not included, the command interpreter
-obtains from the Volume Server a list of the volumes that reside on each
-partition, then changes information in the VLDB as necessary to reflect their
-state on the partition. For example, it creates or updates a VLDB entry
-when it finds a volume for which the VLDB entry is missing or
-incomplete. However, if there is already a VLDB entry that defines a
-different location for the volume, or there are irreconcilable conflicts with
-other VLDB entries, it instead writes a message about the conflict to the
-standard error stream. The command never removes volumes from the file
-server machine.
-<P>To achieve complete VLDB consistency, run this command on all file server
-machines in the cell, and then run the <B>vos syncserv</B> command on all
-file server machines in the cell.
-<P>Using the <B>-volume</B> argument basically combines the effects of
-this command with those of the <B>vos syncserv</B> command, for a single
-volume. The command not only verifies that the VLDB entry is correct
-for the specified volume type (read/write, backup, or read-only), but also
-checks that any related volume types mentioned in the VLDB entry actually
-exist at the site listed in the entry. It is not necessary to provide
-the <B>-server</B> argument (and optionally, <B>-partition</B>
-argument); if one or both is provided, the results are reliable only if
-they specify the actual location of the volume indicated by the
-<B>-volume</B> argument.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine housing the volumes for which to verify
-VLDB entries. Provide the machine's IP address or its host name
-(either fully qualified or using an unambiguous abbreviation). For
-details, see the introductory reference page for the <B>vos</B> command
-suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition housing the volumes for which to verify VLDB
-entries. Provide the <B>-server</B> argument along with this
-one. Provide the partition's complete name with preceding slash
-(for example, <B>/vicepa</B>) or use one of the three acceptable
-abbreviated forms. For details, see the introductory reference page for
-the <B>vos</B> command suite.
-<P><DT><B>-volume
-</B><DD>Specifies the name or volume ID number of a single volume for which to
-verify the VLDB entry. This argument can be combined with the
-<B>-server</B> (and optionally, the <B>-partition</B>)
-argument.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example command verifies the VLDB entry for each volume
-stored on the file server machine <B>fs4.abc.com</B>.
-<PRE> % <B>vos syncvldb fs4.abc.com</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf276.htm#HDRVOS_SYNCSERV">vos syncserv</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf276.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf278.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf277.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf279.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_UNLOCK" HREF="auarf002.htm#ToC_292">vos unlock</A></H2>
-<A NAME="IDX5855"></A>
-<A NAME="IDX5856"></A>
-<A NAME="IDX5857"></A>
-<A NAME="IDX5858"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Unlocks a single VLDB entry
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos unlock -id</B> <<VAR>volume name or ID</VAR>> [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>]
- [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos unlock -i</B> <<VAR>volume name or ID</VAR>> [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos unlock</B> command releases the lock on the Volume Location
-Database (VLDB) entry for the indicated volume.
-<P><STRONG>Cautions</STRONG>
-<P>Do not user this command under normal circumstances.
-<P>It is useful if the VLDB entry is locked but there is no reason to suspect
-inconsistency within the volume or between it and the VLDB. Note that
-it is possible to list information from locked VLDB entries, even though they
-cannot be manipulated in other ways.
-<P>The <B>vos unlockvldb</B> command unlocks several VLDB entries at once,
-or even the entire VLDB. The <B>vos lock</B> command locks a VLDB
-entry so that no one else can perform an action that requires writing the
-VLDB.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-id
-</B><DD>Specifies either the complete name or volume ID number of a volume of any
-of the three types.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example unlocks the VLDB entry for the volume
-<B>user.terry</B>.
-<PRE> % <B>vos unlock user.terry</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf267.htm#HDRVOS_LOCK">vos lock</A>
-<P><A HREF="auarf279.htm#HDRVOS_UNLOCKVLDB">vos unlockvldb</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf277.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf279.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf278.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf280.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_UNLOCKVLDB" HREF="auarf002.htm#ToC_293">vos unlockvldb</A></H2>
-<A NAME="IDX5859"></A>
-<A NAME="IDX5860"></A>
-<A NAME="IDX5861"></A>
-<A NAME="IDX5862"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Unlocks several locked VLDB entries
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos unlockvldb</B> [<B>-server</B> <<VAR>machine name</VAR>>] [<B>-partition</B> <<VAR>partition name</VAR>>]
- [<B>-cell</B> <<VAR>cell name</VAR>>] [<B>-noauth</B>] [<B>-localauth</B>]
- [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos unlockv</B> [<B>-s</B> <<VAR>machine name</VAR>>] [<B>-p</B> <<VAR>partition name</VAR>>]
- [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos unlockvldb</B> command releases the lock on the Volume
-Location Database (VLDB) entries indicated by the combination of arguments
-provided:
-<UL>
-<P><LI>To unlock all entries in the VLDB, provide no arguments
-<P><LI>To unlock all entries that mention a file server machine in a site
-definition, provide its name with the <B>-server</B> argument
-<P><LI>To unlock all entries that mention a partition on any file server machine
-in a site definition, provide the partition name with the
-<B>-partition</B> argument
-<P><LI>To unlock all entries that mention a specific site, provide both the
-<B>-server</B> and <B>-partition</B> arguments.
-</UL>
-<P>To unlock a single volume, use the <B>vos unlock</B> command
-instead.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command under normal circumstances.
-<P>It is useful if VLDB entries for volumes at a certain site are locked but
-there is no reason to suspect inconsistency within the volume or between it
-and the VLDB. Note that it is possible to list information from locked
-VLDB entries, even though they cannot be manipulated in other ways.
-<P>The <B>vos lock</B> command locks a VLDB entry so that no one else can
-perform an action that requires writing the VLDB.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine for which to unlock VLDB
-entries. Provide the machine's IP address or its host name (either
-fully qualified or using an unambiguous abbreviation). For details, see
-the introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) for which to unlock VLDB entries. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following command unlocks all locked entries in the VLDB.
-<PRE> % <B>vos unlockvldb</B>
-
-</PRE>
-<P>The following command unlocks all locked VLDB entries that mention the
-<B>/vicepa</B> partition in a site definition.
-<PRE> % <B>vos unlockvldb -partition a</B>
-
-</PRE>
-<P>The following command unlocks all locked VLDB entries that refer to volumes
-on the <B>/vicepc</B> partition of the file server machine
-<B>fs3.abc.com</B>.
-<PRE> % <B>vos unlockvldb -server fs3.abc.com -partition c</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf267.htm#HDRVOS_LOCK">vos lock</A>
-<P><A HREF="auarf278.htm#HDRVOS_UNLOCK">vos unlock</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf278.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf280.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf279.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf281.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRVOS_ZAP" HREF="auarf002.htm#ToC_294">vos zap</A></H2>
-<A NAME="IDX5863"></A>
-<A NAME="IDX5864"></A>
-<A NAME="IDX5865"></A>
-<A NAME="IDX5866"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Removes a volume from its site without writing to the VLDB
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>vos zap -server</B> <<VAR>machine name</VAR>> <B>-partition</B> <<VAR>partition name</VAR>>
- <B>-id</B> <<VAR>volume ID</VAR>> [<B>-force</B>] [<B>-backup</B>] [<B>-cell</B> <<VAR>cell name</VAR>>]
- [<B>-noauth</B>] [<B>-localauth</B>] [<B>-verbose</B>] [<B>-help</B>]
-
-<B>vos z -s</B> <<VAR>machine name</VAR>> <B>-p</B> <<VAR>partition name</VAR>> <B>-i</B> <<VAR>volume ID</VAR>>
- [<B>-f</B>] [<B>-b</B>] [<B>-c</B> <<VAR>cell name</VAR>>] [<B>-n</B>] [<B>-l</B>] [<B>-v</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>vos zap</B> command removes the volume with the specified
-<VAR>volume ID</VAR> from the site defined by the <B>-server</B> and
-<B>-partition</B> arguments, without attempting to change the
-corresponding Volume Location Database (VLDB) entry. If removing the
-volume can possibly result in incorrect data in the VLDB, a warning message is
-displayed.
-<P>The <B>-force</B> flag removes a volume even if it cannot be "attached"
-(brought online), which can happen either because the volume is extremely
-damaged or because the Salvager functioned abnormally. Without this
-flag, this command cannot remove volumes that are not attachable. See
-also the <B>Cautions</B> section.
-<P>To remove the specified read/write volume's backup version at the same
-time, include the <B>-backup</B> flag.
-<P><STRONG>Cautions</STRONG>
-<P>Do not use this command as the standard way to remove a volume, as it is
-likely to put the VLDB out of sync with the volumes on servers. Use the
-<B>vos remove</B> command instead.
-<P>This command is useful in situations where it is important to delete the
-volume, but for some reason the VLDB is unreachable--for example, because
-s the Volume Location Server is unavailable. The issuer can remove the
-VLDB entry later with the <B>vos remove</B> or <B>vos delentry</B>
-command, or it is removed automatically when the <B>vos syncserv</B> and
-<B>vos syncvldb</B> commands run.
-<P>To remove a read-only site defined in the VLDB by mistake, before a copy
-actually exists at the site, use the <B>vos remsite</B> command. To
-remove an entire VLDB entry without affecting volumes at their sites, use the
-<B>vos delentry</B> command.
-<P>Do not use the <B>-force</B> flag if the volume is online, but only
-when attempts to remove the volume with the <B>vos remove</B> or the
-<B>vos zap</B> command have failed, or the volume definitely cannot be
-attached. After using the <B>-force</B> flag, make sure that the
-volume's VLDB entry is also removed (issue the <B>vos delentry</B>
-command if necessary).
-<P>Adding the <B>-force</B> flag makes the command take considerably
-longer--about as long as a salvage of the relevant partition--since
-the Volume Server examines all inodes on the partition for traces of the
-volume.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>-server
-</B><DD>Identifies the file server machine from which to remove the volume.
-Provide the machine's IP address or its host name (either fully qualified
-or using an unambiguous abbreviation). For details, see the
-introductory reference page for the <B>vos</B> command suite.
-<P><DT><B>-partition
-</B><DD>Identifies the partition (on the file server machine specified by the
-<B>-server</B> argument) from which to remove the volume. Provide
-the partition's complete name with preceding slash (for example,
-<B>/vicepa</B>) or use one of the three acceptable abbreviated
-forms. For details, see the introductory reference page for the
-<B>vos</B> command suite.
-<P><DT><B>-id
-</B><DD>Specifies the volume ID number of the volume to remove, which can be of
-any of the three types. The volume name is not acceptable.
-<P><DT><B>-force
-</B><DD>Removes the volume even though it cannot be attached (brought
-online). Use only after the failure of previous attempts to remove the
-volume by using the <B>vos remove</B> command or the <B>vos</B>
-command without this flag.
-<P><DT><B>-backup
-</B><DD>Removes the backup version of the read/write volume specified by the
-<B>-id</B> argument. Do not use this flag if the <B>-id</B>
-argument identifies a read-only or backup volume.
-<P><DT><B>-cell
-</B><DD>Names the cell in which to run the command. Do not combine this
-argument with the <B>-localauth</B> flag. For more details, see the
-introductory <B>vos</B> reference page.
-<P><DT><B>-noauth
-</B><DD>Assigns the unprivileged identity <B>anonymous</B> to the
-issuer. Do not combine this flag with the <B>-localauth</B>
-flag. For more details, see the introductory <B>vos</B> reference
-page.
-<P><DT><B>-localauth
-</B><DD>Constructs a server ticket using a key from the local
-<B>/usr/afs/etc/KeyFile</B> file. The <B>vos</B> command
-interpreter presents it to the Volume Server and Volume Location Server during
-mutual authentication. Do not combine this flag with the
-<B>-cell</B> argument or <B>-noauth</B> flag. For more details,
-see the introductory <B>vos</B> reference page.
-<P><DT><B>-verbose
-</B><DD>Produces on the standard output stream a detailed trace of the
-command's execution. If this argument is omitted, only warnings
-and error messages appear.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Examples</STRONG>
-<P>The following example removes the volume with volume ID 536870988 from the
-<B>/vicepf</B> partition of the file server machine
-<B>fs6.abc.com</B>, without noting the change in the
-VLDB.
-<PRE> % <B>vos zap -server fs6.abc.com -partition f -id 536870988</B>
-
-</PRE>
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be listed in the <B>/usr/afs/etc/UserList</B> file on
-the machine specified with the <B>-server</B> argument and on each
-database server machine. If the <B>-localauth</B> flag is included,
-the issuer must instead be logged on to a server machine as the local
-superuser <B>root</B>.
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf252.htm#HDRVOS_INTRO">vos</A>
-<P><A HREF="auarf259.htm#HDRVOS_DELENTRY">vos delentry</A>
-<P><A HREF="auarf271.htm#HDRVOS_REMOVE">vos remove</A>
-<P><A HREF="auarf272.htm#HDRVOS_REMSITE">vos remsite</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf279.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf281.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf280.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf282.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRXFS_SIZE_CHECK" HREF="auarf002.htm#ToC_295">xfs_size_check</A></H2>
-<A NAME="IDX5867"></A>
-<A NAME="IDX5868"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Verifies proper inode configuration
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>xfs_size_check</B>
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>xfs_size_check</B> command, when run on a file server machine
-that runs IRIX version 6.2 or higher and uses XFS-formatted partitions
-as server partitions (conventionally mounted at <B>/vicep</B>
-directories), verifies that each partition uses 512-byte inodes. AFS
-stores information in the inodes on server partitions, and the 256-byte inode
-size that XFS uses by default is not large enough.
-<P><STRONG>Cautions</STRONG>
-<P>This command is available on in the AFS distribution for IRIX system types
-that can use XFS-formatted partitions as server partitions.
-<P><STRONG>Output</STRONG>
-<P>If all server partitions are properly configured, the command produces no
-output. Otherwise, it prints the following header:
-<PRE> Need to remake the following partitions:
-
-</PRE>
-<P>and then the following message for each partition on which to run the IRIX
-<B>mkfs</B> command with the indicated options:
-<PRE> <VAR>device</VAR>: mkfs -t xfs -i size=512 -l size=4000b <VAR>device</VAR>
-
-</PRE>
-<P>where <VAR>device</VAR> is in a format like <B>/dev/dsk/dks0d0s0</B> for
-a single disk partition or <B>/dev/xlv/xlv0</B> for a logical
-volume.
-<P><STRONG>Privilege Required</STRONG>
-<P>The issuer must be logged in as the local superuser <B>root</B>.
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf280.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf282.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf281.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf283.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRXSTAT_CM_TEST" HREF="auarf002.htm#ToC_296">xstat_cm_test</A></H2>
-<A NAME="IDX5869"></A>
-<A NAME="IDX5870"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays data collections from the Cache Manager
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>xstat_cm_test</B> [<B>initcmd</B>] <B>-cmname</B> <<VAR>Cache Manager name(s) to monitor</VAR>><SUP>+</SUP>
- <B>-collID</B> <<VAR>Collection(s) to fetch</VAR>><SUP>+</SUP> [<B>-onceonly</B>]
- [<B>-frequency</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-period</B> <<VAR>data collection time, in minutes</VAR>>] [<B>-debug</B>] [<B>-help</B>]
-
-<B>xstat_cm_test</B> [<B>i</B>] <B>-cm</B> <<VAR>Cache Manager name(s) to monitor</VAR>><SUP>+</SUP>
- <B>-co</B> <<VAR>Collection(s) to fetch</VAR>><SUP>+</SUP> [<B>-o</B>]
- [<B>-f</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-p</B> <<VAR>data collection time, in minutes</VAR>>] [<B>-d</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>xstat_cm_test</B> command tests the routines in the
-<B>libxstat_cm.a</B> library and displays the data collections
-associated with the Cache Manager. The command executes in the
-foreground.
-<P>The command produces a large volume of output; to save it for later
-analysis, direct it to a file.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-cmname
-</B><DD>Specifies the fully qualified hostname of each client machine for which to
-monitor the Cache Manager.
-<P><DT><B>-collID
-</B><DD>Specifies each data collection to return, which defines the type and
-amount of data the command interpreter gathers about the Cache Manager.
-Data is returned in a predefined data structure.
-<P>There are three acceptable values:
-<DL>
-<P><DT><B>0
-</B><DD>Provides profiling information about the numbers of times different
-internal Cache Manager routines were called since the Cache Manager
-started.
-<P><DT><B>1
-</B><DD>Reports various internal performance statistics related to the Cache
-Manager (for example, statistics about how effectively the cache is being used
-and the quantity of intracell and intercell data access).
-<P><DT><B>2
-</B><DD>Reports all of the internal performance statistics provided by the
-<B>1</B> setting, plus some additional, detailed performance figures (for
-example, statistics about the number of RPCs sent by the Cache Manager and how
-long they take to complete, and statistics regarding authentication, access,
-and PAG information associated with data access).
-</DL>
-<P><DT><B>-onceonly
-</B><DD>Gathers statistics just one time. Omit this flag to have the
-command continue to probe the Cache Manager for statistics at the frequency
-specified by the <B>-frequency</B> argument; in this case press
-<<B>Ctrl-c</B>> to stop the probes.
-<P><DT><B>-frequency
-</B><DD>Sets the frequency in seconds at which the program initiates probes to the
-Cache Manager. The default is 30 seconds.
-<P><DT><B>-period
-</B><DD>Sets the number of minutes the program runs; at the end of this
-period of time, the program exits. The default is 10 minutes.
-<P><DT><B>-debug
-</B><DD>Displays a trace on the standard output stream as the command runs.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf283.htm#HDRXSTAT_FS_TEST">xstat_fs_test</A>
-<P>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf281.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf283.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf282.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <A HREF="auarf284.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<P>
-<H2><A NAME="HDRXSTAT_FS_TEST" HREF="auarf002.htm#ToC_297">xstat_fs_test</A></H2>
-<A NAME="IDX5871"></A>
-<A NAME="IDX5872"></A>
-<P><STRONG>Purpose</STRONG>
-<P>Displays data collections from the File Server process
-<P><STRONG>Synopsis</STRONG>
-<PRE><B>xstat_fs_test</B> [<B>initcmd</B>] <B>-fsname</B> <<VAR>File Server name(s) to monitor</VAR>><SUP>+</SUP>
- <B>-collID</B> <<VAR>Collection(s) to fetch</VAR>><SUP>+</SUP> [<B>-onceonly</B>]
- [<B>-frequency</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-period</B> <<VAR>data collection time, in minutes</VAR>>] [<B>-debug</B>] [<B>-help</B>]
-
-<B>xstat_fs_test</B> [<B>initcmd</B>] <B>-fs</B> <<VAR>File Server name(s) to monitor</VAR>><SUP>+</SUP>
- <B>-c</B> <<VAR>Collection(s) to fetch</VAR>><SUP>+</SUP> [<B>-o</B>]
- [<B>-fr</B> <<VAR>poll frequency, in seconds</VAR>>]
- [<B>-p</B> <<VAR>data collection time, in minutes</VAR>>] [<B>-d</B>] [<B>-h</B>]
-</PRE>
-<P><STRONG>Description</STRONG>
-<P>The <B>xstat_fs_test</B> command tests the routines in the
-<B>libxstat_fs.a</B> library and displays the data collections
-associated with the File Server (the <B>fs</B> process). The
-command executes in the foreground.
-<P>The command produces a large volume of output; to save it for later
-analysis, direct it to a file.
-<P><STRONG>Options</STRONG>
-<DL>
-<P><DT><B>initcmd
-</B><DD>Accommodates the command's use of the AFS command parser, and is
-optional.
-<P><DT><B>-fsname
-</B><DD>Specifies the fully qualified hostname of each file server machine for
-which to monitor the File Server process.
-<P><DT><B>-collID
-</B><DD>Specifies each data collection to return, which defines the type and
-amount of data the command interpreter gathers about the File Server.
-Data is returned in a predefined data structure.
-<P>There are three acceptable values:
-<DL>
-<P><DT><B>0
-</B><DD>Provides profiling information about the numbers of times different
-internal File Server routines were called since the File Server
-started. This value is not currently implemented; it returns no
-data.
-<P><DT><B>1
-</B><DD>Reports various internal performance statistics related to the File Server
-(for example, vnode cache entries and <B>Rx</B> protocol activity).
-<P><DT><B>2
-</B><DD>Reports all of the internal performance statistics provided by the
-<B>1</B> setting, plus some additional, detailed performance figures about
-the File Server (for example, minimum, maximum, and cumulative statistics
-regarding File Server RPCs, how long they take to complete, and how many
-succeed).
-</DL>
-<P><DT><B>-onceonly
-</B><DD>Gathers statistics just one time. Omit this flag to have the
-command continue to probe the Cache Manager for statistics at the frequency
-specified by the <B>-frequency</B> argument; in this case press
-<<B>Ctrl-c</B>> to stop the probes.
-<P><DT><B>-frequency
-</B><DD>Sets the frequency in seconds at which the program initiates probes to the
-Cache Manager. The default is 30 seconds.
-<P><DT><B>-period
-</B><DD>Sets the number of minutes the program runs; at the end of this
-period of time, the program exits. The default is 10 minutes.
-<P><DT><B>-debug
-</B><DD>Displays a trace on the standard output stream as the command runs.
-<P><DT><B>-help
-</B><DD>Prints the online help for this command. All other valid options
-are ignored.
-</DL>
-<P><STRONG>Related Information</STRONG>
-<P><A HREF="auarf282.htm#HDRXSTAT_CM_TEST">xstat_cm_test</A>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf282.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <A HREF="auarf284.htm"><IMG SRC="../next.gif" BORDER="0" ALT="[Next Topic]"></A> <A HREF="auarf284.htm#HDRINDEX"><IMG SRC="../index.gif" BORDER="0" ALT="[Index]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
-<HTML><HEAD>
-<TITLE>Administration Reference</TITLE>
-<!-- Begin Header Records ========================================== -->
-<!-- /tmp/idwt3672/auarf000.scr converted by idb2h R4.2 (359) ID -->
-<!-- Workbench Version (AIX) on 3 Oct 2000 at 16:18:30 -->
-<META HTTP-EQUIV="updated" CONTENT="Tue, 03 Oct 2000 16:18:29">
-<META HTTP-EQUIV="review" CONTENT="Wed, 03 Oct 2001 16:18:29">
-<META HTTP-EQUIV="expires" CONTENT="Thu, 03 Oct 2002 16:18:29">
-</HEAD><BODY>
-<!-- (C) IBM Corporation 2000. All Rights Reserved -->
-<BODY bgcolor="ffffff">
-<!-- End Header Records ============================================ -->
-<A NAME="Top_Of_Page"></A>
-<H1>Administration Reference</H1>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf283.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Bot_Of_Page"><IMG SRC="../bot.gif" BORDER="0" ALT="[Bottom of Topic]"></A> <P>
-<P>
-<HR><H1><A NAME="HDRINDEX" HREF="auarf002.htm#ToC_298">Index</A></H1>
-<A NAME="IDX0_41" HREF="#IDX1_41">A</A>
-<A NAME="IDX0_42" HREF="#IDX1_42">B</A>
-<A NAME="IDX0_43" HREF="#IDX1_43">C</A>
-<A NAME="IDX0_44" HREF="#IDX1_44">D</A>
-<A NAME="IDX0_45" HREF="#IDX1_45">E</A>
-<A NAME="IDX0_46" HREF="#IDX1_46">F</A>
-<A NAME="IDX0_47" HREF="#IDX1_47">G</A>
-<A NAME="IDX0_48" HREF="#IDX1_48">H</A>
-<A NAME="IDX0_49" HREF="#IDX1_49">I</A>
-<A NAME="IDX0_4A" HREF="#IDX1_4A">J</A>
-<A NAME="IDX0_4B" HREF="#IDX1_4B">K</A>
-<A NAME="IDX0_4C" HREF="#IDX1_4C">L</A>
-<A NAME="IDX0_4D" HREF="#IDX1_4D">M</A>
-<A NAME="IDX0_4E" HREF="#IDX1_4E">N</A>
-<A NAME="IDX0_4F" HREF="#IDX1_4F">O</A>
-<A NAME="IDX0_50" HREF="#IDX1_50">P</A>
-<A NAME="IDX0_51" HREF="#IDX1_51">Q</A>
-<A NAME="IDX0_52" HREF="#IDX1_52">R</A>
-<A NAME="IDX0_53" HREF="#IDX1_53">S</A>
-<A NAME="IDX0_54" HREF="#IDX1_54">T</A>
-<A NAME="IDX0_55" HREF="#IDX1_55">U</A>
-<A NAME="IDX0_56" HREF="#IDX1_56">V</A>
-<A NAME="IDX0_57" HREF="#IDX1_57">W</A>
-<A NAME="IDX0_58" HREF="#IDX1_58">X</A>
-<HR>
-<STRONG><A NAME="IDX1_41" HREF="#IDX0_41">A</A></STRONG>
-<MENU>
-<LI>A instruction
-<MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4119">(4119)</A>
-</MENU>
-<LI>access
-<MENU>
-<LI>count, in volume header
-<A HREF="auarf261.htm#IDX5683">(5683)</A>, <A HREF="auarf266.htm#IDX5759">(5759)</A>
-</MENU>
-<LI>access control list
-<MENU>
-<LI>see entry: <I>ACL</I>
-<A HREF="auarf210.htm#IDX5222">(5222)</A>
-</MENU>
-<LI>ACL
-<MENU>
-<LI>adding entries
-<A HREF="auarf157.htm#IDX4925">(4925)</A>
-<LI>all shorthand notation
-<A HREF="auarf157.htm#IDX4938">(4938)</A>
-<LI>cleaning
-<A HREF="auarf135.htm#IDX4747">(4747)</A>
-<LI>clearing
-<A HREF="auarf157.htm#IDX4927">(4927)</A>
-<LI>copying
-<A HREF="auarf136.htm#IDX4753">(4753)</A>
-<LI>default set by vos create command
-<A HREF="auarf258.htm#IDX5625">(5625)</A>
-<LI>defined
-<A HREF="auarf210.htm#IDX5221">(5221)</A>
-<LI>displaying
-<A HREF="auarf148.htm#IDX4854">(4854)</A>
-<LI>none shorthand notation
-<A HREF="auarf157.htm#IDX4942">(4942)</A>
-<LI>read shorthand notation
-<A HREF="auarf157.htm#IDX4944">(4944)</A>
-<LI>removing entries
-<A HREF="auarf157.htm#IDX4926">(4926)</A>
-<LI>removing obsolete AFS UIDs
-<A HREF="auarf135.htm#IDX4746">(4746)</A>
-<LI>setting
-<A HREF="auarf157.htm#IDX4924">(4924)</A>
-<LI>setting with uss
-<A HREF="auarf055.htm#IDX4127">(4127)</A>, <A HREF="auarf055.htm#IDX4179">(4179)</A>
-<LI>shorthand notation for permissions
-<A HREF="auarf157.htm#IDX4939">(4939)</A>
-<LI>write shorthand notation
-<A HREF="auarf157.htm#IDX4946">(4946)</A>
-</MENU>
-<LI>active clients statistic in scout
-<A HREF="auarf233.htm#IDX5462">(5462)</A>
-<LI>add instruction in uss bulk input file
-<A HREF="auarf054.htm#IDX4103">(4103)</A>
-<LI>adding
-<MENU>
-<LI>ACL permissions entry
-<A HREF="auarf157.htm#IDX4930">(4930)</A>
-<LI>database server machine to CellServDB file (server)
-<A HREF="auarf094.htm#IDX4453">(4453)</A>
-<LI>dump level to Backup System dump hierarchy
-<A HREF="auarf061.htm#IDX4222">(4222)</A>
-<LI>privileged user to UserList file
-<A HREF="auarf096.htm#IDX4466">(4466)</A>
-<LI>read-only site definition in VLDB
-<A HREF="auarf253.htm#IDX5590">(5590)</A>
-<LI>server encryption key to KeyFile file
-<A HREF="auarf095.htm#IDX4456">(4456)</A>
-<LI>Tape Coordinator entry to Backup Database
-<A HREF="auarf062.htm#IDX4237">(4237)</A>
-<LI>user or machine to group
-<A HREF="auarf211.htm#IDX5237">(5237)</A>
-<LI>volume entry to volume set in Backup Database
-<A HREF="auarf063.htm#IDX4245">(4245)</A>, <A HREF="auarf063.htm#IDX4252">(4252)</A>
-<LI>volume set definition to Backup Database
-<A HREF="auarf064.htm#IDX4260">(4260)</A>
-</MENU>
-<LI>admin argument
-<MENU>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5510">(5510)</A>
-</MENU>
-<LI>ADMIN flag in Authentication Database entry
-<A HREF="auarf181.htm#IDX5061">(5061)</A>, <A HREF="auarf193.htm#IDX5143">(5143)</A>
-<LI>administrative file
-<MENU>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3863">(3863)</A>
-</MENU>
-<LI>admin_username argument
-<MENU>
-<LI>on all kas commands
-<A HREF="auarf181.htm#IDX5064">(5064)</A>
-</MENU>
-<LI>AFS Backup System
-<MENU>
-<LI>see entry: <I>Backup System</I>
-<A HREF="auarf060.htm#IDX4207">(4207)</A>
-</MENU>
-<LI>AFS GID (group ID)
-<MENU>
-<LI>assigning to group
-<A HREF="auarf214.htm#IDX5267">(5267)</A>
-<LI>learning given group name
-<A HREF="auarf217.htm#IDX5326">(5326)</A>
-</MENU>
-<LI>AFS server process
-<MENU>
-<LI>see entry: <I>server process</I>
-<A HREF="auarf093.htm#IDX4440">(4440)</A>
-</MENU>
-<LI>AFS tape name
-<MENU>
-<LI>see entry: <I>tape (Backup System)</I>
-<A HREF="auarf079.htm#IDX4355">(4355)</A>
-</MENU>
-<LI>AFS UID
-<MENU>
-<LI>assigning in uss
-<A HREF="auarf243.htm#IDX5528">(5528)</A>
-<LI>assigning to user or machine with pts createuser command
-<A HREF="auarf215.htm#IDX5286">(5286)</A>
-<LI>displaying
-<A HREF="auarf217.htm#IDX5341">(5341)</A>
-<LI>learning given user/machine name
-<A HREF="auarf217.htm#IDX5325">(5325)</A>
-<LI>removing obsolete from ACL
-<A HREF="auarf135.htm#IDX4750">(4750)</A>
-</MENU>
-<LI>afsd command
-<A HREF="auarf058.htm#IDX4184">(4184)</A>
-<LI>afsmonitor
-<MENU>
-<LI>configuration file
-<A HREF="auarf052.htm#IDX4036">(4036)</A>
-</MENU>
-<LI>afsmonitor program
-<MENU>
-<LI>initialization command
-<A HREF="auarf058.htm#IDX4193">(4193)</A>
-<LI>setting terminal type
-<A HREF="auarf059.htm#IDX4200">(4200)</A>
-</MENU>
-<LI>afszcm.cat file
-<A HREF="auarf041.htm#IDX4005">(4005)</A>
-<LI>all shorthand notation for ACL permissions
-<A HREF="auarf157.htm#IDX4937">(4937)</A>
-<LI>all-or-nothing release of read-only volumes
-<A HREF="auarf270.htm#IDX5795">(5795)</A>
-<LI>appended dump
-<MENU>
-<LI>displaying record for
-<A HREF="auarf074.htm#IDX4323">(4323)</A>
-<LI>see entry: <I>dump</I>
-<A HREF="auarf073.htm#IDX4311">(4311)</A>
-</MENU>
-<LI>ASK instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3905">(3905)</A>
-<LI>assigning
-<MENU>
-<LI>AFS GID to group
-<A HREF="auarf214.htm#IDX5271">(5271)</A>
-<LI>AFS UID to user
-<A HREF="auarf215.htm#IDX5290">(5290)</A>
-</MENU>
-<LI>at-sys (@sys) variable in pathnames
-<A HREF="auarf165.htm#IDX4998">(4998)</A>, <A HREF="auarf234.htm#IDX5472">(5472)</A>
-<LI>authenticated identity
-<MENU>
-<LI>acquiring on NFS client of non-supported type
-<A HREF="auarf201.htm#IDX5185">(5185)</A>
-<LI>acquiring with klog
-<A HREF="auarf200.htm#IDX5182">(5182)</A>
-<LI>discarding while in kas interactive mode
-<A HREF="auarf191.htm#IDX5123">(5123)</A>
-</MENU>
-<LI>authentication
-<MENU>
-<LI>imposing restrictions with kas
-<A HREF="auarf193.htm#IDX5142">(5142)</A>
-<LI>imposing restrictions with uss template A instruction
-<A HREF="auarf055.htm#IDX4118">(4118)</A>
-</MENU>
-<LI>Authentication Database
-<MENU>
-<LI>changing/setting password in
-<A HREF="auarf202.htm#IDX5191">(5191)</A>
-<LI>creating entry
-<A HREF="auarf183.htm#IDX5076">(5076)</A>
-<LI>deleting entry
-<A HREF="auarf184.htm#IDX5081">(5081)</A>
-<LI>displaying all entries
-<A HREF="auarf189.htm#IDX5115">(5115)</A>
-<LI>displaying entry
-<A HREF="auarf185.htm#IDX5085">(5085)</A>
-<LI>displaying key
-<A HREF="auarf185.htm#IDX5086">(5086)</A>
-<LI>entry, creating with uss
-<A HREF="auarf243.htm#IDX5527">(5527)</A>
-<LI>entry, deleting with uss
-<A HREF="auarf246.htm#IDX5551">(5551)</A>
-<LI>files constituting
-<A HREF="auarf045.htm#IDX4015">(4015)</A>
-<LI>information in
-<A HREF="auarf185.htm#IDX5099">(5099)</A>
-<LI>setting flags and expiration dates
-<A HREF="auarf193.htm#IDX5133">(5133)</A>
-<LI>setting key field using password
-<A HREF="auarf194.htm#IDX5150">(5150)</A>
-<LI>setting password in
-<A HREF="auarf194.htm#IDX5151">(5151)</A>
-<LI>status, verifying
-<A HREF="auarf180.htm#IDX5056">(5056)</A>
-</MENU>
-<LI>Authentication Server
-<MENU>
-<LI>displaying statistics
-<A HREF="auarf195.htm#IDX5159">(5159)</A>
-<LI>displaying traces of privileged actions
-<A HREF="auarf199.htm#IDX5175">(5175)</A>
-<LI>listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3914">(3914)</A>
-<LI>listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3922">(3922)</A>
-<LI>log file
-<A HREF="auarf012.htm#IDX3870">(3870)</A>
-<LI>log files for privileged actions
-<A HREF="auarf013.htm#IDX3873">(3873)</A>
-<LI>starting
-<A HREF="auarf198.htm#IDX5172">(5172)</A>
-<LI>unlocking locked user account
-<A HREF="auarf197.htm#IDX5169">(5169)</A>
-</MENU>
-<LI>AuthLog file
-<A HREF="auarf012.htm#IDX3868">(3868)</A>
-<LI>AuthLog.dir and AuthLog.pag files
-<A HREF="auarf013.htm#IDX3871">(3871)</A>
-<LI>authorization checking
-<MENU>
-<LI>NoAuth file
-<A HREF="auarf028.htm#IDX3966">(3966)</A>
-<LI>setting requirements on server machine
-<A HREF="auarf115.htm#IDX4617">(4617)</A>
-</MENU>
-<LI>automatic restart times for BOS Server
-<MENU>
-<LI>see entry: <I>restart times for BOS Server</I>
-<A HREF="auarf103.htm#IDX4541">(4541)</A>
-</MENU>
-<LI>AUTOQUERY instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3906">(3906)</A>
-<LI>availability of data
-<MENU>
-<LI>interrupted by dumping
-<A HREF="auarf260.htm#IDX5649">(5649)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_42" HREF="#IDX0_42">B</A></STRONG>
-<MENU>
-<LI>B instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4041">(4041)</A>
-</MENU>
-<LI>backup
-<MENU>
-<LI>see entry: <I>backup commands</I>
-<A HREF="auarf060.htm#IDX4206">(4206)</A>
-<LI>see entry: <I>Backup System</I>
-<A HREF="auarf060.htm#IDX4205">(4205)</A>
-</MENU>
-<LI>backup commands
-<MENU>
-<LI>adddump
-<A HREF="auarf061.htm#IDX4218">(4218)</A>
-<LI>addhost
-<A HREF="auarf062.htm#IDX4229">(4229)</A>
-<LI>addvolentry
-<A HREF="auarf063.htm#IDX4240">(4240)</A>, <A HREF="auarf063.htm#IDX4247">(4247)</A>
-<LI>addvolset
-<A HREF="auarf064.htm#IDX4255">(4255)</A>
-<LI>apropos
-<A HREF="auarf065.htm#IDX4261">(4261)</A>
-<LI>common options
-<A HREF="auarf060.htm#IDX4211">(4211)</A>
-<LI>dbverify
-<A HREF="auarf066.htm#IDX4264">(4264)</A>
-<LI>deldump
-<A HREF="auarf067.htm#IDX4267">(4267)</A>
-<LI>deletedump
-<A HREF="auarf068.htm#IDX4275">(4275)</A>
-<LI>delhost
-<A HREF="auarf069.htm#IDX4281">(4281)</A>
-<LI>delvolentry
-<A HREF="auarf070.htm#IDX4286">(4286)</A>
-<LI>delvolset
-<A HREF="auarf071.htm#IDX4292">(4292)</A>
-<LI>diskrestore
-<A HREF="auarf072.htm#IDX4296">(4296)</A>
-<LI>dump
-<A HREF="auarf073.htm#IDX4302">(4302)</A>
-<LI>dumpinfo
-<A HREF="auarf074.htm#IDX4316">(4316)</A>
-<LI>help
-<A HREF="auarf075.htm#IDX4324">(4324)</A>
-<LI>interactive
-<A HREF="auarf076.htm#IDX4327">(4327)</A>
-<LI>introduction
-<A HREF="auarf060.htm#IDX4204">(4204)</A>
-<LI>jobs
-<A HREF="auarf077.htm#IDX4332">(4332)</A>
-<LI>kill
-<A HREF="auarf078.htm#IDX4339">(4339)</A>
-<LI>labeltape
-<A HREF="auarf079.htm#IDX4345">(4345)</A>
-<LI>listdumps
-<A HREF="auarf080.htm#IDX4357">(4357)</A>
-<LI>listhosts
-<A HREF="auarf081.htm#IDX4365">(4365)</A>
-<LI>listvolsets
-<A HREF="auarf082.htm#IDX4374">(4374)</A>
-<LI>privilege requirements
-<A HREF="auarf060.htm#IDX4217">(4217)</A>
-<LI>quit
-<A HREF="auarf083.htm#IDX4380">(4380)</A>
-<LI>readlabel
-<A HREF="auarf084.htm#IDX4386">(4386)</A>
-<LI>restoredb
-<A HREF="auarf085.htm#IDX4394">(4394)</A>
-<LI>savedb
-<A HREF="auarf086.htm#IDX4397">(4397)</A>
-<LI>scantape
-<A HREF="auarf087.htm#IDX4400">(4400)</A>
-<LI>setexp
-<A HREF="auarf088.htm#IDX4406">(4406)</A>
-<LI>status
-<A HREF="auarf089.htm#IDX4412">(4412)</A>
-<LI>volinfo
-<A HREF="auarf090.htm#IDX4416">(4416)</A>
-<LI>volrestore
-<A HREF="auarf091.htm#IDX4422">(4422)</A>
-<LI>volsetrestore
-<A HREF="auarf092.htm#IDX4428">(4428)</A>
-</MENU>
-<LI>Backup Database
-<MENU>
-<LI>dump hierarchy, displaying
-<A HREF="auarf080.htm#IDX4361">(4361)</A>
-<LI>dump level, creating
-<A HREF="auarf061.htm#IDX4224">(4224)</A>
-<LI>dump level, removing
-<A HREF="auarf067.htm#IDX4271">(4271)</A>
-<LI>dump record, deleting
-<A HREF="auarf068.htm#IDX4278">(4278)</A>
-<LI>dump record, displaying
-<A HREF="auarf074.htm#IDX4319">(4319)</A>
-<LI>expiration date, setting on existing dump level
-<A HREF="auarf088.htm#IDX4409">(4409)</A>
-<LI>expiration date, setting on new dump level
-<A HREF="auarf061.htm#IDX4226">(4226)</A>
-<LI>files constituting
-<A HREF="auarf042.htm#IDX4010">(4010)</A>
-<LI>information recorded
-<A HREF="auarf060.htm#IDX4209">(4209)</A>
-<LI>port offset number, assigning to Tape Coordinator
-<A HREF="auarf062.htm#IDX4234">(4234)</A>
-<LI>port offset number, displaying
-<A HREF="auarf081.htm#IDX4370">(4370)</A>
-<LI>restoring from tape
-<A HREF="auarf085.htm#IDX4396">(4396)</A>
-<LI>saving to tape
-<A HREF="auarf086.htm#IDX4399">(4399)</A>
-<LI>status, verifying
-<A HREF="auarf066.htm#IDX4266">(4266)</A>
-<LI>Tape Coordinator entry, creating
-<A HREF="auarf062.htm#IDX4235">(4235)</A>
-<LI>Tape Coordinator entry, deleting
-<A HREF="auarf069.htm#IDX4283">(4283)</A>
-<LI>Tape Coordinator entry, displaying
-<A HREF="auarf081.htm#IDX4371">(4371)</A>
-<LI>volume dump history, displaying
-<A HREF="auarf090.htm#IDX4418">(4418)</A>
-<LI>volume entry in volume set, displaying
-<A HREF="auarf082.htm#IDX4378">(4378)</A>
-<LI>volume entry, adding to volume set
-<A HREF="auarf063.htm#IDX4243">(4243)</A>, <A HREF="auarf063.htm#IDX4250">(4250)</A>
-<LI>volume entry, removing from volume set
-<A HREF="auarf070.htm#IDX4289">(4289)</A>
-<LI>volume set, creating
-<A HREF="auarf064.htm#IDX4258">(4258)</A>
-<LI>volume set, deleting
-<A HREF="auarf071.htm#IDX4294">(4294)</A>
-<LI>volume set, restoring
-<A HREF="auarf092.htm#IDX4433">(4433)</A>
-</MENU>
-<LI>backup extension on volume name
-<A HREF="auarf255.htm#IDX5603">(5603)</A>
-<MENU>
-<LI>added by vos backup command
-<A HREF="auarf255.htm#IDX5604">(5604)</A>
-<LI>added by vos backupsys command
-<A HREF="auarf256.htm#IDX5611">(5611)</A>
-</MENU>
-<LI>Backup field in volume header
-<A HREF="auarf261.htm#IDX5675">(5675)</A>, <A HREF="auarf266.htm#IDX5751">(5751)</A>
-<LI>Backup Server
-<MENU>
-<LI>initialization command
-<A HREF="auarf125.htm#IDX4687">(4687)</A>
-<LI>listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3917">(3917)</A>
-<LI>listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3925">(3925)</A>
-<LI>log file
-<A HREF="auarf014.htm#IDX3876">(3876)</A>, <A HREF="auarf015.htm#IDX3879">(3879)</A>
-</MENU>
-<LI>Backup System
-<MENU>
-<LI>Backup Server process, starting
-<A HREF="auarf125.htm#IDX4690">(4690)</A>
-<LI>database (see entry: <I>Backup Database</I>)
-<A HREF="auarf060.htm#IDX4208">(4208)</A>
-<LI>interactive mode, entering
-<A HREF="auarf076.htm#IDX4331">(4331)</A>
-<LI>interactive mode, exiting
-<A HREF="auarf083.htm#IDX4385">(4385)</A>
-<LI>job ID number, displaying
-<A HREF="auarf077.htm#IDX4334">(4334)</A>
-<LI>job ID number, using to halt operation
-<A HREF="auarf078.htm#IDX4343">(4343)</A>
-<LI>operations, displaying pending and running
-<A HREF="auarf077.htm#IDX4335">(4335)</A>
-<LI>operations, halting in interactive mode
-<A HREF="auarf078.htm#IDX4341">(4341)</A>
-<LI>regular expressions
-<A HREF="auarf063.htm#IDX4254">(4254)</A>
-<LI>tape capacity, displaying from label
-<A HREF="auarf084.htm#IDX4391">(4391)</A>
-<LI>tape capacity, recording on label
-<A HREF="auarf079.htm#IDX4352">(4352)</A>
-<LI>Tape Coordinator, initializing
-<A HREF="auarf126.htm#IDX4696">(4696)</A>
-<LI>tape, creating label
-<A HREF="auarf079.htm#IDX4351">(4351)</A>
-<LI>tape, displaying label
-<A HREF="auarf084.htm#IDX4390">(4390)</A>
-</MENU>
-<LI>backup volume
-<MENU>
-<LI>creating
-<A HREF="auarf255.htm#IDX5602">(5602)</A>
-<LI>creating many at once
-<A HREF="auarf256.htm#IDX5610">(5610)</A>
-<LI>dumping
-<A HREF="auarf260.htm#IDX5648">(5648)</A>
-<LI>ID number
-<A HREF="auarf258.htm#IDX5637">(5637)</A>
-<LI>ID number in volume header
-<A HREF="auarf261.htm#IDX5671">(5671)</A>, <A HREF="auarf266.htm#IDX5747">(5747)</A>
-<LI>moving
-<A HREF="auarf268.htm#IDX5774">(5774)</A>
-<LI>name, changing
-<A HREF="auarf273.htm#IDX5828">(5828)</A>
-<LI>removed by read/write move
-<A HREF="auarf268.htm#IDX5772">(5772)</A>
-<LI>removed by read/write removal
-<A HREF="auarf271.htm#IDX5810">(5810)</A>
-<LI>removing
-<A HREF="auarf271.htm#IDX5812">(5812)</A>
-</MENU>
-<LI>BackupLog file
-<A HREF="auarf014.htm#IDX3874">(3874)</A>
-<LI>BAK version of binary file
-<MENU>
-<LI>creation by bos install command
-<A HREF="auarf105.htm#IDX4554">(4554)</A>
-<LI>listing time stamp on
-<A HREF="auarf101.htm#IDX4521">(4521)</A>
-<LI>removing from /usr/afs/bin directory
-<A HREF="auarf109.htm#IDX4578">(4578)</A>
-<LI>use by bos uninstall command
-<A HREF="auarf123.htm#IDX4678">(4678)</A>
-</MENU>
-<LI>Basic OverSeer Server
-<MENU>
-<LI>see entry: <I>BOS Server</I>
-<A HREF="auarf093.htm#IDX4437">(4437)</A>
-</MENU>
-<LI>bdb.DB0 file
-<A HREF="auarf042.htm#IDX4006">(4006)</A>
-<LI>bdb.DBSYS1 file
-<A HREF="auarf042.htm#IDX4008">(4008)</A>
-<LI>binary distribution machine
-<A HREF="auarf105.htm#IDX4552">(4552)</A>, <A HREF="auarf123.htm#IDX4676">(4676)</A>
-<LI>binary file
-<MENU>
-<LI>installing
-<A HREF="auarf105.htm#IDX4550">(4550)</A>
-<LI>listing time stamp on
-<A HREF="auarf101.htm#IDX4519">(4519)</A>
-<LI>uninstalling
-<A HREF="auarf123.htm#IDX4674">(4674)</A>
-</MENU>
-<LI>block special device
-<MENU>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4045">(4045)</A>
-</MENU>
-<LI>bos commands
-<MENU>
-<LI>addhost
-<A HREF="auarf094.htm#IDX4451">(4451)</A>
-<LI>addkey
-<A HREF="auarf095.htm#IDX4463">(4463)</A>
-<LI>adduser
-<A HREF="auarf096.htm#IDX4471">(4471)</A>
-<LI>apropos
-<A HREF="auarf097.htm#IDX4473">(4473)</A>
-<LI>common options
-<A HREF="auarf093.htm#IDX4443">(4443)</A>
-<LI>create
-<A HREF="auarf098.htm#IDX4485">(4485)</A>
-<LI>delete
-<A HREF="auarf099.htm#IDX4509">(4509)</A>
-<LI>exec
-<A HREF="auarf100.htm#IDX4513">(4513)</A>
-<LI>getcell (see entry: <I>listhosts</I>)
-<A HREF="auarf106.htm#IDX4562">(4562)</A>
-<LI>getdate
-<A HREF="auarf101.htm#IDX4516">(4516)</A>
-<LI>getlog
-<A HREF="auarf102.htm#IDX4527">(4527)</A>
-<LI>getrestart
-<A HREF="auarf103.htm#IDX4543">(4543)</A>
-<LI>help
-<A HREF="auarf104.htm#IDX4545">(4545)</A>
-<LI>install
-<A HREF="auarf105.htm#IDX4548">(4548)</A>
-<LI>listhosts
-<A HREF="auarf106.htm#IDX4561">(4561)</A>
-<LI>listkeys
-<A HREF="auarf107.htm#IDX4566">(4566)</A>
-<LI>listusers
-<A HREF="auarf108.htm#IDX4573">(4573)</A>
-<LI>privilege requirements
-<A HREF="auarf093.htm#IDX4450">(4450)</A>
-<LI>prune
-<A HREF="auarf109.htm#IDX4575">(4575)</A>
-<LI>removehost
-<A HREF="auarf110.htm#IDX4588">(4588)</A>
-<LI>removekey
-<A HREF="auarf111.htm#IDX4596">(4596)</A>
-<LI>removeuser
-<A HREF="auarf112.htm#IDX4601">(4601)</A>
-<LI>restart
-<A HREF="auarf113.htm#IDX4603">(4603)</A>
-<LI>salvage
-<A HREF="auarf114.htm#IDX4615">(4615)</A>
-<LI>setauth
-<A HREF="auarf115.htm#IDX4620">(4620)</A>
-<LI>setcellname
-<A HREF="auarf116.htm#IDX4622">(4622)</A>
-<LI>setrestart
-<A HREF="auarf117.htm#IDX4634">(4634)</A>
-<LI>shutdown
-<A HREF="auarf118.htm#IDX4640">(4640)</A>
-<LI>start
-<A HREF="auarf119.htm#IDX4644">(4644)</A>
-<LI>startup
-<A HREF="auarf120.htm#IDX4652">(4652)</A>
-<LI>status
-<A HREF="auarf121.htm#IDX4656">(4656)</A>
-<LI>stop
-<A HREF="auarf122.htm#IDX4665">(4665)</A>
-<LI>uninstall
-<A HREF="auarf123.htm#IDX4671">(4671)</A>
-</MENU>
-<LI>BOS Server
-<A HREF="auarf093.htm#IDX4436">(4436)</A>
-<MENU>
-<LI>memory state
-<A HREF="auarf016.htm#IDX3894">(3894)</A>
-<LI>restart times, displaying
-<A HREF="auarf103.htm#IDX4537">(4537)</A>
-<LI>restart times, setting
-<A HREF="auarf117.htm#IDX4631">(4631)</A>
-<LI>restarting
-<A HREF="auarf113.htm#IDX4607">(4607)</A>
-<LI>SALVAGE.fs file, response to
-<A HREF="auarf029.htm#IDX3971">(3971)</A>
-<LI>starting
-<A HREF="auarf124.htm#IDX4682">(4682)</A>
-</MENU>
-<LI>BosConfig file
-<A HREF="auarf016.htm#IDX3880">(3880)</A>
-<MENU>
-<LI>creating entry with bos create command
-<A HREF="auarf098.htm#IDX4484">(4484)</A>
-<LI>displaying entry with bos status command
-<A HREF="auarf121.htm#IDX4662">(4662)</A>
-<LI>removing entry with bos delete command
-<A HREF="auarf099.htm#IDX4506">(4506)</A>
-</MENU>
-<LI>BosLog file
-<A HREF="auarf015.htm#IDX3877">(3877)</A>
-<LI>bosserver command
-<A HREF="auarf124.htm#IDX4680">(4680)</A>
-<LI>BUFFERSIZE instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3907">(3907)</A>
-<LI>bulk input file
-<MENU>
-<LI>see entry: <I>uss bulk input file</I>
-<A HREF="auarf054.htm#IDX4100">(4100)</A>
-</MENU>
-<LI>bulk mode in uss
-<A HREF="auarf245.htm#IDX5543">(5543)</A>
-<LI>buserver command
-<A HREF="auarf125.htm#IDX4685">(4685)</A>
-<LI>buserver process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4487">(4487)</A>
-</MENU>
-<LI>butc command
-<A HREF="auarf126.htm#IDX4691">(4691)</A>
-</MENU>
-<STRONG><A NAME="IDX1_43" HREF="#IDX0_43">C</A></STRONG>
-<MENU>
-<LI>C instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4042">(4042)</A>
-</MENU>
-<LI>Cache Manager
-<MENU>
-<LI>changing database server machines known to
-<A HREF="auarf154.htm#IDX4908">(4908)</A>
-<LI>configuring with afsd
-<A HREF="auarf058.htm#IDX4189">(4189)</A>
-<LI>configuring with fs commands
-<A HREF="auarf131.htm#IDX4716">(4716)</A>
-<LI>disabling messages
-<A HREF="auarf152.htm#IDX4890">(4890)</A>
-<LI>displaying amount of cache used
-<A HREF="auarf143.htm#IDX4832">(4832)</A>
-<LI>displaying cache size
-<A HREF="auarf143.htm#IDX4831">(4831)</A>
-<LI>displaying database server machines known to
-<A HREF="auarf149.htm#IDX4862">(4862)</A>
-<LI>displaying inaccessible server machines
-<A HREF="auarf133.htm#IDX4734">(4734)</A>
-<LI>displaying server machine preference ranks
-<A HREF="auarf146.htm#IDX4846">(4846)</A>
-<LI>flushing directory/file from data cache
-<A HREF="auarf140.htm#IDX4808">(4808)</A>
-<LI>flushing entire volume from data cache
-<A HREF="auarf142.htm#IDX4821">(4821)</A>
-<LI>flushing mount point from data cache
-<A HREF="auarf141.htm#IDX4815">(4815)</A>
-<LI>initializing with afsd
-<A HREF="auarf058.htm#IDX4188">(4188)</A>
-<LI>interfaces not registered with File Server, setting
-<A HREF="auarf026.htm#IDX3956">(3956)</A>
-<LI>interfaces registered with File Server, displaying
-<A HREF="auarf145.htm#IDX4841">(4841)</A>
-<LI>interfaces registered with File Server, setting
-<A HREF="auarf024.htm#IDX3945">(3945)</A>, <A HREF="auarf160.htm#IDX4963">(4963)</A>
-<LI>logging messages
-<A HREF="auarf152.htm#IDX4889">(4889)</A>
-<LI>monitoring status with afsmonitor
-<A HREF="auarf058.htm#IDX4196">(4196)</A>
-<LI>NetInfo file
-<A HREF="auarf024.htm#IDX3944">(3944)</A>
-<LI>NetRestrict file
-<A HREF="auarf026.htm#IDX3955">(3955)</A>
-<LI>setting cache size
-<A HREF="auarf158.htm#IDX4952">(4952)</A>
-<LI>setting server machine preference ranks
-<A HREF="auarf162.htm#IDX4973">(4973)</A>
-<LI>setting the interval between server probes
-<A HREF="auarf133.htm#IDX4735">(4735)</A>
-<LI>volume name to ID mapping, forcing update of
-<A HREF="auarf134.htm#IDX4739">(4739)</A>
-<LI>VolumeItems file
-<A HREF="auarf040.htm#IDX4002">(4002)</A>
-</MENU>
-<LI>cache-related file
-<MENU>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3864">(3864)</A>
-</MENU>
-<LI>CacheItems file
-<A HREF="auarf017.htm#IDX3897">(3897)</A>
-<LI>cell
-<MENU>
-<LI>client
-<A HREF="auarf149.htm#IDX4864">(4864)</A>, <A HREF="auarf154.htm#IDX4906">(4906)</A>
-<LI>database server machines listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3919">(3919)</A>
-<LI>database server machines listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3927">(3927)</A>
-<LI>membership of client machine
-<A HREF="auarf032.htm#IDX3977">(3977)</A>
-<LI>membership of server machine
-<A HREF="auarf033.htm#IDX3982">(3982)</A>
-<LI>name, setting
-<A HREF="auarf116.htm#IDX4628">(4628)</A>
-<LI>setuid status, displaying
-<A HREF="auarf144.htm#IDX4835">(4835)</A>
-<LI>setuid status, setting
-<A HREF="auarf159.htm#IDX4955">(4955)</A>
-</MENU>
-<LI>cell argument
-<MENU>
-<LI>on backup commands
-<A HREF="auarf060.htm#IDX4212">(4212)</A>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4444">(4444)</A>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5065">(5065)</A>
-<LI>on pts commands
-<A HREF="auarf210.htm#IDX5231">(5231)</A>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5511">(5511)</A>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5578">(5578)</A>
-</MENU>
-<LI>CellServDB file (client version)
-<A HREF="auarf019.htm#IDX3912">(3912)</A>
-<MENU>
-<LI>displaying contents as copied into kernel memory
-<A HREF="auarf149.htm#IDX4865">(4865)</A>
-</MENU>
-<LI>CellServDB file (server version)
-<A HREF="auarf020.htm#IDX3920">(3920)</A>
-<MENU>
-<LI>adding entry with bos addhost command
-<A HREF="auarf094.htm#IDX4454">(4454)</A>
-<LI>creating with bos setcellname command
-<A HREF="auarf116.htm#IDX4623">(4623)</A>
-<LI>displaying contents with bos listhosts command
-<A HREF="auarf106.htm#IDX4558">(4558)</A>
-<LI>removing entry with bos removehost command
-<A HREF="auarf110.htm#IDX4590">(4590)</A>
-</MENU>
-<LI>cellular mount point
-<A HREF="auarf153.htm#IDX4902">(4902)</A>
-<LI>CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3900">(3900)</A>
-<LI>changing
-<MENU>
-<LI>data cache size
-<A HREF="auarf158.htm#IDX4947">(4947)</A>
-<LI>database server machines listed in client kernel
-<A HREF="auarf154.htm#IDX4905">(4905)</A>
-<LI>name of Protection Database entry
-<A HREF="auarf224.htm#IDX5393">(5393)</A>
-<LI>owner of Protection Database entry
-<A HREF="auarf213.htm#IDX5251">(5251)</A>
-<LI>password in Authentication Database
-<A HREF="auarf202.htm#IDX5189">(5189)</A>
-<LI>volume name
-<A HREF="auarf273.htm#IDX5824">(5824)</A>
-<LI>volume quota
-<A HREF="auarf161.htm#IDX4967">(4967)</A>
-</MENU>
-<LI>character special device
-<MENU>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4052">(4052)</A>
-</MENU>
-<LI>character string
-<MENU>
-<LI>converting to octal key form
-<A HREF="auarf196.htm#IDX5164">(5164)</A>
-</MENU>
-<LI>checking
-<MENU>
-<LI>AFS client as exporter non-AFS file system
-<A HREF="auarf139.htm#IDX4800">(4800)</A>
-<LI>server machine status
-<A HREF="auarf133.htm#IDX4731">(4731)</A>
-</MENU>
-<LI>cleaning
-<MENU>
-<LI>ACL
-<A HREF="auarf135.htm#IDX4748">(4748)</A>
-</MENU>
-<LI>clearing
-<MENU>
-<LI>ACL
-<A HREF="auarf157.htm#IDX4932">(4932)</A>
-</MENU>
-<LI>client machine
-<MENU>
-<LI>as exporter of non-AFS file system
-<A HREF="auarf139.htm#IDX4802">(4802)</A>
-<LI>cell membership
-<A HREF="auarf032.htm#IDX3978">(3978)</A>
-<LI>changing database server machines known to
-<A HREF="auarf154.htm#IDX4909">(4909)</A>
-<LI>changing size of data cache
-<A HREF="auarf158.htm#IDX4951">(4951)</A>
-<LI>configuring local disk with package
-<A HREF="auarf204.htm#IDX5200">(5200)</A>
-<LI>displaying database server machines known to
-<A HREF="auarf149.htm#IDX4863">(4863)</A>
-<LI>displaying home cell of
-<A HREF="auarf168.htm#IDX5018">(5018)</A>
-<LI>displaying system type
-<A HREF="auarf165.htm#IDX4989">(4989)</A>, <A HREF="auarf234.htm#IDX5470">(5470)</A>
-<LI>setting system type
-<A HREF="auarf165.htm#IDX4993">(4993)</A>
-</MENU>
-<LI>client machines statistic in scout
-<A HREF="auarf233.htm#IDX5463">(5463)</A>
-<LI>client portion of Update Server
-<MENU>
-<LI>see entry: <I>upclient process</I>
-<A HREF="auarf240.htm#IDX5500">(5500)</A>
-</MENU>
-<LI>clone
-<A HREF="auarf270.htm#IDX5785">(5785)</A>
-<MENU>
-<LI>forcing creation of new
-<A HREF="auarf270.htm#IDX5802">(5802)</A>
-</MENU>
-<LI>cloning
-<MENU>
-<LI>for backup
-<A HREF="auarf255.htm#IDX5599">(5599)</A>, <A HREF="auarf256.htm#IDX5608">(5608)</A>
-<LI>volume for replication
-<A HREF="auarf270.htm#IDX5790">(5790)</A>
-</MENU>
-<LI>commands
-<MENU>
-<LI>afsd
-<A HREF="auarf058.htm#IDX4185">(4185)</A>
-<LI>afsmonitor
-<A HREF="auarf058.htm#IDX4194">(4194)</A>
-<LI>backup (introduction)
-<A HREF="auarf060.htm#IDX4203">(4203)</A>
-<LI>backup adddump
-<A HREF="auarf061.htm#IDX4219">(4219)</A>
-<LI>backup addhost
-<A HREF="auarf062.htm#IDX4230">(4230)</A>
-<LI>backup addvolentry
-<A HREF="auarf063.htm#IDX4239">(4239)</A>, <A HREF="auarf063.htm#IDX4246">(4246)</A>
-<LI>backup addvolset
-<A HREF="auarf064.htm#IDX4256">(4256)</A>
-<LI>backup apropos
-<A HREF="auarf065.htm#IDX4262">(4262)</A>
-<LI>backup dbverify
-<A HREF="auarf066.htm#IDX4265">(4265)</A>
-<LI>backup deldump
-<A HREF="auarf067.htm#IDX4268">(4268)</A>
-<LI>backup deletedump
-<A HREF="auarf068.htm#IDX4276">(4276)</A>
-<LI>backup delhost
-<A HREF="auarf069.htm#IDX4280">(4280)</A>
-<LI>backup delvolentry
-<A HREF="auarf070.htm#IDX4285">(4285)</A>
-<LI>backup delvolset
-<A HREF="auarf071.htm#IDX4291">(4291)</A>
-<LI>backup diskrestore
-<A HREF="auarf072.htm#IDX4297">(4297)</A>
-<LI>backup dump
-<A HREF="auarf073.htm#IDX4303">(4303)</A>
-<LI>backup dumpinfo
-<A HREF="auarf074.htm#IDX4317">(4317)</A>
-<LI>backup help
-<A HREF="auarf075.htm#IDX4325">(4325)</A>
-<LI>backup interactive
-<A HREF="auarf076.htm#IDX4328">(4328)</A>
-<LI>backup jobs
-<A HREF="auarf077.htm#IDX4333">(4333)</A>
-<LI>backup kill
-<A HREF="auarf078.htm#IDX4340">(4340)</A>
-<LI>backup labeltape
-<A HREF="auarf079.htm#IDX4346">(4346)</A>
-<LI>backup listdumps
-<A HREF="auarf080.htm#IDX4358">(4358)</A>
-<LI>backup listhosts
-<A HREF="auarf081.htm#IDX4366">(4366)</A>
-<LI>backup listvolsets
-<A HREF="auarf082.htm#IDX4375">(4375)</A>
-<LI>backup quit
-<A HREF="auarf083.htm#IDX4381">(4381)</A>
-<LI>backup readlabel
-<A HREF="auarf084.htm#IDX4387">(4387)</A>
-<LI>backup restoredb
-<A HREF="auarf085.htm#IDX4395">(4395)</A>
-<LI>backup savedb
-<A HREF="auarf086.htm#IDX4398">(4398)</A>
-<LI>backup scantape
-<A HREF="auarf087.htm#IDX4401">(4401)</A>
-<LI>backup setexp
-<A HREF="auarf088.htm#IDX4407">(4407)</A>
-<LI>backup status
-<A HREF="auarf089.htm#IDX4413">(4413)</A>
-<LI>backup volinfo
-<A HREF="auarf090.htm#IDX4417">(4417)</A>
-<LI>backup volrestore
-<A HREF="auarf091.htm#IDX4423">(4423)</A>
-<LI>backup volsetrestore
-<A HREF="auarf092.htm#IDX4429">(4429)</A>
-<LI>bos (introduction)
-<A HREF="auarf093.htm#IDX4435">(4435)</A>
-<LI>bos addhost
-<A HREF="auarf094.htm#IDX4452">(4452)</A>
-<LI>bos addkey
-<A HREF="auarf095.htm#IDX4464">(4464)</A>
-<LI>bos adduser
-<A HREF="auarf096.htm#IDX4472">(4472)</A>
-<LI>bos apropos
-<A HREF="auarf097.htm#IDX4474">(4474)</A>
-<LI>bos create
-<A HREF="auarf098.htm#IDX4486">(4486)</A>
-<LI>bos delete
-<A HREF="auarf099.htm#IDX4510">(4510)</A>
-<LI>bos exec
-<A HREF="auarf100.htm#IDX4514">(4514)</A>
-<LI>bos getdate
-<A HREF="auarf101.htm#IDX4520">(4520)</A>
-<LI>bos getlog
-<A HREF="auarf102.htm#IDX4528">(4528)</A>
-<LI>bos getrestart
-<A HREF="auarf103.htm#IDX4544">(4544)</A>
-<LI>bos help
-<A HREF="auarf104.htm#IDX4546">(4546)</A>
-<LI>bos install
-<A HREF="auarf105.htm#IDX4553">(4553)</A>
-<LI>bos listhosts
-<A HREF="auarf106.htm#IDX4560">(4560)</A>
-<LI>bos listkeys
-<A HREF="auarf107.htm#IDX4567">(4567)</A>
-<LI>bos listusers
-<A HREF="auarf108.htm#IDX4574">(4574)</A>
-<LI>bos prune
-<A HREF="auarf109.htm#IDX4582">(4582)</A>
-<LI>bos removehost
-<A HREF="auarf110.htm#IDX4592">(4592)</A>
-<LI>bos removekey
-<A HREF="auarf111.htm#IDX4597">(4597)</A>
-<LI>bos removeuser
-<A HREF="auarf112.htm#IDX4602">(4602)</A>
-<LI>bos restart
-<A HREF="auarf113.htm#IDX4608">(4608)</A>
-<LI>bos salvage
-<A HREF="auarf114.htm#IDX4616">(4616)</A>
-<LI>bos setauth
-<A HREF="auarf115.htm#IDX4621">(4621)</A>
-<LI>bos setcellname
-<A HREF="auarf116.htm#IDX4629">(4629)</A>
-<LI>bos setrestart
-<A HREF="auarf117.htm#IDX4635">(4635)</A>
-<LI>bos shutdown
-<A HREF="auarf118.htm#IDX4641">(4641)</A>
-<LI>bos start
-<A HREF="auarf119.htm#IDX4649">(4649)</A>
-<LI>bos startup
-<A HREF="auarf120.htm#IDX4655">(4655)</A>
-<LI>bos status
-<A HREF="auarf121.htm#IDX4660">(4660)</A>
-<LI>bos stop
-<A HREF="auarf122.htm#IDX4670">(4670)</A>
-<LI>bos uninstall
-<A HREF="auarf123.htm#IDX4677">(4677)</A>
-<LI>bosserver
-<A HREF="auarf124.htm#IDX4681">(4681)</A>
-<LI>buserver
-<A HREF="auarf125.htm#IDX4686">(4686)</A>
-<LI>butc
-<A HREF="auarf126.htm#IDX4692">(4692)</A>
-<LI>dlog
-<A HREF="auarf127.htm#IDX4698">(4698)</A>
-<LI>dpass
-<A HREF="auarf128.htm#IDX4700">(4700)</A>
-<LI>executing remotely
-<A HREF="auarf100.htm#IDX4512">(4512)</A>
-<LI>fileserver
-<A HREF="auarf129.htm#IDX4702">(4702)</A>
-<LI>fms
-<A HREF="auarf130.htm#IDX4706">(4706)</A>
-<LI>fs apropos
-<A HREF="auarf132.htm#IDX4726">(4726)</A>
-<LI>fs checkservers
-<A HREF="auarf133.htm#IDX4729">(4729)</A>
-<LI>fs checkvolumes
-<A HREF="auarf134.htm#IDX4737">(4737)</A>
-<LI>fs cleanacl
-<A HREF="auarf135.htm#IDX4752">(4752)</A>
-<LI>fs copyacl
-<A HREF="auarf136.htm#IDX4756">(4756)</A>
-<LI>fs diskfree
-<A HREF="auarf137.htm#IDX4771">(4771)</A>
-<LI>fs examine
-<A HREF="auarf138.htm#IDX4795">(4795)</A>
-<LI>fs exportafs
-<A HREF="auarf139.htm#IDX4797">(4797)</A>
-<LI>fs flush
-<A HREF="auarf140.htm#IDX4812">(4812)</A>
-<LI>fs flushmount
-<A HREF="auarf141.htm#IDX4818">(4818)</A>
-<LI>fs flushvolume
-<A HREF="auarf142.htm#IDX4824">(4824)</A>
-<LI>fs getcacheparms
-<A HREF="auarf143.htm#IDX4826">(4826)</A>
-<LI>fs getcellstatus
-<A HREF="auarf144.htm#IDX4834">(4834)</A>
-<LI>fs getclientaddrs
-<A HREF="auarf145.htm#IDX4840">(4840)</A>
-<LI>fs getserverprefs
-<A HREF="auarf146.htm#IDX4845">(4845)</A>
-<LI>fs help
-<A HREF="auarf147.htm#IDX4852">(4852)</A>
-<LI>fs listacl
-<A HREF="auarf148.htm#IDX4859">(4859)</A>
-<LI>fs listcells
-<A HREF="auarf149.htm#IDX4868">(4868)</A>
-<LI>fs listquota
-<A HREF="auarf150.htm#IDX4870">(4870)</A>
-<LI>fs lsmount
-<A HREF="auarf151.htm#IDX4888">(4888)</A>
-<LI>fs messages
-<A HREF="auarf152.htm#IDX4892">(4892)</A>
-<LI>fs mkmount
-<A HREF="auarf153.htm#IDX4897">(4897)</A>
-<LI>fs newcell
-<A HREF="auarf154.htm#IDX4912">(4912)</A>
-<LI>fs quota
-<A HREF="auarf155.htm#IDX4914">(4914)</A>
-<LI>fs rmmount
-<A HREF="auarf156.htm#IDX4923">(4923)</A>
-<LI>fs setacl
-<A HREF="auarf157.htm#IDX4936">(4936)</A>
-<LI>fs setcachesize
-<A HREF="auarf158.htm#IDX4954">(4954)</A>
-<LI>fs setcell
-<A HREF="auarf159.htm#IDX4960">(4960)</A>
-<LI>fs setclientaddrs
-<A HREF="auarf160.htm#IDX4962">(4962)</A>
-<LI>fs setquota
-<A HREF="auarf161.htm#IDX4970">(4970)</A>
-<LI>fs setserverprefs
-<A HREF="auarf162.htm#IDX4972">(4972)</A>
-<LI>fs setvol
-<A HREF="auarf163.htm#IDX4984">(4984)</A>
-<LI>fs storebehind
-<A HREF="auarf164.htm#IDX4985">(4985)</A>
-<LI>fs sysname
-<A HREF="auarf165.htm#IDX4988">(4988)</A>
-<LI>fs whereis
-<A HREF="auarf166.htm#IDX5007">(5007)</A>
-<LI>fs whichcell
-<A HREF="auarf167.htm#IDX5014">(5014)</A>
-<LI>fs wscell
-<A HREF="auarf168.htm#IDX5020">(5020)</A>
-<LI>fstrace (introduction)
-<A HREF="auarf169.htm#IDX5026">(5026)</A>
-<LI>fstrace apropos
-<A HREF="auarf170.htm#IDX5029">(5029)</A>
-<LI>fstrace dump
-<A HREF="auarf172.htm#IDX5032">(5032)</A>
-<LI>fstrace help
-<A HREF="auarf173.htm#IDX5034">(5034)</A>
-<LI>fstrace lslog
-<A HREF="auarf174.htm#IDX5037">(5037)</A>
-<LI>fstrace lsset
-<A HREF="auarf175.htm#IDX5039">(5039)</A>
-<LI>fstrace setlog
-<A HREF="auarf176.htm#IDX5041">(5041)</A>
-<LI>fstrace setset
-<A HREF="auarf177.htm#IDX5043">(5043)</A>
-<LI>ftpd (AFS version)
-<A HREF="auarf178.htm#IDX5045">(5045)</A>
-<LI>inetd (AFS version)
-<A HREF="auarf179.htm#IDX5050">(5050)</A>
-<LI>kadb_check
-<A HREF="auarf180.htm#IDX5055">(5055)</A>
-<LI>kas apropos
-<A HREF="auarf182.htm#IDX5071">(5071)</A>
-<LI>kas create
-<A HREF="auarf183.htm#IDX5074">(5074)</A>
-<LI>kas delete
-<A HREF="auarf184.htm#IDX5079">(5079)</A>
-<LI>kas examine
-<A HREF="auarf185.htm#IDX5083">(5083)</A>
-<LI>kas forgetticket
-<A HREF="auarf186.htm#IDX5105">(5105)</A>
-<LI>kas help
-<A HREF="auarf187.htm#IDX5110">(5110)</A>
-<LI>kas list
-<A HREF="auarf189.htm#IDX5113">(5113)</A>
-<LI>kas listtickets
-<A HREF="auarf190.htm#IDX5117">(5117)</A>
-<LI>kas noauthentication
-<A HREF="auarf191.htm#IDX5120">(5120)</A>
-<LI>kas quit
-<A HREF="auarf192.htm#IDX5125">(5125)</A>
-<LI>kas setfields
-<A HREF="auarf193.htm#IDX5131">(5131)</A>
-<LI>kas setpassword
-<A HREF="auarf194.htm#IDX5148">(5148)</A>
-<LI>kas statistics
-<A HREF="auarf195.htm#IDX5156">(5156)</A>
-<LI>kas stringtokey
-<A HREF="auarf196.htm#IDX5162">(5162)</A>
-<LI>kas unlock
-<A HREF="auarf197.htm#IDX5168">(5168)</A>
-<LI>kaserver
-<A HREF="auarf198.htm#IDX5171">(5171)</A>
-<LI>kdb
-<A HREF="auarf199.htm#IDX5174">(5174)</A>
-<LI>klog
-<A HREF="auarf200.htm#IDX5177">(5177)</A>
-<LI>knfs
-<A HREF="auarf201.htm#IDX5184">(5184)</A>
-<LI>kpasswd
-<A HREF="auarf202.htm#IDX5188">(5188)</A>
-<LI>kpwvalid
-<A HREF="auarf203.htm#IDX5195">(5195)</A>
-<LI>package
-<A HREF="auarf204.htm#IDX5198">(5198)</A>
-<LI>package apropos
-<A HREF="auarf205.htm#IDX5205">(5205)</A>
-<LI>package help
-<A HREF="auarf206.htm#IDX5208">(5208)</A>
-<LI>package_test
-<A HREF="auarf207.htm#IDX5211">(5211)</A>
-<LI>pagsh
-<A HREF="auarf208.htm#IDX5214">(5214)</A>
-<LI>prdb_check
-<A HREF="auarf209.htm#IDX5218">(5218)</A>
-<LI>pts adduser
-<A HREF="auarf211.htm#IDX5236">(5236)</A>
-<LI>pts apropos
-<A HREF="auarf212.htm#IDX5245">(5245)</A>
-<LI>pts chown
-<A HREF="auarf213.htm#IDX5248">(5248)</A>
-<LI>pts creategroup
-<A HREF="auarf214.htm#IDX5253">(5253)</A>
-<LI>pts createuser
-<A HREF="auarf215.htm#IDX5275">(5275)</A>
-<LI>pts delete
-<A HREF="auarf216.htm#IDX5294">(5294)</A>
-<LI>pts examine
-<A HREF="auarf217.htm#IDX5304">(5304)</A>
-<LI>pts help
-<A HREF="auarf218.htm#IDX5351">(5351)</A>
-<LI>pts listentries
-<A HREF="auarf219.htm#IDX5354">(5354)</A>
-<LI>pts listmax
-<A HREF="auarf220.htm#IDX5360">(5360)</A>
-<LI>pts listowned
-<A HREF="auarf221.htm#IDX5368">(5368)</A>
-<LI>pts membership
-<A HREF="auarf222.htm#IDX5375">(5375)</A>
-<LI>pts removeuser
-<A HREF="auarf223.htm#IDX5383">(5383)</A>
-<LI>pts rename
-<A HREF="auarf224.htm#IDX5391">(5391)</A>
-<LI>pts setfields
-<A HREF="auarf225.htm#IDX5397">(5397)</A>
-<LI>pts setmax
-<A HREF="auarf226.htm#IDX5410">(5410)</A>
-<LI>ptserver
-<A HREF="auarf227.htm#IDX5418">(5418)</A>
-<LI>rcp (AFS version)
-<A HREF="auarf228.htm#IDX5423">(5423)</A>
-<LI>rsh (AFS version)
-<A HREF="auarf229.htm#IDX5429">(5429)</A>
-<LI>runntp
-<A HREF="auarf230.htm#IDX5434">(5434)</A>
-<LI>rxdebug
-<A HREF="auarf231.htm#IDX5441">(5441)</A>
-<LI>salvager
-<A HREF="auarf232.htm#IDX5443">(5443)</A>
-<LI>scout
-<A HREF="auarf233.htm#IDX5448">(5448)</A>
-<LI>sys
-<A HREF="auarf234.htm#IDX5469">(5469)</A>
-<LI>tokens
-<A HREF="auarf235.htm#IDX5478">(5478)</A>
-<LI>translate_et
-<A HREF="auarf236.htm#IDX5482">(5482)</A>
-<LI>udebug
-<A HREF="auarf237.htm#IDX5485">(5485)</A>
-<LI>unlog
-<A HREF="auarf238.htm#IDX5488">(5488)</A>
-<LI>up
-<A HREF="auarf239.htm#IDX5494">(5494)</A>
-<LI>upclient
-<A HREF="auarf240.htm#IDX5498">(5498)</A>
-<LI>upserver
-<A HREF="auarf241.htm#IDX5504">(5504)</A>
-<LI>uss add
-<A HREF="auarf243.htm#IDX5518">(5518)</A>
-<LI>uss apropos
-<A HREF="auarf244.htm#IDX5537">(5537)</A>
-<LI>uss bulk
-<A HREF="auarf245.htm#IDX5540">(5540)</A>
-<LI>uss delete
-<A HREF="auarf246.htm#IDX5544">(5544)</A>
-<LI>uss help
-<A HREF="auarf247.htm#IDX5555">(5555)</A>
-<LI>vldb_check
-<A HREF="auarf248.htm#IDX5558">(5558)</A>
-<LI>vlserver
-<A HREF="auarf249.htm#IDX5561">(5561)</A>
-<LI>volinfo
-<A HREF="auarf250.htm#IDX5565">(5565)</A>
-<LI>volserver
-<A HREF="auarf251.htm#IDX5567">(5567)</A>
-<LI>vos (introduction)
-<A HREF="auarf252.htm#IDX5569">(5569)</A>
-<LI>vos addsite
-<A HREF="auarf253.htm#IDX5588">(5588)</A>
-<LI>vos apropos
-<A HREF="auarf254.htm#IDX5594">(5594)</A>
-<LI>vos backup
-<A HREF="auarf255.htm#IDX5597">(5597)</A>
-<LI>vos backupsys
-<A HREF="auarf256.htm#IDX5606">(5606)</A>
-<LI>vos changeaddr
-<A HREF="auarf257.htm#IDX5613">(5613)</A>
-<LI>vos create
-<A HREF="auarf258.htm#IDX5615">(5615)</A>
-<LI>vos delentry
-<A HREF="auarf259.htm#IDX5639">(5639)</A>
-<LI>vos dump
-<A HREF="auarf260.htm#IDX5643">(5643)</A>
-<LI>vos examine
-<A HREF="auarf261.htm#IDX5655">(5655)</A>
-<LI>vos help
-<A HREF="auarf262.htm#IDX5696">(5696)</A>
-<LI>vos listaddrs
-<A HREF="auarf263.htm#IDX5699">(5699)</A>
-<LI>vos listpart
-<A HREF="auarf264.htm#IDX5704">(5704)</A>
-<LI>vos listvldb
-<A HREF="auarf265.htm#IDX5709">(5709)</A>
-<LI>vos listvol
-<A HREF="auarf266.htm#IDX5730">(5730)</A>
-<LI>vos lock
-<A HREF="auarf267.htm#IDX5762">(5762)</A>
-<LI>vos move
-<A HREF="auarf268.htm#IDX5767">(5767)</A>
-<LI>vos partinfo
-<A HREF="auarf269.htm#IDX5776">(5776)</A>
-<LI>vos release
-<A HREF="auarf270.htm#IDX5783">(5783)</A>
-<LI>vos remove
-<A HREF="auarf271.htm#IDX5806">(5806)</A>
-<LI>vos remsite
-<A HREF="auarf272.htm#IDX5814">(5814)</A>
-<LI>vos rename
-<A HREF="auarf273.htm#IDX5820">(5820)</A>
-<LI>vos restore
-<A HREF="auarf274.htm#IDX5830">(5830)</A>
-<LI>vos status
-<A HREF="auarf275.htm#IDX5834">(5834)</A>
-<LI>vos syncserv
-<A HREF="auarf276.htm#IDX5839">(5839)</A>
-<LI>vos syncvldb
-<A HREF="auarf277.htm#IDX5847">(5847)</A>
-<LI>vos unlock
-<A HREF="auarf278.htm#IDX5856">(5856)</A>
-<LI>vos unlockvldb
-<A HREF="auarf279.htm#IDX5860">(5860)</A>
-<LI>vos zap
-<A HREF="auarf280.htm#IDX5864">(5864)</A>
-<LI>xfs_size_check
-<A HREF="auarf281.htm#IDX5868">(5868)</A>
-<LI>xstat_cm_test
-<A HREF="auarf282.htm#IDX5870">(5870)</A>
-<LI>xstat_fs_test
-<A HREF="auarf283.htm#IDX5872">(5872)</A>
-</MENU>
-<LI>common options
-<MENU>
-<LI>on backup commands
-<A HREF="auarf060.htm#IDX4210">(4210)</A>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4442">(4442)</A>
-<LI>on fs commands
-<A HREF="auarf131.htm#IDX4720">(4720)</A>
-<LI>on fstrace commands
-<A HREF="auarf169.htm#IDX5024">(5024)</A>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5057">(5057)</A>
-<LI>on pts commands
-<A HREF="auarf210.htm#IDX5227">(5227)</A>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5508">(5508)</A>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5576">(5576)</A>
-</MENU>
-<LI>configuration file
-<MENU>
-<LI>see entry: <I>afsmonitor configuration file</I>
-<A HREF="auarf052.htm#IDX4037">(4037)</A>
-<LI>see entry: <I>CFG_<device_name> configuration file</I>
-<A HREF="auarf018.htm#IDX3904">(3904)</A>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3862">(3862)</A>
-<LI>see entry: <I>package configuration file</I>
-<A HREF="auarf053.htm#IDX4039">(4039)</A>
-</MENU>
-<LI>configuring
-<MENU>
-<LI>Cache Manager with afsd
-<A HREF="auarf058.htm#IDX4187">(4187)</A>
-<LI>Cache Manager with fs commands
-<A HREF="auarf131.htm#IDX4718">(4718)</A>
-<LI>local disk of client with package
-<A HREF="auarf204.htm#IDX5199">(5199)</A>
-</MENU>
-<LI>connections statistic in scout
-<A HREF="auarf233.htm#IDX5459">(5459)</A>
-<LI>contacting
-<MENU>
-<LI>file server with fs commands
-<A HREF="auarf131.htm#IDX4717">(4717)</A>
-</MENU>
-<LI>controller file
-<MENU>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3867">(3867)</A>
-</MENU>
-<LI>controlling
-<MENU>
-<LI>Cache Manager with fs commands
-<A HREF="auarf131.htm#IDX4719">(4719)</A>
-<LI>server process status with entry in BosConfig file
-<A HREF="auarf016.htm#IDX3883">(3883)</A>
-</MENU>
-<LI>converting
-<MENU>
-<LI>character string to octal key form
-<A HREF="auarf196.htm#IDX5163">(5163)</A>
-</MENU>
-<LI>copying
-<MENU>
-<LI>access control list
-<A HREF="auarf136.htm#IDX4754">(4754)</A>
-<LI>file remotely with rcp command (AFS version)
-<A HREF="auarf228.htm#IDX5426">(5426)</A>
-<LI>files and directories
-<A HREF="auarf239.htm#IDX5495">(5495)</A>
-</MENU>
-<LI>core files
-<MENU>
-<LI>removing from /usr/afs/logs directory
-<A HREF="auarf109.htm#IDX4581">(4581)</A>
-</MENU>
-<LI>creating
-<MENU>
-<LI>Authentication Database entry
-<A HREF="auarf183.htm#IDX5075">(5075)</A>
-<LI>Authentication Database entry with uss
-<A HREF="auarf243.htm#IDX5523">(5523)</A>
-<LI>backup volume
-<A HREF="auarf255.htm#IDX5600">(5600)</A>
-<LI>backup volumes, many at once
-<A HREF="auarf256.htm#IDX5609">(5609)</A>
-<LI>buserver process
-<A HREF="auarf098.htm#IDX4488">(4488)</A>
-<LI>directory with uss
-<A HREF="auarf055.htm#IDX4125">(4125)</A>, <A HREF="auarf055.htm#IDX4145">(4145)</A>
-<LI>dump level in Backup System dump hierarchy
-<A HREF="auarf061.htm#IDX4221">(4221)</A>
-<LI>file with uss
-<A HREF="auarf055.htm#IDX4133">(4133)</A>, <A HREF="auarf055.htm#IDX4139">(4139)</A>
-<LI>fs process
-<A HREF="auarf098.htm#IDX4490">(4490)</A>
-<LI>group in Protection Database
-<A HREF="auarf214.htm#IDX5255">(5255)</A>
-<LI>hard link with uss
-<A HREF="auarf055.htm#IDX4152">(4152)</A>
-<LI>kaserver process
-<A HREF="auarf098.htm#IDX4492">(4492)</A>
-<LI>machine entry in Protection Database
-<A HREF="auarf215.htm#IDX5279">(5279)</A>
-<LI>mount point
-<A HREF="auarf153.htm#IDX4894">(4894)</A>
-<LI>mount point with uss
-<A HREF="auarf055.htm#IDX4168">(4168)</A>
-<LI>PAG with pagsh command
-<A HREF="auarf208.htm#IDX5216">(5216)</A>
-<LI>privileged user in UserList file
-<A HREF="auarf096.htm#IDX4468">(4468)</A>
-<LI>Protection Database entry with uss
-<A HREF="auarf243.htm#IDX5522">(5522)</A>
-<LI>ptserver process
-<A HREF="auarf098.htm#IDX4494">(4494)</A>
-<LI>read-only volume
-<A HREF="auarf270.htm#IDX5789">(5789)</A>
-<LI>read/write volume
-<A HREF="auarf258.htm#IDX5616">(5616)</A>
-<LI>runntp process
-<A HREF="auarf098.htm#IDX4496">(4496)</A>
-<LI>server encryption key
-<A HREF="auarf095.htm#IDX4458">(4458)</A>
-<LI>server process in BosConfig file
-<A HREF="auarf098.htm#IDX4479">(4479)</A>
-<LI>symbolic link with uss
-<A HREF="auarf055.htm#IDX4158">(4158)</A>
-<LI>Tape Coordinator entry in Backup Database
-<A HREF="auarf062.htm#IDX4236">(4236)</A>
-<LI>ticket (tokens) for server process
-<A HREF="auarf200.htm#IDX5178">(5178)</A>
-<LI>upclient process
-<A HREF="auarf098.htm#IDX4498">(4498)</A>
-<LI>upserver process
-<A HREF="auarf098.htm#IDX4500">(4500)</A>
-<LI>user account with uss
-<A HREF="auarf243.htm#IDX5520">(5520)</A>
-<LI>user accounts in bulk
-<A HREF="auarf245.htm#IDX5541">(5541)</A>
-<LI>user entry in Protection Database
-<A HREF="auarf215.htm#IDX5278">(5278)</A>
-<LI>vlserver process
-<A HREF="auarf098.htm#IDX4502">(4502)</A>
-<LI>volume (see type--read/write, etc.)
-<A HREF="auarf258.htm#IDX5617">(5617)</A>
-<LI>volume set in Backup Database
-<A HREF="auarf064.htm#IDX4259">(4259)</A>
-<LI>volume with uss
-<A HREF="auarf055.htm#IDX4167">(4167)</A>, <A HREF="auarf243.htm#IDX5524">(5524)</A>
-</MENU>
-<LI>creation date
-<MENU>
-<LI>recorded in volume header
-<A HREF="auarf261.htm#IDX5679">(5679)</A>, <A HREF="auarf266.htm#IDX5755">(5755)</A>
-</MENU>
-<LI>creator
-<MENU>
-<LI>Protection Database entry, displaying
-<A HREF="auarf217.htm#IDX5332">(5332)</A>
-</MENU>
-<LI>cron process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4505">(4505)</A>
-<LI>recorded in <I>BosConfig</I> file
-<A HREF="auarf016.htm#IDX3886">(3886)</A>
-</MENU>
-<LI>curses graphics utility
-<MENU>
-<LI>afsmonitor program
-<A HREF="auarf059.htm#IDX4198">(4198)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_44" HREF="#IDX0_44">D</A></STRONG>
-<MENU>
-<LI>D instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4056">(4056)</A>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4120">(4120)</A>
-</MENU>
-<LI>daily restart time for new binaries
-<MENU>
-<LI>see entry: <I>restart times for BOS Server</I>
-<A HREF="auarf103.htm#IDX4540">(4540)</A>
-</MENU>
-<LI>data
-<MENU>
-<LI>availability interrupted by dumping
-<A HREF="auarf260.htm#IDX5650">(5650)</A>
-</MENU>
-<LI>data cache
-<MENU>
-<LI>changing size of
-<A HREF="auarf158.htm#IDX4949">(4949)</A>
-<LI>displaying amount used
-<A HREF="auarf143.htm#IDX4828">(4828)</A>
-<LI>displaying size
-<A HREF="auarf143.htm#IDX4827">(4827)</A>
-<LI>flushing directory/file
-<A HREF="auarf140.htm#IDX4806">(4806)</A>
-<LI>flushing entire volume
-<A HREF="auarf142.htm#IDX4819">(4819)</A>
-<LI>flushing mount point
-<A HREF="auarf141.htm#IDX4813">(4813)</A>
-<LI>resetting to default size
-<A HREF="auarf158.htm#IDX4950">(4950)</A>
-<LI>setting location with afsd
-<A HREF="auarf058.htm#IDX4191">(4191)</A>
-<LI>setting size with afsd
-<A HREF="auarf058.htm#IDX4190">(4190)</A>
-</MENU>
-<LI>database file
-<MENU>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3866">(3866)</A>
-</MENU>
-<LI>database server machine
-<MENU>
-<LI>adding to CellServDB file (server)
-<A HREF="auarf094.htm#IDX4455">(4455)</A>
-<LI>changing client kernel list of
-<A HREF="auarf154.htm#IDX4907">(4907)</A>
-<LI>displaying from client kernel
-<A HREF="auarf149.htm#IDX4861">(4861)</A>
-<LI>displaying list in CellServDB file (server)
-<A HREF="auarf106.htm#IDX4559">(4559)</A>
-<LI>listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3918">(3918)</A>
-<LI>listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3926">(3926)</A>
-<LI>removing from CellServDB file (server)
-<A HREF="auarf110.htm#IDX4591">(4591)</A>
-</MENU>
-<LI>date on file
-<MENU>
-<LI>see entry: <I>time stamp</I>
-<A HREF="auarf101.htm#IDX4524">(4524)</A>
-</MENU>
-<LI>date-specific restore
-<MENU>
-<LI>see entry: <I>restoring</I>
-<A HREF="auarf091.htm#IDX4427">(4427)</A>
-</MENU>
-<LI>default
-<MENU>
-<LI>ACL for new volume
-<A HREF="auarf258.htm#IDX5627">(5627)</A>
-<LI>volume quota
-<A HREF="auarf258.htm#IDX5628">(5628)</A>
-</MENU>
-<LI>define statement
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4085">(4085)</A>
-</MENU>
-<LI>defining
-<MENU>
-<LI>block special device with package
-<A HREF="auarf053.htm#IDX4044">(4044)</A>
-<LI>capacity of Backup System tape
-<A HREF="auarf079.htm#IDX4348">(4348)</A>
-<LI>character special device with package
-<A HREF="auarf053.htm#IDX4051">(4051)</A>
-<LI>directory with package
-<A HREF="auarf053.htm#IDX4059">(4059)</A>
-<LI>file with package
-<A HREF="auarf053.htm#IDX4066">(4066)</A>
-<LI>privileged user in UserList file
-<A HREF="auarf096.htm#IDX4467">(4467)</A>
-<LI>read-only site in VLDB
-<A HREF="auarf253.htm#IDX5589">(5589)</A>
-<LI>server encryption key
-<A HREF="auarf095.htm#IDX4457">(4457)</A>
-<LI>socket with package
-<A HREF="auarf053.htm#IDX4080">(4080)</A>
-<LI>symbolic link with package
-<A HREF="auarf053.htm#IDX4073">(4073)</A>
-<LI>system type of client machine
-<A HREF="auarf165.htm#IDX4991">(4991)</A>
-</MENU>
-<LI>delete instruction in uss bulk input file
-<A HREF="auarf054.htm#IDX4105">(4105)</A>
-<LI>deleting
-<MENU>
-<LI>Authentication Database entry
-<A HREF="auarf184.htm#IDX5080">(5080)</A>
-<LI>Authentication Database entry with uss
-<A HREF="auarf246.htm#IDX5549">(5549)</A>
-<LI>dump level from Backup Database
-<A HREF="auarf067.htm#IDX4272">(4272)</A>
-<LI>dump record from Backup Database
-<A HREF="auarf068.htm#IDX4279">(4279)</A>
-<LI>Protection Database entry
-<A HREF="auarf216.htm#IDX5295">(5295)</A>
-<LI>Protection Database entry with uss
-<A HREF="auarf246.htm#IDX5548">(5548)</A>
-<LI>see also entry: <I>removing</I>
-<A HREF="auarf067.htm#IDX4273">(4273)</A>
-<LI>server process from BosConfig file
-<A HREF="auarf099.htm#IDX4507">(4507)</A>
-<LI>Tape Coordinator entry from Backup Database
-<A HREF="auarf069.htm#IDX4284">(4284)</A>
-<LI>user account with uss
-<A HREF="auarf246.htm#IDX5546">(5546)</A>
-<LI>VLDB entry (but not volume header)
-<A HREF="auarf259.htm#IDX5641">(5641)</A>
-<LI>volume set from Backup Database
-<A HREF="auarf071.htm#IDX4295">(4295)</A>
-<LI>volume with uss
-<A HREF="auarf246.htm#IDX5552">(5552)</A>
-</MENU>
-<LI>delvolume instruction in uss bulk input file
-<A HREF="auarf054.htm#IDX4107">(4107)</A>
-<LI>desynchronization of VLDB/volume headers
-<MENU>
-<LI>fixing
-<A HREF="auarf276.htm#IDX5845">(5845)</A>, <A HREF="auarf277.htm#IDX5854">(5854)</A>
-</MENU>
-<LI>determining
-<MENU>
-<LI>cell membership of client machine
-<A HREF="auarf032.htm#IDX3979">(3979)</A>
-<LI>cell membership of server machine
-<A HREF="auarf033.htm#IDX3984">(3984)</A>
-<LI>filemark size for tape device
-<A HREF="auarf130.htm#IDX4709">(4709)</A>
-<LI>success of replication
-<A HREF="auarf270.htm#IDX5793">(5793)</A>
-<LI>tape capacity (Backup System)
-<A HREF="auarf130.htm#IDX4710">(4710)</A>
-</MENU>
-<LI>device
-<MENU>
-<LI>see entry: <I>block special device</I>
-<A HREF="auarf053.htm#IDX4046">(4046)</A>
-<LI>see entry: <I>character special device</I>
-<A HREF="auarf053.htm#IDX4053">(4053)</A>
-</MENU>
-<LI>directories
-<MENU>
-<LI>/usr/afs/bin
-<A HREF="auarf101.htm#IDX4526">(4526)</A>, <A HREF="auarf109.htm#IDX4583">(4583)</A>
-<LI>/usr/afs/logs
-<A HREF="auarf102.htm#IDX4535">(4535)</A>, <A HREF="auarf109.htm#IDX4584">(4584)</A>
-</MENU>
-<LI>directory
-<MENU>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4126">(4126)</A>, <A HREF="auarf055.htm#IDX4146">(4146)</A>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4060">(4060)</A>
-<LI>displaying ACL
-<A HREF="auarf148.htm#IDX4855">(4855)</A>
-<LI>displaying home cell
-<A HREF="auarf167.htm#IDX5012">(5012)</A>
-<LI>flushing from cache
-<A HREF="auarf140.htm#IDX4809">(4809)</A>
-<LI>name, translating to volume name
-<A HREF="auarf137.htm#IDX4766">(4766)</A>
-<LI>name, translating to volume name or ID
-<A HREF="auarf138.htm#IDX4783">(4783)</A>
-<LI>overwriting with uss
-<A HREF="auarf243.htm#IDX5532">(5532)</A>
-<LI>setting ACL
-<A HREF="auarf157.htm#IDX4933">(4933)</A>
-</MENU>
-<LI>directory/file name
-<MENU>
-<LI>translating to volume name
-<A HREF="auarf150.htm#IDX4880">(4880)</A>
-</MENU>
-<LI>disabling
-<MENU>
-<LI>export of non-AFS file system
-<A HREF="auarf139.htm#IDX4799">(4799)</A>
-</MENU>
-<LI>discarding
-<MENU>
-<LI>authenticated identity in kas interactive mode
-<A HREF="auarf191.htm#IDX5121">(5121)</A>
-<LI>ticket/tokens
-<A HREF="auarf238.htm#IDX5490">(5490)</A>
-<LI>tickets
-<A HREF="auarf186.htm#IDX5108">(5108)</A>
-</MENU>
-<LI>disk cache
-<MENU>
-<LI>CacheItems file
-<A HREF="auarf017.htm#IDX3899">(3899)</A>
-<LI>V<I>n</I> files
-<A HREF="auarf036.htm#IDX3989">(3989)</A>
-<LI>VolumeItems file
-<A HREF="auarf040.htm#IDX4003">(4003)</A>
-</MENU>
-<LI>disk partition
-<MENU>
-<LI>see entry: <I>partition</I>
-<A HREF="auarf072.htm#IDX4300">(4300)</A>
-</MENU>
-<LI>displaying
-<MENU>
-<LI>ACL
-<A HREF="auarf148.htm#IDX4857">(4857)</A>
-<LI>all entries in Authentication Database
-<A HREF="auarf189.htm#IDX5114">(5114)</A>
-<LI>Authentication Database entry
-<A HREF="auarf185.htm#IDX5084">(5084)</A>
-<LI>Backup System operations, pending and running
-<A HREF="auarf077.htm#IDX4338">(4338)</A>
-<LI>BOS Server restart times
-<A HREF="auarf103.htm#IDX4538">(4538)</A>
-<LI>Cache Manager preference ranks for server machines
-<A HREF="auarf146.htm#IDX4848">(4848)</A>
-<LI>CellServDB file (server version) contents
-<A HREF="auarf106.htm#IDX4557">(4557)</A>
-<LI>client interfaces registered with File Server
-<A HREF="auarf145.htm#IDX4843">(4843)</A>
-<LI>client machine
-<A HREF="auarf168.htm#IDX5017">(5017)</A>
-<LI>creator of Protection Database entry
-<A HREF="auarf217.htm#IDX5317">(5317)</A>
-<LI>data cache amount used
-<A HREF="auarf143.htm#IDX4829">(4829)</A>
-<LI>data cache size
-<A HREF="auarf143.htm#IDX4830">(4830)</A>
-<LI>database server machines from client kernel
-<A HREF="auarf149.htm#IDX4860">(4860)</A>
-<LI>database server machines in CellServDB file (server version)
-<A HREF="auarf106.htm#IDX4556">(4556)</A>
-<LI>directory/file location
-<A HREF="auarf166.htm#IDX5003">(5003)</A>
-<LI>dump hierarchy from Backup Database
-<A HREF="auarf080.htm#IDX4362">(4362)</A>
-<LI>dump level expiration date from Backup System
-<A HREF="auarf080.htm#IDX4363">(4363)</A>
-<LI>dump record from Backup Database
-<A HREF="auarf074.htm#IDX4320">(4320)</A>
-<LI>dump record from tape (Backup System)
-<A HREF="auarf087.htm#IDX4403">(4403)</A>
-<LI>expiration date for tape from Backup Database
-<A HREF="auarf074.htm#IDX4321">(4321)</A>
-<LI>file server machine entries from VLDB
-<A HREF="auarf263.htm#IDX5701">(5701)</A>
-<LI>group memberships, number
-<A HREF="auarf217.htm#IDX5318">(5318)</A>
-<LI>group-creation quota
-<A HREF="auarf217.htm#IDX5320">(5320)</A>
-<LI>groups owned by user/group
-<A HREF="auarf221.htm#IDX5369">(5369)</A>
-<LI>groups user or machine belongs to
-<A HREF="auarf222.htm#IDX5377">(5377)</A>
-<LI>home cell of directory/file
-<A HREF="auarf167.htm#IDX5010">(5010)</A>
-<LI>job ID number (Backup System)
-<A HREF="auarf077.htm#IDX4337">(4337)</A>
-<LI>key version number from Authentication Database
-<A HREF="auarf185.htm#IDX5088">(5088)</A>
-<LI>key version number from KeyFile file
-<A HREF="auarf107.htm#IDX4568">(4568)</A>
-<LI>log files from server machine
-<A HREF="auarf102.htm#IDX4529">(4529)</A>
-<LI>max group id counter in Protection Database
-<A HREF="auarf220.htm#IDX5363">(5363)</A>
-<LI>max user id counter in Protection Database
-<A HREF="auarf220.htm#IDX5364">(5364)</A>
-<LI>members of group
-<A HREF="auarf222.htm#IDX5376">(5376)</A>
-<LI>mount point
-<A HREF="auarf151.htm#IDX4885">(4885)</A>
-<LI>owner of Protection Database entry
-<A HREF="auarf217.htm#IDX5316">(5316)</A>
-<LI>partition blocks available
-<A HREF="auarf137.htm#IDX4764">(4764)</A>, <A HREF="auarf138.htm#IDX4782">(4782)</A>
-<LI>partition blocks used
-<A HREF="auarf137.htm#IDX4763">(4763)</A>
-<LI>partition percent used
-<A HREF="auarf137.htm#IDX4762">(4762)</A>, <A HREF="auarf150.htm#IDX4879">(4879)</A>
-<LI>partition size
-<A HREF="auarf137.htm#IDX4761">(4761)</A>, <A HREF="auarf138.htm#IDX4781">(4781)</A>
-<LI>partition size, space available
-<A HREF="auarf269.htm#IDX5777">(5777)</A>
-<LI>partitions on file server machine
-<A HREF="auarf264.htm#IDX5707">(5707)</A>
-<LI>port offset number for Tape Coordinator, from Backup Database
-<A HREF="auarf081.htm#IDX4373">(4373)</A>
-<LI>privacy flags on Protection Database entry
-<A HREF="auarf217.htm#IDX5319">(5319)</A>
-<LI>privileged users from UserList file
-<A HREF="auarf108.htm#IDX4570">(4570)</A>
-<LI>Protection Database entries, all
-<A HREF="auarf219.htm#IDX5355">(5355)</A>
-<LI>Protection Database entry
-<A HREF="auarf217.htm#IDX5307">(5307)</A>
-<LI>server encryption key in Authentication Database
-<A HREF="auarf185.htm#IDX5091">(5091)</A>
-<LI>server encryption keys in KeyFile file
-<A HREF="auarf107.htm#IDX4563">(4563)</A>
-<LI>server machine status
-<A HREF="auarf133.htm#IDX4732">(4732)</A>
-<LI>server process run status and BosConfig entry
-<A HREF="auarf121.htm#IDX4659">(4659)</A>
-<LI>setuid status
-<A HREF="auarf144.htm#IDX4837">(4837)</A>
-<LI>statistics from Authentication Server
-<A HREF="auarf195.htm#IDX5157">(5157)</A>
-<LI>system type of client machine
-<A HREF="auarf165.htm#IDX4990">(4990)</A>, <A HREF="auarf234.htm#IDX5471">(5471)</A>
-<LI>Tape Coordinator entry from Backup Database
-<A HREF="auarf081.htm#IDX4372">(4372)</A>
-<LI>Tape Coordinator status
-<A HREF="auarf089.htm#IDX4415">(4415)</A>
-<LI>tape label (Backup System)
-<A HREF="auarf084.htm#IDX4393">(4393)</A>
-<LI>tickets held by issuer
-<A HREF="auarf190.htm#IDX5118">(5118)</A>
-<LI>time stamp on binary file
-<A HREF="auarf101.htm#IDX4517">(4517)</A>
-<LI>VLDB entry for volume
-<A HREF="auarf265.htm#IDX5711">(5711)</A>
-<LI>volume dump history from Backup Database
-<A HREF="auarf090.htm#IDX4420">(4420)</A>
-<LI>volume entry from VLDB
-<A HREF="auarf265.htm#IDX5710">(5710)</A>
-<LI>volume header
-<A HREF="auarf266.htm#IDX5731">(5731)</A>
-<LI>volume header and VLDB entry
-<A HREF="auarf261.htm#IDX5656">(5656)</A>
-<LI>volume percent used
-<A HREF="auarf150.htm#IDX4878">(4878)</A>
-<LI>volume quota percent used
-<A HREF="auarf155.htm#IDX4916">(4916)</A>
-<LI>volume quota, with volume & partition info.
-<A HREF="auarf138.htm#IDX4779">(4779)</A>
-<LI>volume quota, with volume size
-<A HREF="auarf150.htm#IDX4876">(4876)</A>
-<LI>Volume Server status
-<A HREF="auarf275.htm#IDX5836">(5836)</A>
-<LI>volume set (Backup System)
-<A HREF="auarf082.htm#IDX4379">(4379)</A>
-<LI>volume size
-<A HREF="auarf138.htm#IDX4780">(4780)</A>, <A HREF="auarf150.htm#IDX4877">(4877)</A>
-</MENU>
-<LI>dlog command
-<A HREF="auarf127.htm#IDX4697">(4697)</A>
-<LI>dpass command
-<A HREF="auarf128.htm#IDX4699">(4699)</A>
-<LI>dryrun flag
-<MENU>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5513">(5513)</A>
-</MENU>
-<LI>dumb terminal
-<MENU>
-<LI>use with afsmonitor
-<A HREF="auarf059.htm#IDX4202">(4202)</A>
-</MENU>
-<LI>dump
-<MENU>
-<LI>appended, creating
-<A HREF="auarf073.htm#IDX4308">(4308)</A>
-<LI>creating
-<A HREF="auarf073.htm#IDX4315">(4315)</A>
-<LI>full, creating
-<A HREF="auarf073.htm#IDX4309">(4309)</A>
-<LI>incremental, creating
-<A HREF="auarf073.htm#IDX4310">(4310)</A>
-<LI>initial, creating
-<A HREF="auarf073.htm#IDX4307">(4307)</A>
-</MENU>
-<LI>dump hierarchy (Backup System)
-<MENU>
-<LI>adding dump level
-<A HREF="auarf061.htm#IDX4223">(4223)</A>
-<LI>displaying
-<A HREF="auarf080.htm#IDX4360">(4360)</A>
-<LI>removing dump level
-<A HREF="auarf067.htm#IDX4270">(4270)</A>
-</MENU>
-<LI>dump level (Backup System)
-<MENU>
-<LI>creating in dump hierarchy
-<A HREF="auarf061.htm#IDX4220">(4220)</A>
-<LI>displaying
-<A HREF="auarf080.htm#IDX4359">(4359)</A>
-<LI>removing from dump hierarchy
-<A HREF="auarf067.htm#IDX4269">(4269)</A>
-<LI>setting expiration date at creation time
-<A HREF="auarf061.htm#IDX4225">(4225)</A>
-<LI>setting expiration date on existing
-<A HREF="auarf088.htm#IDX4408">(4408)</A>
-</MENU>
-<LI>dump record (Backup System)
-<MENU>
-<LI>created in Backup Database during dump
-<A HREF="auarf073.htm#IDX4306">(4306)</A>
-<LI>deleting from Backup Database
-<A HREF="auarf068.htm#IDX4277">(4277)</A>
-<LI>displaying for single volume
-<A HREF="auarf090.htm#IDX4421">(4421)</A>
-<LI>displaying from Backup Database
-<A HREF="auarf074.htm#IDX4318">(4318)</A>
-<LI>reading from tape
-<A HREF="auarf087.htm#IDX4402">(4402)</A>
-</MENU>
-<LI>dumping
-<MENU>
-<LI>volume with backup dump command
-<A HREF="auarf073.htm#IDX4304">(4304)</A>
-<LI>volume with vos dump command
-<A HREF="auarf260.htm#IDX5644">(5644)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_45" HREF="#IDX0_45">E</A></STRONG>
-<MENU>
-<LI>E instruction
-<MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4131">(4131)</A>
-</MENU>
-<LI>enabling
-<MENU>
-<LI>export of non-AFS file system
-<A HREF="auarf139.htm#IDX4798">(4798)</A>
-</MENU>
-<LI>encryption key
-<MENU>
-<LI>in Authentication Database
-<A HREF="auarf185.htm#IDX5101">(5101)</A>
-<LI>see entry: <I>server encryption key</I>
-<A HREF="auarf023.htm#IDX3937">(3937)</A>
-</MENU>
-<LI>End-of-File mark
-<MENU>
-<LI>see: <I>filemark</I>
-<A HREF="auarf130.htm#IDX4712">(4712)</A>
-</MENU>
-<LI>entering
-<MENU>
-<LI>interactive mode (Backup System)
-<A HREF="auarf076.htm#IDX4330">(4330)</A>
-</MENU>
-<LI>entry
-<MENU>
-<LI>Authentication Database (see entry: <I>Authentication Database</I>)
-<A HREF="auarf185.htm#IDX5100">(5100)</A>
-<LI>VLDB (see entry: <I>volume, VLDB entry</I>)
-<A HREF="auarf261.htm#IDX5658">(5658)</A>
-</MENU>
-<LI>EOF mark
-<MENU>
-<LI>see: <I>filemark</I>
-<A HREF="auarf130.htm#IDX4713">(4713)</A>
-</MENU>
-<LI>error codes
-<MENU>
-<LI>translating numbers to messages
-<A HREF="auarf236.htm#IDX5483">(5483)</A>
-</MENU>
-<LI>examining
-<MENU>
-<LI>see entry: <I>displaying</I>
-<A HREF="auarf217.htm#IDX5305">(5305)</A>
-</MENU>
-<LI>executing
-<MENU>
-<LI>commands remotely
-<A HREF="auarf100.htm#IDX4511">(4511)</A>
-</MENU>
-<LI>exiting
-<MENU>
-<LI>interactive mode (Backup System)
-<A HREF="auarf083.htm#IDX4383">(4383)</A>
-</MENU>
-<LI>expiration date
-<MENU>
-<LI>of Authentication Database entry, displaying
-<A HREF="auarf185.htm#IDX5092">(5092)</A>
-<LI>of Authentication Database entry, setting
-<A HREF="auarf193.htm#IDX5135">(5135)</A>
-</MENU>
-<LI>expiration date (Backup System)
-<MENU>
-<LI>displaying for dump level
-<A HREF="auarf080.htm#IDX4364">(4364)</A>
-<LI>displaying for tape
-<A HREF="auarf074.htm#IDX4322">(4322)</A>
-<LI>setting for dump level at creation
-<A HREF="auarf061.htm#IDX4227">(4227)</A>
-<LI>setting for existing dump level
-<A HREF="auarf088.htm#IDX4410">(4410)</A>
-</MENU>
-<LI>export of non-AFS file system
-<MENU>
-<LI>by AFS client
-<A HREF="auarf139.htm#IDX4801">(4801)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_46" HREF="#IDX0_46">F</A></STRONG>
-<MENU>
-<LI>F instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4063">(4063)</A>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4137">(4137)</A>
-</MENU>
-<LI>failed authentication attempts
-<MENU>
-<LI>displaying limit from Authentication Database entry
-<A HREF="auarf185.htm#IDX5096">(5096)</A>
-</MENU>
-<LI>fast flag on vos listvol command
-<A HREF="auarf266.htm#IDX5734">(5734)</A>
-<LI>fetching statistic in scout
-<A HREF="auarf233.htm#IDX5460">(5460)</A>
-<LI>file
-<MENU>
-<LI>copying remotely with rcp command (AFS version)
-<A HREF="auarf228.htm#IDX5427">(5427)</A>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4134">(4134)</A>, <A HREF="auarf055.htm#IDX4140">(4140)</A>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4067">(4067)</A>
-<LI>displaying ACL on parent directory
-<A HREF="auarf148.htm#IDX4856">(4856)</A>
-<LI>displaying home cell
-<A HREF="auarf167.htm#IDX5011">(5011)</A>
-<LI>flushing from cache
-<A HREF="auarf140.htm#IDX4810">(4810)</A>
-<LI>name, translating to volume name
-<A HREF="auarf137.htm#IDX4767">(4767)</A>
-<LI>name, translating to volume name or ID
-<A HREF="auarf138.htm#IDX4784">(4784)</A>
-<LI>overwriting with uss
-<A HREF="auarf243.htm#IDX5533">(5533)</A>
-<LI>setting ACL on parent directory
-<A HREF="auarf157.htm#IDX4934">(4934)</A>
-</MENU>
-<LI>FILE instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3908">(3908)</A>
-<LI>File Server
-<MENU>
-<LI>client interfaces not registered, setting
-<A HREF="auarf026.htm#IDX3957">(3957)</A>
-<LI>client interfaces registered, displaying
-<A HREF="auarf145.htm#IDX4842">(4842)</A>
-<LI>client interfaces registered, setting
-<A HREF="auarf024.htm#IDX3946">(3946)</A>, <A HREF="auarf160.htm#IDX4964">(4964)</A>
-<LI>contacting with fs commands
-<A HREF="auarf131.htm#IDX4715">(4715)</A>
-<LI>interfaces not registered in VLDB
-<MENU>
-<LI>setting in NetRestrict file
-<A HREF="auarf027.htm#IDX3961">(3961)</A>
-</MENU>
-<LI>interfaces registered in VLDB
-<MENU>
-<LI>listed in sysid file
-<A HREF="auarf049.htm#IDX4025">(4025)</A>
-<LI>setting in NetInfo file
-<A HREF="auarf025.htm#IDX3950">(3950)</A>
-</MENU>
-<LI>log file
-<A HREF="auarf021.htm#IDX3930">(3930)</A>
-<LI>monitoring status with afsmonitor
-<A HREF="auarf058.htm#IDX4195">(4195)</A>
-<LI>monitoring status with scout
-<A HREF="auarf233.htm#IDX5451">(5451)</A>
-<LI>starting
-<A HREF="auarf129.htm#IDX4703">(4703)</A>
-</MENU>
-<LI>file server machine
-<MENU>
-<LI>as site for volume
-<A HREF="auarf166.htm#IDX5002">(5002)</A>
-<LI>displaying AFS partitions on
-<A HREF="auarf264.htm#IDX5706">(5706)</A>
-<LI>displaying interfaces from VLDB server entry
-<A HREF="auarf263.htm#IDX5700">(5700)</A>
-<LI>displaying log files
-<A HREF="auarf102.htm#IDX4532">(4532)</A>
-<LI>installing AFS server binary files
-<A HREF="auarf105.htm#IDX4551">(4551)</A>
-<LI>monitoring outages of
-<A HREF="auarf233.htm#IDX5456">(5456)</A>
-<LI>partition size and space available, displaying
-<A HREF="auarf269.htm#IDX5780">(5780)</A>
-<LI>restoring all volumes on partition (Backup System)
-<A HREF="auarf072.htm#IDX4301">(4301)</A>
-<LI>salvaging volumes on
-<A HREF="auarf114.htm#IDX4611">(4611)</A>
-<LI>see also entry: <I>server machine</I>
-<A HREF="auarf102.htm#IDX4533">(4533)</A>
-</MENU>
-<LI>file system
-<MENU>
-<LI>export of non-AFS by AFS client
-<A HREF="auarf139.htm#IDX4803">(4803)</A>
-<LI>restoring internal consistency (salvaging)
-<A HREF="auarf114.htm#IDX4614">(4614)</A>
-</MENU>
-<LI>FileLog file
-<A HREF="auarf021.htm#IDX3928">(3928)</A>
-<LI>filemark
-<MENU>
-<LI>size, determining for tape device
-<A HREF="auarf130.htm#IDX4711">(4711)</A>
-</MENU>
-<LI>files
-<MENU>
-<LI>afszcm.cat
-<A HREF="auarf041.htm#IDX4004">(4004)</A>
-<LI>AuthLog
-<A HREF="auarf012.htm#IDX3869">(3869)</A>
-<LI>AuthLog.dir and AuthLog.pag
-<A HREF="auarf013.htm#IDX3872">(3872)</A>
-<LI>BackupLog
-<A HREF="auarf014.htm#IDX3875">(3875)</A>
-<LI>bdb.DB0
-<A HREF="auarf042.htm#IDX4007">(4007)</A>
-<LI>bdb.DBSYS1
-<A HREF="auarf042.htm#IDX4009">(4009)</A>
-<LI>BosConfig
-<A HREF="auarf016.htm#IDX3881">(3881)</A>
-<LI>BosLog
-<A HREF="auarf015.htm#IDX3878">(3878)</A>
-<LI>CacheItems
-<A HREF="auarf017.htm#IDX3898">(3898)</A>
-<LI>CellServDB (client version)
-<A HREF="auarf019.htm#IDX3913">(3913)</A>
-<LI>CellServDB (server version)
-<A HREF="auarf020.htm#IDX3921">(3921)</A>
-<LI>CFG_<I>device_name</I>
-<A HREF="auarf018.htm#IDX3901">(3901)</A>
-<LI>FileLog
-<A HREF="auarf021.htm#IDX3929">(3929)</A>
-<LI>FORCESALVAGE
-<A HREF="auarf022.htm#IDX3932">(3932)</A>
-<LI>kaserver.DB0
-<A HREF="auarf045.htm#IDX4012">(4012)</A>
-<LI>kaserver.DBSYS1
-<A HREF="auarf045.htm#IDX4014">(4014)</A>
-<LI>kaserverauxdb
-<A HREF="auarf046.htm#IDX4017">(4017)</A>
-<LI>KeyFile
-<A HREF="auarf023.htm#IDX3935">(3935)</A>
-<LI>NetInfo (client version)
-<A HREF="auarf024.htm#IDX3943">(3943)</A>
-<LI>NetInfo (server version)
-<A HREF="auarf025.htm#IDX3949">(3949)</A>
-<LI>NetRestrict (client version)
-<A HREF="auarf026.htm#IDX3954">(3954)</A>
-<LI>NetRestrict (server version)
-<A HREF="auarf027.htm#IDX3960">(3960)</A>
-<LI>NoAuth
-<A HREF="auarf028.htm#IDX3965">(3965)</A>
-<LI>prdb.DB0
-<A HREF="auarf047.htm#IDX4019">(4019)</A>
-<LI>prdb.DBSYS1
-<A HREF="auarf047.htm#IDX4021">(4021)</A>
-<LI>SALVAGE.fs
-<A HREF="auarf029.htm#IDX3968">(3968)</A>
-<LI>SalvageLog
-<A HREF="auarf030.htm#IDX3973">(3973)</A>
-<LI>sysid
-<A HREF="auarf049.htm#IDX4024">(4024)</A>
-<LI>tapeconfig
-<A HREF="auarf050.htm#IDX4028">(4028)</A>
-<LI>ThisCell (client version)
-<A HREF="auarf032.htm#IDX3976">(3976)</A>
-<LI>ThisCell (server version)
-<A HREF="auarf033.htm#IDX3981">(3981)</A>
-<LI>UserList
-<A HREF="auarf035.htm#IDX3986">(3986)</A>
-<LI>V<I>n</I>
-<A HREF="auarf036.htm#IDX3988">(3988)</A>
-<LI>V<I>vol_ID</I>.vol
-<A HREF="auarf037.htm#IDX3991">(3991)</A>
-<LI>vldb.DB0
-<A HREF="auarf051.htm#IDX4031">(4031)</A>
-<LI>vldb.DBSYS1
-<A HREF="auarf051.htm#IDX4033">(4033)</A>
-<LI>VLLog
-<A HREF="auarf038.htm#IDX3995">(3995)</A>
-<LI>VolserLog
-<A HREF="auarf039.htm#IDX3998">(3998)</A>
-<LI>VolumeItems
-<A HREF="auarf040.htm#IDX4001">(4001)</A>
-</MENU>
-<LI>fileserver command
-<A HREF="auarf129.htm#IDX4701">(4701)</A>
-<LI>fileserver process
-<MENU>
-<LI>part of fs entry in BosConfig file
-<A HREF="auarf016.htm#IDX3888">(3888)</A>
-</MENU>
-<LI>flag
-<MENU>
-<LI>see entry: <I>privacy flags</I>
-<A HREF="auarf217.htm#IDX5334">(5334)</A>
-<LI>see entry: <I>status flag, in BosConfig file</I>
-<A HREF="auarf016.htm#IDX3893">(3893)</A>
-</MENU>
-<LI>flushing
-<MENU>
-<LI>directory/file from data cache
-<A HREF="auarf140.htm#IDX4807">(4807)</A>
-<LI>entire volume from data cache
-<A HREF="auarf142.htm#IDX4820">(4820)</A>
-<LI>mount point from data cache
-<A HREF="auarf141.htm#IDX4814">(4814)</A>
-</MENU>
-<LI>fms command
-<A HREF="auarf130.htm#IDX4705">(4705)</A>
-<LI>force flag
-<MENU>
-<LI>on pts commands
-<A HREF="auarf210.htm#IDX5232">(5232)</A>
-</MENU>
-<LI>FORCESALVAGE file
-<A HREF="auarf022.htm#IDX3931">(3931)</A>
-<LI>fs commands
-<MENU>
-<LI>apropos
-<A HREF="auarf132.htm#IDX4725">(4725)</A>
-<LI>checkservers
-<A HREF="auarf133.htm#IDX4728">(4728)</A>
-<LI>checkvolumes
-<A HREF="auarf134.htm#IDX4736">(4736)</A>
-<LI>cleanacl
-<A HREF="auarf135.htm#IDX4751">(4751)</A>
-<LI>common options
-<A HREF="auarf131.htm#IDX4721">(4721)</A>
-<LI>copyacl
-<A HREF="auarf136.htm#IDX4755">(4755)</A>
-<LI>diskfree
-<A HREF="auarf137.htm#IDX4770">(4770)</A>
-<LI>examine
-<A HREF="auarf138.htm#IDX4794">(4794)</A>
-<LI>exportafs
-<A HREF="auarf139.htm#IDX4796">(4796)</A>
-<LI>flush
-<A HREF="auarf140.htm#IDX4811">(4811)</A>
-<LI>flushmount
-<A HREF="auarf141.htm#IDX4817">(4817)</A>
-<LI>flushvolume
-<A HREF="auarf142.htm#IDX4823">(4823)</A>
-<LI>getcacheparms
-<A HREF="auarf143.htm#IDX4825">(4825)</A>
-<LI>getcellstatus
-<A HREF="auarf144.htm#IDX4833">(4833)</A>
-<LI>getclientaddrs
-<A HREF="auarf145.htm#IDX4839">(4839)</A>
-<LI>getserverprefs
-<A HREF="auarf146.htm#IDX4844">(4844)</A>
-<LI>help
-<A HREF="auarf147.htm#IDX4851">(4851)</A>
-<LI>listacl
-<A HREF="auarf148.htm#IDX4858">(4858)</A>
-<LI>listcells
-<A HREF="auarf149.htm#IDX4867">(4867)</A>
-<LI>listquota
-<A HREF="auarf150.htm#IDX4869">(4869)</A>
-<LI>lsmount
-<A HREF="auarf151.htm#IDX4887">(4887)</A>
-<LI>messages
-<A HREF="auarf152.htm#IDX4891">(4891)</A>
-<LI>mkmount
-<A HREF="auarf153.htm#IDX4896">(4896)</A>
-<LI>newcell
-<A HREF="auarf154.htm#IDX4911">(4911)</A>
-<LI>privilege requirements
-<A HREF="auarf131.htm#IDX4724">(4724)</A>
-<LI>quota
-<A HREF="auarf155.htm#IDX4913">(4913)</A>
-<LI>rmmount
-<A HREF="auarf156.htm#IDX4922">(4922)</A>
-<LI>setacl
-<A HREF="auarf157.htm#IDX4935">(4935)</A>
-<LI>setcachesize
-<A HREF="auarf158.htm#IDX4953">(4953)</A>
-<LI>setcell
-<A HREF="auarf159.htm#IDX4959">(4959)</A>
-<LI>setclientaddrs
-<A HREF="auarf160.htm#IDX4961">(4961)</A>
-<LI>setquota
-<A HREF="auarf161.htm#IDX4969">(4969)</A>
-<LI>setserverprefs
-<A HREF="auarf162.htm#IDX4971">(4971)</A>
-<LI>setvol
-<A HREF="auarf163.htm#IDX4983">(4983)</A>
-<LI>storebehind
-<A HREF="auarf164.htm#IDX4986">(4986)</A>
-<LI>sysname
-<A HREF="auarf165.htm#IDX4987">(4987)</A>
-<LI>whereis
-<A HREF="auarf166.htm#IDX5006">(5006)</A>
-<LI>whichcell
-<A HREF="auarf167.htm#IDX5013">(5013)</A>
-<LI>wscell
-<A HREF="auarf168.htm#IDX5019">(5019)</A>
-</MENU>
-<LI>fs process
-<MENU>
-<LI>creating
-<A HREF="auarf098.htm#IDX4504">(4504)</A>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4489">(4489)</A>
-<LI>recorded in <I>BosConfig</I> file
-<A HREF="auarf016.htm#IDX3887">(3887)</A>
-</MENU>
-<LI>fstrace commands
-<MENU>
-<LI>apropos
-<A HREF="auarf170.htm#IDX5028">(5028)</A>
-<LI>common options
-<A HREF="auarf169.htm#IDX5025">(5025)</A>
-<LI>dump
-<A HREF="auarf172.htm#IDX5031">(5031)</A>
-<LI>help
-<A HREF="auarf173.htm#IDX5033">(5033)</A>
-<LI>lslog
-<A HREF="auarf174.htm#IDX5036">(5036)</A>
-<LI>lsset
-<A HREF="auarf175.htm#IDX5038">(5038)</A>
-<LI>privilege requirements
-<A HREF="auarf169.htm#IDX5022">(5022)</A>
-<LI>setlog
-<A HREF="auarf176.htm#IDX5040">(5040)</A>
-<LI>setset
-<A HREF="auarf177.htm#IDX5042">(5042)</A>
-</MENU>
-<LI>ftpd command (AFS version)
-<A HREF="auarf178.htm#IDX5044">(5044)</A>
-<LI>full dump
-<A HREF="auarf260.htm#IDX5651">(5651)</A>
-<MENU>
-<LI>see entry: <I>dump</I>
-<A HREF="auarf073.htm#IDX4312">(4312)</A>
-</MENU>
-<LI>full restore
-<A HREF="auarf092.htm#IDX4431">(4431)</A>
-<MENU>
-<LI>see entry: <I>restoring</I>
-<A HREF="auarf091.htm#IDX4426">(4426)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_47" HREF="#IDX0_47">G</A></STRONG>
-<MENU>
-<LI>G instruction
-<MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4143">(4143)</A>
-</MENU>
-<LI>gathering
-<MENU>
-<LI>statistics from Authentication Server
-<A HREF="auarf195.htm#IDX5158">(5158)</A>
-</MENU>
-<LI>group
-<MENU>
-<LI>AFS GID, displaying
-<A HREF="auarf217.htm#IDX5330">(5330)</A>
-<LI>AFS GID, mapping to name
-<A HREF="auarf217.htm#IDX5328">(5328)</A>
-<LI>AFS GID, setting
-<A HREF="auarf214.htm#IDX5269">(5269)</A>
-<LI>defined
-<A HREF="auarf210.htm#IDX5223">(5223)</A>
-<LI>groups owned, displaying
-<A HREF="auarf221.htm#IDX5370">(5370)</A>
-<LI>members, adding
-<A HREF="auarf211.htm#IDX5238">(5238)</A>
-<LI>members, displaying
-<A HREF="auarf222.htm#IDX5378">(5378)</A>
-<LI>members, displaying number
-<A HREF="auarf217.htm#IDX5335">(5335)</A>
-<LI>members, removing
-<A HREF="auarf223.htm#IDX5385">(5385)</A>
-<LI>name, changing in Protection Database
-<A HREF="auarf224.htm#IDX5395">(5395)</A>
-<LI>name, mapping to AFS GID
-<A HREF="auarf217.htm#IDX5329">(5329)</A>
-<LI>name, rules for format
-<A HREF="auarf214.htm#IDX5261">(5261)</A>
-<LI>orphaned, displaying
-<A HREF="auarf221.htm#IDX5371">(5371)</A>
-<LI>prefix-less
-<A HREF="auarf214.htm#IDX5263">(5263)</A>
-<LI>privacy flags on Protection Database entry, displaying
-<A HREF="auarf217.htm#IDX5338">(5338)</A>
-<LI>privacy flags on Protection Database entry, setting
-<A HREF="auarf225.htm#IDX5404">(5404)</A>
-<LI>Protection Database entries, display all
-<A HREF="auarf219.htm#IDX5357">(5357)</A>
-<LI>Protection Database entry, creating
-<A HREF="auarf214.htm#IDX5256">(5256)</A>
-<LI>Protection Database entry, deleting
-<A HREF="auarf216.htm#IDX5296">(5296)</A>
-<LI>regular
-<A HREF="auarf214.htm#IDX5262">(5262)</A>
-</MENU>
-<LI>group ID
-<MENU>
-<LI>see entry: <I>AFS GID</I>
-<A HREF="auarf214.htm#IDX5268">(5268)</A>
-</MENU>
-<LI>group-creation quota
-<MENU>
-<LI>defined
-<A HREF="auarf217.htm#IDX5349">(5349)</A>
-<LI>displaying
-<A HREF="auarf217.htm#IDX5337">(5337)</A>
-<LI>lowered by pts creategroup command
-<A HREF="auarf214.htm#IDX5259">(5259)</A>
-<LI>restored by pts delete
-<A HREF="auarf216.htm#IDX5302">(5302)</A>
-<LI>setting on Protection Database entry
-<A HREF="auarf225.htm#IDX5403">(5403)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_48" HREF="#IDX0_48">H</A></STRONG>
-<MENU>
-<LI>hard link
-<MENU>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4153">(4153)</A>
-<LI>overwriting with uss
-<A HREF="auarf243.htm#IDX5534">(5534)</A>
-</MENU>
-<LI>help
-<MENU>
-<LI>for backup commands
-<A HREF="auarf075.htm#IDX4326">(4326)</A>
-<LI>for bos commands
-<A HREF="auarf104.htm#IDX4547">(4547)</A>
-<LI>for fs commands
-<A HREF="auarf147.htm#IDX4853">(4853)</A>
-<LI>for fstrace commands
-<A HREF="auarf173.htm#IDX5035">(5035)</A>
-<LI>for kas commands
-<A HREF="auarf187.htm#IDX5111">(5111)</A>
-<LI>for package commands
-<A HREF="auarf206.htm#IDX5209">(5209)</A>
-<LI>for pts commands
-<A HREF="auarf218.htm#IDX5352">(5352)</A>
-<LI>for uss commands
-<A HREF="auarf247.htm#IDX5556">(5556)</A>
-<LI>for vos commands
-<A HREF="auarf262.htm#IDX5697">(5697)</A>
-</MENU>
-<LI>help flag
-<MENU>
-<LI>on backup commands
-<A HREF="auarf060.htm#IDX4213">(4213)</A>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4445">(4445)</A>
-<LI>on fs commands
-<A HREF="auarf131.htm#IDX4722">(4722)</A>
-<LI>on fstrace commands
-<A HREF="auarf169.htm#IDX5023">(5023)</A>, <A HREF="auarf169.htm#IDX5027">(5027)</A>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5066">(5066)</A>
-<LI>on pts commands
-<A HREF="auarf210.htm#IDX5233">(5233)</A>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5512">(5512)</A>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5579">(5579)</A>
-</MENU>
-<LI>help string
-<MENU>
-<LI>see entry: <I>keyword</I>
-<A HREF="auarf097.htm#IDX4476">(4476)</A>
-</MENU>
-<LI>home cell
-<MENU>
-<LI>displaying for client machine
-<A HREF="auarf168.htm#IDX5016">(5016)</A>
-<LI>displaying for directory/file
-<A HREF="auarf167.htm#IDX5009">(5009)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_49" HREF="#IDX0_49">I</A></STRONG>
-<MENU>
-<LI>idempotency
-<MENU>
-<LI>of vos commands
-<A HREF="auarf252.htm#IDX5572">(5572)</A>
-</MENU>
-<LI>ifdef statement
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4091">(4091)</A>
-</MENU>
-<LI>ifndef statement
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4094">(4094)</A>
-</MENU>
-<LI>include statement
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4096">(4096)</A>
-</MENU>
-<LI>incremental dump
-<A HREF="auarf260.htm#IDX5652">(5652)</A>
-<MENU>
-<LI>see entry: <I>dump</I>
-<A HREF="auarf073.htm#IDX4314">(4314)</A>
-</MENU>
-<LI>inetd command (AFS version)
-<A HREF="auarf179.htm#IDX5049">(5049)</A>
-<LI>initial dump
-<MENU>
-<LI>see entry: <I>dump</I>
-<A HREF="auarf073.htm#IDX4313">(4313)</A>
-</MENU>
-<LI>initializing
-<MENU>
-<LI>Backup Server
-<A HREF="auarf125.htm#IDX4689">(4689)</A>
-<LI>Cache Manager with afsd
-<A HREF="auarf058.htm#IDX4186">(4186)</A>
-<LI>FTP Daemon
-<A HREF="auarf178.htm#IDX5048">(5048)</A>
-<LI>Internet daemon
-<A HREF="auarf179.htm#IDX5053">(5053)</A>
-<LI>NTPD, with runntp
-<A HREF="auarf230.htm#IDX5437">(5437)</A>
-<LI>Protection Server
-<A HREF="auarf227.htm#IDX5421">(5421)</A>
-<LI>server process
-<A HREF="auarf098.htm#IDX4483">(4483)</A>
-<LI>Tape Coordinator
-<A HREF="auarf126.htm#IDX4695">(4695)</A>
-</MENU>
-<LI>installing
-<MENU>
-<LI>binary file
-<A HREF="auarf105.htm#IDX4549">(4549)</A>
-</MENU>
-<LI>interactive mode
-<MENU>
-<LI>kas commands
-<A HREF="auarf181.htm#IDX5062">(5062)</A>
-<LI>kas, quitting from
-<A HREF="auarf192.htm#IDX5129">(5129)</A>
-</MENU>
-<LI>interactive mode (Backup System)
-<MENU>
-<LI>entering
-<A HREF="auarf076.htm#IDX4329">(4329)</A>
-<LI>exiting
-<A HREF="auarf083.htm#IDX4382">(4382)</A>
-<LI>halting operation
-<A HREF="auarf078.htm#IDX4342">(4342)</A>
-</MENU>
-<LI>Internet file transfer protocol daemon (AFS version)
-<A HREF="auarf178.htm#IDX5047">(5047)</A>
-<LI>Internet services daemon (AFS version)
-<A HREF="auarf179.htm#IDX5052">(5052)</A>
-</MENU>
-<STRONG><A NAME="IDX1_4A" HREF="#IDX0_4A">J</A></STRONG>
-<MENU>
-<LI>job ID number (Backup System)
-<MENU>
-<LI>displaying
-<A HREF="auarf077.htm#IDX4336">(4336)</A>
-<LI>using to halt operation
-<A HREF="auarf078.htm#IDX4344">(4344)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_4B" HREF="#IDX0_4B">K</A></STRONG>
-<MENU>
-<LI>kadb_check command
-<A HREF="auarf180.htm#IDX5054">(5054)</A>
-<LI>kas commands
-<MENU>
-<LI>apropos
-<A HREF="auarf182.htm#IDX5070">(5070)</A>
-<LI>common options
-<A HREF="auarf181.htm#IDX5058">(5058)</A>
-<LI>create
-<A HREF="auarf183.htm#IDX5073">(5073)</A>
-<LI>delete
-<A HREF="auarf184.htm#IDX5078">(5078)</A>
-<LI>examine
-<A HREF="auarf185.htm#IDX5082">(5082)</A>
-<LI>forgetticket
-<A HREF="auarf186.htm#IDX5104">(5104)</A>
-<LI>help
-<A HREF="auarf187.htm#IDX5109">(5109)</A>
-<LI>interactive mode
-<A HREF="auarf181.htm#IDX5063">(5063)</A>
-<LI>list
-<A HREF="auarf189.htm#IDX5112">(5112)</A>
-<LI>listtickets
-<A HREF="auarf190.htm#IDX5116">(5116)</A>
-<LI>noauthentication
-<A HREF="auarf191.htm#IDX5124">(5124)</A>
-<LI>privilege requirements
-<A HREF="auarf181.htm#IDX5060">(5060)</A>
-<LI>quit
-<A HREF="auarf192.htm#IDX5126">(5126)</A>
-<LI>setfields
-<A HREF="auarf193.htm#IDX5130">(5130)</A>
-<LI>setpassword
-<A HREF="auarf194.htm#IDX5147">(5147)</A>
-<LI>statistics
-<A HREF="auarf195.htm#IDX5155">(5155)</A>
-<LI>stringtokey
-<A HREF="auarf196.htm#IDX5161">(5161)</A>
-<LI>unlock
-<A HREF="auarf197.htm#IDX5167">(5167)</A>
-</MENU>
-<LI>kaserver command
-<A HREF="auarf198.htm#IDX5170">(5170)</A>
-<LI>kaserver process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4491">(4491)</A>
-</MENU>
-<LI>kaserver.DB0 file
-<A HREF="auarf045.htm#IDX4011">(4011)</A>
-<LI>kaserver.DBSYS1 file
-<A HREF="auarf045.htm#IDX4013">(4013)</A>
-<LI>kaserverauxdb file
-<A HREF="auarf046.htm#IDX4016">(4016)</A>
-<LI>kdb command
-<A HREF="auarf199.htm#IDX5173">(5173)</A>
-<LI>kernel
-<MENU>
-<LI>list of database server machines, changing
-<A HREF="auarf154.htm#IDX4910">(4910)</A>
-<LI>list of database server machines, examining
-<A HREF="auarf149.htm#IDX4866">(4866)</A>
-</MENU>
-<LI>key
-<MENU>
-<LI>deriving from character string
-<A HREF="auarf196.htm#IDX5165">(5165)</A>
-<LI>see entry: <I>server encryption key</I>
-<A HREF="auarf023.htm#IDX3938">(3938)</A>
-</MENU>
-<LI>key field in Authentication Database
-<MENU>
-<LI>setting using password
-<A HREF="auarf194.htm#IDX5152">(5152)</A>
-</MENU>
-<LI>key version number
-<A HREF="auarf023.htm#IDX3939">(3939)</A>
-<MENU>
-<LI>displaying from Authentication Database
-<A HREF="auarf185.htm#IDX5089">(5089)</A>
-<LI>listing from KeyFile file
-<A HREF="auarf107.htm#IDX4569">(4569)</A>
-<LI>rules for
-<A HREF="auarf095.htm#IDX4465">(4465)</A>
-<LI>setting in KeyFile file
-<A HREF="auarf095.htm#IDX4461">(4461)</A>
-</MENU>
-<LI>KeyFile file
-<A HREF="auarf023.htm#IDX3934">(3934)</A>
-<MENU>
-<LI>adding key with bos addkey command
-<A HREF="auarf095.htm#IDX4460">(4460)</A>
-<LI>displaying keys with bos listkeys command
-<A HREF="auarf107.htm#IDX4565">(4565)</A>
-<LI>removing key with bos removekey command
-<A HREF="auarf111.htm#IDX4595">(4595)</A>
-</MENU>
-<LI>keyword
-<MENU>
-<LI>using to get help on backup commands
-<A HREF="auarf065.htm#IDX4263">(4263)</A>
-<LI>using to get help on bos commands
-<A HREF="auarf097.htm#IDX4475">(4475)</A>
-<LI>using to get help on fs commands
-<A HREF="auarf132.htm#IDX4727">(4727)</A>
-<LI>using to get help on fstrace commands
-<A HREF="auarf170.htm#IDX5030">(5030)</A>
-<LI>using to get help on kas commands
-<A HREF="auarf182.htm#IDX5072">(5072)</A>
-<LI>using to get help on package commands
-<A HREF="auarf205.htm#IDX5206">(5206)</A>
-<LI>using to get help on pts commands
-<A HREF="auarf212.htm#IDX5246">(5246)</A>
-<LI>using to get help on uss commands
-<A HREF="auarf244.htm#IDX5538">(5538)</A>
-<LI>using to get help on vos commands
-<A HREF="auarf254.htm#IDX5595">(5595)</A>
-</MENU>
-<LI>klog command
-<A HREF="auarf200.htm#IDX5176">(5176)</A>
-<LI>knfs command
-<A HREF="auarf201.htm#IDX5183">(5183)</A>
-<LI>kpasswd command
-<A HREF="auarf202.htm#IDX5187">(5187)</A>
-<LI>kpwvalid command
-<A HREF="auarf203.htm#IDX5194">(5194)</A>
-</MENU>
-<STRONG><A NAME="IDX1_4C" HREF="#IDX0_4C">L</A></STRONG>
-<MENU>
-<LI>L instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4070">(4070)</A>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4149">(4149)</A>
-</MENU>
-<LI>labeling
-<MENU>
-<LI>tape for Backup System
-<A HREF="auarf079.htm#IDX4347">(4347)</A>
-</MENU>
-<LI>learning
-<MENU>
-<LI>home cell of directory/file
-<A HREF="auarf167.htm#IDX5008">(5008)</A>
-<LI>volume ID number given directory/file name
-<A HREF="auarf138.htm#IDX4787">(4787)</A>
-<LI>volume location given directory/file name
-<A HREF="auarf166.htm#IDX5005">(5005)</A>
-<LI>volume name given directory/file name
-<A HREF="auarf137.htm#IDX4769">(4769)</A>, <A HREF="auarf138.htm#IDX4786">(4786)</A>, <A HREF="auarf150.htm#IDX4882">(4882)</A>
-<LI>volume quota given directory/file name
-<A HREF="auarf138.htm#IDX4788">(4788)</A>
-</MENU>
-<LI>leaving
-<MENU>
-<LI>kas interactive mode
-<A HREF="auarf192.htm#IDX5127">(5127)</A>
-</MENU>
-<LI>lifetime
-<MENU>
-<LI>see entry: <I>ticket lifetime</I>
-<A HREF="auarf185.htm#IDX5094">(5094)</A>
-</MENU>
-<LI>link
-<MENU>
-<LI>see entry: <I>hard link, symbolic link</I>
-<A HREF="auarf055.htm#IDX4156">(4156)</A>
-</MENU>
-<LI>listing
-<MENU>
-<LI>see entry: <I>displaying</I>
-<A HREF="auarf217.htm#IDX5306">(5306)</A>
-<LI>tokens held by issuer
-<A HREF="auarf235.htm#IDX5479">(5479)</A>
-</MENU>
-<LI>local disk
-<MENU>
-<LI>configuring on client, using package
-<A HREF="auarf204.htm#IDX5201">(5201)</A>
-</MENU>
-<LI>localauth flag
-<MENU>
-<LI>on backup commands
-<A HREF="auarf060.htm#IDX4214">(4214)</A>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4446">(4446)</A>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5580">(5580)</A>
-</MENU>
-<LI>lock status
-<MENU>
-<LI>displaying limit from Authentication Database entry
-<A HREF="auarf185.htm#IDX5098">(5098)</A>
-</MENU>
-<LI>locking
-<MENU>
-<LI>VLDB entry
-<A HREF="auarf267.htm#IDX5763">(5763)</A>
-</MENU>
-<LI>locktime
-<MENU>
-<LI>displaying limit from Authentication Database entry
-<A HREF="auarf185.htm#IDX5097">(5097)</A>
-<LI>setting in Authentication Database entry
-<A HREF="auarf193.htm#IDX5140">(5140)</A>
-</MENU>
-<LI>log file
-<MENU>
-<LI>displaying from server machine
-<A HREF="auarf102.htm#IDX4530">(4530)</A>
-<LI>see entry: <I>files</I>
-<A HREF="auarf011.htm#IDX3865">(3865)</A>
-</MENU>
-<LI>long flag on vos listvol command
-<A HREF="auarf266.htm#IDX5735">(5735)</A>
-</MENU>
-<STRONG><A NAME="IDX1_4D" HREF="#IDX0_4D">M</A></STRONG>
-<MENU>
-<LI>machine entry in Protection Database
-<MENU>
-<LI>adding to group
-<A HREF="auarf211.htm#IDX5240">(5240)</A>
-<LI>AFS UID, setting
-<A HREF="auarf215.htm#IDX5288">(5288)</A>
-<LI>creating
-<A HREF="auarf215.htm#IDX5284">(5284)</A>
-<LI>deleting
-<A HREF="auarf216.htm#IDX5298">(5298)</A>
-<LI>group memberships, displaying
-<A HREF="auarf222.htm#IDX5380">(5380)</A>
-<LI>group-creation quota, setting
-<A HREF="auarf225.htm#IDX5407">(5407)</A>
-<LI>privacy flags, setting
-<A HREF="auarf225.htm#IDX5408">(5408)</A>
-<LI>wildcard name format
-<A HREF="auarf215.htm#IDX5285">(5285)</A>
-</MENU>
-<LI>maintaining
-<MENU>
-<LI>synchrony of VLDB with volume headers
-<A HREF="auarf252.htm#IDX5575">(5575)</A>
-</MENU>
-<LI>max group id counter in Protection Database
-<MENU>
-<LI>affected by setting AFS GID
-<A HREF="auarf214.htm#IDX5273">(5273)</A>
-<LI>displaying
-<A HREF="auarf220.htm#IDX5362">(5362)</A>
-<LI>setting
-<A HREF="auarf226.htm#IDX5412">(5412)</A>
-</MENU>
-<LI>max user id counter in Protection Database
-<MENU>
-<LI>affected by setting AFS UID
-<A HREF="auarf215.htm#IDX5291">(5291)</A>
-<LI>displaying
-<A HREF="auarf220.htm#IDX5361">(5361)</A>
-<LI>setting
-<A HREF="auarf226.htm#IDX5411">(5411)</A>
-</MENU>
-<LI>MaxQuota field in volume header
-<A HREF="auarf261.htm#IDX5678">(5678)</A>, <A HREF="auarf266.htm#IDX5754">(5754)</A>
-<LI>member
-<MENU>
-<LI>Protection Database group, adding
-<A HREF="auarf211.htm#IDX5241">(5241)</A>
-<LI>Protection Database group, removing
-<A HREF="auarf223.htm#IDX5387">(5387)</A>
-</MENU>
-<LI>memory state of BOS Server
-<A HREF="auarf016.htm#IDX3895">(3895)</A>
-<LI>messages
-<MENU>
-<LI>associated with volume, creating
-<A HREF="auarf163.htm#IDX4981">(4981)</A>
-<LI>associated with volume, examining
-<A HREF="auarf138.htm#IDX4792">(4792)</A>
-</MENU>
-<LI>monitoring
-<MENU>
-<LI>disk usage with scout
-<A HREF="auarf233.htm#IDX5449">(5449)</A>, <A HREF="auarf233.htm#IDX5466">(5466)</A>
-<LI>File Server status with scout
-<A HREF="auarf233.htm#IDX5450">(5450)</A>
-<LI>outages with scout
-<A HREF="auarf233.htm#IDX5455">(5455)</A>
-</MENU>
-<LI>MOUNT instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3909">(3909)</A>
-<LI>mount point
-<MENU>
-<LI>cellular
-<A HREF="auarf153.htm#IDX4903">(4903)</A>
-<LI>creating
-<A HREF="auarf153.htm#IDX4893">(4893)</A>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4170">(4170)</A>
-<LI>displaying
-<A HREF="auarf151.htm#IDX4884">(4884)</A>
-<LI>flushing from cache
-<A HREF="auarf141.htm#IDX4816">(4816)</A>
-<LI>read/write
-<A HREF="auarf153.htm#IDX4901">(4901)</A>
-<LI>regular
-<A HREF="auarf153.htm#IDX4899">(4899)</A>
-<LI>removing
-<A HREF="auarf156.htm#IDX4918">(4918)</A>
-</MENU>
-<LI>mounting
-<MENU>
-<LI>foreign volume in local cell
-<A HREF="auarf153.htm#IDX4904">(4904)</A>
-</MENU>
-<LI>moving
-<MENU>
-<LI>volume
-<A HREF="auarf268.htm#IDX5768">(5768)</A>
-</MENU>
-<LI>mutual authentication
-<A HREF="auarf023.htm#IDX3940">(3940)</A>
-</MENU>
-<STRONG><A NAME="IDX1_4E" HREF="#IDX0_4E">N</A></STRONG>
-<MENU>
-<LI>name
-<MENU>
-<LI>cell (see entry: <I>cell, name</I>)
-<A HREF="auarf116.htm#IDX4625">(4625)</A>
-<LI>see entry: <I> group name</I>
-<A HREF="auarf214.htm#IDX5257">(5257)</A>
-<LI>see entry: <I>username</I>
-<A HREF="auarf215.htm#IDX5292">(5292)</A>
-<LI>see entry: <I>volume name</I>
-<A HREF="auarf273.htm#IDX5825">(5825)</A>
-</MENU>
-<LI>NAME_CHECK instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3910">(3910)</A>
-<LI>needs salvage status flag in volume header
-<A HREF="auarf261.htm#IDX5668">(5668)</A>, <A HREF="auarf266.htm#IDX5744">(5744)</A>
-<LI>negative ACL permissions
-<MENU>
-<LI>setting
-<A HREF="auarf157.htm#IDX4928">(4928)</A>
-</MENU>
-<LI>NetInfo file (client version)
-<A HREF="auarf024.htm#IDX3942">(3942)</A>
-<LI>NetInfo file (server version)
-<A HREF="auarf025.htm#IDX3948">(3948)</A>
-<LI>NetRestrict file (client version)
-<A HREF="auarf026.htm#IDX3953">(3953)</A>
-<LI>NetRestrict file (server version)
-<A HREF="auarf027.htm#IDX3959">(3959)</A>
-<LI>Network File System
-<MENU>
-<LI>see entry: <I>NFS</I>
-<A HREF="auarf139.htm#IDX4805">(4805)</A>
-</MENU>
-<LI>Network Time Protocol Daemon
-<MENU>
-<LI>see entry:<I> NTPD</I>
-<A HREF="auarf230.htm#IDX5436">(5436)</A>
-</MENU>
-<LI>New release
-<MENU>
-<LI>status flag on site definition in VLDB entry
-<A HREF="auarf261.htm#IDX5694">(5694)</A>, <A HREF="auarf265.htm#IDX5728">(5728)</A>
-</MENU>
-<LI>New Release flag in VLDB
-<MENU>
-<LI>as indicator of failed vos release operation
-<A HREF="auarf270.htm#IDX5800">(5800)</A>
-</MENU>
-<LI>NFS
-<MENU>
-<LI>export of by AFS client
-<A HREF="auarf139.htm#IDX4804">(4804)</A>
-<LI>obtaining authenticated AFS access from non-supported client
-<A HREF="auarf201.htm#IDX5186">(5186)</A>
-</MENU>
-<LI>NFS/AFS Translator
-<MENU>
-<LI>enabling Cache Manager
-<A HREF="auarf058.htm#IDX4192">(4192)</A>
-</MENU>
-<LI>NoAuth file
-<A HREF="auarf028.htm#IDX3964">(3964)</A>
-<LI>noauth flag
-<MENU>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4447">(4447)</A>, <A HREF="auarf252.htm#IDX5581">(5581)</A>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5067">(5067)</A>
-<LI>on pts commands
-<A HREF="auarf210.htm#IDX5234">(5234)</A>
-</MENU>
-<LI>NOCPW flag in Authentication Database entry
-<A HREF="auarf193.htm#IDX5146">(5146)</A>
-<LI>none shorthand notation for ACL permissions
-<A HREF="auarf157.htm#IDX4941">(4941)</A>
-<LI>NOSEAL flag in Authentication Database entry
-<A HREF="auarf193.htm#IDX5145">(5145)</A>
-<LI>Not released
-<MENU>
-<LI>status flag on site definition in VLDB entry
-<A HREF="auarf261.htm#IDX5692">(5692)</A>, <A HREF="auarf265.htm#IDX5726">(5726)</A>
-</MENU>
-<LI>NOTGS flag in Authentication Database entry
-<A HREF="auarf193.htm#IDX5144">(5144)</A>
-<LI>NTPD
-<MENU>
-<LI>initializing with runntp
-<A HREF="auarf230.htm#IDX5435">(5435)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_4F" HREF="#IDX0_4F">O</A></STRONG>
-<MENU>
-<LI>Off-line status flag in volume header
-<A HREF="auarf261.htm#IDX5667">(5667)</A>, <A HREF="auarf266.htm#IDX5743">(5743)</A>
-<LI>offline message
-<MENU>
-<LI>creating
-<A HREF="auarf163.htm#IDX4982">(4982)</A>
-<LI>examining
-<A HREF="auarf138.htm#IDX4793">(4793)</A>
-</MENU>
-<LI>Old release
-<MENU>
-<LI>status flag on site definition in VLDB entry
-<A HREF="auarf261.htm#IDX5693">(5693)</A>, <A HREF="auarf265.htm#IDX5727">(5727)</A>
-</MENU>
-<LI>Old Release flag in VLDB
-<MENU>
-<LI>as indicator of failed vos release operation
-<A HREF="auarf270.htm#IDX5801">(5801)</A>
-</MENU>
-<LI>OLD version of binary file
-<MENU>
-<LI>creation by bos install command
-<A HREF="auarf105.htm#IDX4555">(4555)</A>
-<LI>listing time stamp on
-<A HREF="auarf101.htm#IDX4522">(4522)</A>
-<LI>removing from /usr/afs/bin directory
-<A HREF="auarf109.htm#IDX4579">(4579)</A>
-<LI>use by bos uninstall command
-<A HREF="auarf123.htm#IDX4679">(4679)</A>
-</MENU>
-<LI>On-line status flag in volume header
-<A HREF="auarf261.htm#IDX5666">(5666)</A>, <A HREF="auarf266.htm#IDX5742">(5742)</A>
-<LI>operating system
-<MENU>
-<LI>AFS system names
-<A HREF="auarf165.htm#IDX4997">(4997)</A>
-</MENU>
-<LI>outages
-<MENU>
-<LI>BOS Server
-<A HREF="auarf124.htm#IDX4684">(4684)</A>
-<LI>monitoring with afsmonitor
-<A HREF="auarf058.htm#IDX4197">(4197)</A>
-<LI>monitoring with scout
-<A HREF="auarf233.htm#IDX5453">(5453)</A>
-</MENU>
-<LI>overwriting
-<MENU>
-<LI>directories/files/links with uss
-<A HREF="auarf243.htm#IDX5531">(5531)</A>
-</MENU>
-<LI>owner
-<MENU>
-<LI>Protection Database entry, changing
-<A HREF="auarf213.htm#IDX5250">(5250)</A>
-<LI>Protection Database entry, defined
-<A HREF="auarf217.htm#IDX5345">(5345)</A>
-<LI>Protection Database entry, displaying
-<A HREF="auarf217.htm#IDX5331">(5331)</A>
-<LI>Protection Database entry, setting
-<A HREF="auarf214.htm#IDX5258">(5258)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_50" HREF="#IDX0_50">P</A></STRONG>
-<MENU>
-<LI>package
-<MENU>
-<LI>C instruction in configuration file
-<A HREF="auarf053.htm#IDX4049">(4049)</A>
-<LI>command, syntax defined
-<A HREF="auarf204.htm#IDX5197">(5197)</A>
-<LI>configuration file (see entry: <I>package configuration file</I>)
-<A HREF="auarf053.htm#IDX4038">(4038)</A>
-<LI>D instruction in configuration file
-<A HREF="auarf053.htm#IDX4057">(4057)</A>
-<LI>define instruction in configuration file
-<A HREF="auarf053.htm#IDX4084">(4084)</A>
-<LI>defining block special device with B instruction
-<A HREF="auarf053.htm#IDX4043">(4043)</A>
-<LI>defining character special device
-<A HREF="auarf053.htm#IDX4050">(4050)</A>
-<LI>defining directory
-<A HREF="auarf053.htm#IDX4058">(4058)</A>
-<LI>defining file
-<A HREF="auarf053.htm#IDX4065">(4065)</A>
-<LI>defining socket
-<A HREF="auarf053.htm#IDX4079">(4079)</A>
-<LI>defining symbolic link
-<A HREF="auarf053.htm#IDX4072">(4072)</A>
-<LI>F instruction in configuration file
-<A HREF="auarf053.htm#IDX4064">(4064)</A>
-<LI>ifdef instruction in configuration file
-<A HREF="auarf053.htm#IDX4090">(4090)</A>
-<LI>ifndef instruction in configuration file
-<A HREF="auarf053.htm#IDX4093">(4093)</A>
-<LI>include instruction in configuration file
-<A HREF="auarf053.htm#IDX4097">(4097)</A>
-<LI>L instruction in configuration file
-<A HREF="auarf053.htm#IDX4071">(4071)</A>
-<LI>privilege requirements
-<A HREF="auarf204.htm#IDX5203">(5203)</A>
-<LI>S instruction in configuration file
-<A HREF="auarf053.htm#IDX4078">(4078)</A>
-<LI>undef instruction in configuration file
-<A HREF="auarf053.htm#IDX4087">(4087)</A>
-</MENU>
-<LI>package commands
-<MENU>
-<LI>apropos
-<A HREF="auarf205.htm#IDX5204">(5204)</A>
-<LI>help
-<A HREF="auarf206.htm#IDX5207">(5207)</A>
-</MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4040">(4040)</A>
-<MENU>
-<LI>B instruction
-<A HREF="auarf053.htm#IDX4047">(4047)</A>
-<LI>C instruction
-<A HREF="auarf053.htm#IDX4054">(4054)</A>
-<LI>D instruction
-<A HREF="auarf053.htm#IDX4061">(4061)</A>
-<LI>define instruction
-<A HREF="auarf053.htm#IDX4086">(4086)</A>
-<LI>defining block special device
-<A HREF="auarf053.htm#IDX4048">(4048)</A>
-<LI>defining character special device
-<A HREF="auarf053.htm#IDX4055">(4055)</A>
-<LI>defining directory
-<A HREF="auarf053.htm#IDX4062">(4062)</A>
-<LI>defining file
-<A HREF="auarf053.htm#IDX4069">(4069)</A>
-<LI>defining socket
-<A HREF="auarf053.htm#IDX4083">(4083)</A>
-<LI>defining symbolic link
-<A HREF="auarf053.htm#IDX4076">(4076)</A>
-<LI>F instruction
-<A HREF="auarf053.htm#IDX4068">(4068)</A>
-<LI>ifdef instruction
-<A HREF="auarf053.htm#IDX4092">(4092)</A>
-<LI>ifndef instruction
-<A HREF="auarf053.htm#IDX4095">(4095)</A>
-<LI>include instruction
-<A HREF="auarf053.htm#IDX4098">(4098)</A>
-<LI>L instruction
-<A HREF="auarf053.htm#IDX4075">(4075)</A>
-<LI>S instruction
-<A HREF="auarf053.htm#IDX4082">(4082)</A>
-<LI>undef instruction
-<A HREF="auarf053.htm#IDX4089">(4089)</A>
-</MENU>
-<LI>package_test command
-<A HREF="auarf207.htm#IDX5210">(5210)</A>
-<LI>PAG
-<MENU>
-<LI>creating with pagsh command
-<A HREF="auarf208.htm#IDX5215">(5215)</A>
-</MENU>
-<LI>pagsh command
-<A HREF="auarf208.htm#IDX5213">(5213)</A>
-<LI>partition
-<MENU>
-<LI>blocks available, displaying
-<A HREF="auarf137.htm#IDX4760">(4760)</A>, <A HREF="auarf269.htm#IDX5779">(5779)</A>
-<LI>blocks used, displaying
-<A HREF="auarf137.htm#IDX4759">(4759)</A>
-<LI>displaying blocks available
-<A HREF="auarf138.htm#IDX4775">(4775)</A>
-<LI>displaying for file server machine
-<A HREF="auarf264.htm#IDX5705">(5705)</A>
-<LI>displaying size
-<A HREF="auarf138.htm#IDX4774">(4774)</A>
-<LI>monitoring usage of
-<A HREF="auarf233.htm#IDX5465">(5465)</A>
-<LI>monitoring usage with scout
-<A HREF="auarf233.htm#IDX5452">(5452)</A>
-<LI>moving volumes
-<A HREF="auarf268.htm#IDX5770">(5770)</A>
-<LI>percent used, displaying
-<A HREF="auarf137.htm#IDX4758">(4758)</A>
-<LI>restoring all volumes (Backup System)
-<A HREF="auarf072.htm#IDX4299">(4299)</A>
-<LI>salvage triggered by SALVAGE.fs file
-<A HREF="auarf029.htm#IDX3970">(3970)</A>
-<LI>salvaging volumes on
-<A HREF="auarf114.htm#IDX4610">(4610)</A>
-<LI>size, displaying
-<A HREF="auarf137.htm#IDX4757">(4757)</A>, <A HREF="auarf269.htm#IDX5778">(5778)</A>
-</MENU>
-<LI>partition argument
-<MENU>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5582">(5582)</A>
-</MENU>
-<LI>password
-<MENU>
-<LI>changing/setting in Authentication Database
-<A HREF="auarf202.htm#IDX5190">(5190)</A>
-<LI>checking quality of
-<A HREF="auarf194.htm#IDX5154">(5154)</A>, <A HREF="auarf202.htm#IDX5193">(5193)</A>
-<LI>checking quality using kpwvalid program
-<A HREF="auarf203.htm#IDX5196">(5196)</A>
-<LI>defining initial in Authentication Database
-<A HREF="auarf183.htm#IDX5077">(5077)</A>
-<LI>generating octal form of
-<A HREF="auarf196.htm#IDX5166">(5166)</A>
-<LI>imposing restrictions with kas setfields command
-<A HREF="auarf193.htm#IDX5141">(5141)</A>
-<LI>imposing restrictions with uss template A instruction
-<A HREF="auarf055.htm#IDX4117">(4117)</A>
-<LI>in Authentication Database
-<A HREF="auarf185.htm#IDX5102">(5102)</A>
-<LI>setting in Authentication Database
-<A HREF="auarf194.htm#IDX5153">(5153)</A>
-</MENU>
-<LI>password lifetime
-<MENU>
-<LI>displaying from Authentication Database entry
-<A HREF="auarf185.htm#IDX5095">(5095)</A>
-<LI>setting in Authentication Database entry
-<A HREF="auarf193.htm#IDX5138">(5138)</A>
-</MENU>
-<LI>password reuse
-<MENU>
-<LI>setting restrictions on in Authentication Database entry
-<A HREF="auarf193.htm#IDX5139">(5139)</A>
-</MENU>
-<LI>password_for_admin argument
-<MENU>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5068">(5068)</A>
-</MENU>
-<LI>permanent name
-<MENU>
-<LI>see entry: <I>tape (Backup System)</I>
-<A HREF="auarf079.htm#IDX4354">(4354)</A>
-</MENU>
-<LI>port offset number (Tape Coordinator)
-<MENU>
-<LI>assigning in Backup Database
-<A HREF="auarf062.htm#IDX4233">(4233)</A>
-<LI>displaying from Backup Database
-<A HREF="auarf081.htm#IDX4369">(4369)</A>
-</MENU>
-<LI>portoffset argument
-<MENU>
-<LI>on backup commands
-<A HREF="auarf060.htm#IDX4215">(4215)</A>
-</MENU>
-<LI>prdb.DB0 file
-<A HREF="auarf047.htm#IDX4018">(4018)</A>
-<LI>prdb.DBSYS1 file
-<A HREF="auarf047.htm#IDX4020">(4020)</A>
-<LI>prdb_check command
-<A HREF="auarf209.htm#IDX5217">(5217)</A>
-<LI>preference ranks
-<MENU>
-<LI>displaying
-<A HREF="auarf146.htm#IDX4850">(4850)</A>
-<LI>setting
-<A HREF="auarf162.htm#IDX4977">(4977)</A>
-</MENU>
-<LI>prefix-less group
-<MENU>
-<LI>see entry: <I>group</I>
-<A HREF="auarf214.htm#IDX5264">(5264)</A>
-</MENU>
-<LI>privacy flags
-<MENU>
-<LI>Protection Database entry, displaying
-<A HREF="auarf217.htm#IDX5333">(5333)</A>
-<LI>Protection Database entry, setting
-<A HREF="auarf225.htm#IDX5402">(5402)</A>
-</MENU>
-<LI>privilege requirements
-<MENU>
-<LI>for backup commands
-<A HREF="auarf060.htm#IDX4216">(4216)</A>
-<LI>for bos commands
-<A HREF="auarf093.htm#IDX4449">(4449)</A>
-<LI>for fs commands
-<A HREF="auarf131.htm#IDX4723">(4723)</A>
-<LI>for fstrace commands
-<A HREF="auarf169.htm#IDX5021">(5021)</A>
-<LI>for kas commands
-<A HREF="auarf181.htm#IDX5059">(5059)</A>
-<LI>for package command
-<A HREF="auarf204.htm#IDX5202">(5202)</A>
-<LI>for pts commands
-<A HREF="auarf210.htm#IDX5229">(5229)</A>
-<LI>for uss commands
-<A HREF="auarf242.htm#IDX5515">(5515)</A>
-<LI>for vos commands
-<A HREF="auarf252.htm#IDX5585">(5585)</A>
-</MENU>
-<LI>privileged users
-<MENU>
-<LI>adding to UserList file
-<A HREF="auarf096.htm#IDX4470">(4470)</A>
-<LI>listing from UserList file
-<A HREF="auarf108.htm#IDX4571">(4571)</A>
-<LI>removing from UserList file
-<A HREF="auarf112.htm#IDX4599">(4599)</A>
-<LI>setting ADMIN flag in Authentication Database
-<A HREF="auarf193.htm#IDX5137">(5137)</A>
-<LI>system:administrators group, adding
-<A HREF="auarf211.htm#IDX5243">(5243)</A>
-<LI>system:administrators group, removing
-<A HREF="auarf223.htm#IDX5389">(5389)</A>
-</MENU>
-<LI>process
-<MENU>
-<LI>see entry: <I>server process</I>
-<A HREF="auarf093.htm#IDX4439">(4439)</A>
-</MENU>
-<LI>program
-<MENU>
-<LI>controlling setuid status
-<A HREF="auarf159.htm#IDX4956">(4956)</A>
-<LI>displaying setuid status
-<A HREF="auarf144.htm#IDX4836">(4836)</A>
-</MENU>
-<LI>protection
-<MENU>
-<LI>AFS vs. UNIX
-<A HREF="auarf210.htm#IDX5220">(5220)</A>
-</MENU>
-<LI>Protection Database
-<A HREF="auarf210.htm#IDX5225">(5225)</A>
-<MENU>
-<LI>all entries, displaying
-<A HREF="auarf219.htm#IDX5356">(5356)</A>
-<LI>creator of entry defined
-<A HREF="auarf217.htm#IDX5346">(5346)</A>
-<LI>creator of entry, displaying
-<A HREF="auarf217.htm#IDX5312">(5312)</A>
-<LI>files constituting
-<A HREF="auarf047.htm#IDX4022">(4022)</A>
-<LI>group entry, creating
-<A HREF="auarf214.htm#IDX5254">(5254)</A>
-<LI>group entry, deleting
-<A HREF="auarf216.htm#IDX5301">(5301)</A>
-<LI>group entry, displaying
-<A HREF="auarf217.htm#IDX5310">(5310)</A>
-<LI>group members, adding
-<A HREF="auarf211.htm#IDX5242">(5242)</A>
-<LI>group members, removing
-<A HREF="auarf223.htm#IDX5388">(5388)</A>
-<LI>group membership, displaying
-<A HREF="auarf222.htm#IDX5381">(5381)</A>
-<LI>group memberships, displaying number
-<A HREF="auarf217.htm#IDX5315">(5315)</A>
-<LI>group-creation quota defined
-<A HREF="auarf217.htm#IDX5348">(5348)</A>
-<LI>group-creation quota, displaying
-<A HREF="auarf217.htm#IDX5314">(5314)</A>
-<LI>group-creation quota, setting
-<A HREF="auarf225.htm#IDX5401">(5401)</A>
-<LI>groups owned, displaying
-<A HREF="auarf221.htm#IDX5373">(5373)</A>
-<LI>machine entry, creating
-<A HREF="auarf215.htm#IDX5277">(5277)</A>
-<LI>machine entry, deleting
-<A HREF="auarf216.htm#IDX5300">(5300)</A>
-<LI>machine entry, displaying
-<A HREF="auarf217.htm#IDX5309">(5309)</A>
-<LI>max group id counter, displaying
-<A HREF="auarf220.htm#IDX5366">(5366)</A>
-<LI>max group id counter, setting
-<A HREF="auarf226.htm#IDX5416">(5416)</A>
-<LI>max user id counter, displaying
-<A HREF="auarf220.htm#IDX5365">(5365)</A>
-<LI>max user id counter, setting
-<A HREF="auarf226.htm#IDX5415">(5415)</A>
-<LI>membership count defined
-<A HREF="auarf217.htm#IDX5347">(5347)</A>
-<LI>membership count, displaying
-<A HREF="auarf217.htm#IDX5340">(5340)</A>
-<LI>name of entry, changing
-<A HREF="auarf224.htm#IDX5392">(5392)</A>
-<LI>owner of entry defined
-<A HREF="auarf217.htm#IDX5344">(5344)</A>
-<LI>owner of entry, changing
-<A HREF="auarf213.htm#IDX5249">(5249)</A>
-<LI>owner of entry, displaying
-<A HREF="auarf217.htm#IDX5311">(5311)</A>
-<LI>owner of entry, setting initial
-<A HREF="auarf214.htm#IDX5266">(5266)</A>
-<LI>privacy flags, displaying
-<A HREF="auarf217.htm#IDX5313">(5313)</A>
-<LI>privacy flags, setting
-<A HREF="auarf225.htm#IDX5400">(5400)</A>
-<LI>status, verifying
-<A HREF="auarf209.htm#IDX5219">(5219)</A>
-<LI>user entry, creating
-<A HREF="auarf215.htm#IDX5276">(5276)</A>
-<LI>user entry, creating with uss
-<A HREF="auarf243.htm#IDX5526">(5526)</A>
-<LI>user entry, deleting
-<A HREF="auarf216.htm#IDX5299">(5299)</A>
-<LI>user entry, deleting with uss
-<A HREF="auarf246.htm#IDX5550">(5550)</A>
-<LI>user entry, displaying
-<A HREF="auarf217.htm#IDX5308">(5308)</A>
-</MENU>
-<LI>protection group
-<MENU>
-<LI>see entry: <I>group</I>
-<A HREF="auarf210.htm#IDX5224">(5224)</A>
-</MENU>
-<LI>Protection Server
-<A HREF="auarf210.htm#IDX5226">(5226)</A>
-<MENU>
-<LI>listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3915">(3915)</A>
-<LI>listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3923">(3923)</A>
-<LI>starting
-<A HREF="auarf227.htm#IDX5419">(5419)</A>
-</MENU>
-<LI>pts commands
-<MENU>
-<LI>adduser
-<A HREF="auarf211.htm#IDX5235">(5235)</A>
-<LI>apropos
-<A HREF="auarf212.htm#IDX5244">(5244)</A>
-<LI>chown
-<A HREF="auarf213.htm#IDX5247">(5247)</A>
-<LI>common options
-<A HREF="auarf210.htm#IDX5228">(5228)</A>
-<LI>creategroup
-<A HREF="auarf214.htm#IDX5252">(5252)</A>
-<LI>createuser
-<A HREF="auarf215.htm#IDX5274">(5274)</A>
-<LI>delete
-<A HREF="auarf216.htm#IDX5293">(5293)</A>
-<LI>examine
-<A HREF="auarf217.htm#IDX5303">(5303)</A>
-<LI>help
-<A HREF="auarf218.htm#IDX5350">(5350)</A>
-<LI>listentries
-<A HREF="auarf219.htm#IDX5353">(5353)</A>
-<LI>listmax
-<A HREF="auarf220.htm#IDX5359">(5359)</A>
-<LI>listowned
-<A HREF="auarf221.htm#IDX5367">(5367)</A>
-<LI>membership
-<A HREF="auarf222.htm#IDX5374">(5374)</A>
-<LI>privilege requirements
-<A HREF="auarf210.htm#IDX5230">(5230)</A>
-<LI>removeuser
-<A HREF="auarf223.htm#IDX5382">(5382)</A>
-<LI>rename
-<A HREF="auarf224.htm#IDX5390">(5390)</A>
-<LI>setfields
-<A HREF="auarf225.htm#IDX5396">(5396)</A>
-<LI>setmax
-<A HREF="auarf226.htm#IDX5409">(5409)</A>
-</MENU>
-<LI>ptserver command
-<A HREF="auarf227.htm#IDX5417">(5417)</A>
-<LI>ptserver process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4493">(4493)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_51" HREF="#IDX0_51">Q</A></STRONG>
-<MENU>
-<LI>quitting
-<MENU>
-<LI>backup interactive mode
-<A HREF="auarf083.htm#IDX4384">(4384)</A>
-<LI>kas interactive mode
-<A HREF="auarf192.htm#IDX5128">(5128)</A>
-</MENU>
-<LI>quota
-<MENU>
-<LI>(see entry: <I>volume quota</I>)
-<A HREF="auarf258.htm#IDX5623">(5623)</A>
-<LI>see entry: <I>group-creation quota</I>
-<A HREF="auarf214.htm#IDX5260">(5260)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_52" HREF="#IDX0_52">R</A></STRONG>
-<MENU>
-<LI>RClone field in volume header
-<A HREF="auarf261.htm#IDX5676">(5676)</A>, <A HREF="auarf266.htm#IDX5752">(5752)</A>
-<LI>rcp command (AFS version)
-<A HREF="auarf228.htm#IDX5422">(5422)</A>
-<LI>read shorthand notation for ACL permissions
-<A HREF="auarf157.htm#IDX4943">(4943)</A>
-<LI>read-only extension on volume name
-<MENU>
-<LI>added by vos release command
-<A HREF="auarf270.htm#IDX5804">(5804)</A>
-</MENU>
-<LI>read-only volume
-<MENU>
-<LI>creating
-<A HREF="auarf270.htm#IDX5788">(5788)</A>
-<LI>defining site in VLDB
-<A HREF="auarf253.htm#IDX5591">(5591)</A>
-<LI>dumping
-<A HREF="auarf260.htm#IDX5647">(5647)</A>
-<LI>forcing Cache Manager to see new release
-<A HREF="auarf134.htm#IDX4741">(4741)</A>
-<LI>ID number
-<A HREF="auarf258.htm#IDX5636">(5636)</A>
-<LI>ID number in volume header
-<A HREF="auarf261.htm#IDX5670">(5670)</A>, <A HREF="auarf266.htm#IDX5746">(5746)</A>
-<LI>moving
-<A HREF="auarf268.htm#IDX5773">(5773)</A>
-<LI>name, changing
-<A HREF="auarf273.htm#IDX5827">(5827)</A>
-<LI>need for all-or-nothing release
-<A HREF="auarf270.htm#IDX5796">(5796)</A>
-<LI>removing
-<A HREF="auarf271.htm#IDX5811">(5811)</A>
-<LI>site, removing mistakenly defined
-<A HREF="auarf272.htm#IDX5817">(5817)</A>
-</MENU>
-<LI>read/write mount point
-<A HREF="auarf153.htm#IDX4900">(4900)</A>
-<LI>read/write volume
-<MENU>
-<LI>cloning for backup version
-<A HREF="auarf255.htm#IDX5598">(5598)</A>
-<LI>cloning for replication
-<A HREF="auarf270.htm#IDX5791">(5791)</A>
-<LI>cloning multiple for backup version
-<A HREF="auarf256.htm#IDX5607">(5607)</A>
-<LI>creating
-<A HREF="auarf258.htm#IDX5624">(5624)</A>
-<LI>dumping
-<A HREF="auarf260.htm#IDX5646">(5646)</A>
-<LI>ID number
-<A HREF="auarf258.htm#IDX5635">(5635)</A>
-<LI>ID number in volume header
-<A HREF="auarf261.htm#IDX5669">(5669)</A>, <A HREF="auarf266.htm#IDX5745">(5745)</A>
-<LI>moving
-<A HREF="auarf268.htm#IDX5771">(5771)</A>
-<LI>name, changing
-<A HREF="auarf273.htm#IDX5826">(5826)</A>
-<LI>removing
-<A HREF="auarf271.htm#IDX5809">(5809)</A>
-</MENU>
-<LI>regular expression
-<MENU>
-<LI>Backup System
-<A HREF="auarf063.htm#IDX4253">(4253)</A>
-</MENU>
-<LI>regular group
-<MENU>
-<LI>see entry: <I>group</I>
-<A HREF="auarf214.htm#IDX5265">(5265)</A>
-</MENU>
-<LI>regular mount point
-<A HREF="auarf153.htm#IDX4898">(4898)</A>
-<LI>release
-<MENU>
-<LI>status flags on site definitions in VLDB entry
-<A HREF="auarf261.htm#IDX5689">(5689)</A>, <A HREF="auarf265.htm#IDX5723">(5723)</A>
-</MENU>
-<LI>ReleaseClone
-<A HREF="auarf270.htm#IDX5798">(5798)</A>
-<LI>ReleaseClone volume
-<MENU>
-<LI>ID number in volume header
-<A HREF="auarf261.htm#IDX5672">(5672)</A>, <A HREF="auarf266.htm#IDX5748">(5748)</A>
-</MENU>
-<LI>releasing read-only volume
-<MENU>
-<LI>forcing Cache Manager to see
-<A HREF="auarf134.htm#IDX4745">(4745)</A>
-<LI>with vos release command
-<A HREF="auarf270.htm#IDX5797">(5797)</A>
-</MENU>
-<LI>remote
-<MENU>
-<LI>command execution with bos exec
-<A HREF="auarf100.htm#IDX4515">(4515)</A>
-<LI>file copy with rcp command (AFS version)
-<A HREF="auarf228.htm#IDX5425">(5425)</A>
-<LI>shell with rsh command (AFS version)
-<A HREF="auarf229.htm#IDX5431">(5431)</A>
-</MENU>
-<LI>removing
-<MENU>
-<LI>.BAK version of binary file
-<A HREF="auarf109.htm#IDX4576">(4576)</A>
-<LI>.OLD version of binary file
-<A HREF="auarf109.htm#IDX4577">(4577)</A>
-<LI>ACL entry
-<A HREF="auarf157.htm#IDX4931">(4931)</A>
-<LI>core file from /usr/afs/logs directory
-<A HREF="auarf109.htm#IDX4580">(4580)</A>
-<LI>database server machine from CellServDB file (server)
-<A HREF="auarf110.htm#IDX4589">(4589)</A>
-<LI>mount point
-<A HREF="auarf156.htm#IDX4919">(4919)</A>
-<LI>obsolete AFS UIDs from ACL
-<A HREF="auarf135.htm#IDX4749">(4749)</A>
-<LI>privileged users from UserList file
-<A HREF="auarf112.htm#IDX4598">(4598)</A>
-<LI>see also entry: <I>deleting</I>
-<A HREF="auarf067.htm#IDX4274">(4274)</A>
-<LI>server encryption key from KeyFile file
-<A HREF="auarf111.htm#IDX4593">(4593)</A>
-<LI>user from group
-<A HREF="auarf223.htm#IDX5384">(5384)</A>
-<LI>volume
-<A HREF="auarf271.htm#IDX5808">(5808)</A>
-<LI>volume entry from volume set in Backup Database
-<A HREF="auarf070.htm#IDX4290">(4290)</A>
-<LI>volume from site, without changing VLDB
-<A HREF="auarf280.htm#IDX5865">(5865)</A>
-<LI>volume site mistakenly defined
-<A HREF="auarf272.htm#IDX5815">(5815)</A>
-</MENU>
-<LI>renaming
-<MENU>
-<LI>volume
-<A HREF="auarf273.htm#IDX5821">(5821)</A>
-</MENU>
-<LI>replacing binary file
-<MENU>
-<LI>see entry: <I>uninstalling</I>
-<A HREF="auarf123.htm#IDX4673">(4673)</A>
-</MENU>
-<LI>replication
-<A HREF="auarf270.htm#IDX5784">(5784)</A>
-<MENU>
-<LI>determining success of
-<A HREF="auarf270.htm#IDX5792">(5792)</A>
-<LI>forcing creation of new clone
-<A HREF="auarf270.htm#IDX5803">(5803)</A>
-<LI>need for all-or-nothing release
-<A HREF="auarf270.htm#IDX5794">(5794)</A>
-<LI>role of ReleaseClone in
-<A HREF="auarf270.htm#IDX5799">(5799)</A>
-</MENU>
-<LI>restart times for BOS Server
-<MENU>
-<LI>displaying
-<A HREF="auarf103.htm#IDX4536">(4536)</A>
-<LI>setting
-<A HREF="auarf117.htm#IDX4630">(4630)</A>
-</MENU>
-<LI>restarting
-<MENU>
-<LI>server process
-<A HREF="auarf113.htm#IDX4606">(4606)</A>
-</MENU>
-<LI>restoring
-<MENU>
-<LI>internal consistency in file system (salvaging)
-<A HREF="auarf114.htm#IDX4613">(4613)</A>
-<LI>synchrony of VLDB and volume headers
-<A HREF="auarf276.htm#IDX5843">(5843)</A>, <A HREF="auarf277.htm#IDX5852">(5852)</A>
-<LI>volume, all in volume set (Backup System)
-<A HREF="auarf092.htm#IDX4434">(4434)</A>
-<LI>volume, all on partition (Backup System)
-<A HREF="auarf072.htm#IDX4298">(4298)</A>
-<LI>volume, single (Backup System)
-<A HREF="auarf091.htm#IDX4425">(4425)</A>
-<LI>volumes with vos command
-<A HREF="auarf274.htm#IDX5832">(5832)</A>
-</MENU>
-<LI>ROnly field in volume header
-<A HREF="auarf261.htm#IDX5674">(5674)</A>, <A HREF="auarf266.htm#IDX5750">(5750)</A>
-<LI>rsh command (AFS version)
-<A HREF="auarf229.htm#IDX5428">(5428)</A>
-<LI>runntp command
-<A HREF="auarf230.htm#IDX5433">(5433)</A>
-<LI>runntp process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4495">(4495)</A>
-</MENU>
-<LI>RWrite field in volume header
-<A HREF="auarf261.htm#IDX5673">(5673)</A>, <A HREF="auarf266.htm#IDX5749">(5749)</A>
-<LI>Rx
-<MENU>
-<LI>tracing activity
-<A HREF="auarf231.htm#IDX5442">(5442)</A>
-</MENU>
-<LI>rxdebug command
-<A HREF="auarf231.htm#IDX5440">(5440)</A>
-</MENU>
-<STRONG><A NAME="IDX1_53" HREF="#IDX0_53">S</A></STRONG>
-<MENU>
-<LI>S instruction
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4077">(4077)</A>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4150">(4150)</A>
-</MENU>
-<LI>SALVAGE.fs file
-<A HREF="auarf029.htm#IDX3967">(3967)</A>
-<LI>SalvageLog file
-<A HREF="auarf030.htm#IDX3972">(3972)</A>
-<LI>salvager process
-<MENU>
-<LI>command for invoking manually
-<A HREF="auarf232.htm#IDX5445">(5445)</A>
-<LI>log file
-<A HREF="auarf030.htm#IDX3974">(3974)</A>
-<LI>part of fs entry in BosConfig file
-<A HREF="auarf016.htm#IDX3890">(3890)</A>
-<LI>SALVAGE.fs file as trigger
-<A HREF="auarf029.htm#IDX3969">(3969)</A>
-</MENU>
-<LI>salvaging volume
-<MENU>
-<LI>with bos salvage command
-<A HREF="auarf114.htm#IDX4612">(4612)</A>
-<LI>with salvager command
-<A HREF="auarf232.htm#IDX5444">(5444)</A>
-</MENU>
-<LI>savevolume instruction in uss bulk input file
-<A HREF="auarf054.htm#IDX4109">(4109)</A>
-<LI>scanning
-<MENU>
-<LI>Backup System tape
-<A HREF="auarf087.htm#IDX4405">(4405)</A>
-</MENU>
-<LI>scout
-<MENU>
-<LI>command syntax for
-<A HREF="auarf233.htm#IDX5447">(5447)</A>
-<LI>disk usage
-<A HREF="auarf233.htm#IDX5467">(5467)</A>
-<LI>outages, monitoring
-<A HREF="auarf233.htm#IDX5454">(5454)</A>
-<LI>statistics available
-<A HREF="auarf233.htm#IDX5457">(5457)</A>
-</MENU>
-<LI>server
-<MENU>
-<LI>see entry: <I>server process</I>
-<A HREF="auarf093.htm#IDX4441">(4441)</A>
-</MENU>
-<LI>server argument
-<MENU>
-<LI>on bos commands
-<A HREF="auarf093.htm#IDX4448">(4448)</A>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5583">(5583)</A>
-</MENU>
-<LI>server encryption key
-<A HREF="auarf023.htm#IDX3936">(3936)</A>
-<MENU>
-<LI>adding to KeyFile file
-<A HREF="auarf095.htm#IDX4459">(4459)</A>
-<LI>displaying from Authentication Database
-<A HREF="auarf185.htm#IDX5090">(5090)</A>
-<LI>in Authentication Database
-<A HREF="auarf185.htm#IDX5103">(5103)</A>
-<LI>listing from KeyFile file
-<A HREF="auarf107.htm#IDX4564">(4564)</A>
-<LI>removing from KeyFile file
-<A HREF="auarf111.htm#IDX4594">(4594)</A>
-</MENU>
-<LI>server machine
-<MENU>
-<LI>cell membership
-<A HREF="auarf033.htm#IDX3983">(3983)</A>
-<LI>checking status with fs checkservers command
-<A HREF="auarf133.htm#IDX4730">(4730)</A>
-<LI>displaying Cache Manager preference ranks
-<A HREF="auarf146.htm#IDX4847">(4847)</A>
-<LI>maintaining clock with NTPD
-<A HREF="auarf230.htm#IDX5439">(5439)</A>
-<LI>restart times, displaying
-<A HREF="auarf103.htm#IDX4542">(4542)</A>
-<LI>restart times, setting
-<A HREF="auarf117.htm#IDX4633">(4633)</A>
-<LI>setting authorization checking requirements
-<A HREF="auarf115.htm#IDX4619">(4619)</A>
-<LI>setting Cache Manager preference ranks
-<A HREF="auarf162.htm#IDX4974">(4974)</A>
-</MENU>
-<LI>server partition
-<MENU>
-<LI>FORCESALVAGE file
-<A HREF="auarf022.htm#IDX3933">(3933)</A>
-<LI>V<I>vol_ID</I>.vol files
-<A HREF="auarf037.htm#IDX3992">(3992)</A>
-</MENU>
-<LI>server portion of Update Server
-<MENU>
-<LI>see entry: <I>upserver process</I>
-<A HREF="auarf241.htm#IDX5506">(5506)</A>
-</MENU>
-<LI>server process
-<A HREF="auarf093.htm#IDX4438">(4438)</A>
-<MENU>
-<LI>BosConfig file entry
-<A HREF="auarf016.htm#IDX3882">(3882)</A>
-<LI>creating in BosConfig file
-<A HREF="auarf098.htm#IDX4477">(4477)</A>
-<LI>creating ticket (tokens) for
-<A HREF="auarf200.htm#IDX5179">(5179)</A>
-<LI>deleting from BosConfig file
-<A HREF="auarf099.htm#IDX4508">(4508)</A>
-<LI>displaying BosConfig entry
-<A HREF="auarf121.htm#IDX4658">(4658)</A>
-<LI>displaying log file
-<A HREF="auarf102.htm#IDX4531">(4531)</A>
-<LI>listing run status
-<A HREF="auarf121.htm#IDX4657">(4657)</A>
-<LI>listing time stamp on binary file
-<A HREF="auarf101.htm#IDX4518">(4518)</A>
-<LI>restarting
-<A HREF="auarf113.htm#IDX4604">(4604)</A>
-<LI>starting
-<A HREF="auarf120.htm#IDX4650">(4650)</A>
-<LI>starting (changing status flag in BosConfig)
-<A HREF="auarf119.htm#IDX4642">(4642)</A>
-<LI>starting on server
-<A HREF="auarf098.htm#IDX4478">(4478)</A>
-<LI>stopping (changing BosConfig status flag)
-<A HREF="auarf122.htm#IDX4663">(4663)</A>
-<LI>stopping (no change to BosConfig status flag)
-<A HREF="auarf118.htm#IDX4636">(4636)</A>
-<LI>stopping and immediately restarting
-<A HREF="auarf113.htm#IDX4605">(4605)</A>
-<LI>types
-<A HREF="auarf016.htm#IDX3885">(3885)</A>
-<LI>uninstalling binary file
-<A HREF="auarf123.htm#IDX4675">(4675)</A>
-</MENU>
-<LI>server tickets
-<MENU>
-<LI>discarding
-<A HREF="auarf186.htm#IDX5106">(5106)</A>
-</MENU>
-<LI>servers argument
-<MENU>
-<LI>on kas commands
-<A HREF="auarf181.htm#IDX5069">(5069)</A>
-</MENU>
-<LI>setting
-<MENU>
-<LI>ACL
-<A HREF="auarf157.htm#IDX4929">(4929)</A>
-<LI>ACL with uss
-<A HREF="auarf055.htm#IDX4128">(4128)</A>, <A HREF="auarf055.htm#IDX4180">(4180)</A>
-<LI>AFS GID for group
-<A HREF="auarf214.htm#IDX5270">(5270)</A>
-<LI>AFS UID for user
-<A HREF="auarf215.htm#IDX5289">(5289)</A>
-<LI>Authentication Database entry flags and expiration dates
-<A HREF="auarf193.htm#IDX5132">(5132)</A>
-<LI>authorization checking requirements on server machine
-<A HREF="auarf115.htm#IDX4618">(4618)</A>
-<LI>BOS Server
-<A HREF="auarf117.htm#IDX4632">(4632)</A>
-<LI>Cache Manager preference ranks
-<A HREF="auarf162.htm#IDX4976">(4976)</A>
-<LI>cell name in CellServDB file
-<A HREF="auarf116.htm#IDX4627">(4627)</A>
-<LI>cell name in ThisCell file
-<A HREF="auarf116.htm#IDX4626">(4626)</A>
-<LI>client interfaces not registered with File Server, in NetInfo file
-<A HREF="auarf026.htm#IDX3958">(3958)</A>
-<LI>client interfaces registered with File Server
-<A HREF="auarf160.htm#IDX4965">(4965)</A>
-<LI>client interfaces registered with File Server, in NetInfo file
-<A HREF="auarf024.htm#IDX3947">(3947)</A>
-<LI>data cache size
-<A HREF="auarf158.htm#IDX4948">(4948)</A>
-<LI>expiration date on existing Backup System dump level
-<A HREF="auarf088.htm#IDX4411">(4411)</A>
-<LI>expiration date on new dump level (Backup System)
-<A HREF="auarf061.htm#IDX4228">(4228)</A>
-<LI>File Server interfaces not registered in VLDB, in NetRestrict file
-<A HREF="auarf027.htm#IDX3963">(3963)</A>
-<LI>File Server interfaces registered in VLDB, in NetInfo file
-<A HREF="auarf025.htm#IDX3952">(3952)</A>
-<LI>group-creation quota
-<A HREF="auarf225.htm#IDX5399">(5399)</A>
-<LI>initial owner for group
-<A HREF="auarf214.htm#IDX5272">(5272)</A>
-<LI>key field in Authentication Database, using password
-<A HREF="auarf194.htm#IDX5149">(5149)</A>
-<LI>key version number in KeyFile file
-<A HREF="auarf095.htm#IDX4462">(4462)</A>
-<LI>max group id counter in Protection Database
-<A HREF="auarf226.htm#IDX5413">(5413)</A>
-<LI>max user id counter in Protection Database
-<A HREF="auarf226.htm#IDX5414">(5414)</A>
-<LI>password in Authentication Database
-<A HREF="auarf202.htm#IDX5192">(5192)</A>
-<LI>privacy flags on Protection Database entry
-<A HREF="auarf225.htm#IDX5398">(5398)</A>
-<LI>setuid status
-<A HREF="auarf159.htm#IDX4957">(4957)</A>
-<LI>status flag in BOS Server memory to NotRun
-<A HREF="auarf122.htm#IDX4669">(4669)</A>
-<LI>status flag in BOS Server memory to Run
-<A HREF="auarf119.htm#IDX4648">(4648)</A>, <A HREF="auarf120.htm#IDX4654">(4654)</A>
-<LI>status flag in BosConfig file
-<A HREF="auarf098.htm#IDX4482">(4482)</A>
-<LI>status flag in BosConfig file to NotRun
-<A HREF="auarf122.htm#IDX4668">(4668)</A>
-<LI>status flag in BosConfig file to Run
-<A HREF="auarf119.htm#IDX4647">(4647)</A>
-<LI>system type of client machine
-<A HREF="auarf165.htm#IDX4992">(4992)</A>
-<LI>volume ACL, default at creation
-<A HREF="auarf258.htm#IDX5629">(5629)</A>
-<LI>volume quota
-<A HREF="auarf161.htm#IDX4966">(4966)</A>, <A HREF="auarf163.htm#IDX4978">(4978)</A>
-<LI>volume quota with uss
-<A HREF="auarf055.htm#IDX4177">(4177)</A>
-<LI>volume quota, default at creation
-<A HREF="auarf258.htm#IDX5630">(5630)</A>
-</MENU>
-<LI>setuid privilege
-<MENU>
-<LI>controlling
-<A HREF="auarf159.htm#IDX4958">(4958)</A>
-<LI>displaying
-<A HREF="auarf144.htm#IDX4838">(4838)</A>
-</MENU>
-<LI>shell
-<MENU>
-<LI>opening remotely with rsh command (AFS version)
-<A HREF="auarf229.htm#IDX5432">(5432)</A>
-</MENU>
-<LI>shorthand notation for ACL permissions
-<A HREF="auarf157.htm#IDX4940">(4940)</A>
-<LI>shutting down
-<MENU>
-<LI>server process
-<A HREF="auarf118.htm#IDX4638">(4638)</A>
-</MENU>
-<LI>simple process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4503">(4503)</A>
-<LI>recorded in <I>BosConfig</I> file
-<A HREF="auarf016.htm#IDX3891">(3891)</A>
-</MENU>
-<LI>site
-<MENU>
-<LI>count in VLDB
-<A HREF="auarf261.htm#IDX5685">(5685)</A>, <A HREF="auarf265.htm#IDX5719">(5719)</A>
-</MENU>
-<LI>size
-<MENU>
-<LI>displaying from Backup System tape label
-<A HREF="auarf084.htm#IDX4392">(4392)</A>
-<LI>partition, displaying with space available
-<A HREF="auarf269.htm#IDX5781">(5781)</A>
-<LI>recording on Backup System tape label
-<A HREF="auarf079.htm#IDX4353">(4353)</A>
-<LI>tape device filemark, determining
-<A HREF="auarf130.htm#IDX4714">(4714)</A>
-</MENU>
-<LI>skipauth flag
-<MENU>
-<LI>on uss commands
-<A HREF="auarf242.htm#IDX5514">(5514)</A>
-</MENU>
-<LI>socket
-<MENU>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4081">(4081)</A>
-</MENU>
-<LI>starting
-<MENU>
-<LI>Backup Server
-<A HREF="auarf125.htm#IDX4688">(4688)</A>
-<LI>client portion of Update Server
-<A HREF="auarf240.htm#IDX5501">(5501)</A>
-<LI>NTPD, with runntp
-<A HREF="auarf230.htm#IDX5438">(5438)</A>
-<LI>process on server (changing status flag in BosConfig)
-<A HREF="auarf119.htm#IDX4643">(4643)</A>
-<LI>process on server (no change to status flag in BosConfig)
-<A HREF="auarf120.htm#IDX4651">(4651)</A>
-<LI>Protection Server
-<A HREF="auarf227.htm#IDX5420">(5420)</A>
-<LI>Salvager by hand
-<A HREF="auarf232.htm#IDX5446">(5446)</A>
-<LI>server portion of Update Server
-<A HREF="auarf241.htm#IDX5507">(5507)</A>
-<LI>server process
-<A HREF="auarf098.htm#IDX4480">(4480)</A>
-<LI>Tape Coordinator
-<A HREF="auarf126.htm#IDX4694">(4694)</A>
-</MENU>
-<LI>statistics
-<MENU>
-<LI>Authentication Server
-<A HREF="auarf195.htm#IDX5160">(5160)</A>
-<LI>available in scout
-<A HREF="auarf233.htm#IDX5458">(5458)</A>
-</MENU>
-<LI>status
-<MENU>
-<LI>displaying for server machine
-<A HREF="auarf133.htm#IDX4733">(4733)</A>
-<LI>listing for server process
-<A HREF="auarf121.htm#IDX4661">(4661)</A>
-<LI>Volume Server, displaying
-<A HREF="auarf275.htm#IDX5835">(5835)</A>
-</MENU>
-<LI>status flag
-<MENU>
-<LI>for process in BOS Server memory, about
-<A HREF="auarf016.htm#IDX3896">(3896)</A>
-<LI>for process in BosConfig file, about
-<A HREF="auarf016.htm#IDX3892">(3892)</A>
-<LI>in Authentication Database, displaying
-<A HREF="auarf185.htm#IDX5087">(5087)</A>
-<LI>in Authentication Database, setting
-<A HREF="auarf193.htm#IDX5134">(5134)</A>
-<LI>release, on site definitions in VLDB entry
-<A HREF="auarf261.htm#IDX5691">(5691)</A>, <A HREF="auarf265.htm#IDX5725">(5725)</A>
-<LI>setting to NotRun for process, in BosConfig file
-<A HREF="auarf122.htm#IDX4666">(4666)</A>
-<LI>setting to NotRun for process, in BOS Server memory
-<A HREF="auarf118.htm#IDX4639">(4639)</A>, <A HREF="auarf122.htm#IDX4667">(4667)</A>
-<LI>setting to Run for process, in BOS Server memory
-<A HREF="auarf119.htm#IDX4646">(4646)</A>, <A HREF="auarf120.htm#IDX4653">(4653)</A>
-<LI>setting to Run for process, in BosConfig file
-<A HREF="auarf098.htm#IDX4481">(4481)</A>, <A HREF="auarf119.htm#IDX4645">(4645)</A>
-</MENU>
-<LI>status flags in volume header
-<A HREF="auarf261.htm#IDX5665">(5665)</A>, <A HREF="auarf266.htm#IDX5741">(5741)</A>
-<LI>stopping
-<MENU>
-<LI>server process (changing status flag in BosConfig)
-<A HREF="auarf122.htm#IDX4664">(4664)</A>
-<LI>server process (no change to BosConfig status flag)
-<A HREF="auarf118.htm#IDX4637">(4637)</A>
-</MENU>
-<LI>storing statistic in scout
-<A HREF="auarf233.htm#IDX5461">(5461)</A>
-<LI>symbolic link
-<MENU>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4159">(4159)</A>
-<LI>defining with package
-<A HREF="auarf053.htm#IDX4074">(4074)</A>
-<LI>overwriting with uss
-<A HREF="auarf243.htm#IDX5535">(5535)</A>
-</MENU>
-<LI>synchrony of VLDB and volume headers
-<MENU>
-<LI>maintained by VL and Volume Servers
-<A HREF="auarf252.htm#IDX5574">(5574)</A>
-<LI>restoring
-<A HREF="auarf276.htm#IDX5842">(5842)</A>, <A HREF="auarf277.htm#IDX5848">(5848)</A>, <A HREF="auarf277.htm#IDX5851">(5851)</A>
-</MENU>
-<LI>sys (@sys) variable in pathnames
-<A HREF="auarf165.htm#IDX4999">(4999)</A>, <A HREF="auarf234.htm#IDX5473">(5473)</A>
-<LI>sys command
-<A HREF="auarf234.htm#IDX5468">(5468)</A>
-<LI>sysid file
-<A HREF="auarf049.htm#IDX4023">(4023)</A>
-<LI>sysname
-<A HREF="auarf165.htm#IDX4996">(4996)</A>
-<LI>system outages, reducing
-<A HREF="auarf124.htm#IDX4683">(4683)</A>
-<LI>system type
-<MENU>
-<LI>AFS system names
-<A HREF="auarf165.htm#IDX4995">(4995)</A>
-<LI>client machine
-<A HREF="auarf165.htm#IDX4994">(4994)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_54" HREF="#IDX0_54">T</A></STRONG>
-<MENU>
-<LI>tape (Backup System)
-<MENU>
-<LI>capacity on label, setting
-<A HREF="auarf079.htm#IDX4350">(4350)</A>
-<LI>capacity, determining
-<A HREF="auarf130.htm#IDX4708">(4708)</A>
-<LI>capacity, displaying from label
-<A HREF="auarf084.htm#IDX4389">(4389)</A>
-<LI>label, displaying
-<A HREF="auarf084.htm#IDX4388">(4388)</A>
-<LI>labeling
-<A HREF="auarf079.htm#IDX4349">(4349)</A>
-<LI>reading dump records
-<A HREF="auarf087.htm#IDX4404">(4404)</A>
-</MENU>
-<LI>Tape Coordinator
-<MENU>
-<LI>Backup Database entry, creating
-<A HREF="auarf062.htm#IDX4231">(4231)</A>
-<LI>Backup Database entry, deleting
-<A HREF="auarf069.htm#IDX4282">(4282)</A>
-<LI>Backup Database entry, displaying
-<A HREF="auarf081.htm#IDX4368">(4368)</A>
-<LI>CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3903">(3903)</A>
-<LI>configuration file for all devices
-<A HREF="auarf050.htm#IDX4029">(4029)</A>
-<LI>configuration file for specific device (CFG)
-<A HREF="auarf018.htm#IDX3902">(3902)</A>
-<LI>filemark size, determining
-<A HREF="auarf130.htm#IDX4707">(4707)</A>
-<LI>initializing
-<A HREF="auarf126.htm#IDX4693">(4693)</A>
-<LI>port offset number, assigning in Backup Database
-<A HREF="auarf062.htm#IDX4232">(4232)</A>
-<LI>port offset number, displaying from Backup Database
-<A HREF="auarf081.htm#IDX4367">(4367)</A>
-<LI>status, displaying
-<A HREF="auarf089.htm#IDX4414">(4414)</A>
-</MENU>
-<LI>tape device (Backup System)
-<MENU>
-<LI>see entry: <I>Tape Coordinator</I>
-<A HREF="auarf062.htm#IDX4238">(4238)</A>
-</MENU>
-<LI>tape name
-<MENU>
-<LI>see entry: <I>tape (Backup System)</I>
-<A HREF="auarf079.htm#IDX4356">(4356)</A>
-</MENU>
-<LI>tapeconfig file
-<A HREF="auarf050.htm#IDX4027">(4027)</A>
-<LI>template file in uss
-<MENU>
-<LI>see entry: <I>uss template file</I>
-<A HREF="auarf055.htm#IDX4111">(4111)</A>
-</MENU>
-<LI>terminal type
-<MENU>
-<LI>setting for afsmonitor
-<A HREF="auarf059.htm#IDX4201">(4201)</A>
-</MENU>
-<LI>testing
-<MENU>
-<LI>package files
-<A HREF="auarf207.htm#IDX5212">(5212)</A>
-</MENU>
-<LI>ThisCell file (client version)
-<A HREF="auarf032.htm#IDX3975">(3975)</A>
-<LI>ThisCell file (client)
-<MENU>
-<LI>displaying contents with fs wscell command
-<A HREF="auarf168.htm#IDX5015">(5015)</A>
-</MENU>
-<LI>ThisCell file (server version)
-<A HREF="auarf033.htm#IDX3980">(3980)</A>
-<LI>ThisCell file (server)
-<MENU>
-<LI>creating with bos setcellname command
-<A HREF="auarf116.htm#IDX4624">(4624)</A>
-</MENU>
-<LI>ticket lifetime
-<MENU>
-<LI>displaying from Authentication Database
-<A HREF="auarf185.htm#IDX5093">(5093)</A>
-<LI>setting in Authentication Database
-<A HREF="auarf193.htm#IDX5136">(5136)</A>
-</MENU>
-<LI>tickets
-<A HREF="auarf023.htm#IDX3941">(3941)</A>
-<MENU>
-<LI>creating for server process
-<A HREF="auarf200.htm#IDX5180">(5180)</A>
-<LI>discarding
-<A HREF="auarf238.htm#IDX5489">(5489)</A>
-<LI>displaying for issuer of command
-<A HREF="auarf190.htm#IDX5119">(5119)</A>
-<LI>listing for user
-<A HREF="auarf235.htm#IDX5480">(5480)</A>
-<LI>see entry: <I>server tickets</I>
-<A HREF="auarf186.htm#IDX5107">(5107)</A>
-</MENU>
-<LI>time stamp
-<MENU>
-<LI>listing for binary file
-<A HREF="auarf101.htm#IDX4523">(4523)</A>
-</MENU>
-<LI>tokens
-<MENU>
-<LI>command
-<A HREF="auarf235.htm#IDX5477">(5477)</A>
-<LI>creating for server process
-<A HREF="auarf200.htm#IDX5181">(5181)</A>
-<LI>discarding
-<A HREF="auarf238.htm#IDX5491">(5491)</A>
-<LI>listing for user
-<A HREF="auarf235.htm#IDX5476">(5476)</A>
-</MENU>
-<LI>tokens command
-<A HREF="auarf235.htm#IDX5475">(5475)</A>
-<LI>translate_et command
-<A HREF="auarf236.htm#IDX5481">(5481)</A>
-<LI>translating
-<MENU>
-<LI>AFS ID to user/group name
-<A HREF="auarf217.htm#IDX5322">(5322)</A>
-<LI>directory/file name to volume ID number
-<A HREF="auarf138.htm#IDX4777">(4777)</A>
-<LI>directory/file name to volume location
-<A HREF="auarf166.htm#IDX5004">(5004)</A>
-<LI>directory/file name to volume name
-<A HREF="auarf137.htm#IDX4765">(4765)</A>, <A HREF="auarf138.htm#IDX4776">(4776)</A>, <A HREF="auarf150.htm#IDX4874">(4874)</A>
-<LI>directory/file name to volume quota
-<A HREF="auarf138.htm#IDX4778">(4778)</A>, <A HREF="auarf150.htm#IDX4875">(4875)</A>
-<LI>directory/file name to volume quota percent used
-<A HREF="auarf155.htm#IDX4917">(4917)</A>
-<LI>user/group name to AFS ID
-<A HREF="auarf217.htm#IDX5321">(5321)</A>
-<LI>volume ID number from location
-<A HREF="auarf266.htm#IDX5737">(5737)</A>
-<LI>volume location from volume name/ID number
-<A HREF="auarf265.htm#IDX5714">(5714)</A>
-<LI>volume location to ID number
-<A HREF="auarf266.htm#IDX5736">(5736)</A>
-<LI>volume name to volume ID number
-<A HREF="auarf261.htm#IDX5661">(5661)</A>
-<LI>volume name/ID number to volume location
-<A HREF="auarf265.htm#IDX5713">(5713)</A>
-</MENU>
-<LI>type flag for volume
-<MENU>
-<LI>VLDB entry
-<A HREF="auarf261.htm#IDX5687">(5687)</A>, <A HREF="auarf265.htm#IDX5721">(5721)</A>
-<LI>volume header
-<A HREF="auarf261.htm#IDX5664">(5664)</A>, <A HREF="auarf266.htm#IDX5740">(5740)</A>
-</MENU>
-<LI>types of AFS server processes
-<A HREF="auarf016.htm#IDX3884">(3884)</A>
-</MENU>
-<STRONG><A NAME="IDX1_55" HREF="#IDX0_55">U</A></STRONG>
-<MENU>
-<LI>Ubik
-<MENU>
-<LI>tracing
-<A HREF="auarf237.htm#IDX5486">(5486)</A>
-</MENU>
-<LI>udebug command
-<A HREF="auarf237.htm#IDX5484">(5484)</A>
-<LI>UID
-<MENU>
-<LI>see entry: <I>AFS GID</I>
-<A HREF="auarf217.htm#IDX5324">(5324)</A>
-<LI>see entry: <I>AFS UID</I>
-<A HREF="auarf217.htm#IDX5323">(5323)</A>
-<LI>see entry: <I>UNIX UID</I>
-<A HREF="auarf217.htm#IDX5343">(5343)</A>
-</MENU>
-<LI>unauthenticating
-<MENU>
-<LI>while in kas interactive mode
-<A HREF="auarf191.htm#IDX5122">(5122)</A>
-<LI>with unlog command
-<A HREF="auarf238.htm#IDX5492">(5492)</A>
-</MENU>
-<LI>undef statement
-<MENU>
-<LI>package configuration file
-<A HREF="auarf053.htm#IDX4088">(4088)</A>
-</MENU>
-<LI>uninstalling
-<MENU>
-<LI>binary file
-<A HREF="auarf123.htm#IDX4672">(4672)</A>
-</MENU>
-<LI>UNIX commands
-<MENU>
-<LI>ftpd (AFS version)
-<A HREF="auarf178.htm#IDX5046">(5046)</A>
-<LI>inetd (AFS version)
-<A HREF="auarf179.htm#IDX5051">(5051)</A>
-<LI>rcp (AFS version)
-<A HREF="auarf228.htm#IDX5424">(5424)</A>
-<LI>rsh (AFS version)
-<A HREF="auarf229.htm#IDX5430">(5430)</A>
-</MENU>
-<LI>UNIX UID
-<MENU>
-<LI>functional difference from AFS UID
-<A HREF="auarf217.htm#IDX5342">(5342)</A>
-</MENU>
-<LI>unlocking
-<MENU>
-<LI>volume entries (multiple) in VLDB
-<A HREF="auarf279.htm#IDX5861">(5861)</A>
-<LI>volume entry in VLDB
-<A HREF="auarf278.htm#IDX5857">(5857)</A>
-</MENU>
-<LI>unlog command
-<A HREF="auarf238.htm#IDX5487">(5487)</A>
-<LI>UNMOUNT instruction in CFG_<I>device_name</I> file
-<A HREF="auarf018.htm#IDX3911">(3911)</A>
-<LI>unmounting volume
-<A HREF="auarf156.htm#IDX4921">(4921)</A>
-<LI>up command
-<A HREF="auarf239.htm#IDX5493">(5493)</A>
-<LI>upclient command
-<A HREF="auarf240.htm#IDX5496">(5496)</A>
-<LI>upclient process
-<A HREF="auarf240.htm#IDX5497">(5497)</A>
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4497">(4497)</A>
-</MENU>
-<LI>update date
-<MENU>
-<LI>recorded in volume header
-<A HREF="auarf261.htm#IDX5681">(5681)</A>, <A HREF="auarf266.htm#IDX5757">(5757)</A>
-</MENU>
-<LI>Update Server
-<MENU>
-<LI>starting client portion
-<A HREF="auarf240.htm#IDX5499">(5499)</A>
-<LI>starting server portion
-<A HREF="auarf241.htm#IDX5505">(5505)</A>
-</MENU>
-<LI>updating
-<MENU>
-<LI>Cache Manager mapping of volume names to IDs
-<A HREF="auarf134.htm#IDX4740">(4740)</A>
-</MENU>
-<LI>upserver command
-<A HREF="auarf241.htm#IDX5502">(5502)</A>
-<LI>upserver process
-<A HREF="auarf241.htm#IDX5503">(5503)</A>
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4499">(4499)</A>
-</MENU>
-<LI>user
-<MENU>
-<LI>account (see entry: <I>user account</I>)
-<A HREF="auarf243.htm#IDX5519">(5519)</A>
-<LI>adding to group
-<A HREF="auarf211.htm#IDX5239">(5239)</A>
-<LI>AFS UID, setting
-<A HREF="auarf215.htm#IDX5281">(5281)</A>, <A HREF="auarf215.htm#IDX5287">(5287)</A>
-<LI>group memberships, displaying number
-<A HREF="auarf217.htm#IDX5336">(5336)</A>
-<LI>group-creation quota, setting in Protection Database
-<A HREF="auarf225.htm#IDX5405">(5405)</A>
-<LI>groups belonged to, displaying
-<A HREF="auarf222.htm#IDX5379">(5379)</A>
-<LI>groups owned, displaying
-<A HREF="auarf221.htm#IDX5372">(5372)</A>
-<LI>mapping name to AFS UID
-<A HREF="auarf217.htm#IDX5327">(5327)</A>
-<LI>name, assigning
-<A HREF="auarf215.htm#IDX5283">(5283)</A>
-<LI>name, assigning in uss
-<A HREF="auarf243.htm#IDX5529">(5529)</A>
-<LI>name, changing in Protection Database
-<A HREF="auarf224.htm#IDX5394">(5394)</A>
-<LI>name, rules for format
-<A HREF="auarf215.htm#IDX5282">(5282)</A>
-<LI>privacy flags on Protection Database entry, displaying
-<A HREF="auarf217.htm#IDX5339">(5339)</A>
-<LI>privacy flags on Protection Database entry, setting
-<A HREF="auarf225.htm#IDX5406">(5406)</A>
-<LI>Protection Database entries, display all
-<A HREF="auarf219.htm#IDX5358">(5358)</A>
-<LI>Protection Database entry, creating
-<A HREF="auarf215.htm#IDX5280">(5280)</A>
-<LI>Protection Database entry, deleting
-<A HREF="auarf216.htm#IDX5297">(5297)</A>
-<LI>removing from group
-<A HREF="auarf223.htm#IDX5386">(5386)</A>
-</MENU>
-<LI>user account
-<MENU>
-<LI>creating multiple
-<A HREF="auarf245.htm#IDX5542">(5542)</A>
-<LI>creating with uss
-<A HREF="auarf243.htm#IDX5521">(5521)</A>
-<LI>deleting with uss
-<A HREF="auarf246.htm#IDX5547">(5547)</A>
-</MENU>
-<LI>UserList file
-<A HREF="auarf035.htm#IDX3985">(3985)</A>
-<MENU>
-<LI>adding user with bos adduser command
-<A HREF="auarf096.htm#IDX4469">(4469)</A>
-<LI>displaying users with bos listusers command
-<A HREF="auarf108.htm#IDX4572">(4572)</A>
-<LI>removing user with bos removeuser command
-<A HREF="auarf112.htm#IDX4600">(4600)</A>
-</MENU>
-<LI>usr/afs/bin directory
-<MENU>
-<LI>checking time stamps on files
-<A HREF="auarf101.htm#IDX4525">(4525)</A>
-<LI>removing .BAK files
-<A HREF="auarf109.htm#IDX4585">(4585)</A>
-<LI>removing .OLD files
-<A HREF="auarf109.htm#IDX4586">(4586)</A>
-</MENU>
-<LI>usr/afs/logs directory
-<MENU>
-<LI>displaying log files
-<A HREF="auarf102.htm#IDX4534">(4534)</A>
-<LI>removing core files
-<A HREF="auarf109.htm#IDX4587">(4587)</A>
-</MENU>
-<LI>uss
-<MENU>
-<LI>bulk input file (see entry: <I>uss bulk input file</I>)
-<A HREF="auarf054.htm#IDX4099">(4099)</A>
-<LI>creating directory
-<A HREF="auarf055.htm#IDX4122">(4122)</A>
-<LI>creating directory for even distribution
-<A HREF="auarf055.htm#IDX4144">(4144)</A>
-<LI>creating file by echoing
-<A HREF="auarf055.htm#IDX4132">(4132)</A>
-<LI>creating file from prototype
-<A HREF="auarf055.htm#IDX4138">(4138)</A>
-<LI>creating hard link
-<A HREF="auarf055.htm#IDX4151">(4151)</A>
-<LI>creating symbolic link
-<A HREF="auarf055.htm#IDX4157">(4157)</A>
-<LI>creating volume
-<A HREF="auarf055.htm#IDX4163">(4163)</A>
-<LI>improving password/login security
-<A HREF="auarf055.htm#IDX4114">(4114)</A>
-<LI>mounting volume
-<A HREF="auarf055.htm#IDX4164">(4164)</A>
-<LI>overwriting behavior
-<A HREF="auarf243.htm#IDX5530">(5530)</A>
-<LI>running command
-<A HREF="auarf055.htm#IDX4182">(4182)</A>
-<LI>setting ACL
-<A HREF="auarf055.htm#IDX4130">(4130)</A>, <A HREF="auarf055.htm#IDX4166">(4166)</A>
-<LI>setting volume quota
-<A HREF="auarf055.htm#IDX4165">(4165)</A>
-<LI>template file (see entry: <I>uss template file</I>)
-<A HREF="auarf055.htm#IDX4110">(4110)</A>
-</MENU>
-<LI>uss bulk input file
-<A HREF="auarf054.htm#IDX4101">(4101)</A>
-<MENU>
-<LI>add instruction
-<A HREF="auarf054.htm#IDX4102">(4102)</A>
-<LI>delete instruction
-<A HREF="auarf054.htm#IDX4104">(4104)</A>
-<LI>delvolume instruction
-<A HREF="auarf054.htm#IDX4106">(4106)</A>
-<LI>savevolume instruction
-<A HREF="auarf054.htm#IDX4108">(4108)</A>
-</MENU>
-<LI>uss commands
-<MENU>
-<LI>add
-<A HREF="auarf243.htm#IDX5517">(5517)</A>
-<LI>apropos
-<A HREF="auarf244.htm#IDX5536">(5536)</A>
-<LI>bulk
-<A HREF="auarf245.htm#IDX5539">(5539)</A>
-<LI>common options
-<A HREF="auarf242.htm#IDX5509">(5509)</A>
-<LI>delete
-<A HREF="auarf246.htm#IDX5545">(5545)</A>
-<LI>help
-<A HREF="auarf247.htm#IDX5554">(5554)</A>
-<LI>privilege requirements
-<A HREF="auarf242.htm#IDX5516">(5516)</A>
-</MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4112">(4112)</A>
-<MENU>
-<LI>A instruction
-<A HREF="auarf055.htm#IDX4113">(4113)</A>, <A HREF="auarf055.htm#IDX4116">(4116)</A>
-<LI>creating directory
-<A HREF="auarf055.htm#IDX4123">(4123)</A>
-<LI>creating directory for even distribution
-<A HREF="auarf055.htm#IDX4148">(4148)</A>
-<LI>creating file
-<A HREF="auarf055.htm#IDX4136">(4136)</A>, <A HREF="auarf055.htm#IDX4142">(4142)</A>
-<LI>creating hard link
-<A HREF="auarf055.htm#IDX4155">(4155)</A>
-<LI>creating mount point
-<A HREF="auarf055.htm#IDX4174">(4174)</A>
-<LI>creating symbolic link
-<A HREF="auarf055.htm#IDX4161">(4161)</A>
-<LI>creating volume
-<A HREF="auarf055.htm#IDX4173">(4173)</A>
-<LI>D instruction
-<A HREF="auarf055.htm#IDX4124">(4124)</A>
-<LI>D line
-<A HREF="auarf055.htm#IDX4121">(4121)</A>
-<LI>E instruction
-<A HREF="auarf055.htm#IDX4135">(4135)</A>
-<LI>F instruction
-<A HREF="auarf055.htm#IDX4141">(4141)</A>
-<LI>G line
-<A HREF="auarf055.htm#IDX4147">(4147)</A>
-<LI>improving password/login security
-<A HREF="auarf055.htm#IDX4115">(4115)</A>
-<LI>L instruction
-<A HREF="auarf055.htm#IDX4154">(4154)</A>
-<LI>S instruction
-<A HREF="auarf055.htm#IDX4160">(4160)</A>
-<LI>setting ACL
-<A HREF="auarf055.htm#IDX4129">(4129)</A>, <A HREF="auarf055.htm#IDX4176">(4176)</A>
-<LI>setting volume quota
-<A HREF="auarf055.htm#IDX4175">(4175)</A>
-<LI>V instruction
-<A HREF="auarf055.htm#IDX4172">(4172)</A>
-<LI>X instruction
-<A HREF="auarf055.htm#IDX4183">(4183)</A>
-<LI>zero length
-<A HREF="auarf055.htm#IDX4178">(4178)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_56" HREF="#IDX0_56">V</A></STRONG>
-<MENU>
-<LI>V instruction
-<MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4162">(4162)</A>
-</MENU>
-<LI>V<I>n</I> file
-<A HREF="auarf036.htm#IDX3987">(3987)</A>
-<LI>V<I>vol_ID</I>.vol file
-<A HREF="auarf037.htm#IDX3990">(3990)</A>
-<LI>variables
-<MENU>
-<LI>@sys in pathnames
-<A HREF="auarf165.htm#IDX5000">(5000)</A>, <A HREF="auarf234.htm#IDX5474">(5474)</A>
-</MENU>
-<LI>verbose flag
-<MENU>
-<LI>on vos commands
-<A HREF="auarf252.htm#IDX5584">(5584)</A>
-</MENU>
-<LI>VL Database
-<MENU>
-<LI>status, verifying
-<A HREF="auarf248.htm#IDX5559">(5559)</A>
-</MENU>
-<LI>VL Server
-<A HREF="auarf252.htm#IDX5571">(5571)</A>
-<MENU>
-<LI>displaying Cache Manager preference ranks
-<A HREF="auarf146.htm#IDX4849">(4849)</A>
-<LI>listed in client CellServDB file
-<A HREF="auarf019.htm#IDX3916">(3916)</A>
-<LI>listed in server CellServDB file
-<A HREF="auarf020.htm#IDX3924">(3924)</A>
-<LI>setting Cache Manager preference ranks
-<A HREF="auarf162.htm#IDX4975">(4975)</A>
-<LI>starting
-<A HREF="auarf249.htm#IDX5562">(5562)</A>
-</MENU>
-<LI>VLDB
-<MENU>
-<LI>deleting entry (but not volume header)
-<A HREF="auarf259.htm#IDX5640">(5640)</A>
-<LI>displaying file server machine interfaces
-<A HREF="auarf263.htm#IDX5702">(5702)</A>
-<LI>displaying volume entry and volume header
-<A HREF="auarf261.htm#IDX5657">(5657)</A>
-<LI>examining volume entry
-<A HREF="auarf265.htm#IDX5712">(5712)</A>
-<LI>files constituting
-<A HREF="auarf051.htm#IDX4034">(4034)</A>
-<LI>read-only site for volume, defining
-<A HREF="auarf253.htm#IDX5592">(5592)</A>
-<LI>read-only site for volume, removing mistakenly defined
-<A HREF="auarf272.htm#IDX5818">(5818)</A>
-<LI>release status flags in volume entry
-<A HREF="auarf261.htm#IDX5690">(5690)</A>, <A HREF="auarf265.htm#IDX5724">(5724)</A>
-<LI>server machine interfaces not registered
-<MENU>
-<LI>setting in NetRestrict file
-<A HREF="auarf027.htm#IDX3962">(3962)</A>
-</MENU>
-<LI>server machine interfaces registered
-<MENU>
-<LI>listed in sysid file
-<A HREF="auarf049.htm#IDX4026">(4026)</A>
-<LI>setting in NetInfo file
-<A HREF="auarf025.htm#IDX3951">(3951)</A>
-</MENU>
-<LI>site count for volume
-<A HREF="auarf261.htm#IDX5686">(5686)</A>, <A HREF="auarf265.htm#IDX5720">(5720)</A>
-<LI>synchronizing with volume headers
-<A HREF="auarf276.htm#IDX5844">(5844)</A>, <A HREF="auarf277.htm#IDX5853">(5853)</A>
-<LI>volume entry, creating
-<A HREF="auarf258.htm#IDX5631">(5631)</A>
-<LI>volume entry, locking
-<A HREF="auarf267.htm#IDX5764">(5764)</A>
-<LI>volume entry, unlocking
-<A HREF="auarf278.htm#IDX5858">(5858)</A>
-<LI>volume entry, unlocking multiple
-<A HREF="auarf279.htm#IDX5862">(5862)</A>
-<LI>volume type flags
-<A HREF="auarf261.htm#IDX5688">(5688)</A>, <A HREF="auarf265.htm#IDX5722">(5722)</A>
-</MENU>
-<LI>vldb.DB0 file
-<A HREF="auarf051.htm#IDX4030">(4030)</A>
-<LI>vldb.DBSYS1 file
-<A HREF="auarf051.htm#IDX4032">(4032)</A>
-<LI>vldb_check command
-<A HREF="auarf248.htm#IDX5557">(5557)</A>
-<LI>VLLog file
-<A HREF="auarf038.htm#IDX3994">(3994)</A>
-<LI>vlserver command
-<A HREF="auarf249.htm#IDX5560">(5560)</A>
-<LI>vlserver process
-<MENU>
-<LI>creating with bos create command
-<A HREF="auarf098.htm#IDX4501">(4501)</A>
-</MENU>
-<LI>volinfo command
-<A HREF="auarf250.htm#IDX5564">(5564)</A>
-<LI>VolserLog file
-<A HREF="auarf039.htm#IDX3997">(3997)</A>
-<LI>volserver command
-<A HREF="auarf251.htm#IDX5566">(5566)</A>
-<LI>volserver process
-<MENU>
-<LI>part of fs entry in BosConfig file
-<A HREF="auarf016.htm#IDX3889">(3889)</A>
-</MENU>
-<LI>volume
-<MENU>
-<LI>backup (see entry: backup volume)
-<A HREF="auarf255.htm#IDX5601">(5601)</A>
-<LI>Cache Manager
-<A HREF="auarf134.htm#IDX4738">(4738)</A>
-<LI>counter in header for number of accesses
-<A HREF="auarf261.htm#IDX5684">(5684)</A>, <A HREF="auarf266.htm#IDX5760">(5760)</A>
-<LI>creating
-<A HREF="auarf258.htm#IDX5619">(5619)</A>
-<LI>creating mount point
-<A HREF="auarf153.htm#IDX4895">(4895)</A>
-<LI>creating with uss
-<A HREF="auarf055.htm#IDX4169">(4169)</A>, <A HREF="auarf243.htm#IDX5525">(5525)</A>
-<LI>Creation date in volume header
-<A HREF="auarf261.htm#IDX5680">(5680)</A>, <A HREF="auarf266.htm#IDX5756">(5756)</A>
-<LI>deleting with uss
-<A HREF="auarf246.htm#IDX5553">(5553)</A>
-<LI>displaying mount point
-<A HREF="auarf151.htm#IDX4886">(4886)</A>
-<LI>dump history, displaying
-<A HREF="auarf090.htm#IDX4419">(4419)</A>
-<LI>dumping using Backup System
-<A HREF="auarf073.htm#IDX4305">(4305)</A>
-<LI>dumping with vos dump command
-<A HREF="auarf260.htm#IDX5645">(5645)</A>
-<LI>flushing from data cache
-<A HREF="auarf142.htm#IDX4822">(4822)</A>
-<LI>header, displaying
-<A HREF="auarf266.htm#IDX5732">(5732)</A>, <A HREF="auarf266.htm#IDX5733">(5733)</A>
-<LI>header, displaying with VLDB entry
-<A HREF="auarf261.htm#IDX5659">(5659)</A>
-<LI>header, synchronizing with VLDB entry
-<A HREF="auarf276.htm#IDX5840">(5840)</A>, <A HREF="auarf277.htm#IDX5849">(5849)</A>
-<LI>host partition size, listing
-<A HREF="auarf138.htm#IDX4772">(4772)</A>
-<LI>ID number (see entry: <I>volume ber</I>)
-<A HREF="auarf258.htm#IDX5633">(5633)</A>
-<LI>ID number from name, translating
-<A HREF="auarf261.htm#IDX5663">(5663)</A>
-<LI>ID number, allocating
-<A HREF="auarf258.htm#IDX5620">(5620)</A>
-<LI>ID number, learning from volume location
-<A HREF="auarf266.htm#IDX5739">(5739)</A>
-<LI>ID number, translating to location
-<A HREF="auarf265.htm#IDX5716">(5716)</A>
-<LI>Last Update date in volume header
-<A HREF="auarf261.htm#IDX5682">(5682)</A>, <A HREF="auarf266.htm#IDX5758">(5758)</A>
-<LI>location, translating from name/ID number
-<A HREF="auarf265.htm#IDX5717">(5717)</A>
-<LI>location, translating to volume ID number
-<A HREF="auarf266.htm#IDX5738">(5738)</A>
-<LI>message associated with, creating
-<A HREF="auarf163.htm#IDX4980">(4980)</A>
-<LI>messages associated with, examining
-<A HREF="auarf138.htm#IDX4791">(4791)</A>
-<LI>moving
-<A HREF="auarf268.htm#IDX5769">(5769)</A>
-<LI>name to ID number, translating
-<A HREF="auarf261.htm#IDX5662">(5662)</A>
-<LI>name, assigning
-<A HREF="auarf258.htm#IDX5618">(5618)</A>
-<LI>name, changing
-<A HREF="auarf273.htm#IDX5823">(5823)</A>
-<LI>name, learning given directory/file name
-<A HREF="auarf138.htm#IDX4785">(4785)</A>
-<LI>name, translating to location
-<A HREF="auarf265.htm#IDX5715">(5715)</A>
-<LI>partition percent use, listing
-<A HREF="auarf150.htm#IDX4871">(4871)</A>
-<LI>percent use, listing
-<A HREF="auarf150.htm#IDX4873">(4873)</A>
-<LI>quota (see entry: <I>volume quota</I>)
-<A HREF="auarf258.htm#IDX5622">(5622)</A>
-<LI>read-only (see entry: read-only volume)
-<A HREF="auarf270.htm#IDX5787">(5787)</A>
-<LI>read-only site, removing mistakenly defined
-<A HREF="auarf272.htm#IDX5816">(5816)</A>
-<LI>read/write (see entry: <I>read/write volume</I>)
-<A HREF="auarf258.htm#IDX5621">(5621)</A>
-<LI>removing
-<A HREF="auarf271.htm#IDX5807">(5807)</A>
-<LI>removing mount point for
-<A HREF="auarf156.htm#IDX4920">(4920)</A>
-<LI>removing without changing VLDB
-<A HREF="auarf280.htm#IDX5866">(5866)</A>
-<LI>renaming
-<A HREF="auarf273.htm#IDX5822">(5822)</A>
-<LI>replicating
-<A HREF="auarf270.htm#IDX5786">(5786)</A>
-<LI>restoring all in volume set with Backup System
-<A HREF="auarf092.htm#IDX4430">(4430)</A>
-<LI>restoring single with Backup System
-<A HREF="auarf091.htm#IDX4424">(4424)</A>
-<LI>restoring with vos command
-<A HREF="auarf274.htm#IDX5831">(5831)</A>
-<LI>salvaging
-<A HREF="auarf114.htm#IDX4609">(4609)</A>
-<LI>size, listing
-<A HREF="auarf138.htm#IDX4773">(4773)</A>, <A HREF="auarf150.htm#IDX4872">(4872)</A>
-<LI>VLDB entry, displaying
-<A HREF="auarf265.htm#IDX5718">(5718)</A>
-<LI>VLDB entry, displaying with header
-<A HREF="auarf261.htm#IDX5660">(5660)</A>
-<LI>VLDB entry, locking
-<A HREF="auarf267.htm#IDX5765">(5765)</A>
-<LI>VLDB entry, synchronizing with header
-<A HREF="auarf276.htm#IDX5841">(5841)</A>, <A HREF="auarf277.htm#IDX5850">(5850)</A>
-<LI>volume ID number (see entry: <I>volume ber</I>)
-<A HREF="auarf258.htm#IDX5634">(5634)</A>
-</MENU>
-<LI>volume entry (Backup System)
-<MENU>
-<LI>adding to volume set
-<A HREF="auarf063.htm#IDX4241">(4241)</A>, <A HREF="auarf063.htm#IDX4248">(4248)</A>
-<LI>displaying from volume set
-<A HREF="auarf082.htm#IDX4377">(4377)</A>
-<LI>removing from volume set
-<A HREF="auarf070.htm#IDX4287">(4287)</A>
-</MENU>
-<LI>volume header
-<MENU>
-<LI>see entry: <I>Vvol_ID.vol file</I>
-<A HREF="auarf037.htm#IDX3993">(3993)</A>
-</MENU>
-<LI>volume ID number
-<MENU>
-<LI>Cache Manager
-<A HREF="auarf134.htm#IDX4744">(4744)</A>
-<LI>defined
-<A HREF="auarf258.htm#IDX5632">(5632)</A>
-<LI>learning given directory/file name
-<A HREF="auarf138.htm#IDX4789">(4789)</A>
-</MENU>
-<LI>volume location
-<MENU>
-<LI>learning given directory/file name
-<A HREF="auarf166.htm#IDX5001">(5001)</A>
-</MENU>
-<LI>Volume Location Database
-<MENU>
-<LI>see entry: <I>VLDB</I>
-<A HREF="auarf051.htm#IDX4035">(4035)</A>
-</MENU>
-<LI>Volume Location Server
-<MENU>
-<LI>log file
-<A HREF="auarf038.htm#IDX3996">(3996)</A>
-<LI>see entry: <I>VL Server</I>
-<A HREF="auarf249.htm#IDX5563">(5563)</A>
-</MENU>
-<LI>volume name
-<MENU>
-<LI>Cache Manager
-<A HREF="auarf134.htm#IDX4742">(4742)</A>
-<LI>Cache Manager forced to see change to
-<A HREF="auarf134.htm#IDX4743">(4743)</A>
-<LI>learning given directory/file name
-<A HREF="auarf137.htm#IDX4768">(4768)</A>, <A HREF="auarf150.htm#IDX4881">(4881)</A>
-</MENU>
-<LI>volume quota
-<MENU>
-<LI>allowing users to exceed
-<A HREF="auarf129.htm#IDX4704">(4704)</A>
-<LI>displaying percent used
-<A HREF="auarf155.htm#IDX4915">(4915)</A>
-<LI>displaying with volume & partition info.
-<A HREF="auarf138.htm#IDX4790">(4790)</A>
-<LI>displaying with volume size
-<A HREF="auarf150.htm#IDX4883">(4883)</A>
-<LI>recorded in volume header
-<A HREF="auarf261.htm#IDX5677">(5677)</A>, <A HREF="auarf266.htm#IDX5753">(5753)</A>
-<LI>setting
-<A HREF="auarf161.htm#IDX4968">(4968)</A>, <A HREF="auarf163.htm#IDX4979">(4979)</A>
-<LI>setting default for new volume
-<A HREF="auarf258.htm#IDX5626">(5626)</A>
-<LI>setting with uss
-<A HREF="auarf055.htm#IDX4171">(4171)</A>
-</MENU>
-<LI>Volume Server
-<A HREF="auarf252.htm#IDX5570">(5570)</A>
-<MENU>
-<LI>log file
-<A HREF="auarf039.htm#IDX3999">(3999)</A>
-<LI>starting
-<A HREF="auarf251.htm#IDX5568">(5568)</A>
-<LI>status, displaying
-<A HREF="auarf275.htm#IDX5837">(5837)</A>
-</MENU>
-<LI>volume set (Backup System)
-<MENU>
-<LI>creating
-<A HREF="auarf064.htm#IDX4257">(4257)</A>
-<LI>deleting
-<A HREF="auarf071.htm#IDX4293">(4293)</A>
-<LI>displaying
-<A HREF="auarf082.htm#IDX4376">(4376)</A>
-<LI>restoring
-<A HREF="auarf092.htm#IDX4432">(4432)</A>
-<LI>volume entry, adding
-<A HREF="auarf063.htm#IDX4242">(4242)</A>, <A HREF="auarf063.htm#IDX4249">(4249)</A>
-<LI>volume entry, removing
-<A HREF="auarf070.htm#IDX4288">(4288)</A>
-</MENU>
-<LI>VolumeItems file
-<A HREF="auarf040.htm#IDX4000">(4000)</A>
-<LI>vos commands
-<MENU>
-<LI>addsite
-<A HREF="auarf253.htm#IDX5587">(5587)</A>
-<LI>apropos
-<A HREF="auarf254.htm#IDX5593">(5593)</A>
-<LI>backup
-<A HREF="auarf255.htm#IDX5596">(5596)</A>
-<LI>backupsys
-<A HREF="auarf256.htm#IDX5605">(5605)</A>
-<LI>changeaddr
-<A HREF="auarf257.htm#IDX5612">(5612)</A>
-<LI>common options
-<A HREF="auarf252.htm#IDX5577">(5577)</A>
-<LI>create
-<A HREF="auarf258.htm#IDX5614">(5614)</A>
-<LI>delentry
-<A HREF="auarf259.htm#IDX5638">(5638)</A>
-<LI>dump
-<A HREF="auarf260.htm#IDX5642">(5642)</A>
-<LI>examine
-<A HREF="auarf261.htm#IDX5653">(5653)</A>
-<LI>help
-<A HREF="auarf262.htm#IDX5695">(5695)</A>
-<LI>idempotency
-<A HREF="auarf252.htm#IDX5573">(5573)</A>
-<LI>listaddrs
-<A HREF="auarf263.htm#IDX5698">(5698)</A>
-<LI>listpart
-<A HREF="auarf264.htm#IDX5703">(5703)</A>
-<LI>listvldb
-<A HREF="auarf265.htm#IDX5708">(5708)</A>
-<LI>listvol
-<A HREF="auarf266.htm#IDX5729">(5729)</A>
-<LI>lock
-<A HREF="auarf267.htm#IDX5761">(5761)</A>
-<LI>move
-<A HREF="auarf268.htm#IDX5766">(5766)</A>
-<LI>partinfo
-<A HREF="auarf269.htm#IDX5775">(5775)</A>
-<LI>privilege requirements
-<A HREF="auarf252.htm#IDX5586">(5586)</A>
-<LI>release
-<A HREF="auarf270.htm#IDX5782">(5782)</A>
-<LI>remove
-<A HREF="auarf271.htm#IDX5805">(5805)</A>
-<LI>remsite
-<A HREF="auarf272.htm#IDX5813">(5813)</A>
-<LI>rename
-<A HREF="auarf273.htm#IDX5819">(5819)</A>
-<LI>restore
-<A HREF="auarf274.htm#IDX5829">(5829)</A>
-<LI>status
-<A HREF="auarf275.htm#IDX5833">(5833)</A>
-<LI>syncserv
-<A HREF="auarf276.htm#IDX5838">(5838)</A>
-<LI>syncvldb
-<A HREF="auarf277.htm#IDX5846">(5846)</A>
-<LI>unlock
-<A HREF="auarf278.htm#IDX5855">(5855)</A>
-<LI>unlockvldb
-<A HREF="auarf279.htm#IDX5859">(5859)</A>
-<LI>volinfo (see entry: <I>vos examine</I>)
-<A HREF="auarf261.htm#IDX5654">(5654)</A>
-<LI>zap
-<A HREF="auarf280.htm#IDX5863">(5863)</A>
-</MENU>
-</MENU>
-<STRONG><A NAME="IDX1_57" HREF="#IDX0_57">W</A></STRONG>
-<MENU>
-<LI>weekly restart time for BOS Server
-<MENU>
-<LI>see entry: <I>restart times for BOS Server</I>
-<A HREF="auarf103.htm#IDX4539">(4539)</A>
-</MENU>
-<LI>wildcard
-<MENU>
-<LI>volume entry definition (Backup System)
-<A HREF="auarf063.htm#IDX4244">(4244)</A>, <A HREF="auarf063.htm#IDX4251">(4251)</A>
-</MENU>
-<LI>workstations statistic in scout
-<A HREF="auarf233.htm#IDX5464">(5464)</A>
-<LI>write shorthand notation for ACL permissions
-<A HREF="auarf157.htm#IDX4945">(4945)</A>
-</MENU>
-<STRONG><A NAME="IDX1_58" HREF="#IDX0_58">X</A></STRONG>
-<MENU>
-<LI>X instruction
-<MENU>
-<LI>uss template file
-<A HREF="auarf055.htm#IDX4181">(4181)</A>
-</MENU>
-<LI>xfs_size_check command
-<A HREF="auarf281.htm#IDX5867">(5867)</A>
-<LI>xstat as requirement for running afsmonitor
-<A HREF="auarf059.htm#IDX4199">(4199)</A>
-<LI>xstat_cm_test command
-<A HREF="auarf282.htm#IDX5869">(5869)</A>
-<LI>xstat_fs_test command
-<A HREF="auarf283.htm#IDX5871">(5871)</A>
-</MENU>
-<HR><P ALIGN="center"> <A HREF="../index.htm"><IMG SRC="../books.gif" BORDER="0" ALT="[Return to Library]"></A> <A HREF="auarf002.htm#ToC"><IMG SRC="../toc.gif" BORDER="0" ALT="[Contents]"></A> <A HREF="auarf283.htm"><IMG SRC="../prev.gif" BORDER="0" ALT="[Previous Topic]"></A> <A HREF="#Top_Of_Page"><IMG SRC="../top.gif" BORDER="0" ALT="[Top of Topic]"></A> <P>
-<!-- Begin Footer Records ========================================== -->
-<P><HR><B>
-<br>© <A HREF="http://www.ibm.com/">IBM Corporation 2000.</A> All Rights Reserved
-</B>
-<!-- End Footer Records ============================================ -->
-<A NAME="Bot_Of_Page"></A>
-</BODY></HTML>
<P>Included:
<DL COMPACT>
<DD><A HREF="AdminGuide/auagd000.htm">AFS Administrator's Guide</A>
-<DD><A HREF="AdminReference/auarf000.htm">AFS Administration Reference</A>
<DD><A HREF="QuickStartUnix/auqbg000.htm">AFS Quick Start Guide for UNIX</A>
<DD><A HREF="QuickStartWindows/awqbg000.htm">AFS Quick Start Guide for Windows NT/2000</A>
<DD><A HREF="UserGuide/auusg000.htm">AFS User's Guide</A>
projects / packages / o / openafs.git / commitdiff