Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: time for time details
Message-ID: <6706@ut-sally.UUCP>
Date: Tue, 23-Dec-86 11:50:43 EST
Article-I.D.: ut-sally.6706
Posted: Tue Dec 23 11:50:43 1986
Date-Received: Tue, 23-Dec-86 21:50:17 EST
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 28
Approved: jsq@sally.utexas.edu

From: guy@sun.com (Guy Harris)
Date: Sat, 13 Dec 86 14:14:04 PST

> GMT and UTC are not the same.

However, it's not clear whether the term "GMT", when used in documents
describing the way UNIX handles time, refers to GMT or to the time that
would be kept by a clock set to local British time at some point when
British Summer Time is not in effect and then left to run free.

Since, as you point out, GMT is not readily available from time sources, and
since most hardware and most implementations don't know how to stretch or
shrink seconds, I suspect most implementations definitely don't provide real
live GMT.  In fact, since most hardware doesn't receive any UTC broadcasts,
most implementations don't provide real live UTC, either.  (Some machines
don't even do that great a job at providing *any* sort of
precise-to-the-second indication of current time, given the tendency of
their clocks to drift, or the fact that their clocks are set from somebody's
wristwatch.)

This is all somewhat irrelevant to machines that don't synchronize with UTC
and don't know about leap seconds.  Machines that do synchronize with UTC
will have to worry about whether particular time zones follow UTC or not.
If they insert the leap seconds at the same instant that UTC does, there's
no real problem; if they don't, the offset between UTC and local time
presumably just slowly drifts from being an even number of half-hours.

Volume-Number: Volume 8, Number 68