Re: SCO 5.0.5/5.0.6 bios clock, time zone and synching

From: John Smith (atarts_at_hotmail.com)
Date: 07/31/03 

Date: 30 Jul 2003 18:13:12 -0700

Bela Lubkin <belal@sco.com> wrote in message news:<20030730080625.GO24551@sco.com>...
> Yes: you left out all numeric values. You say the timezone was wrong
> with the BIOS clock set to localtime, and it was wrong with the BIOS
> clock set to UTC. So OK, it's always wrong -- by what offset? Show
> actual examples (and don't make them up, capture real values from actual
> problematic systems).

Okay, ive finished my testing.
RTC of the server is set to UTC. No problem.
Im in Sydney, Australia (UTC+10).
I use SCO Admin -> System -> 'System Time Manager' -> Time (Menu) ->
Change Timezone.
I set the timezone as follows:
Geographical Area: Australia/New Zealand
Australas<sic>: Eastern Australian Time (EST)
Daylight Savings Time: No Automatic DST for this zone.
Accept the above values.
SCO Admin tells me I need to log out and log back in to see the
change. So I do this. When I log back in and check $TZ:

TZ=EST-10

No problem, thats correct. When I run 'date' though:

Thu Jul 31 00:58:50 EST 2003

This is the time in the RTC (which is of course UTC), not the correct
localtime.
Im ignoring DST for the time being.
Ive used the 'tz' binary to set the timezone and the same problem
occurs.
Ive rebooted the server after the changes, same problem occurs.

The system just cant seem to understand that the clock is set to UTC
and that it should obey the timezone settings.

There are two TA's that seem pertinent:
TA#113761 talks about running /etc/TIMEZONE via /etc/profile to make
sure the TZ var is being set for all users. Ive done this but it makes
no difference, the time is still not being displayed properly by the
date command.
TA#115103 talks about there being a known problem with 505 and 506 and
non-standard timezones. The TA suggests disabling RTC tracking and
relinking the kernel. The TA says this can be achieved by making a
change to /etc/conf/pack.d/clock/space.c however this file does not
exist on my testing server which is running on 505. The above dir/file
do exist under 506. I dont know yet if carrying out what this TA says
fixes the problem.

So, I hope thats enough info for you Bela.

cheers

Relevant Pages

  • [SLE] Update - 9.0 time problem solved
    ... To confirm that I had localtime and not UTC set I called up yast2 and checked ... It was showing the correct information including localtime. ... So maybe the last update may have set some file to UTC and rerunning yast2 reset it. ... I am in the US/Central timezone in /etc/sysconfig/clock. ...
    (SuSE)
  • Re: SCO 5.0.5/5.0.6 bios clock, time zone and synching
    ... >> with the BIOS clock set to localtime, and it was wrong with the BIOS ... >> problematic systems). ... > I set the timezone as follows: ...
    (comp.unix.sco.misc)
  • Re: Question about DST changes in the US
    ... boot Windows XP it tells me the same time as Fedora. ... it can keep the motherboard hardware clock in localtime but internally everything is UTC and converted to the user's timezone for display - and different users can be in different timezones at the same time. ...
    (Fedora)
  • Re: Convert system time to another timezone
    ... me the current time based on that timezone. ... Or some hint to create a ... localtime(), ... or run it in a subprocess with its own environment and pass ...
    (comp.unix.solaris)
  • Re: SCO 5.0.5/5.0.6 bios clock, time zone and synching
    ... You say the timezone was wrong ... > with the BIOS clock set to localtime, and it was wrong with the BIOS ... I really should have indicated in my original post that im just ...
    (comp.unix.sco.misc)