Brute force detection of monotonic clock as sysconf is unreliable. Instead rely on clock_gettime failing gracefully with an invalid clockid (which it should do).

1 files changed, 0 insertions, 9 deletions

diff --git a/README b/README
index ef7e7842..b3550c13 100644
--- a/README
+++ b/README
@@ -18,15 +18,6 @@ OS=BSD | Linux
 If you're building for an MMU-less system where fork() does not work, you
 should add -DTHERE_IS_NO_FORK to your CPPFLAGS.
 
-dhcpcd will try and use a monotonic clock when possible.
-Some libc implementations do not correctly report that they have a monotonic
-clock, but they have the headers to make it work. dhcpcd will warn about this.
-Without a monotonic clock, we fall victim of the year 2038 time_t bug on
-32-bit platforms AND the timers will be sufer from clock skew if the system
-clock changes.
-To force the use of a monotonic clock you can add -DFORCE_MONOTONIC
-to your CPPFLAGS.
-
 You can change the default dir with these knobs.
 For example, to satisfy FHS compliance you would do this:-
 LIBEXECDIR=/lib/dhcpcd