Кто подскажет, почему один и тот же конфигурационный файл сервиса ntpd раньше работал под ASP Linux 9.0 и теперь не работает на SUSE 9.1 ? Не работает это значит по этому серверу клиенты не могут выставлять своё время, говорят server не отвечает. Хотя сам сервер для себя время выставляет как надо.
Вот его конфиг (ntp.conf):
--------------------------start--------------------------------------- # Prohibit general access to this service. restrict default ignore
# Permit all access over the loopback interface. This could # be tightened as well, but to do so would effect some of # the administrative functions. restrict 127.0.0.1
# -- CLIENT NETWORK ------- # Permit systems on this network to synchronize with this # time service. Do not permit those systems to modify the # configuration of this service. Also, do not use those # systems as peers for synchronization. # restrict 192.168.1.0 mask 255.255.255.0 notrust nomodify notrap restrict 10.0.3.0 mask 255.255.255.0 notrust nomodify notrap
# --- OUR TIMESERVERS ----- # or remove the default restrict line # Permit time synchronization with our time source, but do not # permit the source to query or modify the service on this system.
# restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap noquery # server mytrustedtimeserverip
# --- NTP MULTICASTCLIENT --- multicastclient # listen on default 224.0.1.1 restrict 224.0.1.1 mask 255.255.255.255 notrust nomodify notrap restrict 10.0.3.0 mask 255.255.255.0 notrust nomodify notrap
# --- GENERAL CONFIGURATION --- # # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # #server 127.127.1.0 # local clock #fudge 127.127.1.0 stratum 10 restrict 195.13.23.5 mask 255.255.255.255 nomodify notrap server 195.13.23.5
restrict 195.13.1.153 mask 255.255.255.255 nomodify notrap server 195.13.1.153
restrict 136.159.2.2 mask 255.255.255.255 nomodify notrap server 136.159.2.2
# # Drift file. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()'ing # it to the file. # driftfile /var/lib/ntp/drift/ntp.drift broadcastdelay 0.008 # # Keys file. If you want to diddle your server at run time, make a # keys file (mode 600 for sure) and define the key number to be # used for making requests. # # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. Note also that # ntpd is started with a -A flag, disabling authentication, that # will have to be removed as well. # # keys /etc/ntp.keys logfile /var/log/ntp # alternate log file # logconfig syncstatus + sysevents --------------------------------------------------end-----------------
P.S. Что-то мне этот переход не очень легко дается, все там не так как бы...
