From bdf19f8fb2f4f2eff2c80bc629f7f6115c04c6e6 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 1 Apr 2016 09:48:36 +0200 Subject: Revert "time-util: fall back to CLOCK_MONOTONIC if CLOCK_BOOTTIME unsupported" --- src/basic/time-util.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'src/basic/time-util.c') diff --git a/src/basic/time-util.c b/src/basic/time-util.c index c16460a198..7ca764abeb 100644 --- a/src/basic/time-util.c +++ b/src/basic/time-util.c @@ -47,15 +47,12 @@ static clockid_t map_clock_id(clockid_t c) { /* Some more exotic archs (s390, ppc, …) lack the "ALARM" flavour of the clocks. Thus, clock_gettime() will * fail for them. Since they are essentially the same as their non-ALARM pendants (their only difference is * when timers are set on them), let's just map them accordingly. This way, we can get the correct time even on - * those archs. - * - * Also, older kernels don't support CLOCK_BOOTTIME: fall back to CLOCK_MONOTONIC. */ + * those archs. */ switch (c) { - case CLOCK_BOOTTIME: case CLOCK_BOOTTIME_ALARM: - return clock_boottime_or_monotonic (); + return CLOCK_BOOTTIME; case CLOCK_REALTIME_ALARM: return CLOCK_REALTIME; -- cgit v1.2.3-54-g00ecf