On Sat, 14 Mar 2015 11:29:32 +0100 "Beck, Andre" <b...@ibh.de> wrote: > Hi, > > isn't that a bug in e2fsck anyway? There is accept_time_fudge which > defaults to true and should take care of this situation.
Possibly; in any case it still logs a warning even when it 'accepts' the incorrect time. I don't know why it's also performing a full fsck on some systems. > Even when it > wouldn't default to true, my e2fsck.conf already had its alias > buggy_init_scripts set to 1. Nevertheless, I'm briefly seeing an fsck > running now on every boot (CMOS clock is ticking CET localtime). > > BTW, no longer fixing up system time before fsck is one thing, but > what about mounting? Ain't that prone to create file timestamps in the > future for everything that is touched before the init system has a > chance to run a correctly parameterized hwclock? [...] No, because the filesystem is mounted read-only initially. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett
signature.asc
Description: This is a digitally signed message part
