On Sun, Sep 14, 2008 at 2:26 AM, John Summerfield <[EMAIL PROTECTED]> wrote:
> I may have missed something. Is there no way that a virtual machine > cannot have use of a clock, corrected for drift, that reflects the > correct time of day, either now or in the future? A TOD clock that does > _not_ reflect changes of timezone settings or DST settings? The TOD clock does not change with DST or timezone setting. The TOD clock runs (close to) GMT. The Operating System applies the current offset to produce local time for user and applications. When a virtual machine issues the STCK instruction to get its virtual TOD clock, it gets GMT as well and must apply its own offset. Do not use the z/VM IPL prompt to change the clock, since it offsets your LPAR TOD from GMT. Note that on a Windows PC, the hardware clock is supposed to run local time rather than GMT. Linux has some tricks during boot to compensate for that and obtain GMT to run its system clock. -Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
