HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS 4.0a w/ NDIS & PKTD
From: hliao@zeus.calstatela.edu (Henry Liao)
Date: 27 Aug 92 12:55:26 PDT
Distribution: world
Organization: Cal State University, Los Angeles
Keywords: pcnfs 4.0a, ndis, pktd, drivers

In article <17ivs0INN9k4@moe.ksu.ksu.edu>, wagner@chepil.weru.ksu.edu (Larry Wagner) writes:
|> hliao@zeus.calstatela.edu (Henry Liao) writes:
|> 
|> >A while back, someone mentioned that it's possible to run packet-based
|> >applications, ie NCSA Telnet, on top of PC-NFS 4.0a w/ NDIS drivers using
|> >some kind of NDIS<->PKTD driver.  Any idea.  
|> 
|> I don't know anything about NDIS drivers, but it is possible to do
|> what you want, PCNFS and packet driver apps together.  You need to
|> get the pktd.sys file to allow PCNFS to use a packet driver and
|> the pktmux package that allows "sharing" of the packet driver among
|> PCNFS and other packet driver apps like NCSA Telnet, etc.
|> Limitations of this approach are very well discussed in the pktmux
|> documentation.
	Thank you for the tip.  Since we are using NDIS drivers extensively
w/ PC-NFS, I prefer to find a NDIS<->PKTD solution.
|>...deleted... 
|> Larry E. Wagner                     | wagner@chepil.weru.ksu.edu
|> USDA-ARS Wind Erosion Research Unit | wagner@matt.ksu.ksu.edu
|> 105B East Waters Hall, KSU          | phone: (913) 532-6807 
|> Manhattan, KS 66506                 | fax:   (913) 532-6528

-Henry Liao					o
California State University, Los Angeles	 )>
Networks & Distributed Systems Group	     ___./]___
VOICE:	(213) 343-4537, 343-4530	hliao@calstatela.edu
FAX:	(213) 343-4575			hliao@csula.bitnet
#include <std/disclaimer.h>
Newsgroups: comp.protocols.time.ntp
From: mrapple@quack.sac.ca.us (Nick Sayer)
Subject: Re: computer clock drift
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: Sat, 29 Aug 1992 17:54:42 GMT

franco@bbn.com (Frank A. Lonigro) writes:

>On average, do the system clocks, in the above mentioned hardware, drift
>more than a half a second an hour?  More than a half a second every 2 hours?
>Every 3 hours?  So on?  Just how bad are these clock in these computers?

Sun Sparcstations (`arch -k` = sun4c) have lousy clocks. They are
usually 100 ppm or so fast. Changing 'tick' in the kernel from
10000 to 9999 usually makes them fairly good. 100 ppm is
8.64 seconds per day. If you're running xntpd v3, 'xntpdc -c lo'
will report the actual ppm drift as the 'frequency'. If you're
running xntpd v2, the frequency number divided by 4096 is the
drift in ppm. My ELC runs xntpd v3 and listens to CHU. I have tick
set to 9999 and xntpdc says my drift is -0.5626373, or half a ppm
fast. That's .04 seconds per day or a bit more than a second
a month.

-- 
Nick Sayer <mrapple@quack.sac.ca.us> | "What walks down stairs, alone or in pairs,
N6QQQ @ N0ARY.#NOCAL.CA.USA.NA       |  rolls over your neighbor's dog?
37 19 49 N / 121 57 36 W             |  It's great for a snack, and fits on your back,
+1 408 249 9630, log in as 'guest'   |  It's Log! Log! Log!" (from Blam-o)
From: tierney@portnoy.lbl.gov.itg (Brian Tierney)
Newsgroups: comp.protocols.time.ntp
Subject: tickadj value for Sun 690mp??
Date: 2 Sep 1992 00:00:21 GMT
Organization: Lawrence Berkeley Laboratory
Distribution: world
Reply-To: tierney@portnoy.lbl.gov.itg
NNTP-Posting-Host: portnoy.lbl.gov

Does anyone know the tickadj value for a 690mp.  A value of 9999 seems to
work well on our other Suns, but not the 690 (I've also tried 9998, and
that doesnt seem to be any better)

