jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-19 07:20:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

DEVEL15-man-page-cellservdb-updates-20090518

Browse Source 
FIXES 124794
LICENSE IPL10

Note in CellServDB man page that it's also used to populate root.afs for
a -dynroot client.  Also document the dynamic lookup of database servers
with -afsdb and provide some more information about when CellServDB has to
contain the cell and when it doesn't.

Mark the backup server as optional, and indicate that the authentication
server is deprecated and CellServDB isn't required for authentication if
Kerberos v5 and aklog are used.


(cherry picked from commit 6df6046813)
This commit is contained in:
Steven Jenkins 2009-05-19 00:35:55 +00:00 committed by Russ Allbery
parent 72f6f09b3e
commit 7be1233224
2 changed files with 37 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/man-pages/README
View File

@ -232,7 +232,6 @@ Known Problems
* The following installed commands have no man pages:
klog.krb
krb.conf
pagsh.krb
tokens.krb
@ -265,8 +264,6 @@ Known Problems
* The salvager actually creates a bunch of SalvageLog files and then
combines them, but the SalvageLog man page doesn't reflect this.
* The CellServDB documentation hasn't been updated for -dynroot.
* The aklog man page isn't in POD. (Neither is the mpp man page, but
I don't think we care about it and it's not currently installed.)

57
doc/man-pages/pod5/CellServDB.pod
View File

@ -15,10 +15,10 @@ servers and lists only the database servers in the local cell.
Along with AFSDB entries in DNS, the client version of the CellServDB file
lists the database server machines in the local cell and any foreign cell
that is to be accessible from the local client machine. Database server
machines run the Authentication Server (optional), Backup Server,
Protection Server, and Volume Location (VL) Server (the B<kaserver>,
B<buserver>, B<ptserver>, and B<vlserver>) processes, which maintain the
cell's administrative AFS databases.
machines run the Authentication Server (optional), Backup Server
(optional), Protection Server, and Volume Location (VL) Server (the
B<kaserver>, B<buserver>, B<ptserver>, and B<vlserver>) processes, which
maintain the cell's administrative AFS databases.
The Cache Manager and other processes running on a client machine use the
list of a cell's database server machines when performing several common
@ -33,16 +33,25 @@ the location of the volume containing a requested file or directory.
=item *
Authenticating users. Client-side authentication programs (such as an
AFS-modified login utility or the B<klog> command interpreter) contact the
Authentication Server to obtain a server ticket, which the AFS server
processes accept as proof that the user is authenticated.
Creating, viewing, and manipulating protection groups. The B<pts> command
interpreter contacts the Protection Server when users create protection
groups or request information from the Protection Database.
=item *
Creating protection groups. The B<pts> command interpreter contacts the
Protection Server when users create protection groups or request
information from the Protection Database.
Populating the contents of the fake F<root.afs> volume mounted at F</afs>
(or the alternative mount point specified in F<cacheinfo>) when B<afsd> is
run in C<-dynroot> mode. The default contents of this directory will
match the cells listed in the client F<CellServDB> file.
=item *
Authenticating users. Client-side authentication programs (such as an
AFS-modified login utility or the B<klog> command interpreter) contact the
Authentication Server to obtain a server ticket, which the AFS server
processes accept as proof that the user is authenticated. This only
applies to AFS cells using the deprecated Authentication Server instead of
Kerberos v5 and B<aklog>.
=back
@ -54,6 +63,14 @@ machine is added to or removed from a cell. To update the kernel-resident
list of database server machines without rebooting, use the B<fs newcell>
command.
If the client attempts to access an AFS cell not listed in F<CellServDB>
and B<afsd> was started with the B<-afsdb> option, the Cache Manager will
attempt an AFSDB DNS record lookup and dynamically add the database server
locations for that cell based on the result of the DNS query. If the
B<-afsdb> option was not used, all AFS cells that will be accessed by a
client machine must either be listed in F<CellServDB> or added with the
B<fs newcell> command.
The F<CellServDB> file is in ASCII format and must reside in the
F</usr/vice/etc> directory on each AFS client machine. Use a text editor
to create and maintain it.
@ -69,15 +86,15 @@ server machines.
The server version of the F<CellServDB> file lists the local cell's
database server machines. These machines run the Authentication Server
(optional), Backup Server, Protection Server, and Volume Location (VL)
Server (the B<kaserver>, B<buserver>, B<ptserver>, and B<vlserver>)
processes, which maintain the cell's administrative AFS databases. The
initial version of the file is created with the B<bos setcellname> command
during the installation of the cell's server machine, which is
automatically recorded as the cell's first database server machine. When
adding or removing database server machines, be sure to update this file
appropriately. It must reside in the F</usr/afs/etc> directory on each AFS
server machine.
(optional), Backup Server (optional), Protection Server, and Volume
Location (VL) Server (the B<kaserver>, B<buserver>, B<ptserver>, and
B<vlserver>) processes, which maintain the cell's administrative AFS
databases. The initial version of the file is created with the B<bos
setcellname> command during the installation of the cell's server machine,
which is automatically recorded as the cell's first database server
machine. When adding or removing database server machines, be sure to
update this file appropriately. It must reside in the F</usr/afs/etc>
directory on each AFS server machine.
The database server processes consult the F<CellServDB> file to learn
about their peers, with which they must maintain constant connections in