A while back, support for memory locking and real-time scheduling was added to more platforms. The chronyd documentation wasn't updated at that time (chronyd.conf was). This patch fixes that.
--- doc/chronyd.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/chronyd.adoc b/doc/chronyd.adoc index d3b78a4..8f2051e 100644 --- a/doc/chronyd.adoc +++ b/doc/chronyd.adoc @@ -146,15 +146,15 @@ system calls. If the filter is missing some system call, *chronyd* could be killed even in normal operation. *-P* _priority_:: -On Linux, this option will select the SCHED_FIFO real-time scheduler at the -specified priority (which must be between 0 and 100). On macOS, this option -must have either a value of 0 (the default) to disable the thread time -constraint policy or 1 for the policy to be enabled. Other systems do not -support this option. +On Linux, FreeBSD, NetBSD, and Solaris, this option will select the SCHED_FIFO +real-time scheduler at the specified priority (which must be between 0 and +100). On macOS, this option must have either a value of 0 (the default) to +disable the thread time constraint policy or 1 for the policy to be enabled. +Other systems do not support this option. *-m*:: This option will lock *chronyd* into RAM so that it will never be paged out. -This mode is only supported on Linux. +This mode is only supported on Linux, FreeBSD, NetBSD, and Solaris. *-x*:: This option disables the control of the system clock. *chronyd* will not try to -- 2.32.0 -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.