On 2005-10-26, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Here is the configuration file for the brodcastclient: > # > # ntpd configuratoin file > # > #act as a broadcast client > broadcastclient > disable auth > > # write drift file > driftfile /var/ntp/ntp.drift
The configuration shown above does not match the 'ntpq -p' output shown below (which I've reformatted for readability). > and the output of `ntpq -p`: > remote refid st t when poll reach delay offset disp >==================================================================== > -puma iix.net.il 3 - 13 16 377 0.72 -4.632 0.37 > -pussycat gatekeeper.no-s 2 - 30 64 377 0.56 -10.886 3.16 puma and pussycat are most likely being rejected because of their offsets. > *panda pussycat 3 u 58 64 376 0.69 -3.413 1.08 > +lioness pussycat 3 u 1 64 377 0.75 -3.544 0.82 > +tiger pussycat 3 u 47 64 176 0.75 -3.297 1.10 > -prbk1 pussycat 3 u 6 128 377 0.79 -10.512 4.27 > -db2test pussycat 3 u 5 256 377 0.67 -2.976 1.40 However, these 5 systems _are_ using pussycat as their sys_peer (i.e. they're synced to pussycat). > -db1test lioness 4 u 49 256 377 0.76 -2.705 0.87 > -panther lioness 4 u 150 256 376 1.11 -1.781 3.08 > > pussycat and puma are the servers that poll from the internet. All the > other systems are unicast server that have puma and pussycat as their > servers and each other as peer... The configuration you included above does not show the peered hosts. -- Steve Kostecke <[EMAIL PROTECTED]> NTP Public Services Project - http://ntp.isc.org/ _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
