Summary: | clock gets crazy, deleting /etc/adjtime fixes it | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tiago Marques <bugs> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tiago Marques
2006-12-03 08:35:17 UTC
afaict, this is by design if something is putting crazy values into adjtime, then that thing is broken ... the fact that clock uses the values in there and your clock goes crazy is not a bug So... what could do that. And why don't i need the file? in my system i edited the clock initscript so it doesn't use adjtime. adjtime is used to handle clock sources that are not sane (which is not an uncommon event) see the "The Adjust Function" in the hwclock manpage This seems to me something that shouldn't be done... Why? Maybe what's putting these values in adjtime is the KDE clock utility, as i usually have computers where i mess alot with the bios, i change the clock alot, but not in a normal way, i can adjust hours, days or even years. If that's the case, that's what has been giving me problems. Maybe the adjtime function should be limited to some minutes of maximum deviation, i had problems with it changing my clock sometimes a few hours, sometimes days. Best regards there's no way to know what is a valid value in adjtime and what is not |