Thanks.
---
/***********************************************************************/
/*  bltierney@lbl.gov      Brian Tierney, Lawrence Berkeley Laboratory */
/***********************************************************************/
From: gwolsk@seidc.UUCP (Guntram Wolski)
Newsgroups: comp.protocols.time.ntp
Subject: strange log messages from xntpd on MIPS RISCos 4.52
Date: 25 Aug 92 17:02:11 GMT
Article-I.D.: seidc.9208251702.AA10955
Distribution: inet
Organization: The Internet


I am running xntpd just fine on SUNOS 4.1.1 on my SUNs, but am getting
strange error messages in my /usr/adm/messages file when I run it
under RISCos 4.52 on my MIPs hardware:

Aug 23 00:02:38 bigsur xntpd[2482]: Previous time adjustment didn't complete
Aug 23 00:11:09 bigsur unix: Adjust CLOCK Hz by 2000 to 6301033
Aug 23 00:11:10 bigsur xntpd[2482]: Previous time adjustment didn't complete

This repeats in my /usr/adm/messages file.  Can anybody enlighten me
on how to fix this?  I have tried increasing/decreasing the CLOCK_ADJ
values in ntp_unixclock.c and include/ntp.h but that doesn't seem to
help.

--G
--
Guntram Wolski                   gwolsk@sei.com
Silicon Engineering, Inc.        408-438-5331 x112
...!{sgiblab,ames}!seidc!gwolsk
Newsgroups: comp.protocols.time.ntp
From: yasoda@ecs.isl.melco.co.jp (Gyota Yasoda)
Subject: The meaning of compliance
Organization: Mitsubishi Electric, Ofuna, Kanagawa, Japan
Distribution: comp
Date: Fri, 28 Aug 1992 12:28:19 GMT

    A simple question. 

    From the below data, what is frequency and compliance telling me?

xntpdc> loopinfo
offset:     0.0033369 seconds
frequency:  -0.3749584 seconds
compliance: -0.0002477 seconds
timer:      28 seconds

    I know that that it is indicating that there is a 3.3369ms difference 
between this machine and its server, but I just can't get the feeling of 
what frequency and especially compliance is supposed to tell me.

    It says in the RFC, "compliance ... an exponential average of all prior 
updates". How do I tie in these three values together?

        Gyota Yasoda [Mitsubishi Electric]
Newsgroups: comp.protocols.time.ntp
From: mrl@uai.com (Mark R. Ludwig)
Subject: Joining the Internet
Organization: Universal Analytics, Inc., Torrance (LA), CA
Date: 27 Aug 92 07:55:46

Can someone point me to information about how to start synchronizing
our local network with the connected Internet?

Thanks in advance.$$
-- 
INET: mrl@uai.com      BANG: uunet!uaisun4!mrl      ICBM: USA; Lower Left Coast
  "You can get a crowd to clap at a phone number, if the inflection is right."
   -- Dave Ross
Newsgroups: comp.protocols.time.ntp
From: kwolters@fred.wellesley.edu (Keith Wolters)
Subject: Re: insane peers
Organization: Wellesley College
X-Newsreader: Tin 1.1 PL5
Date: Thu, 27 Aug 1992 16:15:19 GMT

Keith Wolters (kwolters@fred.wellesley.edu) wrote:
: Hi.  I just installed xntp on a number of machines here so I still
: don't completly understand this stuff.  On a MicroVAX II running
: Ultrix 4.0 I noticed that if I use the lassociations command within
: ntpq, all my peers are listed as being insane.  Can anyone tell what
: that indicates.  Thanks.
I think I figured it out.  I had forgotten that I had that machine
running as timed master.  Once I got rid of the timed daemon.  It got
in line.

Keith
--
Keith Wolters
System Manager
Wellesley College
From: fct@swlvx2.msd.ray.com (Fred Thompson)
Newsgroups: comp.protocols.time.ntp
Subject: Looking for Config file for xntp3 for SGI
Keywords: xntp3 Config Silicon Graphics
Date: 1 Sep 92 15:21:39 GMT
Article-I.D.: swlvx2.1992Sep1.152139.9955
Organization: Raytheon Company, Tewksbury, MA

As the subject says, I am looking for the COnfig file to build xntp3 for
a Silicon Graphics machine. The one I tried doesn't work. ntpdate dies
with an alarm clock error, as does xntpd. Thanks


