From 48abcd3eb789fdd24a2e0a6155b25e6979a39ae0 Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Fri, 7 Sep 2007 12:49:01 +0000 Subject: [PATCH] regen --- doc/arm/Bv9ARM.ch08.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html index b2930915d5..05d7dd32fe 100644 --- a/doc/arm/Bv9ARM.ch08.html +++ b/doc/arm/Bv9ARM.ch08.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -70,16 +70,16 @@

Incrementing and Changing the Serial Number

- Zone serial numbers are just numbers — they aren't date - related. A lot of people set them to a number that represents a - date, usually of the form YYYYMMDDRR. A number of people - tested these numbers for Y2K compliance and set the number - to the year 2000 to see if it would work. They then tried to restore - the old serial number. This caused problems because serial - numbers are used to indicate that a zone has been updated. If the - serial number on the slave server is lower than the serial number - on the master, the slave server will attempt to update its copy of - the zone. + Zone serial numbers are just numbers — they aren't + date related. A lot of people set them to a number that + represents a date, usually of the form YYYYMMDDRR. + Occasionally they will make a mistake and set them to a + "date in the future" then try to correct them by setting + them to the "current date". This causes problems because + serial numbers are used to indicate that a zone has been + updated. If the serial number on the slave server is + lower than the serial number on the master, the slave + server will attempt to update its copy of the zone.

Setting the serial number to a lower number on the master