The following is a suggested addition to the documentation for Bering. (It has been sitting in my outbox for awhile... I don't know why it got stuck there.)
--- Configuring timezone in Bering: a) Obtain the approprate zoneinfo file for your timezone. This binary file will contain generalized rules for converting between GMT and your local time. One location where these files are kept is at http://leaf.sourceforge.net/devel/cstein/files/kernels/zoneinfo/, but their format has not changed in a long time and is not expected to change anytime soon so you can pull one from the Linux distribution of your choice. b) Copy this file to the Bering ramdisk as /etc/localtime. On most conventional Linux distributions, /etc/localtime would be a symbolic link to the appropriate file in /usr/share/zoneinfo/, but that directory is not contained in etc.lrp and having symbolic links across packages is not recommended. c) Use the "date" command to confirm that the zoneinfo file is behaving as desired. d) Set the system date/time. There are three common methods: 1) Reboot the machine and set the time in the BIOS. Note that for a pure linux machine like a router it only makes sense to set the bios clock to UTC (GMT0). 2) Set the Linux time with the "date [MMDDhhmm[[CC]YY][.ss]]" command and back it up to the CMOS clock with "hwclock". For example, if it is 9:05:15 pm on Jan 31, 2002, then you would use # date 013121052002.15 # hwclock --systohc hwclock will set the CMOS clock to UTC. 3) Set the Linux time with "rdate {timeserver}" and back it up to the CMOS clock with "hwclock". For example, if you have a Linux box at 192.168.1.3 (see step f), you can use # rdate -s 192.168.1.3 # hwclock --systohc Note that if you don't have a Linux workstation available, you can use a program like AboutTime for Windows (http://www.arachnoid.com/abouttime/) to set the Windows machine time correctly, and while AboutTime is running and its server options are enabled you can use "rdate" against that machine. e) (Optional) Edit the contents of /etc/timezone to describe your timezone. I am not aware of any packages used with Bering that depend on this file, but it might as well be consistent. f) (Optional) Activate daily clock updating via rdate (udp port 37) to a nearby "time" protocol server. This service is handled internally by the inetd daemon on a *nix workstation. Before synchronizing to such a machine, it should probably be configured to maintain time with the sntp protocol (ntpd or xntpd) against some reliable time source. To activate rdate updating, edit /etc/lrp.conf to specify the ip number of the desired time server for lrp_DATE_SERVER, and uncomment this variable. g) (informational) All lines in /etc/tzvalue should be commented out. h) Backup etc.lrp (to save the results of steps b, e, and f). i) Either reboot, or restart logging (svi sysklogd restart) to cause times recorded by the system logger to use the new timezone information. Also, Greg Morgan provided the following information that may be useful: This site may will help you pick US zones http://www.time.gov/. I found these links illuminating http://www.time.gov/exhibits.html. If you have Windows clients that you want to sync to your firewall, you can use http://www.oneguycoding.com/automachron/ in your systray. External time server lists can be found at http://www.eecis.udel.edu/~mills/ntp/servers.htm http://www.eecis.udel.edu/~mills/ntp/clock1.htm http://www.eecis.udel.edu/~mills/ntp/clock2.htm --- --------------------------------------------------------------------------- Jeff Newmiller The ..... ..... Go Live... DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/Batteries O.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --------------------------------------------------------------------------- ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
