On Thu, Sep 06, 2007 at 06:54:27PM +0100, Ian Jackson wrote:
Content-Description: message body text
> Package: e2fsprogs
> Version: e2fsprogs_1.40.2-1
> Tags: patch
> Severity: minor
>
> If the clock and timezone settings are not wholly reliable, then the
> last check time can end up being in the future, just like the last
> mount and last write times. I think these should be fixed up in the
> same way (as described in eg #343662 and #343645).
I'm not going to apply this patch, because it could be the clock is
totally bogus, and in that case, you *do* want to do an fsck, because
it could have been a very, very long time since a check had been done.
My plan for fixing this given all of the whinging and "it's impossible
to fix this" is that distros who believe this can set in /etc/e2fsck.conf:
[options]
buggy_init_scripts = 1
.... and this will cause e2fsck to allow the CMOS clock to be up to 24
hours into the future, to accomodate people who insist on setting
their CMOS clock to localtime, and yet can't manage to get their init
scripts to do the right thing at e2fsck time.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
