From 20c1a21066a35b4776eca5a6e25c3f8aa50a0b84 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 18 Mar 2022 16:30:26 +0100 Subject: [PATCH] timesyncd: don't abort packet handling if we can't save the timestamp to disk This should not be a fatal error, and it isn't in the other place we call this. --- src/timesync/timesyncd-manager.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c index 193d13742b6..b491db23bc4 100644 --- a/src/timesync/timesyncd-manager.c +++ b/src/timesync/timesyncd-manager.c @@ -569,9 +569,7 @@ static int manager_receive_response(sd_event_source *source, int fd, uint32_t re if (r < 0) log_error_errno(r, "Failed to call clock_adjtime(): %m"); - r = manager_save_time_and_rearm(m); - if (r < 0) - return r; + (void) manager_save_time_and_rearm(m); /* If touch fails, there isn't much we can do. Maybe it'll work next time. */ (void) touch("/run/systemd/timesync/synchronized"); -- 2.47.3