[Sa] Fwd: ntp проблеми

[Vasil Kolev]

В 15:25 +0200 на 25.02.2012 (сб), Georgi Georgiev написа:
> Като гледам в wiki-то никой не си е постнал конф-а, така че остава да
> помоля някой тук, но интересното е, че в конфа няма нещо особено
> (редовете са малко няма какво да се сбърка)..гледам някои с cron
> синхронизират. 


Синхронизирането с cron не е добра идея.

Attach-нал съм един config от моите.

Също така, ntpq/ntpdc имат команда 'sysinfo', която ползава статуса,
например:

vasil at cassie:~$ ntpdc 
ntpdc> sysinfo
system peer:          212.70.148.12
system peer mode:     client
leap indicator:       00
stratum:              3
precision:            -18
root distance:        0.00581 s
root dispersion:      0.05959 s
reference ID:         [212.70.148.12]
reference time:       d2f35ce3.804c4ead  Sat, Feb 25 2012 15:13:07.501
system flags:         auth monitor ntp kernel stats 
jitter:               0.001038 s
stability:            0.000 ppm
broadcastdelay:       0.000000 s
authdelay:            0.000000 s

Двете важни неща са stratum (трябва да е под 5) и leap indicator (00).
-- 
Regards,
Vasil Kolev
-------------- next part --------------
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift


# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable


# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example

# pool.ntp.org maps to about 1000 low-stratum NTP servers.  Your server will
# pick a different set every time it starts up.  Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
server 0.debian.pool.ntp.org iburst
server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst


# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details.  The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines.  Please do this only if you trust everybody on the network!
#disable auth
#broadcastclient
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ludost.net/pipermail/sa/attachments/20120225/94ccc7d3/attachment.pgp>