| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 4 | %general-entities;
|
|---|
| 5 | ]>
|
|---|
| 6 | <sect1 id="ch-scripts-setclock">
|
|---|
| 7 | <title>Configuring the setclock Script</title>
|
|---|
| 8 | <?dbhtml filename="setclock.html"?>
|
|---|
| 9 |
|
|---|
| 10 | <indexterm zone="ch-scripts-setclock">
|
|---|
| 11 | <primary sortas="d-setclock">setclock</primary>
|
|---|
| 12 | <secondary>configuring</secondary></indexterm>
|
|---|
| 13 |
|
|---|
| 14 | <para>The <command>setclock</command> script reads the time from the hardware
|
|---|
| 15 | clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
|
|---|
| 16 | (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
|
|---|
| 17 | hardware clock's time to the local time using the
|
|---|
| 18 | <filename>/etc/localtime</filename> file (which tells the
|
|---|
| 19 | <command>hwclock</command> program which timezone the user is in). There is no
|
|---|
| 20 | way to detect whether or not the hardware clock is set to UTC, so this
|
|---|
| 21 | needs to be configured manually.</para>
|
|---|
| 22 |
|
|---|
| 23 | <para>If you cannot remember whether or not the hardware clock is set to UTC,
|
|---|
| 24 | find out by running the <userinput>hwclock --localtime --show</userinput>
|
|---|
| 25 | command. This will display what the current time is according to the hardware
|
|---|
| 26 | clock. If this time matches whatever your watch says, then the hardware clock is
|
|---|
| 27 | set to local time. If the output from <command>hwclock</command> is not local
|
|---|
| 28 | time, chances are it is set to UTC time. Verify this by adding or subtracting
|
|---|
| 29 | the proper amount of hours for the timezone to the time shown by
|
|---|
| 30 | <command>hwclock</command>. For example, if you are currently in the MST
|
|---|
| 31 | timezone, which is also known as GMT -0700, add seven hours to the local
|
|---|
| 32 | time.</para>
|
|---|
| 33 |
|
|---|
| 34 | <para>Change the value of the <envar>UTC</envar> variable below
|
|---|
| 35 | to a value of <parameter>0</parameter> (zero) if the hardware clock
|
|---|
| 36 | is <emphasis>not</emphasis> set to UTC time.</para>
|
|---|
| 37 |
|
|---|
| 38 | <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
|
|---|
| 39 | the following:</para>
|
|---|
| 40 |
|
|---|
| 41 | <screen><userinput>cat > /etc/sysconfig/clock << "EOF"
|
|---|
| 42 | <literal># Begin /etc/sysconfig/clock
|
|---|
| 43 |
|
|---|
| 44 | UTC=1
|
|---|
| 45 |
|
|---|
| 46 | # End /etc/sysconfig/clock</literal>
|
|---|
| 47 | EOF</userinput></screen>
|
|---|
| 48 |
|
|---|
| 49 | <para>A good hint explaining how to deal with time on LFS is available
|
|---|
| 50 | at <ulink url="&hints-root;time.txt"><phrase
|
|---|
| 51 | condition="pdf">http://www.linuxfromscratch.org/
|
|---|
| 52 | hints/downloads/files/time.txt</phrase></ulink>. It explains issues such as
|
|---|
| 53 | time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
|
|---|
| 54 |
|
|---|
| 55 | </sect1>
|
|---|
| 56 |
|
|---|
