From 48d3ec164bf76708c10d817e7601105cc2798153 Mon Sep 17 00:00:00 2001 From: Russ Allbery Date: Mon, 24 May 2010 14:28:01 -0500 Subject: [PATCH] Update fs {get,set}serverprefs documentation for DNS Mention in the fs getserverprefs and fs setserverprefs documentation that VL servers may also come from DNS AFSDB and SRV records. Document that SRV record information is not (yet) properly used. Change-Id: I223efedf4d00ac1b57b3dce74a807790691abdbf Reviewed-on: http://gerrit.openafs.org/2015 Tested-by: Russ Allbery Tested-by: Derrick Brashear Reviewed-by: Derrick Brashear --- doc/man-pages/README | 3 --- doc/man-pages/pod1/fs_getserverprefs.pod | 21 +++++++++++---------- doc/man-pages/pod1/fs_setserverprefs.pod | 11 +++++++---- 3 files changed, 18 insertions(+), 17 deletions(-) diff --git a/doc/man-pages/README b/doc/man-pages/README index e5e8fb51e5..00577de604 100644 --- a/doc/man-pages/README +++ b/doc/man-pages/README @@ -230,9 +230,6 @@ Known Problems don't just report the deficiency again, but any contributions towards fixing it are greatly appreciated. - * Some of the documentation in fs getserverprefs needs minor updates to - reflect what happens in the dynroot case. - * There are lingering references to AFS Development or AFS Product Support in descriptions of options that one should generally not use. Also, all of the manual references refer to the "IBM" manual. diff --git a/doc/man-pages/pod1/fs_getserverprefs.pod b/doc/man-pages/pod1/fs_getserverprefs.pod index 0bb00c4ef3..c87728390d 100644 --- a/doc/man-pages/pod1/fs_getserverprefs.pod +++ b/doc/man-pages/pod1/fs_getserverprefs.pod @@ -33,17 +33,18 @@ types of rank, lower integer values are more preferred. The Cache Manager stores ranks in kernel memory. Once set, a rank persists until the machine reboots, or until the B command is -used to change it. The reference page for the B command -explains how the Cache Manager sets default ranks, and how to use that -command to change the default values. +used to change it. L explains how the Cache Manager +sets default ranks, and how to use that command to change the default +values. -Default VL Server ranks range from 10,000 to 10,126, and the Cache Manager -assigns them to every machine listed in its copy of the -F file. When the Cache Manager needs to fetch -VLDB information from a cell, it compares the ranks for the VL Server -machines belonging to that cell, and attempts to contact the VL Server -with the lowest integer rank. If the Cache Manager cannot reach the VL -Server (because of server process, machine or network outage), it tries to +Default VL Server ranks range from 10,000 to 10,126. The Cache Manager +assigns ranks to every machine listed in its copy of the +F file or found via DNS AFSDB or SRV records for +the cell when it initializes. When the Cache Manager needs to fetch VLDB +information from a cell, it compares the ranks for the VL Server machines +belonging to that cell, and attempts to contact the VL Server with the +lowest integer rank. If the Cache Manager cannot reach the VL Server +(because of server process, machine or network outage), it tries to contact the VL Server with the next lowest integer rank, and so on. If all of a cell's VL Server machines are unavailable, the Cache Manager cannot fetch data from the cell. diff --git a/doc/man-pages/pod1/fs_setserverprefs.pod b/doc/man-pages/pod1/fs_setserverprefs.pod index 9b4c0c3ffd..299f840f76 100644 --- a/doc/man-pages/pod1/fs_setserverprefs.pod +++ b/doc/man-pages/pod1/fs_setserverprefs.pod @@ -51,10 +51,13 @@ change it. The Cache Manager sets default VL Server preference ranks as it initializes, randomly assigning a rank from the range 10,000 to 10,126 to -each of the machines listed in the local F -file. Machines from different cells can have the same rank, but this does -not present a problem because the Cache Manager consults only one cell's -ranks at a time. +each of the machines liste din the local F +file. If DNS is used to locate VL Servers, the Cache Manager will assign a +rank to every server configured in an AFSDB or SRV record for that +cell. Currently, the priority and weight information from SRV records is +not used. Machines from different cells can have the same rank, but this +does not present a problem because the Cache Manager consults only one +cell's ranks at a time. The Cache Manager sets default preference ranks for file server machine as it fetches volume location information from the VLDB. Each time it learns