dhb@rayssd.UUCP (10/24/84)
I have seen discussions here before about time warps whereby an article could get from one coast to the other several hours before it was posted but the trans-atlantic link has now got that beaten by a mile. The following article arrived here on 10/24 after having passed across the Atlantic and through several sites (not all of which are known for passing the news along in a timely fashion). > Relay-Version: version B 2.10 5/3/83; site rayssd.UUCP > Posting-Version: version B 2.10.1 6/24/83; site ru-cs44.UUCP > Path: rayssd!brunix!foxvax1!wjh12!harvard!seismo!mcvax!ukc!ru-cs44!adrian > From: adrian@ru-cs44.UUCP > Newsgroups: net.sources > Subject: rn - part 1 of 8 (reposting) > Message-ID: <785@ru-cs44.UUCP> > Date: Sat, 27-Oct-84 11:44:47 EDT > Article-I.D.: ru-cs44.785 > Posted: Sat Oct 27 11:44:47 1984 > Date-Received: Wed, 24-Oct-84 09:44:11 EDT > Organization: Reading Univ. UK. > Lines: 1967 Not bad huh? Passed through seven other sites and STILL got here three days before it was posted. I suppose that the folks in England will probably say that they always knew that "the colonies" were a little behind the times! -- Dave Brierley Raytheon Co.; Portsmouth RI; (401)-847-8000 x4073 ...!decvax!brunix!rayssd!dhb ...!allegra!rayssd!dhb ...!linus!rayssd!dhb
jim@hwcs.UUCP (Jim Crammond) (10/30/84)
> I have seen discussions here before about time warps whereby an article > could get from one coast to the other several hours before it was posted > but the trans-atlantic link has now got that beaten by a mile. The > following article arrived here on 10/24 after having passed across the > Atlantic and through several sites (not all of which are known for > passing the news along in a timely fashion). This bug is due to a combination of two things: 1. When getdate converts time from a timezone which is -11 hours from GMT it gets it wrong and returns a time which is one week (-11 hours) in the future. 2. The standard (2.10.1) getdate.y considered "BST" to be "Bering Standard Time" which is clearly wrong because as everyone knows BST is really "British Summer Time". Well, okay BST can mean Bering time too but surely there's no one on the net in the Aleutian Islands, is there? Anyway, Bering Standard Time happens to be -11 hours from GMT. Most uk sites fixed their getdate.y so that BST was equivalent to "GMT DST" which meant that the bug has all but gone. One site that is known still to have this bug is ukc, hence your article got into a time warp. Last Sunday we (in Britain) put our clocks back to GMT, so the bug will sleep once again until next March..... -Jim Crammond Heriot-Watt University, Edinburgh ..!ukc!kcl-cs!hwcs!jim
lee@west44.UUCP (Lee McLoughlin) (11/02/84)
The time warp occurs due to BST being interpreted at Bering Standard Time not British Summer Time at some sites in the UK. -- UKUUCP SUPPORT Lee McLoughlin <UK>!ukc!lmcl kcl-cs!lee "What you once thought was only a nightmare is now a reality!"