hwclockfirst should run before checkroot in rcS.d
Bug #28072 reported by
Debian Bug Importer
This bug report is a duplicate of:
Bug #26926: util-linux: hwclock runs too early, breaking the system time.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
util-linux (Debian) |
Fix Released
|
Unknown
|
|||
util-linux (Ubuntu) |
Invalid
|
High
|
LaMont Jones |
Bug Description
Automatically imported from Debian bug report #344818 http://
Changed in util-linux: | |
status: | Unconfirmed → Fix Released |
Changed in util-linux: | |
status: | Fix Released → Unconfirmed |
Changed in util-linux: | |
status: | Unconfirmed → Fix Released |
To post a comment you must log in.
Message-ID: <email address hidden>
Date: Mon, 26 Dec 2005 10:32:39 -0500 (EST)
From: "Troy A. Johnson" <email address hidden>
To: <email address hidden>
Subject: hwclockfirst should run before checkroot in rcS.d
Package: sysv-rc
Version: 2.86.ds1-6
A comment at the beginning of /etc/init. d/checkroot. sh says that
hwclockfirst should be started beforehand, however that is not the order
in /etc/rcS.d.
In /etc/rcS.d, checkroot is S10 whereas hwclockfirst is S22. This
numbering means that the root file system is checked before the hardware
clock is read.
On my system, the incorrect order causes fsck to warn that the superblock
has a modification date that is in the future. Various attempts at fixing
the fsck warning failed until I discovered that changing hwclockfirst to
S08 (or anything less than S10) eliminates the warning.
Please correct your package so that /etc/rcS. d/S22hwclockfir st.sh is
renamed S08checkroot.sh. Thanks.
-Troy