Hi, On 19-05-16 23:04, Michael Biebl wrote:
Looks like I need to have systemd-timesync run *before* systemd-fsck!?If your hwclock drifts that much, maybe /etc/e2fsck.conf: [options] broken_system_clock=1 (as referenced in my earlier reply) is an option. Can you try that?
Sure, but won't that effectively disable fsck'ing based on 'time since last check'?
Also, is it normal that that config file doesn't exist yet? -- Kind regards, Manuel
