Hi,
I ran into an issue with musl libc on Linux where sched_setscheduler
isn't implemented. Overall, it seems that pthread_setschedparam is
more widely supported across different C libraries and OSs. For
chrony's purposes on Linux, it should make no difference which call is
used.
Below is the
Addendum: Incremental patch so we only include '-pthread' once in the
compilation flags.
Regards,
Stefan
diff --git a/configure b/configure
index 565b888..49ba7bc 100755
--- a/configure
+++ b/configure
@@ -227,6 +227,7 @@ feat_timestamping=1
try_timestamping=0
feat_ntp_signd=0
The extra line wrapping caused the issue.
Updated patch attached with an expanded commit message.
Regards,
Stefan
From d49ca2c7984bc43c2a71bccb382e445844b4acf3 Mon Sep 17 00:00:00 2001
From: "Stefan R. Filipek"
Date: Thu, 4 Apr 2019 19:12:39 -0400
Subject: [PATCH] sys_
> sched.h should be pthread.h?
I should actually include both. sched_get_priority_min/max() is still used.
Updated and squashed patch below.
Regards,
Stefan
>From 6ae435f7417a3d0c634183276a7e9e9ed04f2611 Mon Sep 17 00:00:00 2001
From: "Stefan R. Filipek"
Date: Thu, 4 Apr 201
Thanks for the feedback.
> Could that not lead into situations where chronyd randomly fails later after
> start when it needs to allocate more memory?
With MCL_FUTURE specified, yes it could fail. The thought was to just
abide by the previously set system limits (assuming that is why it
Real-time scheduling and memory locking is available on posix compliant
OSs. This patch centralizes this functionality and brings support to
FreeBSD, NetBSD, and Solaris.
---
configure| 27 ---
doc/chrony.conf.adoc | 46 +-
sys.c| 13 +++--
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
