Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
ok. right, why does my clock KEEP going wrong? i continually use a time server on line to set my clock, and then also use hwclock to write it back to system time, and then my system clock will update itself. but next reboot, or i *think* later in the same boot, the clock will be wrong again. it's current 22 mins slow, but it varies a lot.. the hwclock is currently exactly right, but the system clock .. nope.
If it only happened on boot up then maybe boot script not setting the system clock correct..but it wouldn't be the same on the other distros unless it was a slight incompatability with the sysclock and hwclock..
but if on same boot then I think your computer lives in an alternate universe where clock cycles are slower than our universe, so a year for us would be 164 days to your computer (approximate guess on the 22min difference). I think you should move the computer to a planet that spins 36.6% faster than ours and it should solve your system clock problem. But then your hardware clock would be out..or would it..depending on where you observe the time from.
Originally posted by acid_kewpie ok. right, why does my clock KEEP going wrong? i continually use a time server on line to set my clock, and then also use hwclock to write it back to system time, and then my system clock will update itself. but next reboot, or i *think* later in the same boot, the clock will be wrong again. it's current 22 mins slow, but it varies a lot.. the hwclock is currently exactly right, but the system clock .. nope.
any ideas as to why this keeps happening???
Sure, that's almost always due to a dead/dying CMOS battery.
Originally posted by acid_kewpie hmm, i took the battery out, gave it a good clean, and put it back, and it's been fien since. i'd never touched it before tho, i'm sure.. ahh well. all's well that ends well.
Glad to hear it fixed the problem. Some things just happen outta the blue like that....