-- 
Fred Thompson,   ...!ulowell!swlvx2!fct  or  fct@swlvx2.msd.ray.com
Raytheon Co,     Missile Systems Division, Tewksbury, Mass. 01876
Newsgroups: comp.protocols.time.ntp,comp.unix.aix
From: richb@kronos.com (Rich Braun)
Subject: Re: NTP on RS/6000 - anyone got it working
Date: Tue, 01 Sep 1992 15:53:14 GMT
Organization: Kronos Inc. / Waltham, MA
Disclaimer: This posting is a personal opinion and not that of Kronos Inc.

kdenning@portal.hq.videocart.com (Karl Denninger) writes:
>I'm trying to get NTP working on our network of RS/6000s here, and having
>one hell of a time of it.
>
>What gives?  Is there some bizarreness with AIX that is needed to make this
>work?

We've been running an experimental version on two of our RS/6000s for the
past couple of months.  The University of Delaware is the maintainer of
NTP, and that's where I got this version.  Their anonymous ftp server
no longer has the file I downloaded; I'm not sure which version to use.
There is a brand new distribution in udel.edu:/pub/ntp/xntp3.tar.Z, and
I'll bet that includes RS/6000 support:  take a look there.

In answer to your question, yes, there is a "bizarreness" about AIX
which requires special support.

-rich
From: iglesias@draco.acs.uci.edu (Mike Iglesias)
Subject: Changes to allow tick and tickadj to be set from Config files
Newsgroups: comp.protocols.time.ntp
Organization: University of California, Irvine
Date: 26 Aug 92 16:04:05 GMT


As I promised, here are the changes to make xntpd/ntp_unixclock.c accept
tick and tickadj from the Config files.  Just put -DTICK=xx and 
-DTICKADJ=xx on the DEFS line and ntp_unixclock.c will pick up those
values.  For example:

DEFS= -DREFCLOCK -DNOKMEM -DDEBUG -D_BSD_SIGNALS -DTICK=100 -DTICKADJ=1

Note that this only works for systems that need -DNOKMEM in the Config
file.  If either (or both) TICK and TICKADJ are not specified in the Config
file, the old way of setting them will still work. 


Mike Iglesias                        Internet:    iglesias@draco.acs.uci.edu
University of California, Irvine     BITNET:      iglesias@uci
Office of Academic Computing         uucp:        ...!ucbvax!ucivax!iglesias
Distributed Computing Support        phone:       (714) 856-6926


Feed this to patch:

*** ntp_unixclock.c.dist	Wed Aug 19 19:27:31 1992
--- ntp_unixclock.c	Tue Aug 25 13:02:09 1992
***************
*** 600,611 ****
--- 600,621 ----
  #ifndef HZ
  #define HZ	60
  #endif
+ #ifdef TICKADJ
+ 	*tickadj = TICKADJ;
+ #else	
  #ifdef RS6000
  	*tickadj = 1000;
  #else
  	*tickadj = 500 / HZ;
  #endif /*RS6000*/
+ #endif /*TICKADJ*/
+ 
+ #ifdef TICK
+ 	*tick = TICK;
+ #else
  	*tick = 1000000L / HZ;
+ #endif /*TICK*/
+ 
  #ifdef	DEBUG
  	if (debug)
  		printf("NOTE: Using preset values for tick and tickadj !!\n");
Newsgroups: comp.protocols.time.ntp
From: nrh@buzz.bellcore.com (Nat Howard)
Subject:  flash is going away, so...
Reply-To: nrh@bellcore.com (Nat Howard)
Organization: Bellcore, Morristown, NJ
Date: Thu, 3 Sep 92 16:43:06 GMT

The entry for "flash.bellcore.com" in clocks.txt should be changed.

Old:

flash.bellcore.com (128.96.32.20)
Location: Bell Communications Research, Morristown NJ
Synchronization: NTP primary (WWVB clock), VAX/Unix
Service area: JvNCnet
Access policy: open access
Contact: Nat Howard (timekeeper@bellcore.com)


New:
pi.bellcore.com (128.96.60.5)
Location: Bell Communications Research, Morristown NJ
Synchronization: NTP primary (WWVB clock), Ultrix
Service area: JvNCnet
Access policy: open access
Contact: Nat Howard (timekeeper@bellcore.com)


Just FYI, whoever inherits the flash name will probably
also be running xntp, but at a lower stratum.

It's not clear what machine the flash clock will go to, but
when it goes, I might well announce a second server.

