On Sat, 05 Aug 2000, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Sat, 5 Aug 2000, Federico Sevilla III wrote:
> >
> > 2. Uses ntpdate from the xntp3 package to synchronize the system clock
> > with a time server, right now I'm using tock.usno.navy.mil, there's also
> > tick.usno.navy.mil and ntp2.usno.navy.mil, among others ;
> >
>
> I would suggest a closer time server, such as clock.cuhk.edu.hk (Chinese
> University of Hong Kong). Network latencies are less, and so you have
> less guesswork for NTP to do. More reliable. Can't remember URL of the
> list of NTP servers I found before, but I think it'd be best to find an
> NTP server which is networkologically close to you (Pacific Internet gives
> me ~500 ms latency on clock.cuhk.edu.hk, which was the best I could get
> off my list. Pacific's upstream is in Singapore, but I couldn't find an
> open access, freely-usable server there.).
Yes, I would suggest that one checks first just how far a particular time server
is before using it. HK may be geographically near to PH, but most providers
have their links go directly to the US internet backbone (sat-based ISPs), so
accessing HK would be much farther than the US in these cases.
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
