[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: No Escape
I think it is OK to run SMTP on your MS Windows system
_IF_ the NTP server you point it to is
1) On your local 100BaseT network segment
2) Properly installed and sync'd to multiple
authorative time sources.
The delay over 100BaseT in on the order of 10ms
and you can program your dumb Windows PC SNTP client to
query the local NTP server every 5 minutes. Even the poor
PC clock will not drift much in 5 minutes. Any "jump"
would be close to the clock resolution and not noticed.
This does require a local NTP server. Great, so now you
have a use for that old 486 with 8MB RAM.
My warning about SNTP was not to use it over the Internet.
It works reasonably well on a local network if you have a
stable NTP server.
> -----Original Message-----
> From: Cary Chleborad [mailto:firstname.lastname@example.org]
> Sent: Wednesday, March 14, 2001 12:20 AM
> To: Albertson, Chris
> Cc: email@example.com
> Subject: Re: No Escape
> > Yes, NTP is the best possible solution, literally.
> > Watch out about some Windows NTP clients. The ones I found
> > use what's called "SNTP". This is a Simplified (dumbed down)
> > version of the NTP protocol. SNTP simply asks a server for
> > the current time then _jumps_ the local clock to whatever the
> > server returns.
> I have yet to find a Windows NTP program that doesn't do this. I
> mentioned the NTP stuff because the TASS stuff is running on Linux -
> which has a rather nice implementation of the code.