Finally, I'll probably make "pi" start chiming with the hosts
flash chimes with now.

I'll also post this note to comp.protocols.time.ntp, so that
folks chiming with us can make appropriate arrangements.
From: iglesias@draco.acs.uci.edu (Mike Iglesias)
Subject: xntp v3 Config file for Convex?
Newsgroups: comp.protocols.time.ntp
Organization: University of California, Irvine
Date: 26 Aug 92 22:21:31 GMT


I'd like to start running xntpd on our Convex C240 (ConvexOS 10.0).  Does
anyone have a Config file for the Convex?


Mike
Newsgroups: comp.protocols.time.ntp
From: dundas@chip.Jpl.Nasa.Gov (John Dundas)
Subject: Looking for Spectracom help
Organization: Information Systems Engineering Grp, JPL
Date: Wed, 2 Sep 1992 15:11:03 GMT

I'm trying to use xntp v3 an an A/UX system with a Spectracom Netclock/2
directly attached.  I'm having trouble with the routine wwvb_process()
in the file refclock_wwvb.c.  The file doesn't indicate who the author is
so I hope that individual, or someone knowledgeable, could contact me.

For those interested, I'm having two problems, one general, one specific.
First, there is some double error accounting in that this routine increments
wwvb->baddata and so does the calling routine wwvb_receive() when this
routine returns an error.  Second, I need some help with the filtering code
itself.  I seem to be getting some strange values out of it and I don't know
why.  The clock itself is sync'd and the buffer string it returns is good.

Any help is appreciated!

John Dundas
dundas@salt.jpl.nasa.gov
Xref: sparky comp.protocols.time.ntp:860 comp.unix.aix:9295
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.protocols.time.ntp,comp.unix.aix
Subject: Re: NTP on RS/6000 - anyone got it working
Date: 26 Aug 92 19:29:10 GMT
Organization: /etc/organization


In article <1992Aug26.010304.2081@portal.hq.videocart.com>
kdenning@portal.hq.videocart.com (Karl Denninger) writes:
>
> "ntp" works.  However, ntpd exits with an alarm call.
>
> Is there some bizarreness with AIX that is needed to make this work?

The only "bizarreness" is that AIX by default uses POSIX signals, which
need to be reset after each use.  Link with `-lbsd' or turn off the
SA_OLDSTYLE flag and it should work.

-- 
 \   Charles Hannum, mycroft@ai.mit.edu
 /\  White heterosexual atheist male (WHAM) pride!
From: ben@osiris.usi.utah.edu (Ben Pratt)
Subject: Re: NTP on RS/6000 - anyone got it working
Organization: Utah Supercomputing Institute
Date: Thu, 3 Sep 92 03:24:38 GMT

In article <1992Aug26.192910.22056@mintaka.lcs.mit.edu> 
	mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes:
  > >
  > > "ntp" works.  However, ntpd exits with an alarm call.
  > >
  > > Is there some bizarreness with AIX that is needed to make this work?
  > 
  > The only "bizarreness" is that AIX by default uses POSIX signals, which
  > need to be reset after each use.  Link with `-lbsd' or turn off the
  > SA_OLDSTYLE flag and it should work.

The other ``bizarrness'' is that the tickadj symbol doesn't exist in the
AIX kernel, so you have to hack the code in xntpd.c to avoid a kernel
name lookup and simply hardcode the setting...

Ben
Newsgroups: comp.protocols.time.ntp
From: news@rrzn.uni-hannover.de (News-service administration)
Subject: Looking for Config-File for xntp3 SCO
Organization: RRZN
X-Newsreader: Tin 1.1 PL4
Date: Wed, 2 Sep 1992 07:54:12 GMT

