NTP daemon problem
by mackowiakp from LinuxQuestions.org on (#6EKGT)
I have an HP mini PC (Linux based) in a remote location and several sensors connecting to it via Wi-Fi.
The mini PC runs an NTP daemon and the sensors synchronize their time with the mini PC via NTP.
The connection to this remote location (via GSM Edge) is very poor and there are often long interruptions in communication.
The problem is with time synchronization between the sensors and the mini PC. The synchronization time is very long (e.g. after rebooting the sensor) or - when there is no Internet connection - it does not take place at all.
As if the NTP daemon on the mini PC only acted as a proxy between the sensor and the time patterns defined in the NTP server configuration.
How to configure the time server so that it provides its own current time and does not (most likely) query external servers?
Below is the NTP server configuration.
Code:root# grep "^[^#*/;]" /etc/ntp.conf
driftfile /home/pi/ramdisk/ntp.drift
logfile /dev/null
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
pool 0.ntp.icm.edu.pl prefer
pool 1.pool.ntp.org iburst
pool 2.ntp.navi.pl iburst
pool 3.time.windows.com iburst
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery
disable auth
tinker panic 0
The mini PC runs an NTP daemon and the sensors synchronize their time with the mini PC via NTP.
The connection to this remote location (via GSM Edge) is very poor and there are often long interruptions in communication.
The problem is with time synchronization between the sensors and the mini PC. The synchronization time is very long (e.g. after rebooting the sensor) or - when there is no Internet connection - it does not take place at all.
As if the NTP daemon on the mini PC only acted as a proxy between the sensor and the time patterns defined in the NTP server configuration.
How to configure the time server so that it provides its own current time and does not (most likely) query external servers?
Below is the NTP server configuration.
Code:root# grep "^[^#*/;]" /etc/ntp.conf
driftfile /home/pi/ramdisk/ntp.drift
logfile /dev/null
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
pool 0.ntp.icm.edu.pl prefer
pool 1.pool.ntp.org iburst
pool 2.ntp.navi.pl iburst
pool 3.time.windows.com iburst
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery
disable auth
tinker panic 0