Skip to content

Commit

Permalink
ts2phc: Fix description of holdover option in man page.
Browse files Browse the repository at this point in the history
Fix the man page to explain that the LOCKED_STABLE servo state is
enabled by setting the servo_offset_threshold, not
servo_num_offset_values, which is already enabled by default.

Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
  • Loading branch information
mlichvar authored and richardcochran committed Sep 4, 2024
1 parent bc5d3d0 commit 3cf1795
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ts2phc.8
Original file line number Diff line number Diff line change
Expand Up @@ -283,7 +283,7 @@ The holdover interval, specified in seconds. When the ToD information stops
working (e.g. GNSS receiver lost its fix), ts2phc is allowed for the specified
interval to continue synchronizing the target clock as long as the servo is in
the SERVO_LOCKED_STABLE state. The servo state needs be enabled by the
\fBservo_num_offset_values\fP option. The holdover is not supported with the
\fBservo_offset_threshold\fP option. The holdover is not supported with the
\fB-a\fP option and when \fBts2phc.extts_polarity\fP is set to \fIboth\fP.
The default is 0 (disabled).

Expand Down

0 comments on commit 3cf1795

Please sign in to comment.