I'm looking for an Config-File for an SCO-Unix-Machine
(Siemens/Nixdorf wx200 with '486 CPU)

Thanks in advance

Wolfgang 

--
Wolfgang Zocher
Regionales Rechenzentrum f. Niedersachsen
Schlosswender Str. 5
3000 Hannover
From: maer@nmr.lpc.ethz.ch (Matthias Ernst)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Problems running xntp v3 on SGI Indigo
Date: 26 Aug 92 06:30:16 GMT
Distribution: inet
Organization: The Internet

-> I'm trying to run the latest release of xntp v3 on an SGI Indigo running
-> v4.0.1 of the OS.  xntpd is having trouble keeping the clock in sync,
-> generating lots of STEP adjustments in the syslog file.  Since the
-> SGI build uses -DNOKMEM, it's using the built-in values for tick and
-> tickadj.  I'm assuming these are wrong for the SGI Indigo and that
-> is what is causing the problem.  Does anyone have a good idea for
-> tick and tickadj values for Indigos?
-> 
-> It might be nice to have tick and tickadj settable via the Makefile,
-> say maybe -DTICK=xx and -DTICKADJ=xx, so that building xntp forsystems 
-> that need -DNOKMEM would be easier.  I noticed that there are special
-> cases in the code for the RS6000.  If someone can give me some good values
-> for tick and tickadj for the SGI, I can work up the changes to the
-> code to make -DTICK and -DTICKADJ work, with the current defaults if
-> -DTICK and -DTICKADJ are not set.
-> 
-> 
-> Mike Iglesias                        Internet:    iglesias@draco.acs.uci.edu
-> University of California, Irvine     BITNET:      iglesias@uci
-> Office of Academic Computing         uucp:        ...!ucbvax!ucivax!iglesias
-> Distributed Computing Support        phone:       (714) 856-6926
-> 

I think it must be a specific problem of the INDIGO. The latest version of
xntp3 runs on our SGI 4D/220 (IRIX4.0.1) very stable and I have seen no steps 
during the last two weeks (try ntpq -p redfield.ethz.ch). I saw similar 
problems on IBM/RS6000 when tickadj was too small. That is the reason why I
hard coded the value of 1000 for tickadj on the RS6000 in the code. Try 
setting a larger value of tickadj and check whether xntpd3 is then able
to sync to the other machine. 
I think  its a good idea to be able to set tick and tickadj in the Configfile
but we need a volunteer to do this :-).

Matthias

+-----------------------------------------------------------------------------+
| Matthias Ernst                          Domain: maer@nmr.lpc.ethz.ch        |
| Institut fuer physikalische Chemie      Bitnet: maer@czheth5a.bitnet        |
| Eidgenoessische Technische Hochschule   UUCP:   ...!mcsun!chx400!ethz!maer  |
| ETH-Zentrum                             Phone:  +41/1/256-4374              |
| CH-8092 Zuerich                         Fax:    +41/1/252-3402              |
+-----------------------------------------------------------------------------+
From: shibumi@turbo.bio.net (Kenton A. Hoover)
Newsgroups: comp.protocols.time.ntp
Subject: Accuracy problems on the Heathkit clock
Date: 2 Sep 92 18:39:26 GMT
Reply-To: shibumi@turbo.bio.net
Organization: GenBank Computing Resource for Mol. Biology

At some point in time, there was some discussion about how Heathkit clocks
made poor sources for chimers.  I just recieved the technical manuals for the 
new Motorola 6-channel GPS core receiver.  The interface on it maxes out
at 9600 baud, and I was trying to figure out if it would suffer from the
same problems as the Heathkit in terms of accuracy.  Would someone care to
summarize the reason for the Heathkit's problems?

BTW, the Motorola 6-channel GPS core reciever eval kit will cost $1200.00
and will be available in November. 

| Kenton A. Hoover                                 |      shibumi@net.bio.net |
| BIOSCI Network Administrator                     |                          |
| GenBank/IntelliGenetics, Inc.                    |          +1 415 962 7300 |
|=========== net.bio.net -- The New Home of the bionet Newsgroups ============|
| The United States Tax Court ruled in favor of the Internal Revenue          |
| Service's claim that Irwin Schiff would have to pay $92,000 in back taxes   |
| and penalties.  Schiff is the author of "How Anyone Can Stop Paying Income  |
| Taxes," the now-failed thesis that the IRS lacked the authority to tax      |
| anyone who did not file a return, a strategy he had employed since 1973.    |
Newsgroups: comp.protocols.time.ntp,comp.unix.aix
From: kdenning@portal.hq.videocart.com (Karl Denninger)
Subject: NTP on RS/6000 - anyone got it working
Organization: VideOcart Inc.
Date: Wed, 26 Aug 1992 01:03:04 GMT

I'm trying to get NTP working on our network of RS/6000s here, and having
one hell of a time of it.

"ntp" works.  However, ntpd exits with an alarm call.  The server I am
trying to talk to IS online and responding (I can hit it with an "ntp"
request and it works).

