Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey all. I have a strange and very annoying problem. I'm running gentoo and I have my /etc/conf.d/clock settings set CLOCK="local" and TIMEZONE="EST". I date the date/time using date and everything was fine....
about an hour later the clock was 45 minutes behind. A day later it was far far worse.
Does anyone have any idea why this would happen? I need my system to be 100% reliable and if it cannot even tell what TIME or DAY it is then its pretty useless.
about an hour later the clock was 45 minutes behind.
Something is seriously wrong with your clock.
Does time drift so fast if you are running a "live CD" distro (in which case there's something wrong with your slack install)?
As a temporary fix, you could look into something like an ntp daemon to keep your time synchronised. This can be set up to check the time against a local ntp server and also keep a watch on how fast your local clock "drifts" and gradually apply a correction factor to it.
There are loads of public ntp servers scattered about. If lost you can always use ntpdate pool.ntp.org
But I don't think they'll like it if you poll them every minute (so setup the "drift" file, and check once a day once the drift has been computed).
I was hoping my time issues were a thing of the past (no pun intended) but it seems my clock has drifted by 15 minutes as of this writing. It was fine last night...I'm not sure what the problem here is. Could there be something with my linux config that is overwriting the time or is my mobo really just borked?
Ok guys. I purchased a new power strip hoping this might be a case of an old power strip gone bad. Everything booted correctly and the BIOS reported correct time.
However now my clock is speeding WAY too fast!!! Every 45 or 30 seconds my clock goes past a minute. I can't believe this.
Its interesting to note that date returns the super speed clock but hwclock --show returns a much closer results! It seems accurate.
Any idea why hwclock is ok but date is not?
I've deleted /etc/localtime and copied /usr/share/zoneinfo/EST to /etc/localtime just in case and I've changed TIMEZONE="EST" in /etc/conf.d/clock
This doesn't seem to have fixed anything as my clock is still speeding ahead.
Any help is greatly appreciated. Currently I read somewhere that someone fixed this problem by disabling ACPI in boot as a kernel boot param. I will try this when I return home. I'm still open for ideas.
Thanks.
P.S. I'm running Gentoo and not Slack nowadays. I'll update status soon.
Hey. Sorry I ignored your suggestion for running a LIVECD to check if time drifts there too. I'm a bit hesitant to do that because this server is also my NAS server/Web server/NFS/etc. I have a LOT of things going on on this machine (which is why this time problem is so annoying) and having a livecd running means I cannot have these services up.
I will try this anyway when I know noone needs access to NAS (maybe during the night on saturday or something) and see what results.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.