From 8f5b978e531e7d02513334e3cbed018f7d24d98f Mon Sep 17 00:00:00 2001 From: Alain Guibert Date: Mon, 24 Sep 2007 12:57:22 +0200 Subject: [PATCH] hwclock: do not create a zero adjfile When hwclock --hctosys is started very early during the system startup, with / still mounted read-only, and there was no /etc/adjtime file, hwclock fails creating a default adjfile full of zeroes, and prints an error message. I believe that such zero adjfile is not necessary, because it means exactly the same as no adjfile at all. The attached patch prevents creation of a zero adjfile, of course unless something gets changed (this never happens during a --hctosys). Signed-off-by: Alain Guibert --- hwclock/hwclock.c | 1 + 1 file changed, 1 insertion(+) diff --git a/hwclock/hwclock.c b/hwclock/hwclock.c index bbacf5dc..f138a9fa 100644 --- a/hwclock/hwclock.c +++ b/hwclock/hwclock.c @@ -257,6 +257,7 @@ read_adjtime(struct adjtime *adjtime_p) { adjtime_p->not_adjusted = 0; adjtime_p->last_calib_time = 0; adjtime_p->local_utc = UNKNOWN; + adjtime_p->dirty = FALSE; /* don't create a zero adjfile */ return 0; } -- 2.39.5