What gives?  Is there some bizarreness with AIX that is needed to make this
work?

--
Karl Denninger 		Inet:  kdenning@hq.videocart.com
VideOcart Inc.		Voice: (312) 987-5022
From: iglesias@draco.acs.uci.edu (Mike Iglesias)
Subject: Problems running xntp v3 on SGI Indigo
Newsgroups: comp.protocols.time.ntp
Organization: University of California, Irvine
Date: 25 Aug 92 16:51:59 GMT

I'm trying to run the latest release of xntp v3 on an SGI Indigo running
v4.0.1 of the OS.  xntpd is having trouble keeping the clock in sync,
generating lots of STEP adjustments in the syslog file.  Since the
SGI build uses -DNOKMEM, it's using the built-in values for tick and
tickadj.  I'm assuming these are wrong for the SGI Indigo and that
is what is causing the problem.  Does anyone have a good idea for
tick and tickadj values for Indigos?

It might be nice to have tick and tickadj settable via the Makefile,
say maybe -DTICK=xx and -DTICKADJ=xx, so that building xntp forsystems 
that need -DNOKMEM would be easier.  I noticed that there are special
cases in the code for the RS6000.  If someone can give me some good values
for tick and tickadj for the SGI, I can work up the changes to the
code to make -DTICK and -DTICKADJ work, with the current defaults if
-DTICK and -DTICKADJ are not set.


Mike Iglesias                        Internet:    iglesias@draco.acs.uci.edu
University of California, Irvine     BITNET:      iglesias@uci
Office of Academic Computing         uucp:        ...!ucbvax!ucivax!iglesias
Distributed Computing Support        phone:       (714) 856-6926
Newsgroups: comp.protocols.time.ntp
From: mrapple@quack.sac.ca.us (Nick Sayer)
Subject: Re: Accuracy problems on the Heathkit clock
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
Date: Thu, 3 Sep 1992 19:54:24 GMT

shibumi@turbo.bio.net (Kenton A. Hoover) writes:

>At some point in time, there was some discussion about how Heathkit clocks
>made poor sources for chimers.  I just recieved the technical manuals for the 
>new Motorola 6-channel GPS core receiver.  The interface on it maxes out
>at 9600 baud, and I was trying to figure out if it would suffer from the
>same problems as the Heathkit in terms of accuracy.  Would someone care to
>summarize the reason for the Heathkit's problems?

They pretty much boil down to two things:

1. There is no point in the RS-232 timecode that is an official
"on-time" mark. At 9600 bps, the 20 characters (or so) in the
timecode take 20/960 of a second, or about 20 msec.

2. The timecode lacks sufficient granularity. The timecode itself
contains time down to the nearest 100 msec. This wouldn't be so
bad if it was guaranteed to start or end on time, but that is
not the case. The timecode starts whenever it likes within that
100 msec window. This is the truly damning fault.

#define FLAME
Both of these faults were confirmed by technical support personel
at Heath hot-line. They acknowledged that it was not possible
to get 5 ms timestamps from the clock. They said that the clock
was not supposed to be considered a serious tool. I suspect
this sort of attitude is what did Heath in.
#undef FLAME

The moral: The GC-100 can be trusted to about +/- 120 msec. Hardly
the 5 ms they claim. To be fair, it is possible that the clock
internally gets +/- 5 ms, but that isn't terribly helpful.

>BTW, the Motorola 6-channel GPS core reciever eval kit will cost $1200.00
>and will be available in November. 

Most reasonable clocks define some point within the timecode at which
the time given by the timecode is accurate. For example, CHU timestamps
are on-time at the end of the last stop-bit in the code. Some other
systems send a garbage character and use the begining or end of a
particular bit in that garbage character to signify the point at
which the next (or previous) timestamp is in effect. You can then take
a local clock reading of what time your system THINKS it is when that
bit has arrived, then compare that stamp with the time that the
bit in question represents and thus get a good difference between
the standard and your local clock.

-- 
Nick Sayer <mrapple@quack.sac.ca.us> | 
N6QQQ @ N0ARY.#NOCAL.CA.USA.NA       | "Leave everything to me!"
37 19 49 N / 121 57 36 W             | 
+1 408 249 9630, log in as 'guest'   |     -- Powdered Toast Man