[Info-vax] bizarre problem with system time (not DST)

[Simon Clubley]

On 2015-03-28, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
> On 2015-03-28, Phillip Helbig (undress to reply) <helbig at asclothestro.multivax.de> wrote:
>> In article <mf6a7o$s81$1 at dont-email.me>, Simon Clubley
>><clubley at remove_me.eisner.decus.org-Earth.UFP> writes: 
>>> 
>>> What are the time zone logicals set to on each of the cluster nodes ?
>>
>> They are all the same (except for the change from "-" to "^" due to
>> 8.4), and correct, e.g.:
>>
>> (LNM$SYSTEM_TABLE)
>>   "SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
>>   "SYS$TIMEZONE_DIFFERENTIAL" = "3600"
>>   "SYS$TIMEZONE_NAME" = "CET"
>>   "SYS$TIMEZONE_RULE" = "CET-1CEST-2,M3.5.0/02,M10.4.0/03"
>>
>> Note that the satellite is NOT booting from the upgraded node.
>>
>
> I've no experience with satellites, but is it guaranteed that the
> node which provides boot service also provides the system time ?
>
> If the time zone logicals have changed format in 8.4, and if the
> system time is being picked up from the upgraded system, then how
> do you know the 7.3-2 satellite isn't wrongly interpreting the 8.4
> format timezone rules ?
>

One further thought on that and it's about the 1 hour difference.

_If_ the timezone format is invalid for 7.3-2 because the time has
been served from the 8.4 box, then I wonder if your satellite has
fallen back to using GMT ?

Given that you are not on DST yet, that makes you 1 hour ahead of
GMT which would explain the 1 hour behind the rest of your systems
difference.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world