Difference between revisions of "Setting the System Time"

From wiki.emacinc.com
Jump to: navigation, search
 
(32 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
{{todo|Reviewed by MD: Add section about shutting down ntpd if needed|Klint Youngmeyer|project=oe 4,oe 5,ky,Review,FinalDraft}}
+
{{todo|SEOKWREV (11.17.13-23:00->MD+);(03.04.14-15:35->BS-);(03.19.14-15:35->BS+)|Klint Youngmeyer|project=oe 4,oe 5,ky,md,bs,SEOKWREV}}
  
−
There are two different clocks on a Linux system. The RTC, or hardware clock, is present on most systems and is used to provide a persistent clock using a battery backup and for other purposes like waking the processor up from suspend mode via an alarm interrupt. The hardware clock is generally only accessed to retrieve an initial time when Linux boots and is rarely accessed from a running system. The system clock is implemented in the kernel and is used for timekeeping purposes for the running system. On Linux, time is represented by the number of seconds after the Unix epoch: 00:00:00 UTC on January 1, 1970.
+
{{#seo:
 +
|title=Setting the System Time
 +
|titlemode=append
 +
|keywords=Setting System Time,Updating Clock,Hardware Clock,Local Timezone
 +
|description=Setting the system time on a Linux system.
 +
}}
 +
There are two different clocks on a Linux system. The RTC, or hardware clock, is present on most systems and is used to provide a persistent clock using a battery backup.  It is also used for other purposes, like waking up the processor from suspend mode via an alarm interrupt. The hardware clock is generally only accessed to retrieve an initial time when Linux boots and is rarely accessed from a running system. The system clock is implemented in the kernel and is used for timekeeping purposes for the running system. On Linux, time is represented by the number of seconds after the Unix epoch: 00:00:00 UTC on January 1, 1970.
  
−
== Setting the System Time on EMAC OE Products ==
+
== Before Setting System Time ==
  
 
<!--{{todo|Add info about shutting down ntpd here|Klint Youngmeyer|project=oe 4,oe 5,ky,Review}}
 
<!--{{todo|Add info about shutting down ntpd here|Klint Youngmeyer|project=oe 4,oe 5,ky,Review}}
  
−
'''TODO Klint, you need to tell them how to use the  ps  command with grep to see if ntpd  is running, and if it is, tell them how to shut it down before running  ntpdate.  Then, afterwards, tell them to restart it if it was running.  Reason: ntpdate cannot run successfully if ntpdate is already running.  Also, if ntpd is in use, tell them to use  ntpq -p  to display a list of the timeservers in use by it.  TODO'''-->
+
'''TODO Klint, you need to tell them how to use the  ps  command with grep to see if ntpd  is running, and if it is, tell them how to shut it down before running  ntpdate.  Then, afterwards, tell them to restart it if it was running.  Reason: ntpdate cannot run successfully if ntpdate is already running.  Also, if ntpd is in use, tell them to use  ntpq -p  to display a list of the timeservers in use by it.  TODO'''-->
  
 
Before setting the system time, you must use the following command to ensure that <code>ntpd</code> is not running.
 
Before setting the system time, you must use the following command to ensure that <code>ntpd</code> is not running.
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ ps | grep ntpd
+
root@emac-oe:~# ps | grep [n]tpd
 
ntp    25066    1  0  9958  2260  2 Oct08 ?        00:00:07 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 117:126
 
ntp    25066    1  0  9958  2260  2 Oct08 ?        00:00:07 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 117:126
−
user    28441 13218  0  3397  920  0 17:48 pts/14  00:00:00 grep --color=auto ntpd
+
root@emac-oe:~#
−
$
+
</syntaxhighlight>
  
−
</syntaxhighlight>
 
 
If <code>ntpd</code> is not running, please continue to the section: Updating The Clock. If <code>ntpd</code> is running, as shown in the above command output, you will have to shut down the process before updating the clock and restart it afterwards. To shut down the <code>ntpd</code> process, run the following command:
 
If <code>ntpd</code> is not running, please continue to the section: Updating The Clock. If <code>ntpd</code> is running, as shown in the above command output, you will have to shut down the process before updating the clock and restart it afterwards. To shut down the <code>ntpd</code> process, run the following command:
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ /etc/init.d/ntp stop
+
root@emac-oe:~# /etc/init.d/ntp stop
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 27: Line 32:
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ /etc/init.d/ntp start
+
root@emac-oe:~# /etc/init.d/ntp start
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
You can also view a list of servers in use by <code>ntpd</code> by running the command:
+
When ntpd is running, you can view a list of servers <code>ntpd</code> is using by running the command:
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ ntpq -q
+
root@emac-oe:~# ntpq -q
 
</syntaxhighlight>
 
</syntaxhighlight>
  
−
=== Updating The Clock ===
+
== Updating The Clock ==
  
−
During boot, they system will call the program <code>ntpdate</code> to set the time from an NTP server.  This requires that the device has Internet access. To do this manually run the following command:
+
During boot, the system will call the program <code>ntpdate</code> to set the time from an NTP server.  This requires that the device has Internet access. To do this manually run the following command:
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ ntpdate pool.ntp.org
+
root@emac-oe:~# ntpdate pool.ntp.org
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 47: Line 52:
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
$ date -s "<date_format>"
+
root@emac-oe:~# date -s "<date_format>"
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
The argument <code><date_format></code> can be any of the following:
 
The argument <code><date_format></code> can be any of the following:
−
  <syntaxhighlight lang="console">
+
  <syntaxhighlight lang="text">
 
"hh:mm[:ss]"
 
"hh:mm[:ss]"
 
"[YYYY.]MM.DD-hh:mm[:ss]"
 
"[YYYY.]MM.DD-hh:mm[:ss]"
 
"YYYY-MM-DD hh:mm[:ss]"
 
"YYYY-MM-DD hh:mm[:ss]"
 
"MMDDhhmm[[YY]YY][.ss]"  
 
"MMDDhhmm[[YY]YY][.ss]"  
 +
 +
hh    = hour
 +
mm    = minute
 +
ss    = second
 +
YYYY  = four-digit year
 +
MM    = month
 +
DD    = day
 +
[YY]YY = four-digit year where the first two digits are optional
 
</syntaxhighlight>
 
</syntaxhighlight>
−
hh    = hour<br />
 
−
mm    = minute<br />
 
−
ss    = second<br />
 
−
YYYY  = four-digit year<br />
 
−
MM    = month<br />
 
−
DD    = day<br />
 
−
[YY]YY = four-digit year where the first two digits are optional<br />
 
  
 +
{{imbox | type =  | text = Any portion of a format string with square brackets, such as [:ss], is optional for that format string.  To work correctly, the format string may need to be quoted as shown above or special characters may need to be escaped to prevent interpretation by the shell.}}
  
−
{{Fmbox | type =  | text = Any portion of format string such as [:ss] with square brackets is optional for that format string. The format string must be quoted as shown above to work correctly.}}
 
  
 +
On shutdown the system time is saved to the hardware clock automatically with the following command:
 +
<syntaxhighlight lang="bash">
 +
/etc/init.d/hwclock.sh stop
 +
</syntaxhighlight>
 +
To do this manually after setting the date run the following command:
 +
<syntaxhighlight lang="bash">
 +
/etc/init.d/hwclock.sh restart
 +
</syntaxhighlight>
  
−
On shutdown the system time is saved to the hardware clock automatically with the following command:<syntaxhighlight lang="console">/etc/init.d/hwclock.sh stop</syntaxhighlight>To do this manually after setting the date run the following command:<syntaxhighlight lang="console">/etc/init.d/hwclock.sh restart</syntaxhighlight>
+
== Hardware Clock ==
  
−
== Hardware Clock ==
+
The hardware clock can be accessed through the <code>hwclock</code> command. Running <code>hwclock</code> with no arguments prints the current value stored in the hardware clock. The <code>--systohc</code> option sets the value of the hardware clock using the system clock. This command is called by the system shutdown scripts using <code>/etc/init.d/hwclock.sh</code>. The <code>--hctosys</code> option can be used to set the system clock using the value stored in the hardware clock. This is used by <code>/etc/init.d/hwclock.sh</code> to initialize the system clock during the boot process. Note that the hardware clock is generally set to UTC regardless of the local timezone. On system shutdown, the current system time is saved to the RTC using the <code>/etc/init.d/save-rtc.sh</code> script.<br />
  
−
The hardware clock can be accessed through the ''hwclock'' command. Running ''hwclock'' with no arguments prints the current value stored in the hardware clock. The ''--systohc'' option sets the value of the hardware clock using the system clock. This command is called by the system shutdown scripts using ''/etc/init.d/hwclock.sh''. The ''--hctosys'' option can be used to set the system clock using the value stored in the hardware clock. This is used by ''/etc/init.d/hwclock.sh'' to initialize the system clock during the boot process. Note that the hardware clock is generally set to UTC regardless of the local timezone. On system shutdown, the current system time is saved to the RTC using the ''/etc/init.d/save-rtc.sh'' script.<br />
 
  
 +
{{imbox | type =  | text = On some boards you may receive a message such as ''hwclock: RTC_RD_TIME: Invalid or incomplete multibyte or wide character'' or a similar message when attempting to read the hardware clock. This generally means that the hardware clock has not yet been set, in which case running the <code>hwclock --systohc</code> command will correct the issue.}}<br />
  
−
{{Fmbox | type =  | text = On some boards you may receive a message such as ''hwclock: RTC_RD_TIME: Invalid or incomplete multibyte or wide character'' or a similar message when attempting to read the hardware clock. This generally means that the hardware clock has not yet been set, in which case running the ''hwclock --systohc'' command will correct the issue.}}<br />
+
The system can be configured to use either local time (see [[#local_timezone|Local Timezone]]) or UTC for the hardware clock. Although the hardware clock only holds an absolute time value and no timezone value, adjustments can be made to account for the timezone when reading and setting the clocks. By default, EMAC OE uses the local time value for the hardware clock. If UTC is used for the system clock, or NTP or another method is used to synchronize the clocks, this will not cause an issue. However, if the hardware clock is the primary method used to initialize the system clock, there will be no way to automatically adjust for Daylight Saving Time changes that occur while the system is off. In these cases, it is best to keep the hardware clock in UTC. This can be done easily by adding the line <code>UTC=yes</code> to <code>/etc/default/rcS</code>. Doing so will cause the <code>/etc/init.d/hwclock.sh</code> script to pass the <code>utc</code> option to the <code>hwclock</code> command when setting the hardware clock and when using it to set the system clock. The following example illustrates how the <code>utc</code> option allows the system to automatically account for the timezone when setting and reading the clocks:
  
−
The system can be configured to use either local time (see [[#local_timezone|Local Timezone]]) or UTC for the hardware clock. Although the hardware clock only holds an absolute time value and no timezone value, adjustments can be made to account for the timezone when reading and setting the clocks. By default, EMAC OE uses the local time value for the hardware clock. If UTC is used for the system clock, or NTP or another method is used to synchronize the clocks, this will not cause an issue. However, if the hardware clock is the primary method used to initialize the system clock, there will be no way to automatically adjust for Daylight Saving Time changes that occur while the system is off. In these cases, it is best to keep the hardware clock in UTC. This can be done easily by adding the line ''UTC=yes'' to ''/etc/default/rcS''. Doing so will cause the ''/etc/init.d/hwclock.sh'' script to pass the ''utc'' option to the ''hwclock'' command when setting the hardware clock and when using it to set the system clock. The following example illustrates how the ''utc'' option allows the system to automatically account for the timezone when setting and reading the clocks:<syntaxhighlight lang="console">
+
<syntaxhighlight lang="console">
−
root@som9g20:~# date
+
root@emac-oe:~# date
 
Tue Oct 18 10:34:44 CDT 2011
 
Tue Oct 18 10:34:44 CDT 2011
−
root@som9g20:~# hwclock --utc --systohc
+
root@emac-oe:~# hwclock --utc --systohc
−
root@som9g20:~# hwclock
+
root@emac-oe:~# hwclock
 
Tue Oct 18 15:34:53 2011  0.000000 seconds
 
Tue Oct 18 15:34:53 2011  0.000000 seconds
−
root@som9g20:~# hwclock --utc
+
root@emac-oe:~# hwclock --utc
 
Tue Oct 18 10:34:58 2011  0.000000 seconds
 
Tue Oct 18 10:34:58 2011  0.000000 seconds
−
root@som9g20:~# hwclock --utc --hctosys
+
root@emac-oe:~# hwclock --utc --hctosys
−
root@som9g20:~# date
+
root@emac-oe:~# date
−
Tue Oct 18 10:35:07 CDT 2011</syntaxhighlight>{{Fmbox | type =  | text =If the system is set to use UTC for the hardware clock setting, the ''utc'' option must be passed to ''hwclock'' if it is used outside of the ''/etc/init.d/hwclock.sh'' script to synchronize the hardware and system clocks.}}
+
Tue Oct 18 10:35:07 CDT 2011
 +
root@emac-oe:~#
 +
</syntaxhighlight>
 +
 
 +
{{imbox | type =  | text =If the system is set to use UTC for the hardware clock setting, the <code>utc</code> option must be passed to <code>hwclock</code> if it is used outside of the <code>/etc/init.d/hwclock.sh</code> script to synchronize the hardware and system clocks.}}
  
 
== Local Timezone ==
 
== Local Timezone ==
  
−
By default, EMAC OE systems are set to UTC timezone. Setting the timezone is done by creating a link from <code>/etc/localtime</code> to the desired timezone information file. The most common timezones are installed in the base image; contact EMAC for additional timezone definitions if required. Timezone information files are stored in the <code>/usr/share/zoneinfo</code> directory. For example, for Central Standard Time (CST), the file <code>/usr/share/zoneinfo/America/Chicago</code> or <code>/usr/share/zoneinfo/CST6CDT</code> would be used. This will also allow the system to automatically adjust for Daylight Savings Time.<br />
+
By default, EMAC OE systems are set to UTC timezone. Setting the timezone is done by creating a link from <code>/etc/localtime</code> to the desired timezone information file. The most common timezones are installed in the base image; contact EMAC for additional timezone definitions if required. Timezone information files are stored in the <code>/usr/share/zoneinfo</code> directory. For example, for Central Standard Time (CST), the file <code>/usr/share/zoneinfo/America/Chicago</code> or <code>/usr/share/zoneinfo/CST6CDT</code> would be used. This will also allow the system to automatically adjust for Daylight Saving Time.<br />
  
  
  
−
The example below illustrates the process of setting the timezone. Notice that it is necessary to log out and log back in for the new timezone setting to take effect. The command below that actually sets the timezone is <code>ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime</code>:
+
The example below illustrates the process of setting the timezone. Notice that it is necessary to log out and log back in for the new timezone setting to be shown within a terminal session. The command below that actually sets the timezone is:<br /><code>ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime</code>
  
 
<syntaxhighlight lang="console">
 
<syntaxhighlight lang="console">
−
root@SOM9G20M:~# hwclock
+
root@emac-oe:~# hwclock
 
Thu Feb  4 22:54:48 2010  0.000000 seconds
 
Thu Feb  4 22:54:48 2010  0.000000 seconds
−
root@SOM9G20M:~# date
+
root@emac-oe:~# date
 
Thu Feb  4 22:54:49 UTC 2010
 
Thu Feb  4 22:54:49 UTC 2010
−
root@SOM9G20M:~# rm -rf /etc/localtime ### <--- only necessary if this file exists ###
+
root@emac-oe:~# rm -f /etc/localtime ### <--- only necessary if this file exists ###
−
root@SOM9G20M:~# ### The following line sets the timezone by creating the needed symbolic link: ###
+
root@emac-oe:~# ### The following line sets the timezone by creating the needed symbolic link: ###
−
root@SOM9G20M:~# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
+
root@emac-oe:~# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
−
root@SOM9G20M:~# ### The following line shows the symbolic link that was created to set the timezone ###
+
root@emac-oe:~# ### The following line shows the symbolic link that was created to set the timezone ###
−
root@SOM9G20M:~# ls -l /etc/localtime
+
root@emac-oe:~# ls -l /etc/localtime
 
lrwxrwxrwx    1 root    root          35 Feb  4 22:55 /etc/localtime -> /usr/share/zoneinfo/America/Chicago
 
lrwxrwxrwx    1 root    root          35 Feb  4 22:55 /etc/localtime -> /usr/share/zoneinfo/America/Chicago
−
root@SOM9G20M:~# date
+
root@emac-oe:~# date
 
Thu Feb  4 22:55:46 UTC 2010
 
Thu Feb  4 22:55:46 UTC 2010
−
root@SOM9G20M:~# logout
+
root@emac-oe:~# logout
 
....
 
....
−
SOM9G20M login: root
+
emac-oe login: root
 
Password:
 
Password:
−
root@SOM9G20M:~# date
+
root@emac-oe:~# date
 
Thu Feb  4 16:56:05 CST 2010
 
Thu Feb  4 16:56:05 CST 2010
−
root@SOM9G20M:~# hwclock
+
root@emac-oe:~# hwclock
 
Thu Feb  4 22:56:08 2010  0.000000 seconds
 
Thu Feb  4 22:56:08 2010  0.000000 seconds
−
root@SOM9G20M:~#
+
root@emac-oe:~#
 
</syntaxhighlight>
 
</syntaxhighlight>

Latest revision as of 14:38, 19 March 2014

TODO: {{#todo:SEOKWREV (11.17.13-23:00->MD+);(03.04.14-15:35->BS-);(03.19.14-15:35->BS+)|Klint Youngmeyer|oe 4,oe 5,ky,md,bs,SEOKWREV}}

There are two different clocks on a Linux system. The RTC, or hardware clock, is present on most systems and is used to provide a persistent clock using a battery backup. It is also used for other purposes, like waking up the processor from suspend mode via an alarm interrupt. The hardware clock is generally only accessed to retrieve an initial time when Linux boots and is rarely accessed from a running system. The system clock is implemented in the kernel and is used for timekeeping purposes for the running system. On Linux, time is represented by the number of seconds after the Unix epoch: 00:00:00 UTC on January 1, 1970.

Before Setting System Time

Before setting the system time, you must use the following command to ensure that ntpd is not running. 

root@emac-oe:~# ps | grep [n]tpd
ntp     25066     1  0  9958  2260   2 Oct08 ?        00:00:07 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 117:126
root@emac-oe:~#

If ntpd is not running, please continue to the section: Updating The Clock. If ntpd is running, as shown in the above command output, you will have to shut down the process before updating the clock and restart it afterwards. To shut down the ntpd process, run the following command: 

root@emac-oe:~# /etc/init.d/ntp stop

After you have updated the clock using the instructions in the next section, run the following command to restart the ntpd process: 

root@emac-oe:~# /etc/init.d/ntp start

When ntpd is running, you can view a list of servers ntpd is using by running the command: 

root@emac-oe:~# ntpq -q

Updating The Clock

During boot, the system will call the program ntpdate to set the time from an NTP server. This requires that the device has Internet access. To do this manually run the following command: 

root@emac-oe:~# ntpdate pool.ntp.org

The example above uses the server pool.ntp.org which will retrieve a randomly chosen public NTP server. However, the choice of time server is arbitrary and can be set according to the users' needs. If the device does not have Internet access, then the system date can be set using the following command: 

root@emac-oe:~# date -s "<date_format>"

The argument <date_format> can be any of the following: 

"hh:mm[:ss]"
"[YYYY.]MM.DD-hh:mm[:ss]"
"YYYY-MM-DD hh:mm[:ss]"
"MMDDhhmm[[YY]YY][.ss]" 

hh     = hour
mm     = minute
ss     = second
YYYY   = four-digit year
MM     = month
DD     = day
[YY]YY = four-digit year where the first two digits are optional
Any portion of a format string with square brackets, such as [:ss], is optional for that format string. To work correctly, the format string may need to be quoted as shown above or special characters may need to be escaped to prevent interpretation by the shell.


On shutdown the system time is saved to the hardware clock automatically with the following command: 

/etc/init.d/hwclock.sh stop

To do this manually after setting the date run the following command: 

/etc/init.d/hwclock.sh restart

Hardware Clock

The hardware clock can be accessed through the hwclock command. Running hwclock with no arguments prints the current value stored in the hardware clock. The --systohc option sets the value of the hardware clock using the system clock. This command is called by the system shutdown scripts using /etc/init.d/hwclock.sh. The --hctosys option can be used to set the system clock using the value stored in the hardware clock. This is used by /etc/init.d/hwclock.sh to initialize the system clock during the boot process. Note that the hardware clock is generally set to UTC regardless of the local timezone. On system shutdown, the current system time is saved to the RTC using the /etc/init.d/save-rtc.sh script.


On some boards you may receive a message such as hwclock: RTC_RD_TIME: Invalid or incomplete multibyte or wide character or a similar message when attempting to read the hardware clock. This generally means that the hardware clock has not yet been set, in which case running the hwclock --systohc command will correct the issue.


The system can be configured to use either local time (see Local Timezone) or UTC for the hardware clock. Although the hardware clock only holds an absolute time value and no timezone value, adjustments can be made to account for the timezone when reading and setting the clocks. By default, EMAC OE uses the local time value for the hardware clock. If UTC is used for the system clock, or NTP or another method is used to synchronize the clocks, this will not cause an issue. However, if the hardware clock is the primary method used to initialize the system clock, there will be no way to automatically adjust for Daylight Saving Time changes that occur while the system is off. In these cases, it is best to keep the hardware clock in UTC. This can be done easily by adding the line UTC=yes to /etc/default/rcS. Doing so will cause the /etc/init.d/hwclock.sh script to pass the utc option to the hwclock command when setting the hardware clock and when using it to set the system clock. The following example illustrates how the utc option allows the system to automatically account for the timezone when setting and reading the clocks: 

root@emac-oe:~# date
Tue Oct 18 10:34:44 CDT 2011
root@emac-oe:~# hwclock --utc --systohc
root@emac-oe:~# hwclock
Tue Oct 18 15:34:53 2011  0.000000 seconds
root@emac-oe:~# hwclock --utc
Tue Oct 18 10:34:58 2011  0.000000 seconds
root@emac-oe:~# hwclock --utc --hctosys
root@emac-oe:~# date
Tue Oct 18 10:35:07 CDT 2011
root@emac-oe:~#
If the system is set to use UTC for the hardware clock setting, the utc option must be passed to hwclock if it is used outside of the /etc/init.d/hwclock.sh script to synchronize the hardware and system clocks.

Local Timezone

By default, EMAC OE systems are set to UTC timezone. Setting the timezone is done by creating a link from /etc/localtime to the desired timezone information file. The most common timezones are installed in the base image; contact EMAC for additional timezone definitions if required. Timezone information files are stored in the /usr/share/zoneinfo directory. For example, for Central Standard Time (CST), the file /usr/share/zoneinfo/America/Chicago or /usr/share/zoneinfo/CST6CDT would be used. This will also allow the system to automatically adjust for Daylight Saving Time.


The example below illustrates the process of setting the timezone. Notice that it is necessary to log out and log back in for the new timezone setting to be shown within a terminal session. The command below that actually sets the timezone is:
ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime 

root@emac-oe:~# hwclock
Thu Feb  4 22:54:48 2010  0.000000 seconds
root@emac-oe:~# date
Thu Feb  4 22:54:49 UTC 2010
root@emac-oe:~# rm -f /etc/localtime ### <--- only necessary if this file exists ###
root@emac-oe:~# ### The following line sets the timezone by creating the needed symbolic link: ###
root@emac-oe:~# ln -s /usr/share/zoneinfo/America/Chicago /etc/localtime
root@emac-oe:~# ### The following line shows the symbolic link that was created to set the timezone ###
root@emac-oe:~# ls -l /etc/localtime
lrwxrwxrwx    1 root     root           35 Feb  4 22:55 /etc/localtime -> /usr/share/zoneinfo/America/Chicago
root@emac-oe:~# date
Thu Feb  4 22:55:46 UTC 2010
root@emac-oe:~# logout
....
emac-oe login: root
Password:
root@emac-oe:~# date
Thu Feb  4 16:56:05 CST 2010
root@emac-oe:~# hwclock
Thu Feb  4 22:56:08 2010  0.000000 seconds
root@emac-oe:~#
Retrieved from "https://wiki.emacinc.com/index.php?title=Setting_the_System_Time&oldid=3481"