[ale] set time manually on a RHEL 5.1 server

[Jerry Yu]

The local time reported by 'date' are considered to be correct to users
local to either server.
However, as you can see 'date -u' returned something different, 2-hour
difference to be exact. '-u' allows 'date' to return date/time in UTC (in
the same zone).

Both are up-2-date RHEL 5.1/ppc64 servers.

Foreign# date -u '+%m%d%H%M%Y.%S'
011723142008.07
Foreign# date
Thu Jan 17 22:14:22 GMT+1 2008

USserver# date -u '+%m%d%H%M%Y.%S'
011721132008.42
USserver# date
Thu Jan 17 16:13:54 EST 2008



On Jan 17, 2008 4:06 PM, Jerry Yu <jjj863 at gmail.com> wrote:

> 'date' on that remote server returns "Thu Jan 17 22:04:24 GMT+1 2008".  I
> verified the country is indeed "GMT+1".
> The time above is correct now per the user local to the server.
> However, this is only after I padded 2hours into the 'date -u' returned on
> a server next to me, with TZ set to EST.
>
>
> 2008/1/17 Jeff Lightner <jlightner at water.com>:
>
> >   Remember that the time is actually recorded in UTC (a/ka Zulu or
> > GMT).
> >
> >
> >
> > The DISPLAY of the time however is controlled globally within the system
> > by the timezone file (/etc/localtime) or overridden by the TZ variable if
> > set.
> >
> >
> >
> > You may have the correct UTC time set but the user may be using a
> > different time zone than you expect.
> >
> >
> >
> > You can do "echo $TZ" (or have the user do it if you think his variable
> > is different) to see what value it has.
> >
> > You can do "zdump ?v /etc/localtime" to see what the timezone file
> > you're using by default is actually setting.  (zdump /etc/localtime will
> > just give you its current time).
> >
> >
> >
> > Also make I've seen issues (especially on dual boot systems with
> > Windoze/Linux) where setting the BIOS to use UTC time causes issues between
> > time seen in Linux/Windoze because both try to update the hardware clock on
> > shutdown.
> >
> >
> >
> > FYI:  You probably want to use the hwclock command after you have
> > correct time to insure the hardware clock is correct anyway.
> >
> >
> >  ------------------------------
> >
> > *From:* ale-bounces at ale.org [mailto:ale-bounces at ale.org] *On Behalf Of *Jerry Yu
> > *Sent:* Thursday, January 17, 2008 1:29 PM
> > *To:* ALE
> > *Subject:* [ale] set time manually on a RHEL 5.1 server
> >
> >
> >
> > I need to set the time on a RHEL 5.1 server overseas. It has GMT+1.  No
> > NTP server available. So, I did 'date -u' on another RHEL 5.1 server
> > with EST as its time zone, then apply the timestamp on the GMT+1 server
> > using 'date -u'.
> >
> > The time was set. However, the user local to that server reported the
> > time should be 16:13  instead of 14:13 reported on that server.
> >
> > Any idea? The only thing I can think of, is that they are not GMT+1.
> >   ----------------------------------
> > CONFIDENTIALITY NOTICE: This e-mail may contain privileged or
> > confidential information and is for the sole use of the intended
> > recipient(s). If you are not the intended recipient, any disclosure,
> > copying, distribution, or use of the contents of this information is
> > prohibited and may be unlawful. If you have received this electronic
> > transmission in error, please reply immediately to the sender that you have
> > received the message in error, and delete it. Thank you.
> > ----------------------------------
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...