[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howtos:network_services:ntp [2022/06/30 22:41 (UTC)] – rewrite to Slackware 15.0 and current best practices metaedhowtos:network_services:ntp [2022/09/20 19:46 (UTC)] (current) – [Sources] tag to Slackware 15.0 and additional author metaed
Line 111: Line 111:
   # touch /var/log/ntp.log   # touch /var/log/ntp.log
   # chown ntp:ntp /var/log/ntp.log   # chown ntp:ntp /var/log/ntp.log
 +
 +==== Filtering the log ====
 +
 +NTP lets you filter certain messages out of the log, based on the message's
 +''class'' and ''type''. Currently there are four classes defined:
 +
 +  clock peer sync sys
 +
 +and four types defined:
 +
 +  info events status statistics
 +
 +Because the preinstalled Slackware ''/etc/ntp.conf'' does not customize the
 +filter, you get out-of-box behavior. NTP will pass messages that are tagged
 +with the ''sync'' class and drop all messages that are tagged with any other
 +class.
 +
 +<note important>
 +The out-of-box behavior unfortunately filters the message associated with at
 +least one common fatal condition (termination of the ntpd process when the
 +clock offset exceeds its panic threshold).
 +</note>
 +
 +If you want all available diagnostic messages logged, you should disable all
 +filtering by class or type in ''/etc/ntp.conf'':
 +
 +  logconfig =allall
  
 ===== Statistics gathering ===== ===== Statistics gathering =====
Line 215: Line 242:
 The risk that you run if you don't set //minclock//, //minsane//, and The risk that you run if you don't set //minclock//, //minsane//, and
 //maxclock// properly is that the NTP clock selection algorithm will get it //maxclock// properly is that the NTP clock selection algorithm will get it
-wrong at boot timeand give you inaccurate time, or even panic and exit.+wrong at boot time and give you inaccurate time, or even panic and exit.
 </note> </note>
  
Line 305: Line 332:
  
 System services that should wait to start until the clock is stable can be System services that should wait to start until the clock is stable can be
-preceded by the ''ntp-wait'' command, for example databases. For example, if+preceded by the ''ntp-wait'' command, for example databases. For example,
 you could conceivably edit the MariaDB section of ''/etc/rc.d/rc.M'' to read: you could conceivably edit the MariaDB section of ''/etc/rc.d/rc.M'' to read:
  
Line 423: Line 450:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must remove the tag-word "template" below before saving your new page --> <!-- You must remove the tag-word "template" below before saving your new page -->
-{{tag>howtos time clock synchronization author_kikinovak}}+{{tag>howtos time clock synchronization author_kikinovak slackware_15.0 author_metaed}}

Trace:

howtos:network_services:ntp ()