1 Template: openafs-client/cell-info
3 _Description: DB server host names for your home cell:
4 AFS uses the file /etc/openafs/CellServDB to hold the list of servers that
5 should be contacted to find parts of a cell. The cell you claim this
6 workstation belongs to is not in that file. Enter the host names of the
7 database servers separated by spaces. IMPORTANT: If you are creating a new
8 cell and this machine is to be a database server in that cell, only enter
9 this machine's name; add the other servers later after they are
10 functioning. Also, do not enable the AFS client to start at boot on this
11 server until the cell is configured. When you are ready you can edit
12 /etc/openafs/afs.conf.client to enable the client.
14 Template: openafs-client/thiscell
16 _Description: AFS cell this workstation belongs to:
17 AFS filespace is organized into cells or administrative domains.
18 Each workstation belongs to one cell. Usually the cell is the DNS
19 domain name of the site.
21 Template: openafs-client/cachesize
24 _Description: Size of AFS cache in kB:
25 AFS uses an area of the disk to cache remote files for faster
26 access. This cache will be mounted on /var/cache/openafs. It is
27 important that the cache not overfill the partition it is located
28 on. Often, people find it useful to dedicate a partition to their
31 Template: openafs-client/run-client
34 _Description: Run Openafs client now and at boot?
35 Normally, most users who install the openafs-client package expect AFS to
36 be mounted automatically at boot. However, if you are planning on
37 setting up a new cell or are on a laptop, you may not want it started at
38 boot time. If you choose not to start AFS at boot, run
39 service openafs-client force-start to start the client when you wish
42 Template: openafs-client/afsdb
45 _Description: Look up AFS cells in DNS?
46 In order to contact an AFS cell, you need the IP addresses of the cell's
47 database servers. Normally, this information is read from
48 /etc/openafs/CellServDB. However, if Openafs cannot find a cell in that
49 file, it can use DNS to look for AFSDB records that contain the
52 Template: openafs-client/crypt
55 _Description: Encrypt authenticated traffic with AFS fileserver?
56 AFS provides a weak form of encryption that can optionally be used between
57 a client and the fileservers. While this encryption is weaker than DES
58 and thus is not sufficient for highly confidential data, it does provide
59 some confidentiality and is likely to make the job of a casual attacker
60 significantly more difficult.
62 Template: openafs-client/dynroot
64 __Choices: Yes, Sparse, No
66 _Description: Dynamically generate the contents of /afs?
67 /afs generally contains an entry for each cell that a client can talk to.
68 Traditionally, these entries were generated by servers in the client's
69 home cell. However, OpenAFS clients can generate the contents of /afs
70 dynamically based on the contents of /etc/openafs/CellServDB and DNS.
72 If you generate /afs dynamically, you may need to create
73 /etc/openafs/CellAlias to include aliases for common cells. (The syntax
74 of this file is one line per alias, with the cell name, a space, and then
75 the alias for that cell.)
77 The Sparse option is the same as Yes except that, rather than populating
78 /afs from /etc/openafs/CellServDB immediately, cells other than the local
79 cell will not appear until they are accessed. Cell aliases as set in the
80 CellAlias file are shown as normal, although they may appear to be
81 dangling links until traversed.
83 Template: openafs-client/fakestat
86 _Description: Use fakestat to avoid hangs when listing /afs?
87 Because AFS is a global file space, operations on the /afs directory can
88 generate significant network traffic. If some AFS cells are unavailable
89 then looking at /afs using ls or a graphical file browser may hang your
90 machine for minutes. AFS has an option to simulate answers to these
91 operations locally to avoid these hangs. You want this option under most