1 This is a work-in-progress. My plan is to wikify the existing text, make any updates/corections/additions I can, and then announce the updated FAQ's exisatance to openafs-info. I have tried to contact the current maintainer, but recieved no response - but the last updated date being what it is, perhaps he has a new email.
5 - Formatting Pass 1: Complete
6 - Update Pass: see below
7 - Editing Pass: Not Started
8 - Formatting Pass 2: Not Started
10 -- [[DanielClark]] - 21 Jan 2002
14 - Enlivened Arla links. Fixed a few heading markers. Corrected Transarc address and phone numbers. Improved references to paths in the transarc.com cell. Added MANIFEST for many ftp links because anonymous can't use the "LIST" command. -- [[TedAnderson]] - 29 Jan 2002
18 Archive-name: afs-faq Version: 1.113 Last-modified: 1950 Thursday 9th July 1998
20 # <a name="AFS frequently asked questions"></a> AFS frequently asked questions
24 This posting contains answers to frequently asked questions about AFS. Your comments and contributions are welcome (email: <mpb@acm.org>)
26 Most newsreaders can skip from topic to topic with control-G.
30 <dd><a href="file:///afs/transarc.com/public/afs-contrib/doc/faq/afs-faq.html" target="_top">file:///afs/transarc.com/public/afs-contrib/doc/faq/afs-faq.html</a> <a href="ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/afs-faq.html" target="_top">ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/afs-faq.html</a> <a href="http://www.angelfire.com/hi/plutonic/afs-faq.html" target="_top">http://www.angelfire.com/hi/plutonic/afs-faq.html</a></dd>
37 <li><a href="#AFS frequently asked questions"> AFS frequently asked questions</a><ul>
38 <li><a href="#0 Preamble"> 0 Preamble</a><ul>
39 <li><a href="#0.01 Purpose and audience"> 0.01 Purpose and audience</a></li>
40 <li><a href="#0.02 Acknowledgements"> 0.02 Acknowledgements</a></li>
41 <li><a href="#0.03 Disclaimer"> 0.03 Disclaimer</a></li>
42 <li><a href="#0.04 Release Notes"> 0.04 Release Notes</a></li>
43 <li><a href="#0.05 Quote"> 0.05 Quote</a></li>
46 <li><a href="#1 General"> 1 General</a><ul>
47 <li><a href="#1.01 What is AFS?"> 1.01 What is AFS?</a></li>
48 <li><a href="#1.02 Who supplies AFS?"> 1.02 Who supplies AFS?</a></li>
49 <li><a href="#1.03 What is /afs?"> 1.03 What is /afs?</a></li>
50 <li><a href="#1.04 What is an AFS cell?"> 1.04 What is an AFS cell?</a></li>
51 <li><a href="#1.05 What are the benefits of u"> 1.05 What are the benefits of using AFS?</a><ul>
52 <li><a href="#1.05.a Cache Manager"> 1.05.a Cache Manager</a></li>
53 <li><a href="#1.05.b Location independence"> 1.05.b Location independence</a></li>
54 <li><a href="#1.05.c Scalability"> 1.05.c Scalability</a></li>
55 <li><a href="#1.05.d Improved security"> 1.05.d Improved security</a></li>
56 <li><a href="#1.05.e Single systems image (SS"> 1.05.e Single systems image (SSI)</a></li>
57 <li><a href="#1.05.f Replicated AFS volumes"> 1.05.f Replicated AFS volumes</a></li>
58 <li><a href="#1.05.g Improved robustness to s"> 1.05.g Improved robustness to server crash</a></li>
59 <li><a href="#1.05.h "Easy to use" networking"> 1.05.h "Easy to use" networking</a></li>
60 <li><a href="#1.05.i Communications protocol"> 1.05.i Communications protocol</a></li>
61 <li><a href="#1.05.j Improved system manageme"> 1.05.j Improved system management capability</a></li>
64 <li><a href="#1.06 Which systems is AFS avail"> 1.06 Which systems is AFS available for?</a></li>
65 <li><a href="#1.07 What does "ls /afs" displa"> 1.07 What does "ls /afs" display in the Internet AFS filetree?</a></li>
66 <li><a href="#1.08 Why does AFS use Kerberos"> 1.08 Why does AFS use Kerberos authentication?</a></li>
67 <li><a href="#1.09 Does AFS work over protoco"> 1.09 Does AFS work over protocols other than TCP/IP?</a></li>
68 <li><a href="#1.10 How can I access AFS from"> 1.10 How can I access AFS from my PC?</a></li>
69 <li><a href="#1.11 How does AFS compare with"> 1.11 How does AFS compare with NFS?</a></li>
72 <li><a href="#2 Using AFS"> 2 Using AFS</a><ul>
73 <li><a href="#2.01 What are the differences b"> 2.01 What are the differences between AFS and a unix filesystem?</a></li>
74 <li><a href="#2.02 What is an AFS protection"> 2.02 What is an AFS protection group?</a></li>
75 <li><a href="#2.03 What are the AFS defined p"> 2.03 What are the AFS defined protection groups?</a></li>
76 <li><a href="#2.04 What is an AFS access cont"> 2.04 What is an AFS access control list (ACL)?</a></li>
77 <li><a href="#2.05 What are the AFS access ri"> 2.05 What are the AFS access rights?</a></li>
78 <li><a href="#2.06 What is pagsh?"> 2.06 What is pagsh?</a></li>
79 <li><a href="#2.07 Why use a PAG?"> 2.07 Why use a PAG?</a></li>
80 <li><a href="#2.08 How can I tell if I have a"> 2.08 How can I tell if I have a PAG?</a></li>
81 <li><a href="#2.09 Can I still run cron jobs"> 2.09 Can I still run cron jobs with AFS?</a></li>
82 <li><a href="#2.10 How much disk space does a"> 2.10 How much disk space does a 1 byte file occupy in AFS?</a></li>
83 <li><a href="#2.11 Is it possible to specify"> 2.11 Is it possible to specify a user who is external to the current AFS cell on an ACL?</a></li>
84 <li><a href="#2.12 Are there any problems pri"> 2.12 Are there any problems printing files in /afs?</a></li>
85 <li><a href="#2.13 Can I create a fifo (aka n"> 2.13 Can I create a fifo (aka named pipe) in /afs?</a></li>
86 <li><a href="#2.14 If an AFS server crashes,"> 2.14 If an AFS server crashes, do I have to reboot my AFS client?</a></li>
87 <li><a href="#2.15 Can I use AFS on my diskle"> 2.15 Can I use AFS on my diskless workstation?</a></li>
88 <li><a href="#2.16 Can I test for AFS tokens"> 2.16 Can I test for AFS tokens from within my program?</a></li>
89 <li><a href="#2.17 What's the difference betw"> 2.17 What's the difference between /afs/cellname and /afs/.cellname?</a></li>
90 <li><a href="#2.18 Can I klog as two users on"> 2.18 Can I klog as two users on a machine in the same cell?</a></li>
91 <li><a href="#2.19 What are the ~/._afsXXXX f"> 2.19 What are the ~/.__afsXXXX files?</a></li>
94 <li><a href="#3 AFS administration"> 3 AFS administration</a><ul>
95 <li><a href="#3.01 Is there a version of xdm"> 3.01 Is there a version of xdm available with AFS authentication?</a></li>
96 <li><a href="#3.02 Is there a version of xloc"> 3.02 Is there a version of xlock available with AFS authentication?</a></li>
97 <li><a href="#3.03 What is /afs/@cell?"> 3.03 What is /afs/@cell?</a></li>
98 <li><a href="#3.04 Given that AFS data is loc"> 3.04 Given that AFS data is location independent, how does an AFS client determine which server houses the data its user is attempting to access?</a></li>
99 <li><a href="#3.05 Which protocols does AFS u"> 3.05 Which protocols does AFS use?</a></li>
100 <li><a href="#3.06 Are setuid programs execut"> 3.06 Are setuid programs executable across AFS cell boundaries?</a></li>
101 <li><a href="#3.07 How does AFS maintain cons"> 3.07 How does AFS maintain consistency on read-write files?</a></li>
102 <li><a href="#3.08 How can I run daemons with"> 3.08 How can I run daemons with tokens that do not expire?</a></li>
103 <li><a href="#3.09 Can I check my user's pass"> 3.09 Can I check my user's passwords for security purposes?</a></li>
104 <li><a href="#3.10 Is there a way to automati"> 3.10 Is there a way to automatically balance disk usage across fileservers?</a></li>
105 <li><a href="#3.11 Can I shutdown an AFS file"> 3.11 Can I shutdown an AFS fileserver without affecting users?</a></li>
106 <li><a href="#3.12 How can I set up mail deli"> 3.12 How can I set up mail delivery to users with $HOMEs in AFS?</a></li>
107 <li><a href="#3.13 Should I replicate a _Read"> 3.13 Should I replicate a ReadOnly volume on the same partition and server as the ReadWrite volume?</a></li>
108 <li><a href="#3.14 Should I start AFS before"> 3.14 Should I start AFS before NFS in /etc/inittab?</a></li>
109 <li><a href="#3.15 Will AFS run on a multi-ho"> 3.15 Will AFS run on a multi-homed fileserver?</a></li>
110 <li><a href="#3.16 Can I replicate my user's"> 3.16 Can I replicate my user's home directory AFS volumes?</a></li>
111 <li><a href="#3.17 Which TCP/IP ports and pro"> 3.17 Which TCP/IP ports and protocols do I need to enable in order to operate AFS through my Internet firewall?</a></li>
112 <li><a href="#3.18 What is the Andrew Benchma"> 3.18 What is the Andrew Benchmark?</a></li>
113 <li><a href="#3.19 Is there a version of HP V"> 3.19 Is there a version of HP VUE login with AFS authentication?</a></li>
114 <li><a href="#3.20 How can I list which clien"> 3.20 How can I list which clients have cached files from a server?</a></li>
115 <li><a href="#3.21 Do Backup volumes require"> 3.21 Do Backup volumes require as much space as ReadWrite volumes?</a></li>
116 <li><a href="#3.22 Should I run timed on my A"> 3.22 Should I run timed on my AFS client?</a></li>
117 <li><a href="#3.23 Why should I keep /usr/vic"> 3.23 Why should I keep /usr/vice/etc/CellServDB current?</a></li>
118 <li><a href="#3.24 How can I keep /usr/vice/e"> 3.24 How can I keep /usr/vice/etc/CellServDB current?</a></li>
119 <li><a href="#3.25 How can I compute a list o"> 3.25 How can I compute a list of AFS fileservers?</a></li>
120 <li><a href="#3.26 How can I set up anonymous"> 3.26 How can I set up anonymous FTP login to access /afs?</a></li>
121 <li><a href="#3.27 Where can I find the Andre"> 3.27 Where can I find the Andrew Benchmark?</a></li>
124 <li><a href="#4 Getting more information"> 4 Getting more information</a><ul>
125 <li><a href="#4.01 Is there an anonymous FTP"> 4.01 Is there an anonymous FTP site with AFS information?</a></li>
126 <li><a href="#4.02 Which USENET newsgroups di"> 4.02 Which USENET newsgroups discuss AFS?</a></li>
127 <li><a href="#4.03 Where can I get training i"> 4.03 Where can I get training in AFS?</a></li>
128 <li><a href="#4.04 Where can I find AFS resou"> 4.04 Where can I find AFS resources in World Wide Web (WWW)?</a></li>
129 <li><a href="#4.05 Is there a mailing list fo"> 4.05 Is there a mailing list for AFS topics?</a></li>
130 <li><a href="#4.06 Where can I find an archiv"> 4.06 Where can I find an archive of <a href="mailto:info-afs@transarc.com">info-afs@transarc.com</a>?</a></li>
131 <li><a href="#4.07 Where can I find an archiv"> 4.07 Where can I find an archive of alt.filesystems.afs?</a></li>
132 <li><a href="#4.08 Where can I find AFS relat"> 4.08 Where can I find AFS related GIFs?</a></li>
133 <li><a href="#4.09 Gibt es eine deutsche AFS"> 4.09 Gibt es eine deutsche AFS Benutzer Gruppe?</a></li>
134 <li><a href="#4.10 Donde puedo encontrar info"> 4.10 Donde puedo encontrar informacion en Espanol sobre AFS?</a></li>
137 <li><a href="#5 About the AFS faq"> 5 About the AFS faq</a><ul>
138 <li><a href="#5.01 How can I get a copy of th"> 5.01 How can I get a copy of the AFS faq?</a></li>
139 <li><a href="#5.02 How can I get my question"> 5.02 How can I get my question (and answer) into the AFS faq?</a></li>
140 <li><a href="#5.03 How can I access the AFS f"> 5.03 How can I access the AFS faq via the World Wide Web?</a></li>
143 <li><a href="#6 Bibliography"> 6 Bibliography</a></li>
151 ## <a name="0 Preamble"></a> 0 Preamble
153 ### <a name="0.01 Purpose and audience"></a> 0.01 Purpose and audience
155 The aim of this compilation is to provide information about AFS including:
157 - A brief introduction
158 - Answers to some often asked questions
159 - Pointers to further information
161 Definitive and detailed information on AFS is provided in Transarc's AFS manuals ([23], [24], [25]).
163 The intended audience ranges from people who know little of the subject and want to know more to those who have experience with AFS and wish to share useful information by contributing to the faq.
165 ### <a name="0.02 Acknowledgements"></a> 0.02 Acknowledgements
167 The information presented here has been gleaned from many sources. Some material has been directly contributed by people listed below.
169 - I would like to thank the following for contributing:
170 - Pierette Maniago VanRyzin (Transarc)
171 - Lyle Seaman (Transarc)
172 - Joseph Jackson (Transarc)
173 - Dan Lovinger (Microsoft)
174 - Lucien Van Elsen (IBM)
175 - Jim Rees (University of Michigan)
176 - Derrick J. Brashear (Carnegie Mellon University)
177 - Hans-Werner Paulsen (MPI fuer Astrophysik, Garching)
178 - Margo Hikida (Hewlett Packard)
179 - Michael Fagan (IBM)
180 - Robert Malick (National Institute of Health, USA)
181 - Rainer Toebbicke (European Laboratory for Particle Physics, CERN)
182 - Mic Bowman (Transarc)
184 - Bob Oesterlin (IBM)
185 - Pat Wilson (Dartmouth College)
186 - Cristian Espinoza (Pontificia Universidad Catolica de Chile)
187 - Mary Ann DelBusso (Transarc)
188 - Michael Niksch (IBM)
189 - Kelly Chambers (Transarc)
191 - Thanks also to indirect contributors:
195 - Dawn E. Johnson (Transarc)
196 - David Snearline (University of Michigan Engineering)
197 - Rens Troost (New Century Systems)
198 - Anton Knaus (Carnegie Mellon University)
199 - Mike Shaddock (SAS Institute Inc.)
201 If this compilation has any merit then much credit belongs to Pierette for giving inspiration, support, answers, and proof-reading.
203 ### <a name="0.03 Disclaimer"></a> 0.03 Disclaimer
205 I make no representation about the suitability of this information for any purpose.
207 While every effort is made to keep the information in this document accurate and current, it is provided "as is" with no warranty expressed or implied.
209 ### <a name="0.04 Release Notes"></a> 0.04 Release Notes
211 This compilation contains material used with permission of Transarc Corporation. Permission to copy is given provided any copyright notices and acknowledgements are retained.
213 Column 1 is used to indicate changes from the last issue:
218 Changes from the last version are to be found at the end of this file.
222 ### <a name="0.05 Quote"></a> 0.05 Quote
224 "'Tis true; there's magic in the web of it;" Othello, Act 3 Scene 4
225 --William Shakespeare (1564-1616)
229 ## <a name="1 General"></a> 1 General
231 ### <a name="1.01 What is AFS?"></a> 1.01 What is AFS?
233 AFS is a distributed filesystem that enables co-operating hosts (clients and servers) to efficiently share filesystem resources across both local area and wide area networks.
235 The commercial version of AFS is marketed, maintained, and extended by Transarc Corporation.
237 AFS is based on a distributed file system originally developed at the Information Technology Center at Carnegie-Mellon University that was called the "Andrew File System".
239 "Andrew" was the name of the research project at CMU - honouring th founders of the University. Once Transarc was formed and AFS became a product, the "Andrew" was dropped to indicate that AFS had gone beyond the Andrew research project and had become a supported, product quality filesystem. However, there were a number of existing cells that rooted their filesystem as /afs. At the time, changing the root of the filesystem was a non-trivial undertaking. So, to save the early AFS sites from having to rename their filesystem, AFS remained as the name and filesystem root.
241 ### <a name="1.02 Who supplies AFS?"></a> 1.02 Who supplies AFS?
243 There are currently three sources for AFS: Commercial Transarc (now part of IBM), the open sourced version of former Transarc AFS called [[OpenAFS]] and the independent open source project [[Arla]].
245 <table border="1" cellpadding="0" cellspacing="0">
248 <td> IBM Pittsburgh Lab </td>
249 <td> phone: +1 (412) 667-4400 </td>
253 <td> 11 Stanwix Street </td>
254 <td> fax: +1 (412) 667-6977 </td>
258 <td> Pittsburgh </td>
259 <td> email: <a href="mailto:information@transarc.com">information@transarc.com</a></td>
264 <td><a href="mailto:afs-sales@transarc.com">afs-sales@transarc.com</a></td>
268 <td> United States of America </td>
269 <td> WWW: <a href="http://www.transarc.com" target="_top">http://www.transarc.com</a></td>
273 <td>[[Main/OpenAFS]]</td>
274 <td> WWW: <a href="http://www.openafs.org/" target="_top">http://www.openafs.org/</a></td>
278 <td>[[Main/Arla]]</td>
279 <td> WWW: <a href="http://www.stacken.kth.se/projekt/arla/" target="_top">http://www.stacken.kth.se/projekt/arla/</a></td>
283 ### <a name="1.03 What is /afs?"></a> 1.03 What is /afs?
285 The root of the AFS filetree is /afs. If you execute "ls /afs" you will see directories that correspond to AFS cells (see below). These cells may be local (on same LAN) or remote (eg halfway around the world).
287 With AFS you can access all the filesystem space under /afs with commands you already use (eg: cd, cp, rm, and so on) provided you have been granted permission (see AFS ACL below).
289 ### <a name="1.04 What is an AFS cell?"></a> 1.04 What is an AFS cell?
291 An AFS cell is a collection of servers grouped together administratively and presenting a single, cohesive filesystem. Typically, an AFS cell is a set of hosts that use the same Internet domain name.
293 Normally, a variation of the domain name is used as the AFS cell name.
295 Users log into AFS client workstations which request information and files from the cell's servers on behalf of the users.
297 ### <a name="1.05 What are the benefits of u"></a> 1.05 What are the benefits of using AFS?
299 The main strengths of AFS are its:
303 - simplicity of addressing
305 - communications protocol
307 Here are some of the advantages of using AFS in more detail:
309 #### <a name="1.05.a Cache Manager"></a> 1.05.a Cache Manager
311 AFS client machines run a Cache Manager process. The Cache Manager maintains information about the identities of the users logged into the machine, finds and requests data on their behalf, and keeps chunks of retrieved files on local disk.
313 The effect of this is that as soon as a remote file is accessed a chunk of that file gets copied to local disk and so subsequent accesses (warm reads) are almost as fast as to local disk and considerably faster than a cold read (across the network).
315 Local caching also significantly reduces the amount of network traffic, improving performance when a cold read is necessary.
317 #### <a name="1.05.b Location independence"></a> 1.05.b Location independence
319 Unlike NFS, which makes use of /etc/filesystems (on a client) to map (mount) between a local directory name and a remote filesystem, AFS does its mapping (filename to location) at the server. This has the tremendous advantage of making the served filespace location independent.
321 Location independence means that a user does not need to know which fileserver holds the file, the user only needs to know the pathname of a file. Of course, the user does need to know the name of the AFS cell to which the file belongs. Use of the AFS cellname as the second part of the pathname (eg: /afs/$AFSCELL/somefile) is helpful to distinguish between file namespaces of the local and non-local AFS cells.
323 To understand why such location independence is useful, consider having 20 clients and two servers. Let's say you had to move a filesystem "/home" from server a to server b.
325 Using NFS, you would have to change the /etc/filesystems file on 20 clients and take "/home" off-line while you moved it between servers.
327 With AFS, you simply move the AFS volume(s) which constitute "/home" between the servers. You do this "on-line" while users are actively using files in "/home" with no disruption to their work.
329 (Actually, the AFS equivalent of "/home" would be /afs/$AFSCELL/home where $AFSCELL is the AFS cellname.)
331 #### <a name="1.05.c Scalability"></a> 1.05.c Scalability
333 With location independence comes scalability. An architectural goal of the AFS designers was client/server ratios of 200:1 which has been successfully exceeded at some sites. Transarc do not recommend customers use the 200:1 ratio. A more cautious value of 50:1 is expected to be practical in most cases. It is certainly possible to work with a ratio somewhere between these two values. Exactly what value depends on many factors including: number of AFS files, size of AFS files, rate at which changes are made, rate at which file are being accessed, speed of servers processor, I/O rates, and network bandwidth.
335 AFS cells can range from the small (1 server/client) to the massive (with tens of servers and thousands of clients). Cells can be dynamic: it is simple to add new fileservers or clients and grow the computing resources to meet new user requirements.
337 #### <a name="1.05.d Improved security"></a> 1.05.d Improved security
339 Firstly, AFS makes use of Kerberos to authenticate users. This improves security for several reasons:
341 - passwords do not pass across the network in plaintext
343 - encrypted passwords no longer need to be visible
344 - You don't have to use NIS, aka yellow pages, to distribute /etc/passwd - thus "ypcat passwd" can be eliminated.
345 - If you do choose to use NIS, you can replace the password field with "X" so the encrypted password is not visible. (These issues are discussed in detail in [25]).
347 - AFS uses mutual authentication - both the service provider and service requester prove their identities
349 Secondly, AFS uses access control lists (ACLs) to enable users to restrict access to their own directories.
351 #### <a name="1.05.e Single systems image (SS"></a> 1.05.e Single systems image (SSI)
353 Establishing the same view of filestore from each client and server in a network of systems (that comprise an AFS cell) is an order of magnitude simpler with AFS than it is with, say, NFS.
355 This is useful to do because it enables users to move from workstation to workstation and still have the same view of filestore. It also simplifies part of the systems management workload.
357 In addition, because AFS works well over wide area networks the SSI is also accessible remotely.
359 As an example, consider a company with two widespread divisions (and two AFS cells): ny.acme.com and sf.acme.com. Mr Fudd, based in the New York office, is visiting the San Francisco office.
361 Mr. Fudd can then use any AFS client workstation in the San Francisco office that he can log into (a unprivileged guest account would suffice). He could authenticate himself to the ny.acme.com cell and securely access his New York filespace.
365 The following shows a guest in the sf.acme.com AFS cell:
367 1. add AFS executables directory to PATH
368 2. obtaining a PAG with pagsh command (see 2.06)
369 3. use the klog command to authenticate into the ny.acme.com AFS cell
370 4. making a HOME away from home
371 5. invoking a homely .profile
373 guest@toontown.sf.acme.com $ PATH=/usr/afsws/bin:$PATH # {1}
374 guest@toontown.sf.acme.com $ pagsh # {2}
375 $ klog -cell ny.acme.com -principal elmer # {3}
377 $ HOME=/afs/ny.acme.com/user/elmer; export HOME # {4}
383 It is not necessary for the San Francisco sys admin to give Mr. Fudd an AFS account in the sf.acme.com cell. Mr. Fudd only needs to be able to log into an AFS client that is:
385 1. on the same network as his cell and
386 2. his ny.acme.com cell is mounted in the sf.acme.com cell (as would certainly be the case in a company with two cells).
388 #### <a name="1.05.f Replicated AFS volumes"></a> 1.05.f Replicated AFS volumes
390 AFS files are stored in structures called Volumes. These volumes reside on the disks of the AFS file server machines. Volumes containing frequently accessed data can be read-only replicated on several servers.
392 Cache managers (on users client workstations) will make use of replicate volumes to load balance. If accessing data from one replicate copy, and that copy becomes unavailable due to server or network problems, AFS will automatically start accessing the same data from a different replicate copy.
394 An AFS client workstation will access the closest volume copy. By placing replicate volumes on servers closer to clients (eg on same physical LAN) access to those resources is improved and network traffic reduced.
396 #### <a name="1.05.g Improved robustness to s"></a> 1.05.g Improved robustness to server crash
398 The Cache Manager maintains local copies of remotely accessed files. This is accomplished in the cache by breaking files into chunks of up to 64k (default chunk size). So, for a large file, there may be several chunks in the cache but a small file will occupy a single chunk (which will be only as big as is needed).
400 A "working set" of files that have been accessed on the client is established locally in the client's cache (copied from fileserver(s)).
402 If a fileserver crashes, the client's locally cached file copies remain readable but updates to cached files fail while the server is down.
404 Also, if the AFS configuration has included replicated read-only volumes then alternate fileservers can satisfy requests for files from those volumes.
406 #### <a name="1.05.h "Easy to use" networking"></a> 1.05.h "Easy to use" networking
408 Accessing remote file resources via the network becomes much simpler when using AFS. Users have much less to worry about: want to move a file from a remote site? Just copy it to a different part of /afs.
410 Once you have wide-area AFS in place, you don't have to keep local copies of files. Let AFS fetch and cache those files when you need them.
412 #### <a name="1.05.i Communications protocol"></a> 1.05.i Communications protocol
414 AFS communications protocol is optimized for Wide Area Networks. Retransmitting only the single bad packet in a batch of packets and allowing the number of unacknowledged packets to be higher (than in other protocols, see [4]).
416 #### <a name="1.05.j Improved system manageme"></a> 1.05.j Improved system management capability
418 Systems administrators are able to make configuration changes from any client in the AFS cell (it is not necessary to login to a fileserver).
420 With AFS it is simple to effect changes without having to take systems off-line.
424 A department (with its own AFS cell) was relocated to another office. The cell had several fileservers and many clients. How could they move their systems without causing disruption?
426 First, the network infrastructure was established to the new location. The AFS volumes on one fileserver were migrated to the other fileservers. The "freed up" fileserver was moved to the new office and connected to the network.
428 A second fileserver was "freed up" by moving its AFS volumes across the network to the first fileserver at the new office. The second fileserver was then moved.
430 This process was repeated until all the fileservers were moved.
432 All this happened with users on client workstations continuing to use the cell's filespace. Unless a user saw a fileserver being physically moved (s)he would have no way to tell the change had taken place.
434 Finally, the AFS clients were moved - this was noticed!
436 ### <a name="1.06 Which systems is AFS avail"></a> 1.06 Which systems is AFS available for?
438 AFS runs on systems from: HP, Compaq, IBM, SUN, SGI, Apple ([[MacOSX]]) and PCs with flavours of Unix.
440 AFS has been available for Next and DEC (Ultrix).
442 Transarc customers have done ports to Crays, and the 3090, but all are based on some flavour of unix. Some customers have done work to make AFS data available to PCs and Macs, although they are using something similar to the AFS/NFS translator (a system that enables "NFS only" clients to NFS mount the AFS filetree /afs).
444 There is a client only implementation "AFS Client for Windows/NT".
446 A page describing the current systems for which AFS is supported may be found at:
448 - <http://www.transarc.com/Support/afs/relversions/platforms.html>
450 There are also ports of AFS done by customers available from Transarc on an "as is" unsupported basis.
452 More information on this can be found at:
454 - <file:///afs/transarc.com/public/afs-contrib/bin/README>
455 - <ftp://ftp.transarc.com/pub/afs-contrib/bin/README>
457 These ports of AFS client code include:
459 - HP (Apollo) Domain OS - by Jim Rees at the University of Michigan.
460 - sun386i - by Derek Atkins and Chris Provenzano at MIT.
461 - Linux - by Derek Atkins, mailing list: <linux-afs-request@mit.edu> <http://www.mit.edu:8008/menelaus/linux-afs/>
462 - [[NetBSD]] - by John Kohl, mailing list: <netbsd-afs@mit.edu>
464 There is some information about AFS on OS/2 at:
466 - <http://www.club.cc.cmu.edu/~jgrande/afsos2.html>
468 The AFS on Linux FAQ may be found at:
470 - <http://www.umlug.umd.edu/linuxafs/>
472 Check out the [[OpenAFS]] and [[Arla]] pages for port avilablity.
474 ### <a name="1.07 What does "ls /afs" displa"></a> 1.07 What does "ls /afs" display in the Internet AFS filetree?
476 Essentially this displays the AFS cells that co-operate in the Internet AFS filetree.
478 Note that the output of this will depend on the cell you do it from; a given cell may not have all the publicly advertised cells available, and it may have some cells that aren't advertised outside of the given site.
480 The definitive source for this information is:
482 - <file:///afs/transarc.com/service/etc/CellServDB.export>
484 I've included the list of cell names included in it below:
487 uni-freiburg.de #Albert-Ludwigs-Universitat Freiburg
488 anl.gov #Argonne National Laboratory
489 fl.mcs.anl.gov # Argonne National Laboratory MCS Division FL
490 dapnia.saclay.cea.fr #Axlan-CEA
491 bcc.ac.uk #Bloomsbury Computing Consortium
492 bu.edu #Boston University
493 cs.brown.edu #Brown University Department of Computer Science
494 caspur.it #CASPUR Inter-University Computing Consortium,Rome
496 mathematik-cip.uni-stuttgart.de #CIP-Pool of Math. Dept, Univ. Stuttgart
497 gg.caltech.edu #Caltech Computer Graphics Group
498 cards.com #Cards - Electronic Warfare Associates
499 cheme.cmu.edu #Carnegie Mellon Univ. Chemical Engineering Dept.
500 cmu.edu #Carnegie Mellon University
501 andrew.cmu.edu #Carnegie Mellon University - Campus
502 ce.cmu.edu #Carnegie Mellon University - Civil Eng. Dept.
503 ece.cmu.edu #Carnegie Mellon University - Elec. Comp. Eng. Dept.
504 me.cmu.edu #Carnegie Mellon University - Mechanical Engineering
505 cs.cmu.edu #Carnegie Mellon University - School of Comp. Sci.
506 club.cc.cmu.edu #Carnegie Mellon University Computer Club
507 cert.org #CERT/Coordination Center
508 others.chalmers.se #Chalmers University of Technology - General users
509 cipool.uni-stuttgart.de #CIP Pool, Rechenzentrum University of Stuttgart
510 clarkson.edu #Clarkson University, Potsdam, USA
511 msc.cornell.edu #Cornell University Materials Science Center
512 graphics.cornell.edu #Cornell University Program of Computer Graphics
513 theory.cornell.edu #Cornell University Theory Center
514 ifh.de #DESY-IfH Zeuthen
515 northstar.dartmouth.edu #Dartmouth College, Project Northstar
516 desy.de #Deutsches Elektronen-Synchrotron
517 dkrz.de #Deutsches Klimarechenzentrum Hamburg
518 dis.uniroma1.it #DIS, Univ. "La Sapienza", Rome, area Buonarotti
519 msrc.pnl.gov #EMSL's AFS Cell
520 zdvpool.uni-tuebingen.de#Eberhard-Karls-Universitaet Tuebingen, WS-Pools
522 es.net #Energy Sciences Net
523 research.ec.org #Esprit Research Network of Excellence
524 dce.emsl.pnl.gov #EMSL's DCE Cell
525 cern.ch #European Laboratory for Particle Physics, Geneva
526 fnal.gov #Fermi National Acclerator Laboratory
527 fh-heilbronn.de #Fachhochschule Heilbronn
528 hephy.at #hephy-vienna
529 sleeper.nsa.hp.com #HP Cupertino
530 palo_alto.hpl.hp.com #HP Palo Alto
531 afs.hursley.ibm.com #IBM Hursley Laboratories (UK), external cell
532 ibm.uk #IBM UK, AIX Systems Support Centre
533 zurich.ibm.ch #IBM Zurich Internet Cell
534 ctp.se.ibm.com #IBM/4C, Chalmers, Sweden
535 ipp-hgw.mpg.de #IPP site at Greifswald
536 in2p3.fr #IN2P3 production cell
537 lngs.infn.it #INFN Laboratori Nazionali di Gran Sasso, Italia
538 le.infn.it #INFN Sezione di Lecce, Italia
539 pi.infn.it #INFN Sezione di Pisa
540 ike.uni-stuttgart.de #Institut fuer Kernenergetik, Universitaet Stuttgart
541 ipp-garching.mpg.de #Institut fuer Plasmaphysik
542 csv.ica.uni-stuttgart.de #Institut fuer Computeranwendungen, Uni. Stuttgart
543 iastate.edu #Iowa State University
544 infn.it #Istituto Nazionale di Fisica Nucleare, Italia
545 jpl.nasa.gov #Jet Propulsion Laboratory
546 zdv.uni-mainz.de #Johannes-Gutenberg-Universitaet Mainz
547 isk.kth.se #KTH College of Engineering
548 cc.keio.ac.jp #Keio University, Fac. of Sci. & Tech. Computing Ctr
549 sfc.keio.ac.jp #Keio University, Japan
550 afs-math.zib-berlin.de #Konrad-Zuse-Zentrum fuer Informationstechnik Berlin
551 thermo-a.mw.tu-muenchen.de #Lehrstuhl A fuer Thermodynamik,TUM
552 lrz-muenchen.de #Leibniz-Rechenzentrum Muenchen Germany
553 athena.mit.edu #MIT/Athena cell
554 net.mit.edu #MIT/Network Group cell
555 sipb.mit.edu #MIT/SIPB cell
556 msu.edu #Michigan State University home cell
557 mpa-garching.mpg.de #Max-Planck-Institut fuer Astrophysik
558 federation.atd.net #Multi Resident AFS at Naval Research Lab - CCS
559 isl.ntt.jp #NTT Information and Communication
560 nersc.gov #National Energy Research Supercomputer Center
561 alw.nih.gov #National Institutes of Health
562 nrel.gov #National Renewable Energy Laboratory
563 cmf.nrl.navy.mil #Naval Research Lab
564 lcp.nrl.navy.mil #Naval Research Lab - Lab for Computational Physics
565 nrlfs1.nrl.navy.mil #Naval Research Laboratory
566 eos.ncsu.edu #NCSU - College of Engineering
567 unity.ncsu.edu #NCSU Campus
568 ncat.edu #North Carolina Agricultural and Technical State U.
569 bp.ncsu.edu #North Carolina State University - Backbone Prototype
570 ri.osf.org #OSF Research Institute
571 gr.osf.org #OSF Research Institute, Grenoble
572 urz.uni-magdeburg.de #Otto-von-Guericke-Universitaet, Magdeburg
573 N ovpit.indiana.edu #OVPIT at Indiana University
574 psc.edu #PSC (Pittsburgh Supercomputing Center)
576 phy.bnl.gov #Physics Deptpartment, Brookhaven National Lab
577 postech.ac.kr #Pohang University of Science
578 pppl.gov #Princeton Plasma Physics Laboratory
579 rwcp.or.jp #Real World Computer Partnership(rwcp)
580 rz.uni-jena.de #Rechenzentrum University of Jena, Germany
581 rhrk.uni-kl.de #Rechenzentrum University of Kaiserslautern
582 rus.uni-stuttgart.de #Rechenzentrum University of Stuttgart
583 rhic #Relativistic Heavy Ion Collider
584 rpi.edu #Rensselaer Polytechnic Institute
585 uni-bonn.de #Rheinische Friedrich Wilhelm Univesitaet Bonn
586 rose-hulman.edu #Rose-Hulman Institute of Technology
587 cs.rose-hulman.edu # Rose-Hulman Inst. of Tech., CS Department
588 nada.kth.se #Royal Institute of Technology, NADA
589 rl.ac.uk #Rutherford Appleton Lab, England
590 slac.stanford.edu #Stanford Linear Accelerator Center
591 dsg.stanford.edu #Stanford Univ. - Comp. Sci. - Distributed Systems
592 ir.stanford.edu #Stanford University
593 afs1.scri.fsu.edu #Supercomputer Computations Research Instit
594 ethz.ch #Swiss Federal Inst. of Tech. - Zurich, Switzerland
595 hrzone.th-darmstadt.de #TH-Darmstadt
596 tu-bs.de #Technical University of Braunschweig, Germany
597 tu-chemnitz.de #Technische Universitaet Chemnitz-Zwickau, Germany
598 telos.com #Telos Systems Group - Chantilly, Va.
599 transarc.com #Transarc Corporation
600 cats.ucsc.edu #UC Santa Cruz, Comp and Tech Services, California
601 umr.edu #UMR - Missouri's Technological University
602 hep.net #US High Energy Physics Information cell
603 uni-mannheim.de #Uni Mannheim (Rechenzentrum)
604 ece.ucdavis.edu #Univ California - Davis campus
605 geo.uni-koeln.de #Univ. of Cologne Inst. for Geophysics & Meteorology
606 meteo.uni-koeln.de #Univ. of Cologne Inst. for Geophysics & Meteorology
607 N dsi.uniroma1.it #Univ. Rome-1, Dept. of Computer Science
608 U spv.uniroma1.it #Univ. Rome-1, Area San Pietro in Vincoli
609 N vn.uniroma3.it #Univ. Rome-3, Area Vasca Navale
610 urz.uni-heidelberg.de #Universitaet Heidelberg
611 spc.uchicago.edu #University of Chicago - Social Sciences
612 rrz.uni-koeln.de #University of Cologne - Reg Comp Center
613 wu-wien.ac.at #University of Economics, Vienna, Austria
614 uni-hohenheim.de #University of Hohenheim
615 ncsa.uiuc.edu #University of Illinois
616 wam.umd.edu #University of Maryland Network WAM Project
617 glue.umd.edu #University of Maryland - Project Glue
618 engin.umich.edu #University of Michigan - CAEN
619 umich.edu #University of Michigan - Campus
620 dmsv.med.umich.edu #University of Michigan - DMSV
621 citi.umich.edu #University of Michigan - IFS Development
622 lsa.umich.edu #University of Michigan - LSA College
623 math.lsa.umich.edu #University of Michigan - Math Cell
624 sph.umich.edu #University of Michigan -- School of Public
625 cs.unc.edu #University of North Carolina at Chapel Hill
626 nd.edu #University of Notre Dame
627 pitt.edu #University of Pittsburgh
628 vn.uniroma3.it #University of Rome 3, Area Vasca Navale, Italy
629 isi.edu #University of Southern California/ISI
630 dce.uni-stuttgart.de #University of Stuttgart - DCE/DFS Cell
631 ihf.uni-stuttgart.de #University of Stuttgart, Ins. fuer Hochfrequenz-Tec
632 mathematik.uni-stuttgart.de #University of Stuttgart, Math Dept.
633 cs.utah.edu #University of Utah Computer Science Dept
634 utah.edu #University of Utah Information Tech. Service
635 cs.washington.edu #University of Washington Comp Sci Department
636 wisc.edu #University of Wisconsin-Madison, Campus
637 cs.wisc.edu #University of Wisconsin-Madison, Comp Sci Dept
638 belwue.uni-tuebingen.de #ZDV Universitaet Tuebingen
640 This shows different and widespread organizations making use of the Internet AFS filetree.
642 Note that it is also possible to use AFS "behind the firewall" within the confines of your organization's network - you don't have to participate in the Internet AFS filetree.
644 Indeed, there are lots of benefits of using AFS on a local area network without using the WAN capabilities.
646 ### <a name="1.08 Why does AFS use Kerberos"></a><a name="1.08 Why does AFS use Kerberos "></a> 1.08 Why does AFS use Kerberos authentication?
648 It improves security.
650 Kerberos uses the idea of a trusted third party to prove identification. This is a bit like using a letter of introduction or quoting a referee who will vouch for you.
652 When a user authenticates using the klog command (s)he is prompted for a password. If the password is accepted the Kerberos Authentication Server (KAS) provides the user with an encrypted token (containing a "ticket granting ticket").
654 From that point on, it is the encrypted token that is used to prove the user's identity. These tokens have a limited lifetime (typically a day) and are useless when expired.
656 In AFS, it is possible to authenticate into multiple AFS cells. A summary of the current set of tokens held can be displayed by using the "tokens" command.
660 elmer@toontown $ tokens
662 Tokens held by the Cache Manager:
664 User's (AFS ID 9997) tokens for afs@ny.acme.com [Expires Sep 15 06:50]
665 User's (AFS ID 5391) tokens for afs@sf.acme.com [Expires Sep 15 06:48]
668 Kerberos improves security because a users's password need only be entered once (at klog time).
670 AFS uses Kerberos to do complex mutual authentication which means that both the service requester and the service provider have to prove their identities before a service is granted.
672 Transarc's implementation of Kerberos is slightly different from MIT Kerberos V4 but AFS can work with either version. Joe Jackson wrote about this in: <http://www.cs.cmu.edu/afs/andrew.cmu.edu/usr/shadow/www/afs/afs-with-kerberos.html>
674 For more detail on this and other Kerberos issues see the faq for Kerberos (posted to news.answers and comp.protocols.kerberos) [28]. (Also, see [15], [16], [26], [27])
676 ### <a name="1.09 Does AFS work over protoco"></a> 1.09 Does AFS work over protocols other than TCP/IP?
678 No. AFS was designed to work over TCP/IP.
680 ### <a name="1.10 How can I access AFS from"></a><a name="1.10 How can I access AFS from "></a> 1.10 How can I access AFS from my PC?
682 You can use PC-Interface which is available from Transarc and Locus Computing Corporations.
684 For more information on PC-Interface see the PC-Interface Frequently Asked Questions file in:
686 - <file:///afs/transarc.com/public/afs-contrib/doc/faq/pci.faq>
687 - <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/pci.faq>
689 There is also SAMBA (an SMB/netbios server for UNIX). The current version will authenticate the connecting process with AFS as well.
691 - <http://samba.anu.edu.au/samba/>
695 - <http://samba.anu.edu.au/samba/docs/faq/sambafaq-1.html#ss1.1>
697 The SAMBA mailing list can be joined via: <samba-request@anu.edu.au>
699 ### <a name="1.11 How does AFS compare with"></a><a name="1.11 How does AFS compare with "></a> 1.11 How does AFS compare with NFS?
701 <table border="1" cellpadding="0" cellspacing="0">
704 <th align="center" bgcolor="#99CCCC"><strong> AFS </strong></th>
705 <th align="center" bgcolor="#99CCCC"><strong> NFS </strong></th>
708 <th bgcolor="#99CCCC"><strong> File Access </strong></th>
709 <td> Common name space from all workstations </td>
710 <td> Different file names from different workstations </td>
713 <th bgcolor="#99CCCC"><strong> File Location Tracking </strong></th>
714 <td> Automatic tracking by file system processes and databases </td>
715 <td> Mountpoints to files set by administrators and users </td>
718 <th bgcolor="#99CCCC"><strong> Performance </strong></th>
719 <td> Client caching to reduce network load; callbacks to maintain cache consistency </td>
720 <td> No local disk caching; limited cache consistency </td>
723 <th bgcolor="#99CCCC"><strong> Andrew Benchmark (5 phases, 8 clients) </strong></th>
724 <td> Average time of 210 seconds/client </td>
725 <td> Average time of 280 seconds/client </td>
728 <th bgcolor="#99CCCC"><strong> Scaling capabilities </strong></th>
729 <td> Maintains performance in small and very large installations </td>
730 <td> Best in small to mid-size installations </td>
734 <td> Excellent performance on wide-area configuration </td>
735 <td> Best in local-area configurations </td>
738 <th bgcolor="#99CCCC"><strong> Security </strong></th>
739 <td> Kerberos mutual authentication </td>
740 <td> Security based on unencrypted user ID's </td>
744 <td> Access control lists on directories for user and group access </td>
745 <td> No access control lists </td>
748 <th bgcolor="#99CCCC"><strong> Availability </strong></th>
749 <td> Replicates read-mostly data and AFS system information </td>
750 <td> No replication </td>
753 <th bgcolor="#99CCCC"><strong> Backup Operation </strong></th>
754 <td> No system downtime with specially developed AFS Backup System </td>
755 <td> Standard UNIX backup system </td>
758 <th bgcolor="#99CCCC"><strong> Reconfiguration </strong></th>
759 <td> By volumes (groups of files) </td>
760 <td> Per-file movement </td>
764 <td> No user impact; files remain accessible during moves, and file names do not change </td>
765 <td> Users lose access to files and filenames change (mountpoints need to be reset) </td>
768 <th bgcolor="#99CCCC"><strong> System Management </strong></th>
769 <td> Most tasks performed from any workstation </td>
770 <td> Frequently involves telnet to other workstations </td>
773 <th bgcolor="#99CCCC"><strong> Autonomous Architecture </strong></th>
774 <td> Autonomous administrative units called cells, in addition to file servers and clients </td>
775 <td> File servers and clients </td>
779 <td> No trust required between cells </td>
780 <td> No security distinctions between sites </td>
785 <td colspan="2"> [ source: <a href="ftp://ftp.transarc.com/pub/afsps/doc/afs-nfs.comparison" target="_top">ftp://ftp.transarc.com/pub/afsps/doc/afs-nfs.comparison</a> ] </td>
791 - Some vendors offer more secure versions of NFS but implementations vary. Many NFS ports have no extra security features (such as Kerberos).
793 - The AFS Cache Manager can be configured to work with a RAM (memory) based cache. This offers signifigant performance benefits over a disk based cache. NFS has no such feature. Imagine how much faster it is to access files cached into RAM!
795 - The Andrew benchmark demonstrates that AFS has better performance than NFS as the number of clients increases. A graph of this (taken from Andrew benchmark report) is available in:
796 - 
798 ## <a name="2 Using AFS"></a> 2 Using AFS
800 ### <a name="2.01 What are the differences b"></a> 2.01 What are the differences between AFS and a unix filesystem?
802 Essentially, from a user's point of view, there is little difference between AFS and local unix filestore. Nearly all the commands normally used to access local files can be used to access files in /afs.
804 In the following set of sections, I have attempted to "target" each section to an appropriate type of user by including to the right of each section heading one of: User, Programmer, [[SysAdmin]].
806 Here is a summary of the differences:
808 **Authentication:** [ User ]
810 Before a user can access protected AFS files (s)he needs to become authenticated to AFS using the klog command (Kerberos login) to get a Kerberos "ticket granting ticket" (called a token from here on).
812 Without a token, an unauthenticated user is given the AFS identity "system:anyuser" and as such is only able to access files in directories that have ACLs granting system:anyuser access.
814 Many systems have the klog function built into the system login program. So a user would not even have to know they gain a token on logging in. If you use a system where you have to issue the klog command after login then you should run the pagsh command first (see below).
816 AFS provides access control lists to give more precise control to users wishing to protect their files (see AFS ACL below).
818 **File permissions:** [ User ]
820 Unix mode bits for group and other are ignored. The mode bits for the file owner don't work the way they used to.
822 Users should protect their AFS files with (directory) ACLs only. Just use mode bits to make a file executable.
824 **Data protection with AFS ACLs:** [ User ]
826 Some versions of unix (eg IBM's AIX version 3) allow ACLs on local files. In AFS, ACLs protect directories and used with AFS protection groups (see below) provide a finer granularity of protection than can be achieved with basic unix file permissions. (AFS ACLs are described in more detail below.)
828 **Protection groups:** [ User ]
830 Users can create and maintain their own protection groups in AFS - as opposed to unix where only sys admins can manage protection groups.
832 **Hard links:** [ User ]
834 In AFS, hard links (eg: ln old new) are only valid within a directory. This is because AFS ACLs protect directories (not individual files) and allowing hard links that span directories would subvert ACL protection.
836 Symbolic links work in AFS because they reference a pathname and not an i-node directly. (Hard links reference an i-node directly.)
838 **Changing file protection by moving a file:** [ User ]
840 Moving a file to a different directory will change the protection of a file if the ACL on the new directory if different to the ACL on the original directory.
842 **chown and chgrp:** [ User ]
844 Only members of the AFS group "system:administrators" can use these commands on files in /afs.
846 **Save on close:** [ Programmer ]
848 AFS Cache Manager does not send file modifications to a file server until the close() or fsync() system call.
850 write() system calls only update the local cache copy on the client.
852 Note the difference in semantic of writing a file:
854 <table border="1" cellpadding="0" cellspacing="0">
856 <th bgcolor="#99CCCC"><strong> local unix file: </strong></th>
857 <td> writes update the file "immediately" </td>
860 <th align="center" bgcolor="#99CCCC"><strong> AFS file: </strong></th>
861 <td> local cached copy updated "immediately" but the server copy is only updated when the file is closed or fsync'ed. </td>
865 It is important to understand that most applications (eg: vi, emacs, frame, interleaf, wingz, dogz, etc) issue the close() system call when the user chooses/issues the "save" command in the application.
867 Users are not required to exit the application to "save" their changes back to the server.
869 **byte-range file locking:** [ Programmer ]
871 AFS does not support byte-range locking within a file, although lockf() and fcntl() calls will return 0 (success). The first time a byte-range lock is attempted, AFS will display:
873 "afs: byte-range lock/unlock ignored; make sure no one else else is running this program."
875 **whole file locking:** [ Programmer ]
877 AFS does support advisory locking an entire file with flock(). Processes on the same client workstation that attempt to lock a file obey the proper locking semantics.
879 Processes on different AFS clients requesting a lock on the same file would get EWOULDBLOCK returned.
881 **character and block special files:** [ [[SysAdmin]] ]
883 AFS does not support character and block special files. The mknod command does not create either character or block special files in /afs.
885 **AFS version of fsck:** [ [[SysAdmin]] ]
887 On an AFS server, the partitions containing served files are NOT unix filesystems and standard fsck **must** not be used - use the AFS version instead.
889 ### <a name="2.02 What is an AFS protection"></a><a name="2.02 What is an AFS protection "></a> 2.02 What is an AFS protection group?
891 A named list of users.
893 Group names are used in AFS ACLs to identify lists of users with particular access permissions.
895 In AFS, users can create and maintain their own protection groups. This is different to unix where only the system administrator can manage /etc/group.
897 AFS groups are stored in the protection database on fileserver(s) and managed by using the "pts" command.
899 An AFS group typically has the format:
901 - owner-id:group-name
903 By default, only the owner of a group can change its members.
905 It is possible to have both users and IP addresses as members of an AFS group. By using an IP address like this you can specify all the users from the host with that IP address.
907 ### <a name="2.03 What are the AFS defined p"></a> 2.03 What are the AFS defined protection groups?
910 - Everyone who has access to an AFS client in any cell that is on the same network as your cell.
913 - Everyone who has access to an AFS client in any cell that is on the same network as your cell **and** has valid tokens for your cell (ie has been authenticated in your cell).
915 - system:administrators
916 - Users who have privileges to execute some but not all system administrator commands.
918 ### <a name="2.04 What is an AFS access cont"></a> 2.04 What is an AFS access control list (ACL)?
920 There is an ACL for every directory in AFS. The ACL specifies protection at the directory level (not file level) by listing permissions of users and/or groups to a directory. There is a maximum of 20 entries on an ACL.
924 An AFS ACL is displayed by using the "fs" command as shown below:
926 tweety@toontown $ fs listacl .
932 This ACL shows that members of the AFS protection group "fac:coords" have full access rights to the current directory and "system:anyuser" has only read and lookup rights.
934 The members of "fac:coords" can be determined by accessing the protection group database using the "pts" command as shown below:
936 tweety@toontown $ pts membership fac:coords
937 Members of fac:coords (id: -1577) are:
942 ### <a name="2.05 What are the AFS access ri"></a> 2.05 What are the AFS access rights?
944 In AFS, there are seven access rights that may be set or not set:
946 <table border="1" cellpadding="0" cellspacing="0">
948 <th bgcolor="#99CCCC"><strong> lookup </strong></th>
949 <td><code>l</code></td>
950 <td> Permission to examine the ACL and traverse the directory (needed with most other access rights). Permission to look up filenames in a directory. </td>
953 <th bgcolor="#99CCCC"><strong> read </strong></th>
954 <td><code>r</code></td>
955 <td> View the contents of files in the directory </td>
958 <th bgcolor="#99CCCC"><strong> insert </strong></th>
959 <td><code>i</code></td>
960 <td> Add new files or sub-directories </td>
963 <th bgcolor="#99CCCC"><strong> write </strong></th>
964 <td><code>w</code></td>
965 <td> Modify file contents, use "chmod" </td>
968 <th bgcolor="#99CCCC"><strong> delete </strong></th>
969 <td><code>d</code></td>
970 <td> Remove file(s) in directory </td>
973 <th bgcolor="#99CCCC"><strong> lock </strong></th>
974 <td><code>k</code></td>
975 <td> Permission for programs to "flock" files in the directory </td>
978 <th bgcolor="#99CCCC"><strong> administer </strong></th>
979 <td><code>a</code></td>
980 <td> Ability to change the ACL </td>
984 There are short-hand forms:
986 <table border="1" cellpadding="0" cellspacing="0">
988 <th bgcolor="#99CCCC"><strong> read </strong></th>
989 <td><code>rl</code></td>
990 <td> read and lookup </td>
993 <th bgcolor="#99CCCC"><strong> write </strong></th>
994 <td><code>rlidwk</code></td>
995 <td> all rights except administer </td>
998 <th bgcolor="#99CCCC"><strong> all </strong></th>
999 <td><code>rlidwka</code></td>
1000 <td> all rights </td>
1003 <th bgcolor="#99CCCC"><strong> none </strong></th>
1005 <td> removes all rights </td>
1009 ### <a name="2.06 What is pagsh?"></a> 2.06 What is pagsh?
1011 A command to get a new shell with a process authentication group (PAG).
1013 This is normally used if your system does not use the AFS version of login. It is used to get a PAG prior to running klog.
1015 The PAG uniquely identifies the user to the Cache Manager. Without a PAG the Cache Manager uses the unix UID to identify a user.
1017 ### <a name="2.07 Why use a PAG?"></a> 2.07 Why use a PAG?
1019 There are two reasons:
1021 1. Child processes inherit the PAG and the Kerberos token so they are AFS authenticated.
1023 1. For security: if you don't have a PAG then the Cache Manager identifies you by unix UID. Another user with root access to the client could su to you and therefore use your token.
1025 ### <a name="2.08 How can I tell if I have a"></a> 2.08 How can I tell if I have a PAG?
1027 You can tell if you have a PAG by typing "groups". A PAG is indicated by the appearance of two integers in the list of groups.
1031 sylvester@toontown $ groups
1032 33536 32533 staff catz
1034 ### <a name="2.09 Can I still run cron jobs"></a><a name="2.09 Can I still run cron jobs "></a> 2.09 Can I still run cron jobs with AFS?
1036 Yes, but remember that in order to fully access files in AFS you have to be AFS authenticated. If your cron job doesn't klog then it only gets system:anyuser access.
1038 The klog command has a "-pipe" option which will read a password from stdin. IF (yes, that's a big if :-) you are prepared to store your password in a local (non-AFS) file then you might use the following:
1040 (a) create a "wrapper" script to get a PAG, get your AFS token and execute a command:
1042 #!/usr/afsws/bin/pagsh
1044 # NAME afs_wrap_cron
1045 # AUTHOR Paul Blackburn <mpb@acm.org>
1046 # PURPOSE Run an AFS authenticated cron job.
1047 # Get a PAG, get the user's token,
1048 # then exec user's command
1053 echo "Usage: ${CMD} [ -principal AFSID ] passwordfile command" >&2
1056 if [ ${1} = "-principal" ]; then
1057 PRINCIPAL="${1} ${2}"
1061 if [ -z "${1}" ]; then
1062 echo "${CMD} error: need name of password file" >&2
1070 /usr/afsws/bin/klog ${PRINCIPAL} -pipe < ${passwordfile}
1072 if [ -z "${1}" ]; then
1073 echo "${CMD} error: need name of command to run" >&2
1078 command=`echo ${command_line} | awk '{print $1}'`
1080 # Check if we can run the command.
1081 # If we got this far, it is likely that the command name is correct
1082 # but there may be a problem in accessing the command file.
1083 # If there is an error, log it via syslog (logger) rather than ">&2"
1085 if [ ! -x "${command}" ]; then
1086 M="error: unable to execute command ${command}"
1087 logger -i -t "${CMD}" "${M}"
1091 exec ${command_line}
1093 (b) Store your password in a local (non-AFS) file that only you have access to (perhaps: /home/$USER/.p).
1095 Make sure that this file is mode 600 and also be sure that you trust whoever has root access on this system and whoever has access to backup tapes! Also, don't forget to change this file if you change your AFS password.
1097 (c) In your crontab file, run afs\_wrap\_cron followed by unlog:
1099 0 6 * * * /usr/local/bin/afs_wrap_cron /home/$USER/.p \
1100 $HOME/bin/6AMdaily; /usr/afsws/bin/unlog
1102 Note that you can still run a cron job without getting a token if the task does not need to be AFS authenticated. In this case, you may get stderr from the cron job if your .profile is not accessible because of the ACL protecting your $HOME. Simply redirect to /dev/null:
1104 0 7 * * * $sys_anyuser_readable_dir/7AMdaily 2>/dev/null
1106 ### <a name="2.10 How much disk space does a"></a> 2.10 How much disk space does a 1 byte file occupy in AFS?
1110 Other filesystems allocate different file block sizes. For example, IBM's AIX version 3 journaled file system (JFS) uses 4K blocks (exception: 2K for the 160MB disk drive).
1112 Such blocksize differences lead to variations on the amount of disk space required to store files. Copying a directory from AFS to AIX JFS would require more space in JFS because of the block fragmentation.
1116 (a) Create a one byte file in AFS and use "ls -s" to show how many kilobytes it occupies:
1118 ariel@atlantica $ echo z >/afs/dsea/tmp/one_byte_file
1119 ariel@atlantica $ ls -s /afs/dsea/tmp/one_byte_file
1120 1 /afs/dsea/tmp/one_byte_file
1122 (b) Create same file in local filesystem (AIX JFS):
1124 ariel@atlantica $ echo z >/tmp/one_byte_file
1125 ariel@atlantica $ ls -s /tmp/one_byte_file
1126 4 /tmp/one_byte_file
1128 ### <a name="2.11 Is it possible to specify"></a><a name="2.11 Is it possible to specify "></a> 2.11 Is it possible to specify a user who is external to the current AFS cell on an ACL?
1130 No. You cannot reference a particular user from another AFS cell.
1132 You can specify an IP address on the ACL; this means any and all users from the host with that IP address.
1134 Another solution to this problem is to give the external user an "authentication-only" account in your AFS cell. This means that (s)he can klog (but has no home directory) in your cell.
1136 # Example: AFS administrator creates an authentication-only user
1137 $ uss add daffy "Daffy Duck" -t /dev/null
1138 $ kas setpassword daffy -admin admin
1140 Cross-realm authentication (where co-operating cells are able to specify remore users as "user@remote.cell" on an ACL) is an **unsupported** feature of AFS 3.3a. That means that Transarc doesn't promise to make it work for you, nor keep it running in future releases.
1142 ### <a name="2.12 Are there any problems pri"></a> 2.12 Are there any problems printing files in /afs?
1144 The issue of printing in AFS is almost always the same: what do you send to the printing daemon? Do you send it the bytes you want to print or do you just send the file name containing those bytes? If you send it a file name, you have to be sure that the printing daemon can read it. Most daemons run with no AFS tokens, so can't access directories unless they are open for system:anyuser read access. Often, printing commands (lpr, lp, enq) have an option that allows for both modes of operation, though the default behavior varies from system to system. If you're interested in making your daemons authenticate to AFS, check out the example scripts in AFS-Contrib:
1146 - <file:///afs/transarc.com/public/afs-contrib/tools/reauth-example>
1147 - <ftp://ftp.transarc.com/pub/afs-contrib/tools/reauth-example/MANIFEST>
1149 Another common problem is setuid printing commands. For instance, the "enq" command runs as root, daemon, or some such user. If you aren't using the AFS login and simply issue "klog" to get tokens, those tokens are associated with your uid. When setuid programs run, they lose access to your token and often can't read the file name given as an argument. The solution in this case is to use "pagsh" before "klog" so that your tokens are transferred to subprocesses automatically by group membership. This works even if the uid changes, as for setuid programs.
1151 ### <a name="2.13 Can I create a fifo (aka n"></a> 2.13 Can I create a fifo (aka named pipe) in /afs?
1153 No. AFS does not support "mknod fifofile p".
1155 ### <a name="2.14 If an AFS server crashes,"></a><a name="2.14 If an AFS server crashes, "></a> 2.14 If an AFS server crashes, do I have to reboot my AFS client?
1159 Typically, if an AFS server becomes unavailable, the AFS Cache Manager on your AFS client will see you through the outage until the server returns. This robustness is dependent on the way your AFS cell has been configured including the following factors:
1161 - On the client side:
1162 - How big is the cache?
1163 - Are the files you need already in the cache?
1165 - On the server side:
1166 - How many servers? It's best to have a minimum of three.
1167 - Is the data you are accessing replicated? In AFS, replicas are [[ReadOnly]] copies.
1169 With replicated volumes, the AFS Cache Manager knows about all of the servers on which the replicas are located. Therefore, when the Cache Manager accesses a replicated volume, if the RPC times out, the Cache Manager automatically retrys the RPC, using a different file server.
1171 If necessary, the Cache Manager will attempt to contact all file servers on which a replica of the volume resides.
1173 If you are accessing [[ReadWrite]] volumes on a crashed server then you will not be able to save changes back to the server until it returns.
1175 You don't need to reboot, and the Cache Manager activity is "invisible" to the user.
1177 ### <a name="2.15 Can I use AFS on my diskle"></a> 2.15 Can I use AFS on my diskless workstation?
1179 Yes. The AFS Cache Manager can be configured to work with either a disk based cache or a memory (RAM) based cache. With the latter, you can expect file access from the cache with a whizz!
1181 <http://www.uni-hohenheim.de/~schaefer/afs/info-afs/1306.html>
1183 ### <a name="2.16 Can I test for AFS tokens"></a><a name="2.16 Can I test for AFS tokens "></a> 2.16 Can I test for AFS tokens from within my program?
1185 Yes. Some sample code showing how to do this can be found in:
1187 <file:///afs/transarc.com/public/afs-contrib/tools/auth-samples/listtokens.c> <ftp://ftp.transarc.com/pub/afs-contrib/tools/auth-samples/listtokens.c>
1189 ### <a name="2.17 What's the difference betw"></a> 2.17 What's the difference between /afs/cellname and /afs/.cellname?
1191 AFS has [[ReadOnly]] (RO) and [[ReadWrite]] (RW) volumes.
1193 The convention in AFS is to mount the RW volume "root.cell" as /afs/.cellname and the RO volume "root.cell.readonly" as /afs/cellname.
1195 This is so that when you travel down the /afs/.cellname link, AFS will always use the RW site of any volumes that have RO clones.
1197 This allows your administrator to update the RW copy of a volume and "vos release $volname" so that it will appear in /afs/cellname.
1199 ### <a name="2.18 Can I klog as two users on"></a> 2.18 Can I klog as two users on a machine in the same cell?
1201 Yes, if you use two different PAGs.
1203 It's: "One token per PAG per client system."
1205 From one shell you can only authenticate as a single user of a cell. If you open another shell (with another PAG) you can klog as a different user of the same cell from the same client.
1207 You can authenticate into many cells from one client shell.
1209 ### <a name="2.19 What are the ~/._afsXXXX f"></a> 2.19 What are the ~/.\_\_afsXXXX files?
1211 They are temporary reference files used by the AFS Cache Manager.
1213 In UNIX filesystems, when you a remove a file that is kept open by a process, the file stays around physically while it is no longer referenced in any directory (which you will see as a mismatch between disk space usage according to df and du).
1215 Some applications rely on that feature, e.g. they create a temporary file and remove it immediatley while keeping the file descriptor open. The file then disappears from the filesystem automagically when the process terminates or the file descriptor gets closed otherwise. Such applications could get into trouble with older versions of AFS, where the file could really disappear while it was held open.
1217 Newer versions of AFS rename such files to .\_\_afsXXXX, thus making sure that the data stays around as expected by the application. As soon as the file gets closed, the associated .\_\_afsXXXX should disappear.
1219 ## <a name="3 AFS administration"></a> 3 AFS administration
1221 ### <a name="3.01 Is there a version of xdm"></a><a name="3.01 Is there a version of xdm "></a> 3.01 Is there a version of xdm available with AFS authentication?
1223 Yes, xdm can be found in:
1225 <file:///afs/transarc.com/public/afs-contrib/tools/xdm> <ftp://ftp.transarc.com/pub/afs-contrib/tools/xdm/MANIFEST>
1227 ### <a name="3.02 Is there a version of xloc"></a> 3.02 Is there a version of xlock available with AFS authentication?
1229 Yes, xlock can be found in:
1231 <file:///afs/transarc.com/public/afs-contrib/tools/xlock> <ftp://ftp.transarc.com/pub/afs-contrib/tools/xlock/MANIFEST>
1233 ### <a name="3.03 What is /afs/@cell?"></a> 3.03 What is /afs/@cell?
1235 It is a symbolic link pointing at /afs/$your\_cell\_name.
1237 NB, @cell is not something that is provided by AFS. You may decide it is useful in your cell and wish to create it yourself.
1239 /afs/@cell is useful because:
1241 - If you look after more than one AFS cell, you could create the link in each cell then set your PATH as:
1242 - PATH=$PATH:/afs/@cell/@sys/local/bin
1244 - For most cells, it shortens the path names to be typed in thus reducing typos and saving time.
1246 A disadvantage of using this convention is that when you cd into /afs/@cell then type "pwd" you see "/afs/@cell" instead of the full name of your cell. This may appear confusing if a user wants to tell a user in another cell the pathname to a file.
1248 You could create your own /afs/@cell with the following:
1252 [ -L /afs/@cell ] && echo We already have @cell! && exit
1253 cell=$(cat /usr/vice/etc/ThisCell)
1254 cd /afs/.${cell} && fs mkm temp root.afs
1256 ln -s /afs/${cell} @cell
1257 ln -s /afs/.${cell} .@cell # .@cell for RW path
1258 cd /afs/.${cell} && fs rmm temp
1259 vos release root.afs; fs checkv
1261 <http://www-archive.stanford.edu/lists/info-afs/hyper95/0298.html>
1263 ### <a name="3.04 Given that AFS data is loc"></a> 3.04 Given that AFS data is location independent, how does an AFS client determine which server houses the data its user is attempting to access?
1265 The Volume Location Database (VLDB) is stored on AFS Database Servers and is ideally replicated across 3 or more Database Server machines. Replication of the Database ensures high availability and load balances the requests for the data. The VLDB maintains information regarding the current physical location of all volume data (files and directories) in the cell, including the IP address of the [[FileServer]], and the name of the disk partition the data is stored on.
1267 A list of a cell's Database Servers is stored on the local disk of each AFS Client machine as: /usr/vice/etc/CellServDB
1269 The Database Servers also house the Kerberos Authentication Database (encrypted user and server passwords), the Protection Database (user UID and protection group information) and the Backup Database (used by System Administrators to backup AFS file data to tape).
1271 ### <a name="3.05 Which protocols does AFS u"></a> 3.05 Which protocols does AFS use?
1273 AFS may be thought of as a collection of protocols and software processes, nested one on top of the other. The constant interaction between and within these levels makes AFS a very sophisticated software system.
1275 At the lowest level is the UDP protocol, which is part of TCP/IP. UDP is the connection to the actual network wire. The next protocol level is the remote procedure call (RPC). In general, RPCs allow the developer to build applications using the client/server model, hiding the underlying networking mechanisms. AFS uses Rx, an RPC protocol developed specifically for AFS during its development phase at Carnegie Mellon University.
1277 Above the RPC is a series of server processes and interfaces that all use Rx for communication between machines. Fileserver, volserver, upserver, upclient, and bosserver are server processes that export RPC interfaces to allow their user interface commands to request actions and get information. For example, a bos status command will examine the bos server process on the indicated file server machine.
1279 Database servers use ubik, a replicated database mechanism which is implemented using RPC. Ubik guarantees that the copies of AFS databases of multiple server machines remain consistent. It provides an application programming interface (API) for database reads and writes, and uses RPCs to keep the database synchronized. The database server processes, vlserver, kaserver, and ptserver, reside above ubik. These processes export an RPC interface which allows user commands to control their operation. For instance, the pts command is used to communicate with the ptserver, while the command klog uses the kaserver's RPC interface.
1281 Some application programs are quite complex, and draw on RPC interfaces for communication with an assortment of processes. Scout utilizes the RPC interface to file server processes to display and monitor the status of file servers. The uss command interfaces with kaserver, ptserver, volserver and vlserver to create new user accounts.
1283 The Cache Manager also exports an RPC interface. This interface is used principally by file server machines to break callbacks. It can also be used to obtain Cache Manager status information. The program cmdebug shows the status of a Cache Manager using this interface.
1285 For additional information, Section 1.5 of the AFS System Administrator's Guide and the April 1990 Cache Update contain more information on ubik. Udebug information and short descriptions of all debugging tools were included in the January 1991 Cache Update. Future issues will discuss other debugging tools in more detail.
1287 [ source: <ftp://ftp.transarc.com/pub/afsug/newsletter/apr91> ] [ Copyright 1991 Transarc Corporation ]
1289 ### <a name="3.06 Are setuid programs execut"></a> 3.06 Are setuid programs executable across AFS cell boundaries?
1291 By default, the setuid bit is ignored but the program may be run (without setuid privilege).
1293 It is possible to configure an AFS client to honour the setuid bit. This is achieved by root running:
1295 root@toontown # fs setcell -cell $cellname -suid
1297 (where $cellname is the name of the foreign cell. Use with care!).
1299 NB: making a program setuid (or setgid) in AFS does **not** mean that the program will get AFS permissions of a user or group. To become AFS authenticated, you have to klog. If you are not authenticated, AFS treats you as "system:anyuser".
1301 ### <a name="3.07 How does AFS maintain cons"></a> 3.07 How does AFS maintain consistency on read-write files?
1303 AFS uses a mechanism called "callback".
1305 Callback is a promise from the fileserver that the cache version of a file/directory is up-to-date. It is established by the fileserver with the caching of a file.
1307 When a file is modified the fileserver breaks the callback. When the user accesses the file again the Cache Manager fetches a new copy if the callback has been broken.
1309 The following paragraphs describe AFS callback mechanism in more detail:
1311 If I open() fileA and start reading, and you then open() fileA, write() a change **\*\*and close() or fsync()\*\*** the file to get your changes back to the server - at the time the server accepts and writes your changes to the appropriate location on the server disk, the server also breaks callbacks to all clients to which it issued a copy of fileA.
1313 So my client receives a message to break the callback on fileA, which it dutifully does. But my application (editor, spreadsheet, whatever I'm using to read fileA) is still running, and doesn't really care that the callback has been broken.
1315 When something causes the application to read() more of the file the read() system call executes AFS cache manager code via the VFS switch, which does check the callback and therefore gets new copies of the data.
1317 Of course, the application may not re-read data that it has already read, but that would also be the case if you were both using the same host. So, for both AFS and local files, I may not see your changes.
1319 Now if I exit the application and start it again, or if the application does another open() on the file, then I will see the changes you've made.
1321 This information tends to cause tremendous heartache and discontent - but unnecessarily so. People imagine rampant synchronization problems. In practice this rarely happens and in those rare instances, the data in question is typically not critical enough to cause real problems or crashing and burning of applications. Since 1985, we've found that the synchronization algorithm has been more than adequate in practice - but people still like to worry!
1323 The source of worry is that, if I make changes to a file from my workstation, your workstation is not guaranteed to be notified until I close or fsync the file, at which point AFS guarantees that your workstation will be notified. This is a significant departure from NFS, in which no guarantees are provided.
1325 Partially because of the worry factor and largely because of Posix, this will change in DFS. DFS synchronization semantics are identical to local file system synchronization.
1327 [ DFS is the Distributed File System which is part of the Distributed ] [ Computing Environment (DCE). ]
1329 ### <a name="3.08 How can I run daemons with"></a> 3.08 How can I run daemons with tokens that do not expire?
1331 It is not a good idea to run with tokens that do not expire because this would weaken one of the security features of Kerberos.
1333 A better approach is to re-authenticate just before the token expires.
1335 There are two examples of this that have been contributed to afs-contrib. The first is "reauth":
1337 <file:///afs/transarc.com/public/afs-contrib/tools/reauth/> <ftp://ftp.transarc.com/pub/afs-contrib/tools/reauth/MANIFEST>
1339 The second is "lat":
1341 <file:///afs/transarc.com/public/afs-contrib/pointers/UMich-lat-authenticated-batch-jobs> <ftp://ftp.transarc.com/pub/afs-contrib/pointers/UMich-lat-authenticated-batch-jobs>
1343 ### <a name="3.09 Can I check my user's pass"></a> 3.09 Can I check my user's passwords for security purposes?
1345 Yes. Alec Muffett's Crack tool (at version 4.1f) has been converted to work on the Transarc kaserver database. This modified Crack (AFS Crack) is available via anonymous ftp from:
1347 - <ftp://export.acs.cmu.edu/pub/crack.tar.Z>
1349 and is known to work on: pmax\_\* sun4\*\_\* hp700\_\* rs\_aix\* next\_\*
1351 It uses the file /usr/afs/db/kaserver.DB0, which is the database on the kaserver machine that contains the encrypted passwords. As a bonus, AFS Crack is usually two to three orders of magnitude faster than the standard Crack since there is no concept of salting in a Kerberos database.
1353 On a normal UNIX /etc/passwd file, each password can have been encrypted around 4096 (2^12) different saltings of the crypt(3) algorithm, so for a large number of users it is easy to see that a potentially large (up to 4095) number of seperate encryptions of each word checked has been avoided.
1355 Author: Dan Lovinger Contact: Derrick J. Brashear <shadow+@andrew.cmu.edu>
1357 <table border="1" cellpadding="0" cellspacing="0">
1360 <td> AFS Crack does not work for MIT Kerberos Databases. The author is willing to give general guidance to someone interested in doing the (probably minimal) amount of work to port it to do MIT Kerberos. The author does not have access to a MIT Kerberos server to do this. </td>
1364 ### <a name="3.10 Is there a way to automati"></a> 3.10 Is there a way to automatically balance disk usage across fileservers?
1366 Yes. There is a tool, balance, which does exactly this. It can be retrieved via anonymous ftp from:
1368 - <ftp://ftp.andrew.cmu.edu/pub/balance-1.1a.tar.Z>
1370 Actually, it is possible to write arbitrary balancing algorithms for this tool. The default set of "agents" provided for the current version of balance balance by usage, # of volumes, and activity per week, the latter currently requiring a source patch to the AFS volserver. Balance is highly configurable.
1372 Author: Dan Lovinger Contact: Derrick Brashear <shadow+@andrew.cmu.edu>
1374 ### <a name="3.11 Can I shutdown an AFS file"></a> 3.11 Can I shutdown an AFS fileserver without affecting users?
1376 Yes, this is an example of the flexibility you have in managing AFS.
1378 Before attempting to shutdown an AFS fileserver you have to make some arrangements that any services that were being provided are moved to another AFS fileserver:
1380 1. Move all AFS volumes to another fileserver. (Check you have the space!) This can be done "live" while users are actively using files in those volumes with no detrimental effects.
1382 1. Make sure that critical services have been replicated on one (or more) other fileserver(s). Such services include:
1383 - kaserver - Kerberos Authentication server
1384 - vlserver - Volume Location server
1385 - ptserver - Protection server
1386 - buserver - Backup server
1388 It is simple to test this before the real shutdown by issuing:
1390 bos shutdown $server $service
1392 where: $server is the name of the server to be shutdown
1393 and $service is one (or all) of: kaserver vlserver ptserver buserver
1395 Other points to bear in mind:
1397 - "vos remove" any RO volumes on the server to be shutdown. Create corresponding RO volumes on the 2nd fileserver after moving the RW. There are two reasons for this:
1398 1. An RO on the same partition ("cheap replica") requires less space than a full-copy RO.
1399 2. Because AFS always accesses RO volumes in preference to RW, traffic will be directed to the RO and therefore quiesce the load on the fileserver to be shutdown.
1401 - If the system to be shutdown has the lowest IP address there may be a brief delay in authenticating because of timeout experienced before contacting a second kaserver.
1403 ### <a name="3.12 How can I set up mail deli"></a> 3.12 How can I set up mail delivery to users with $HOMEs in AFS?
1405 There are many ways to do this. Here, only two methods are considered:
1407 Method 1: deliver into local filestore
1409 This is the simplest to implement. Set up your mail delivery to append mail to /var/spool/mail/$USER on one mailserver host. The mailserver is an AFS client so users draw their mail out of local filestore into their AFS $HOME (eg: inc).
1411 Note that if you expect your (AFS unauthenticated) mail delivery program to be able to process .forward files in AFS $HOMEs then you need to add "system:anyuser rl" to each $HOMEs ACL.
1415 - Simple to implement and maintain.
1416 - No need to authenticate into AFS.
1420 - It doesn't scale very well.
1421 - Users have to login to the mailserver to access their new mail.
1422 - Probably less secure than having your mailbox in AFS.
1423 - System administrator has to manage space in /var/spool/mail.
1425 Method 2: deliver into AFS
1427 This takes a little more setting up than the first method.
1429 First, you must have your mail delivery daemon AFS authenticated (probably as "postman"). The reauth example in afs-contrib shows how a daemon can renew its token. You will also need to setup the daemon startup soon after boot time to klog (see the -pipe option).
1431 Second, you need to set up the ACLs so that "postman" has lookup rights down to the user's $HOME and "lik" on $HOME/Mail.
1435 - Scales better than first method.
1436 - Delivers to user's $HOME in AFS giving location independence.
1437 - Probably more secure than first method.
1438 - User responsible for space used by mail.
1442 - More complicated to set up.
1443 - Need to correctly set ACLs down to $HOME/Mail for every user.
1444 - Probably need to store postman's password in a file so that the mail delivery daemon can klog after boot time. This may be OK if the daemon runs on a relatively secure host.
1446 An example of how to do this for IBM RISC System/6000 is auth-sendmail. A beta test version of auth-sendmail can be found in:
1448 <file:///afs/transarc.com/public/afs-contrib/doc/faq/auth-sendmail.tar.Z> <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/auth-sendmail.tar.Z>
1450 ### <a name="3.13 Should I replicate a _Read"></a> 3.13 Should I replicate a [[ReadOnly]] volume on the same partition and server as the [[ReadWrite]] volume?
1452 Yes, Absolutely! It improves the robustness of your served volumes.
1454 If [[ReadOnly]] volumes exist (note use of term **exist** rather than **are available**), Cache Managers will **never** utilize the [[ReadWrite]] version of the volume. The only way to access the RW volume is via the "dot" path (or by special mounting).
1456 This means if **all** RO copies are on dead servers, are offline, are behind a network partition, etc, then clients will not be able to get the data, even if the RW version of the volume is healthy, on a healthy server and in a healthy network.
1458 However, you are **very** strongly encouraged to keep one RO copy of a volume on the **same server and partition** as the RW. There are two reasons for this:
1460 1. The RO that is on the same server and partition as the RW is a clone (just a copy of the header - not a full copy of each file). It therefore is very small, but provides access to the same set of files that all other (full copy) [[ReadOnly]] volume do. Transarc trainers refer to this as the "cheap replica".
1461 2. To prevent the frustration that occurs when all your ROs are unavailable but a perfectly healthy RW was accessible but not used.
1463 If you keep a "cheap replica", then by definition, if the RW is available, one of the RO's is also available, and clients will utilize that site.
1465 ### <a name="3.14 Should I start AFS before"></a><a name="3.14 Should I start AFS before "></a> 3.14 Should I start AFS before NFS in /etc/inittab?
1467 Yes, it is possible to run both AFS and NFS on the same system but you should start AFS first.
1469 In IBM's AIX 3.2, your /etc/inittab would contain:
1471 rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS daemons
1472 rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS daemons
1474 With AIX, you need to load NFS kernel extensions before the AFS KEs in /etc/rc.afs like this:
1477 # example /etc/rc.afs for an AFS fileserver running AIX 3.2
1479 echo "Installing NFS kernel extensions (for AFS+NFS)"
1480 /etc/gfsinstall -a /usr/lib/drivers/nfs.ext
1481 echo "Installing AFS kernel extensions..."
1482 D=/usr/afs/bin/dkload
1483 ${D}/cfgexport -a ${D}/export.ext
1484 ${D}/cfgafs -a ${D}/afs.ext
1485 /usr/afs/bin/bosserver &
1487 ### <a name="3.15 Will AFS run on a multi-ho"></a> 3.15 Will AFS run on a multi-homed fileserver?
1489 (multi-homed = host has more than one network interface.)
1491 Yes, it will. However, AFS was designed for hosts with a single IP address. There can be problems if you have one host name being resolved to several IP addresses.
1493 Transarc suggest designating unique hostnames for each network interface. For example, a host called "spot" has two tokenring and one ethernet interfaces: spot-tr0, spot-tr1, spot-en0. Then, select which interface will be used for AFS and use that hostname in the [[CellServDB]] file (eg: spot-tr0).
1495 You also have to remember to use the AFS interface name with any AFS commands that require a server name (eg: vos listvol spot-tr0).
1497 There is a more detailed discussion of this in the August 1993 issue of "Cache Update" (see: <ftp://ftp.transarc.com/pub/afsug/newsletter/aug93>).
1499 The simplest way of dealing with this is to make your AFS fileservers single-homed (eg only use one network interface).
1501 At release 3.4 of AFS, it is possible to have multi-homed fileservers (but _not_ multi-homed database servers).
1503 ### <a name="3.16 Can I replicate my user's"></a><a name="3.16 Can I replicate my user's "></a> 3.16 Can I replicate my user's home directory AFS volumes?
1507 Users with $HOMEs in /afs normally have an AFS [[ReadWrite]] volume mounted in their home directory.
1509 You can replicate a RW volume but only as a [[ReadOnly]] volume and there can only be one instance of a [[ReadWrite]] volume.
1511 In theory, you could have RO copies of a user's RW volume on a second server but in practice this won't work for the following reasons:
1513 a) AFS has built-in bias to always access the RO copy of a RW volume.
1514 So the user would have a ReadOnly $HOME which is not too useful!
1516 b) Even if a) was not true you would have to arrange frequent
1517 synchronisation of the RO copy with the RW volume (for example:
1518 "vos release user.fred; fs checkv") and this would have to be
1519 done for all such user volumes.
1521 c) Presumably, the idea of replicating is to recover the $HOME
1522 in the event of a server crash. Even if a) and b) were not
1523 problems consider what you might have to do to recover a $HOME:
1525 1) Create a new RW volume for the user on the second server
1526 (perhaps named "user.fred.2").
1528 2) Now, where do you mount it?
1530 The existing mountpoint cannot be used because it already has
1531 the ReadOnly copy of the original volume mounted there.
1533 Let's choose: /afs/MyCell/user/fred.2
1535 3) Copy data from the RO of the original into the new RW volume
1538 4) Change the user's entry in the password file for the new $HOME:
1539 /afs/MyCell/user/fred.2
1541 You would have to attempt steps 1 to 4 for every user who had
1542 their RW volume on the crashed server. By the time you had done
1543 all of this, the crashed server would probably have rebooted.
1545 The bottom line is: you cannot replicate $HOMEs across servers.
1547 ### <a name="3.17 Which TCP/IP ports and pro"></a> 3.17 Which TCP/IP ports and protocols do I need to enable in order to operate AFS through my Internet firewall?
1549 Assuming you have already taken care of nameserving, you may wish to use an Internet timeserver for Network Time Protocol [35] [36]:
1553 A list of NTP servers is available via anonymous FTP from:
1555 - <http://www.eecis.udel.edu/~mills/ntp/servers.html>
1557 For further details on NTP see: <http://www.eecis.udel.edu/~ntp/>
1559 For a "minimal" AFS service which does not allow inbound or outbound klog:
1562 cachemanager 7001/udp
1570 (Ports in the 7020-7029 range are used by the AFS backup system, and won't be needed by external clients performing simple file accesses.)
1572 Additionally, for "klog" to work through the firewall you need to allow inbound and outbound UDP on ports >1024 (probably 1024<port<2048 would suffice depending on the number of simultaneous klogs).
1574 See also: <http://www-archive.stanford.edu/lists/info-afs/hyper95/0874.html>
1576 ### <a name="3.18 What is the Andrew Benchma"></a> 3.18 What is the Andrew Benchmark?
1578 "It is a script that operates on a collection of files constituting an application program. The operations are intended to represent typical actions of an average user. The input to the benchmark is a source tree of about 70 files. The files total about 200 KB in size. The benchmark consists of five distinct phases:
1580 I MakeDir - Construct a target subtree that is identical to the
1582 II Copy - Copy every file from the source subtree to the target subtree.
1583 III ScanDir - Traverse the target subtree and examine the status
1584 of every file in it.
1585 IV ReadAll - Scan every byte of every file in the target subtree.
1586 V Make - Complete and link all files in the target subtree."
1588 Source: <file:///afs/transarc.com/public/afs-contrib/doc/benchmark/Andrew.Benchmark.ps> <ftp://ftp.transarc.com/pub/afs-contrib/doc/benchmark/Andrew.Benchmark.ps>
1590 ### <a name="3.19 Is there a version of HP V"></a> 3.19 Is there a version of HP VUE login with AFS authentication?
1592 Yes, the availability of this is described in: <file:///afs/transarc.com/public/afs-contrib/pointers/HP-VUElogin.txt> <ftp://ftp.transarc.com/pub/afs-contrib/pointers/HP-VUElogin.txt>
1594 If you don't have access to the above, please contact Rajeev Pandey of Hewlett Packard whose email address is <rpandey@cv.hp.com>.
1596 ### <a name="3.20 How can I list which clien"></a> 3.20 How can I list which clients have cached files from a server?
1598 By using the following script:
1603 # AUTHOR Rainer Toebbicke <rtb@dxcern.cern.ch>
1605 # PURPOSE Display AFS clients which have grabbed files from a server
1608 echo "Usage: $0 <afs_server 1> ... <afsserver n>"
1612 /usr/afsws/etc/rxdebug -servers $n -allconn
1613 done | grep '^Connection' | \
1614 while read x y z ipaddr rest; do echo $ipaddr; done | sort -u |
1615 while read ipaddr; do
1617 n="`nslookup $ipaddr`"
1625 ### <a name="3.21 Do Backup volumes require"></a><a name="3.21 Do Backup volumes require "></a> 3.21 Do Backup volumes require as much space as [[ReadWrite]] volumes?
1629 The technique used is to create a new volume, where every file in the RW copy is pointed to by the new backup volume. The files don't exist in the BK, only in the RW volume. The backup volume therefore takes up very little space.
1631 If the user now starts modifying data, the old copy must not be destroyed.
1633 There is a Copy-On-Write bit in the vnode - if the fileserver writes to a vnode with the bit on it allocates a new vnode for the data and turns off the COW bit. The BK volume hangs onto the old data, and the RW volume slowly splits itself away over time.
1635 The BK volume is re-synchronised with the RW next time a "vos backupsys" is run.
1637 The space needed for the BK volume is directly related to the size of all files changed in the RW between runs of "vos backupsys".
1639 ### <a name="3.22 Should I run timed on my A"></a> 3.22 Should I run timed on my AFS client?
1643 The AFS Cache Manager makes use of NTP [35] [36] to synchronise time with your cell's NTP servers.
1645 Typically, one of your AFS cell's servers synchronises with an external NTP server and provides accurate time to your cell.
1647 ### <a name="3.23 Why should I keep /usr/vic"></a> 3.23 Why should I keep /usr/vice/etc/CellServDB current?
1649 On AFS clients, /usr/vice/etc/CellservDB, defines the cells and (their servers) that can be accessed via /afs.
1651 Over time, site details change: servers are added/removed or moved onto new network addresses. New sites appear.
1653 In order to keep up-to-date with such changes, the [[CellservDB]] file on each AFS client should be kept consistent with some master copy (at your site).
1655 As well as updating [[CellservDB]], your AFS administrator should ensure that new cells are mounted in your cell's root.afs volume.
1657 ### <a name="3.24 How can I keep /usr/vice/e"></a> 3.24 How can I keep /usr/vice/etc/CellServDB current?
1659 Do a daily copy from a master source and update the AFS kernel sitelist.
1661 The client [[CellServDB]] file must not reside under /afs and is best located in local filespace.
1663 Simply updating a client [[CellServDB]] file is not enough. You also need to update the AFS kernel sitelist by either: 1 rebooting the client or 1 running "fs newcell $cell\_name $server\_list" for each site in the [[CellServDB]] file.
1665 A script to update the AFS kernel sitelist on a running system is newCellServDB.
1667 <file:///afs/ece.cmu.edu/usr/awk/Public/newCellServDB> <ftp://ftp.ece.cmu.edu/pub/afs-tools/newCellServDB>
1669 One way to distribute [[CellServDB]] is to have a root cron job on each AFS client copy the file then run newCellServDB.
1675 # NAME syncCellServDB
1676 # PURPOSE Update local CellServDB file and update AFS kernel sitelist
1677 # USAGE run by daily root cron job eg:
1678 # 0 3 * * * /usr/local/sbin/syncCellServDB
1680 # NOTE "@cell" is a symbolic link to /afs/$this_cell_name
1682 src=/afs/@cell/service/etc/CellServDB
1683 dst=/usr/vice/etc/CellServDB
1684 xec=/usr/local/sbin/newCellServDB
1685 log=/var/log/syncCellServDB
1687 if [ -s ${src} ]; then
1688 if [ ${src} -nt ${dst} ]; then
1689 cp $dst ${dst}- && cp $src $dst && $xec 2>&1 >$log
1691 echo "master copy no newer: no processing to be done" >$log
1694 echo "zero length file: ${src}" >&2
1697 ### <a name="3.25 How can I compute a list o"></a> 3.25 How can I compute a list of AFS fileservers?
1699 Here is a Korn shell command to do it:
1701 stimpy@nick $ vos listvldb -cell $(cat /usr/vice/etc/ThisCell) \
1702 | awk '(/server/) {print $2}' | sort -u
1704 ### <a name="3.26 How can I set up anonymous"></a> 3.26 How can I set up anonymous FTP login to access /afs?
1706 The easiest way on a primarily "normal" machine (where you don't want to have everything in AFS) is to actually mount root.cell under ~ftp, and then symlink /afs to ~ftp/afs or whatever. It's as simple as changing the mountpoint in /usr/vice/etc/cacheinfo and restarting afsd.
1708 Note that when you do this, anon ftp users can go anywhere system:anyuser can (or worse, if you're using IP-based ACLs and the ftp host is PTS groups). The only "polite" solution I've arrived at is to have the ftp host machine run a minimal [[CellServDB]] and police my ACLs tightly.
1710 Alternatively, you can make ~ftp an AFS volume and just mount whatever you need under that - this works well if you can keep everything in AFS, and you don't have the same problems with anonymous "escapes" into /afs.
1712 Unless you need to do authenticating ftp, you are _strongly_ recommended using wu-ftpdv2.4 (or better).
1714 ### <a name="3.27 Where can I find the Andre"></a> 3.27 Where can I find the Andrew Benchmark?
1716 <file:///afs/transarc.com/public/afs-contrib/doc/faq/ab.tar.Z> [156k] <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/ab.tar.Z> [156k]
1718 This is a tar archive of <file:///afs/cs.cmu.edu/user/satya/ftp/ab/>
1720 ## <a name="4 Getting more information"></a> 4 Getting more information
1722 ### <a name="4.01 Is there an anonymous FTP"></a><a name="4.01 Is there an anonymous FTP "></a> 4.01 Is there an anonymous FTP site with AFS information?
1724 Yes, it is: ftp.transarc.com
1726 A brief summary of contents:
1728 <table border="1" cellpadding="0" cellspacing="0">
1730 <th align="center" bgcolor="#99CCCC"><strong> Path </strong></th>
1731 <th align="center" bgcolor="#99CCCC"><strong> Contents </strong></th>
1734 <td> pub/afsug/README </td>
1735 <td> AFS user group </td>
1738 <td> pub/afsug/newsletter/ </td>
1739 <td> AFS user group newsletters </td>
1742 <td> pub/afs-contrib/ </td>
1743 <td> Contributed by other groups </td>
1746 <td> pub/afs-contrib/bin/README </td>
1747 <td> other client ports (US-only) </td>
1750 <td> pub/afs-contrib/bin.export/ </td>
1751 <td> other client ports </td>
1754 <td> pub/afs-contrib/tools/MANIFEST </td>
1755 <td> miscellaneous tools </td>
1758 <td> pub/afs-contrib/src/README </td>
1759 <td> submissions from source licensees </td>
1762 <td> pub/afs-contrib/doc/MANIFEST </td>
1763 <td> documentation </td>
1766 <td> pub/afs-contrib/pointers/MANIFEST </td>
1767 <td> infomation in other places </td>
1770 <td> pub/afsps/README </td>
1771 <td> AFS product support </td>
1774 <td> pub/afsps/doc/ </td>
1775 <td> release notes, SUPPORTED_SYSTEMS.afs.* </td>
1778 <td> pub/afsps/doc/progint/ </td>
1779 <td> AFS programming interface docs </td>
1783 These directories are also accessible via AFS. For example: <file:///afs/transarc.com/public/anon-ftp/pub/afs-contrib>
1785 (NB "pub" => "public/anon-ftp/pub" when using AFS to access these.)
1787 ### <a name="4.02 Which USENET newsgroups di"></a> 4.02 Which USENET newsgroups discuss AFS?
1789 alt.filesystems.afs and occasionally in comp.unix.admin.
1791 ### <a name="4.03 Where can I get training i"></a> 4.03 Where can I get training in AFS?
1793 Transarc provide user and administrator courses. These can be provided at the customer site or at Transarc's offices.
1795 Transarc's education coordinator may be contacted by:
1799 <dd> +1 412 338 4363 email: <a href="mailto:education@transarc.com">education@transarc.com</a></dd>
1802 <http://www.transarc.com>
1804 ### <a name="4.04 Where can I find AFS resou"></a> 4.04 Where can I find AFS resources in World Wide Web (WWW)?
1806 Here are some I have found (please let me know if you find more):
1808 a) A collection of AFS information maintained by Derrick Brashear at CMU:
1810 http://www.cs.cmu.edu/afs/andrew.cmu.edu/usr/shadow/www/afs.html
1811 (Also accessible in: /afs/andrew.cmu.edu/usr/shadow/www)
1813 b) AFS Beginners Guide (ALW/NIH):
1814 http://www.alw.nih.gov/Docs/AFS/AFS_toc.html
1816 c) NCSA AFS User Guide:
1817 http://www.ncsa.uiuc.edu/Pubs/UserGuides/AFSGuide/AFSv2.1Book.html
1819 d) Transarc AFS Product Information:
1820 http://www.transarc.com/dfs/public/www/htdocs/.hosts/external/Product/EFS/AFS/afsoverview.html
1822 e) CERN AFS User's Guide:
1823 http://wsspinfo.cern.ch/file/doc/afsug.html
1825 f) MIT SIPB's Inessential AFS
1826 http://web.mit.edu/afs/sipb.mit.edu/project/doc/afs/html/afs-new.html
1828 g) Stanford University hypermail archive of info-afs@transarc.com
1829 http://www-archive.stanford.edu/lists/info-afs.html
1832 http://www.umlug.umd.edu/linuxafs/
1834 ### <a name="4.05 Is there a mailing list fo"></a> 4.05 Is there a mailing list for AFS topics?
1836 Yes, it is <info-afs@transarc.com>.
1838 An automated program called Majordomo is now handling the info-afs list. To join the mailing list, send a message to:
1840 <majordomo@transarc.com>
1842 In the body (not the Subject line) of the message, type:
1848 $ mail -s "subscribe to info-afs" <majordomo@transarc.com> <<% subscribe info-afs %
1852 $ mail -s "unsubscribe from info-afs" <majordomo@transarc.com> <<% unsubscribe info-afs
1854 ### <a name="4.06 Where can I find an archiv"></a> 4.06 Where can I find an archive of <info-afs@transarc.com>?
1856 There is a hypermail archive at: <http://www-archive.stanford.edu/lists/info-afs.html>
1858 ### <a name="4.07 Where can I find an archiv"></a> 4.07 Where can I find an archive of alt.filesystems.afs?
1860 <file:///afs/ibm.uk/common/archive/alt.filesystems.afs/>
1862 Both the <info-afs@transarc.com> and alt.filesystems.afs archives are incomplete. If you have material to contribute, please let me know.
1864 ### <a name="4.08 Where can I find AFS relat"></a> 4.08 Where can I find AFS related GIFs?
1866 <file:///afs/transarc.com/public/afs-contrib/doc/faq/images/index.html> <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/images/index.html>
1868 ### <a name="4.09 Gibt es eine deutsche AFS"></a><a name="4.09 Gibt es eine deutsche AFS "></a> 4.09 Gibt es eine deutsche AFS Benutzer Gruppe?
1870 Ja, wenn Sie mitmachen wollen, schicken Sie bitte eine E-Mail an:
1872 <afsdeu-request@hrz.th-darmstadt.de>
1874 Ueber diese Adresse werden "subscribe" und "unsubscribe" Requests bearbeitet.
1876 ### <a name="4.10 Donde puedo encontrar info"></a> 4.10 Donde puedo encontrar informacion en Espanol sobre AFS?
1878 Hay algunas notas en Espanol sobre AFS en: <http://w3.ing.puc.cl/~cet/afs.html>
1880 ## <a name="5 About the AFS faq"></a> 5 About the AFS faq
1882 I started compiling the FAQ after attending an AFS administrators class and while waiting for the distribution tape to arrive from Transarc (back in July 93). The initial goal was to assist users at my site to understand AFS issues.
1884 The FAQ seemed to be a more widely useful resource so it was made generally available.
1886 I hope you have found the AFS FAQ useful.
1888 Your criticism or suggestions for improving it are welcome, so please don't hesitate to email your views (or just say "hello").
1890 This compilation is dedicated to my AFS teacher and all those who inspire through good humour, enthusiasm, wit and wisdom. -- paul <http://acm.org/~mpb/homepage.html>
1892 ### <a name="5.01 How can I get a copy of th"></a> 5.01 How can I get a copy of the AFS faq?
1894 If you do make a copy, please be aware that this compilation changes over time: you will need to do a periodic re-copy to keep your copy up-to-date.
1896 There are two reference sources:
1898 1) The text only version, available via AFS from:
1899 file:///afs/transarc.com/public/afs-contrib/doc/faq/afs.faq
1901 2) The World Wide Web (HTML) version, available via URL:
1902 http://www.angelfire.com/hi/plutonic/afs-faq.html
1904 There are several other ways to get a copy.
1906 via AFS: <file:///afs/transarc.com/public/afs-contrib/doc/faq/afs.faq>
1908 via FTP: <ftp://rtfm.mit.edu/pub/usenet/news.answers/afs-faq>
1910 via WWW: <http://www.angelfire.com/hi/plutonic/afs-faq.html>
1912 via Wiki: <http://grand.central.org/twiki/bin/view/AFSLore/AFSFrequentlyAskedQuestions>
1916 From time to time this faq will be posted to the USENET newsgroups: alt.filesystems.afs alt.answers news.answers
1920 The AFS faq is now available in the file $cd\_mount\_point/faqs/alt/filesystems.afs on CD-ROM "Internet Info" (containing 17,420 documents including other FAQs, RFCs, IENs, etc) from:
1922 Walnut Creek CDROM phone: 1 800 786-9907 (US tollfree)
1923 4041 Pike Lane, Ste D-www +1 510 674-0783
1924 Concord, CA 94250 fax: +1 510 674-0821
1925 United States of America email: orders@cdrom.com
1926 WWW: http://www.cdrom.com/
1928 ### <a name="5.02 How can I get my question"></a><a name="5.02 How can I get my question "></a> 5.02 How can I get my question (and answer) into the AFS faq?
1930 Comments and contributions are welcome, please send to: <mpb@acm.org>
1932 I am looking for reviewers to help me check the material here, please let me know if you would like to help.
1934 ### <a name="5.03 How can I access the AFS f"></a> 5.03 How can I access the AFS faq via the World Wide Web?
1936 To access the World Wide Web you either need your own browser or have telnet access to WWW servers.
1938 WWW browsers exist for most machines. Here's a list of some browsers;
1940 Name System/requirements Available from (among others) <code>**== =================**</code> <code>**==========**</code> Mosaic X windows, MS-Windows, Mac ftp.ncsa.uiuc.edu /Web lynx vt100 ftp.wustl.edu /packages/www/lynx
1942 From your own browser, OPEN or GO to the following document:
1944 <http://www.angelfire.com/hi/plutonic/afs-faq.html>
1946 It is much better to run your own browser but if this is not possible there are several WWW servers accessible via telnet:
1948 \* telnet info.cern.ch then type: go <http://www.angelfire.com/hi/plutonic/afs-faq.html>
1950 \* telnet www.njit.edu (login: www) then type: g <http://www.angelfire.com/hi/plutonic/afs-faq.html>
1952 \* telnet ukanaix.cc.ukans.edu (login: www, needs vt100) then type: ghttp://www.angelfire.com/hi/plutonic/afs-faq.html
1954 ## <a name="6 Bibliography"></a> 6 Bibliography
1956 If documentation is available via anonymous FTP it is indicated by a World Wide Web URL like:
1958 <ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS>
1960 where: athena-dist.mit.edu is the anonymous FTP site and pub/kerberos/doc/usenix.PS is the filename
1962 Similarly, for those who have appropriate access, documents available via AFS are shown with the format:
1966 [1] John H Howard, Michael L Kazar, Sherri G Menees, David A Nichols, M Satyanarayanan, Robert N Sidebotham, Michael J West "Scale and Performance in a Distributed File System", ACM Transactions on Computer Systems, Vol. 6, No. 1, Feb 1988 pp 51-81.
1968 [2] Michael L Kazar, "Synchronisation and Caching Issues in the Andrew File System", USENIX Proceedings, Dallas, TX, Winter 1988
1970 [3] Alfred Z Spector, Michael L Kazar, "Uniting File Systems", UNIX Review, March 1989
1972 [4] Johna Till Johnson, "Distributed File System brings LAN Technology to WANs", Data Communications, November 1990, pp 66-67.
1974 [5] Michael Padovano, PADCOM Associates, "AFS widens your horizons in distributed computing", Systems Integration, March 1991
1976 [6] Steve Lammert, "The AFS 3.0 Backup System", LISA IV Conference Proceedings, Colorado Springs, Colorado, October 1990.
1978 [7] Michael L Kazar, Bruce W Leverett, Owen T Anderson, Vasilis Apostolides, Beth A Bottos, Sailesh Chutani, Craig F Everhart, W Anthony Mason, Shu-Tsui Tu, Edward R Zayas, "DEcorum File System Architectural Overview", USENIX Conference Proceedings, Anaheim, Texas, Summer 1990.
1980 [8] "AFS Drives DCE Selection", Digital Desktop, Vol 1 No 6 Sept 1990.
1982 [9] James J Kistler, M Satyanarayanan, "Disconnected Operation in the Coda Filesystem", CMU School of Computer Science technical report, CMU-CS-91-166 26th July 1991.
1984 [10] Puneet Kumar. M Satyanarayanan, "Log-based Directory Resolution in the Coda File System", CMU School of Computer Science internal document, 2 July 1991.
1986 [11] Edward R Zayas, "Administrative Cells: Proposal for Cooperative Andrew File Systems", Information Technology Center internal document, Carnegie-Mellon University, 25th June 1987
1988 [12] Ed Zayas, Craig Everhart, "Design and Specification of the Cellular Andrew Environment", Information Technology Center, Carnegie-Mellon University, CMU-ITC-070, 2 August 1988
1990 [13] Kazar, Michael L, Information Technology Center, Carnegie-Mellon University, "Ubik - A library for Managing Ubiquitous Data", ITCID, Pittsburgh, PA, 1988
1992 [14] Kazar, Michael L, Information Technology Center, Carnegie-Mellon University, "Quorum Completion", ITCID, Pittsburgh, PA, 1988
1994 [15] SP Miller, BC Neuman, JI Schiller, JH Saltzer, "Kerberos Authentication and Authorization System", Project Athena technical Plan, Section E.2.1, MIT, December 1987 <ftp://athena-dist.mit.edu/pub/kerberos/doc/techplan.PS> <ftp://athena-dist.mit.edu/pub/kerberos/doc/techplan.txt> <file:///afs/watson.ibm.com/projects/agora/papers/kerberos/techplan.PS>
1996 [16] Bill Bryant, "Designing an Authentication System: a Dialogue in Four Scenes", Project Athena internal document, MIT, draft of 8th February 1988 <ftp://athena-dist.mit.edu/pub/kerberos/doc/dialogue.PS> <ftp://athena-dist.mit.edu/pub/kerberos/doc/dialogue.mss> <file:///afs/watson.ibm.com/projects/agora/papers/kerberos/dialogue.PS>
1998 [17] Edward R Zayas, "AFS-3 Programmer's Reference: Architectural Overview", Transarc Corporation, FS-00-D160, September 1991 <ftp://ftp.transarc.com/pub/afsps/doc/progint/archov-doc.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/archov-doc.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/archov-doc.ps> <file:///afs/transarc.com/public/afsps/doc/progint/archov-doc.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/archov-doc.ps>
2000 [18] "AFS Programmer's Reference: Authentication Server Interface", Transarc Corporation, 12th April 1993 <ftp://ftp.transarc.com/pub/afsps/doc/progint/asrv-ispec.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/asrv-ispec.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/asrv-ispec.ps> <file:///afs/transarc.com/public/afsps/doc/progint/asrv-ispec.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/asrv-ispec.ps>
2002 [19] Edward R Zayas, "AFS-3 Programmer's Reference: BOS Server Interface", Transarc Corporation, FS-00-D161, 28th August 1991 <ftp://ftp.transarc.com/pub/afsps/doc/progint/bsrv-spec.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/bsrv-spec.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/bsrv-spec.ps> <file:///afs/transarc.com/public/afsps/doc/progint/bsrv-spec.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/bsrv-spec.ps>
2004 [20] Edward R Zayas, "AFS-3 Programmer's Reference: File Server/Cache Manager Interface", Transarc Corporation, FS-00-D162, 20th August 1991 <ftp://ftp.transarc.com/pub/afsps/doc/progint/fscm-ispec.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/fscm-ispec.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/fscm-ispec.ps> <file:///afs/transarc.com/public/afsps/doc/progint/fscm-ispec.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/fscm-ispec.ps>
2006 [21] Edward R Zayas, "AFS-3 Programmer's Reference: Specification for the Rx Remote Procedure Call Facility", Transarc Corporation, FS-00-D164, 28th August 1991 <ftp://ftp.transarc.com/pub/afsps/doc/progint/rx-spec.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/rx-spec.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/rx-spec.ps> <file:///afs/transarc.com/public/afsps/doc/progint/rx-spec.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/rx-spec.ps>
2008 [22] Edward R Zayas, "AFS-3 Programmer's Reference: Volume Server/Volume Location Server Interface", Transarc Corporation, FS-00-D165, 29th August 1991 <ftp://ftp.transarc.com/pub/afsps/doc/progint/vvl-spec.ps> <ftp://ftp.transarc.com/pub/afsps/doc/progint/vvl-spec.dvi> <file:///afs/transarc.com/public/afsps/doc/progint/vvl-spec.ps> <file:///afs/transarc.com/public/afsps/doc/progint/vvl-spec.dvi> <file:///afs/watson.ibm.com/projects/agora/papers/afs/vvl-spec.ps>
2010 [23] "AFS User Guide", Transarc Corporation, FS-D200-00.08.3
2012 [24] "AFS Commands Reference Manual", Transarc Corporation, FS-D200-00.11.3
2014 [25] "AFS Systems Administrators Guide", Transarc Corporation, FS-D200-00.10.3
2016 [26] Steven M. Bellovin, Michael Merritt "Limitations of the Kerberos Authentication System", Computer Communications Review, October 1990, Vol 20 #5, pp. 119-132 [ftp://research.att.com/dist/internet\_security/kerblimit.usenix.ps](ftp://research.att.com/dist/internet_security/kerblimit.usenix.ps) <file:///afs/watson.ibm.com/projects/agora/papers/kerberos/limitations.PS>
2018 [27] Jennifer G. Steiner, Clifford Neuman, Jeffrey I. Schiller "Kerberos: An Authentication Service for Open Network Systems" <ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS> <ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.txt>
2020 [28] Barry Jaspan "Kerberos Users' Frequently Asked Questions" <ftp://rtfm.mit.edu/pub/usenet/news.answers/kerberos-faq/user> <http://www.ov.com/misc/krb-faq.html>
2022 [29] P. Honeyman, L.B. Huston, M.T. Stolarchuk "Hijacking AFS" <ftp://ftp.sage.usenix.org/pub/usenix/winter92/hijacking-afs.ps.Z> [file:///afs/watson.ibm.com/projects/agora/papers/afs/afs\_hijacking.ps](file:///afs/watson.ibm.com/projects/agora/papers/afs/afs_hijacking.ps)
2024 [30] R.N. Sidebotham "Rx: Extended Remote Procedure Call" Proceedings of the Nationwide File System Workshop Information Technology Center, Carnegie Mellon University, (August 1988)
2026 [31] R.N. Sidebotham "Volumes: The Andrew File System Data Structuring Primitive" Technical Report CMU-ITC-053, Information Technology Center, Carnegie Mellon University, (August 1986)
2028 [32] Cohen, David L. "AFS: NFS on steroids", LAN Technology March 1993 v9 n3 p51(9) [ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/NFS\_on\_steroids](ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/NFS_on_steroids)
2030 [33] Marybeth Schultz "AFS Troubleshooting Tools" Transarc Corporation, January 11 1993, draft document <ftp://ftp.transarc.com/pub/afsps/doc/trguide/external.afsug.ps>
2032 [34] William Stallings "Kerberos Keeps the Enterprise Secure" Data Communications, October 1994, Vol 23 No 14 Page 103
2034 [35] DL Mills "Internet Time Synchronization: the Network Time Protocol" RFC 1129, October 1989 <ftp://nic.ddn.mil/rfc/rfc1129.ps>
2036 [36] DL Mills "Network Time Protocol (Version 3) Specification, Implementation and Analysis" RFC 1305, March 1992 <ftp://nic.ddn.mil/rfc/rfc1305.tar.Z> <ftp://nic.ddn.mil/rfc/rfc1305.txt>
2038 [37] Craig Everhart "Conventions for Names in the Service Directory in the AFS Distributed File System" March 1990 <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/service-spec.ez.ps> <ftp://ftp.transarc.com/pub/afs-contrib/doc/faq/service-spec.ez> <file:///afs/transarc.com/public/afs-contrib/doc/faq/service-spec.ez> <file:///afs/transarc.com/public/afs-contrib/doc/faq/service-spec.ez.ps>
2040 [38] AFS Programmer's Reference Manual <ftp://ftp.transarc.com/pub/afsps/doc/progref/3.0/> <file:///afs/transarc.com/public/afsps/doc/progref/3.0/>
git://git.openafs.org / openafs-wiki.git / blob