On Fri, 14 Feb 2003, Steven Glogger wrote:
> try: time.ethz.ch
> swisstime has sometimes problems...
>
> iroot@idefix(~)> ping time.ethz.ch
> PING weasel.ethz.ch (129.132.97.15) from 81.94.96.66 : 56(84) bytes of data.
> 64 bytes from weasel-rz-fast.ethz.ch (129.132.97.15): icmp_seq=1 ttl=246
> time=6.89 ms
While time.ethz.ch is reachble with ping, it's still not what you want
as a replacement for swisstime:
node:~> ntptrace time.ethz.ch
weasel-rz-fast.ethz.ch: stratum 16, offset 0.060622, synch distance 1.31931
0.0.0.0: *Not Synchronized*
node:~> ntpq -c peers time
remote refid st t when poll reach delay offset jitter
============================================================================
swisstime.ee.et 0.0.0.0 16 - - 64 0 0.000 0.000 16000.0
This means that time.ethz.ch is using swisstime.ee.ethz.ch as its own
timeserver...
For our own server we use the following time servers (from /etc/ntp.conf):
server swisstime.ethz.ch
server time2.euro.apple.com
server time.unizh.ch
server time.inf.ethz.ch
server metasweb01.admin.ch
While we are at it: Wouldn't it be a good idea to have a stable
timeserver at the center of the swiss internet, like e.g. time.tix.ch?
HTH,
Felix
--
Felix Rauch, research assistant at laboratory for computersystems, ETH Zuerich
http://www.nice.ch/~felix/ Member of Swiss Internet User Group: www.siug.ch
This article contains my personal view only! Use of my addresses for marketing
purposes is hereby strictly prohibited according to swiss privacy laws.
----------------------------------------------
[EMAIL PROTECTED] Maillist-Archive:
http://www.mail-archive.com/swinog%40swinog.ch/
