Linux System Administration
It may not appear difficult to keep your clock set correctly. DOS had the ability to set its time directly from the BIOS (Basic In/Out System) and you could set the BIOS time directly from DOS. Now you have to worry about time zones, machine time vs. software time, and finding out how to set the time when your system could be off by 30 seconds every day.
It's easy to set up your system for the correct time and if you're networked, it's easy to keep your time updated. First, get a copy of the zoneinfo package. For releases like Slackware, it is already installed (and may be already set up in Slackware 1.2.0 and later). Look for the /usr/lib/zoneinfo directory. If you don't have that directory, get a copy of the package (see sidebar “Finding zoneinfo”) and install it.
For the best setup, you should set your BIOS (or hardware) clock for GMT (or Zulu, Universal time, or whatever you want to call it). The advantage of having your BIOS clock set to GMT is that Linux will automatically handle daylight savings time conversions for your particular area. You may not want to do this if you still use DOS, but I find that DOOM does not care what time I play. I also found that people in the office think you're really dedicated when you bring in files with time stamps of 2:30AM.
The first thing you should do is boot into Linux and go into the /usr/lib/zoneinfo directory. You should see a list of various time zones. Some are listed by country, some have directories with more listings under them (such as the US directory). Find the file that works with your country or time zone. For my system, this would be the US/Eastern file, as I am in the Eastern Time Zone for the US. If your country is not listed, there is a list of files that relate to times + or - to GMT, such as GMT-6. Find out how far off you are from GMT, and use that file instead.
From here, I create a symbolic link from /usr/lib/zoneinfo/localtime to /usr/lib/zoneinfo/US/Eastern:
ln -sf /usr/lib/zoneinfo/US/Eastern /usr/lib/ zoneinfo/localtime
Another file to link is the posixrules file. This can be linked to localtime. If you have the TZ variable set, the posixrules link will be used to set the correct time zone.
ln -s /usr/lib/zoneinfo/ localtime /usr/lib/ zoneinfo/posixrules
If your BIOS clock is set to GMT, you have to tell Linux this using the clock command. The best way to do it is edit your /etc/rc.d/rc.local file (or /etc/rc.local file if you don't have an rc.d directory) and add the following command anywhere in the file:
#Tell Linux the BIOS is universal time! clock -us
Or if you have your clock set to local time:
#Tell Linux that the BIOS is set for local time already! clock -s
The -s option indicates to set the clock, and the -u option indicates that the BIOS clock is set to 'universal time', or GMT.
From now on, when you use the date command to view the time, you will see the correct local time, along with the time zone you are in:
#date Thu Aug 10 22:15:35 EDT 1994
It's easy to set up your system for the correct time and if you're networked, it's easy to keep your time updated.
If you're networked to other machines with a better sense of time than yours, you can use the netdate command to periodically keep your machine time correct. As root on your machine, just enter the command:
netdate [ -v ] [ -l limit ] <hostl> ... <hostn>
where hostl...hostn is a list of hosts. It is usually best to list hosts that are physically close to your system, especially if you're using a dial-up PPP or SLIP.
The way neLdate works is to collect the hosts into groups based on how close the times are. Of the hosts with the times closest to the local time, the first alphabetical host of that group is used to set the time on the local host. The -v option will list the groups that get created, and the -1 limit option varied the amount of time that netdate will wait for time information from other hosts to come in. A limit of 0 will accept the time of the first host that responds and ignore all the others.
However, netGate does not update your BIOS clock, only the system clock. To update the BIOS clock, use the clock -uw command to 'write' universal time, or clock -w if you keep your BIOS set to local time. One idea you may want to try is creating a shell script which executes the netdate and clock commands automatically and keep it in your /etc directory. This way, if you notice the time is a bit off, you can execute the shell script to update the time, and update your BIOS clock simultaneously.
If you are interested in doing more with the time zones, check out the man pages for date, clock, and netdate. Also in the /usr/lib/zoneinfo directory is a time.doc text file which is good reading.
Free DevOps eBooks, Videos, and more!
Regardless of where you are in your DevOps process, Linux Journal can help!
We offer here the DEFINITIVE DevOps for Dummies, a mobile Application Development Primer, and advice & help from the expert sources like:
- Linux Journal
- Be a Mechanic...with Android and Linux!
- New Products
- Users, Permissions and Multitenant Sites
- Flexible Access Control with Squid Proxy
- Security in Three Ds: Detect, Decide and Deny
- High-Availability Storage with HA-LVM
- DevOps: Everything You Need to Know
- Solving ODEs on Linux
- Tighten Up SSH
- Non-Linux FOSS: MenuMeters