| PLEX86 | ||
|
NTP problem I thinkAre you looking for a new Operating System 271 OK, let's start with the basics: Do you know what Usenet is? Do you know what a News... Problems usibg Cervisia basics OK, I finally got it sort of working. But I'm still having problems getting the revisions of files to update the original, repositoried files. If I'm reading the docs right, when you UPDATE and COMIT... My main machine communicates with four NTP time servers and seems to synchronize very well. For example: NTP problem I think. 269 Jean-David Beyer I let it keep running like that and it calmed down and now talks like this: addtosyslog: synchronized to 192.168.1.251, stratum 2 authagekeys: at 780 keys 1 expired 0 authagekeys: at 840... remote refid st t when poll reach delay offset jitter ============================================================================== *clock2.redhat.c .CDMA. 1 u 884 1024 377 44.875 0.953 0.140 -ip-207-145-113- .GPS. 1 u 651 1024 377 98.490 -4.737 0.344 +206.17.5.9 ntp-1.cns.vt.ed 3 u 68 plus 15 1024 377 35.956 -0.235 1.110 +qnan.org tick.usno.navy. 2 u 730 1024 377 51.688 -0.499 0.720 But my other machine uses the first one as its time server, and it does poorly. For example (these are 15 minutes apart): remote refid st t when poll reach delay offset jitter ============================================================================== trillian.locald 66.187.224.4 2 u 49 64 177 0.402 -84.257 49.075 *trillian.locald 66.187.224.4 2 u 42 64 377 0.499 -247.32 37.68 plus 18 *trillian.locald 66.187.224.4 2 u 39 64 37 0.557 31.644 26.555 *trillian.locald 66.187.224.4 2 u 33 64 377 0.493 84.597 15.818 *trillian.locald 66.187.224.4 2 u 93 128 377 0.440 43.005 32.315 *trillian.locald 66.187.224.4 2 u 91 128 377 0.429 87.670 13.996 Not shown (because I do not have it) is that sometimes the poll interval goes up to about 256, but the offset starts to go up or down, eventually too far, and it starts over again. This is often when the reach differs from 377. But why should it do that? Sometimes the poll interval has gone as high as 512, but not very long. These machines are less than 10 feet apart connected on a very lightly used CAT5 ethernet cable. Note it seems to have missed three synch attempts (reach in the third entry). NTP problem I think. 268 Dan Espen A little shell script: $ while true; do date; ls -lvar-lib-ntp-drift; catvar-lib-ntp-drift; sleep 900; done Mine talks like this... Why does it miss synch attempts? It seems the ethernet connection between the machines is OK: $sbin-ifconfig eth0 Link encap:Ethernet HWaddr 00:30:48:29:1D:5E inet addr:192.168.1.251 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:313619 errors:0 dropped:0 overruns:0 frame:0 TX packets:177900 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 Base address:0x3000 Memory:fc200000-fc220000 -- .~. Jean-David Beyer Registered Linux User 85642. V PGP-Key: 9A2FC99A Registered Machine 241939. ^^-^^ 06:40:01 up 6 days, 22:07, 5 users, load average: 4.47, 4.23, 4.19
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||