1 files changed, 180 insertions, 0 deletions
diff --git a/sag-0.6.1-www/sag-0.6.1.html/x2504.html b/sag-0.6.1-www/sag-0.6.1.html/x2504.html
new file mode 100644
index 0000000..5611eea
--- /dev/null
+++ b/sag-0.6.1-www/sag-0.6.1.html/x2504.html
@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//Norman Walsh//DTD DocBook HTML 1.0//EN">
+<HTML
+><HEAD
+><TITLE
+>When the clock is wrong</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet"><LINK
+REL="HOME"
+TITLE="The Linux System Administrators' Guide"
+HREF="book1.html"><LINK
+REL="UP"
+TITLE="Keeping Time"
+HREF="c2432.html"><LINK
+REL="PREVIOUS"
+TITLE="Showing and setting time"
+HREF="x2457.html"><LINK
+REL="NEXT"
+TITLE="Glossary (DRAFT)"
+HREF="g2516.html"></HEAD
+><BODY
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Linux System Administrators' Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="x2457.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 11. Keeping Time</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="g2516.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2504"
+>When the clock is wrong</A
+></H1
+><P
+> The Linux software clock is not always accurate.  It is
+	kept running by a periodic <I
+CLASS="GLOSSTERM"
+>timer interrupt</I
+>
+	generated by PC hardware.  If the system has too many processes
+	running, it may take too long to service the timer interrupt, and
+	the software clock starts slipping behind.  The hardware clock
+	runs independently and is usually more accurate.  If you boot
+	your computer often (as is the case for most systems that aren't
+	servers), it will usually keep fairly accurate time.  </P
+><P
+> If you need to adjust the hardware clock, it is usually
+	simplest to reboot, go into the BIOS setup screen, and do it
+	from there.  This avoids all trouble that changing system time
+	might cause.  If doing it via BIOS is not an option, set the new
+	time with <B
+CLASS="COMMAND"
+>date</B
+> and <B
+CLASS="COMMAND"
+>clock</B
+>
+	(in that order), but be prepared to reboot, if some part of the
+	system starts acting funny.  </P
+><P
+> A networked computer (even if just over the modem) can
+	check its own clock automatically, by comparing it to some other
+	computer's time.  If the other computer is known to keep very
+	accurate time, then both computers will keep accurate time.
+	This can be done by using the <B
+CLASS="COMMAND"
+>rdate</B
+> and
+	<B
+CLASS="COMMAND"
+>netdate</B
+> commands.  Both check the time of a
+	remote computer (<B
+CLASS="COMMAND"
+>netdate</B
+> can handle several
+	remote computers), and set the local computer's time to that.
+	By running one these commands regularly, your computer will keep
+	as accurate time as the remote computer.  </P
+><P
+> XXX say something intelligent about NTP </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="x2457.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="book1.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="g2516.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Showing and setting time</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="c2432.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Glossary (DRAFT)</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file