diff options
Diffstat (limited to 'sag-0.6.1-www/Invisible/sag-0.6/node110.html')
| -rw-r--r-- | sag-0.6.1-www/Invisible/sag-0.6/node110.html | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/sag-0.6.1-www/Invisible/sag-0.6/node110.html b/sag-0.6.1-www/Invisible/sag-0.6/node110.html new file mode 100644 index 0000000..bf24203 --- /dev/null +++ b/sag-0.6.1-www/Invisible/sag-0.6/node110.html @@ -0,0 +1,59 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> +<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds --> +<HTML> +<HEAD> +<TITLE>When the clock is wrong</TITLE> +<META NAME="description" CONTENT="When the clock is wrong"> +<META NAME="keywords" CONTENT="sag"> +<META NAME="resource-type" CONTENT="document"> +<META NAME="distribution" CONTENT="global"> +<LINK REL=STYLESHEET HREF="sag.css"> +</HEAD> +<BODY LANG="EN" > + <A NAME="tex2html1697" HREF="node111.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html1695" HREF="node106.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html1691" HREF="node109.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html1699" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html1700" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR> +<B> Next:</B> <A NAME="tex2html1698" HREF="node111.html">Measuring Holes</A> +<B>Up:</B> <A NAME="tex2html1696" HREF="node106.html">Keeping Time</A> +<B> Previous:</B> <A NAME="tex2html1692" HREF="node109.html">Showing and setting time</A> +<BR> <P> +<H1><A NAME="SECTION001240000000000000000">When the clock is wrong</A></H1> +<P> + The Linux software clock is not always accurate. It is kept + running by a periodic <b>timer interrupt</b> 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> + 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 <tt>date</tt><A NAME="3189"> </A> and <tt>clock</tt><A NAME="3191"> </A> (in that order), + but be prepared to reboot, if some part of the system starts + acting funny. +<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 <tt>rdate</tt><A NAME="3193"> </A> + and <tt>netdate</tt><A NAME="3195"> </A> commands. + Both check the time of a remote computer (<tt>netdate</tt><A NAME="3197"> </A> 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> + <b>META: </b> say something intelligent about NTP +<P> +<BR> <HR> +<P><ADDRESS> +<I>Lars Wirzenius <BR> +Sat Nov 15 02:32:11 EET 1997</I> +</ADDRESS> +</BODY> +</HTML> |