SO_TIMESTAMP may go away

[Gary E. Miller]

Yo Hal!

Whoops, sorry, this was a reply to the other thread...
> 
> On Mon, 04 Mar 2019 19:31:07 -0800
> Hal Murray via devel <devel at ntpsec.org> wrote:
> 
> > dfoxfranke at gmail.com said:  
> > > One thing to keep in mind is that if the client is using
> > > SO_TIMESTAMP but the server isn't, or vice versa, you're going to
> > > introduce a persistent inaccuracy on the order of a microsecond,
> > > due to the resulting asymmetry in the point at which the timestamp
> > > is captured.     
> > 
> > That's another reason it's hard to notice.  If both systems do it
> > wrong, the errors cancel.  Or partially cancel if their CPU speed
> > doesn't match.  
> 
> Yeah, and that still leaves us reading this differently...
> 
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
> 	gem at rellim.com  Tel:+1 541 382 8588
> 
> 	    Veritas liberabit vos. -- Quid est veritas?
>     "If you can’t measure it, you can’t improve it." - Lord Kelvin




RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 851 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20190304/cb694de0/attachment.bin>