Answer is at the bottom On 2/13/06, Jeff <[EMAIL PROTECTED]> wrote: > Hey Mark. > > I'd also like to pitch in here. > > Since about two weeks ago, my machines are no longer keeping time as > well. I'm getting errors when my systems boot during sysinit - the clock > script fails miserably, and some systems it forces me into console to > try and correct the problem. > > I'm not sure that sysinit scripts have much to do with the system's > time, being that the kernel takes care of time - but again, since about > two weeks back, I have at least 4 systems that will not keep time, > regardless of hwclock or ntpdate commands. > > The following message is recurring on these 4 machines: > > select() to /dev/rtc to wait for clock tick timed out > > Anyone know what's going on here? > > Mark Knecht wrote: > > On 2/13/06, Drew Tomlinson <[EMAIL PROTECTED]> wrote: > > > > > >>Anyway, I really appreciate your thoughts. Because this box runs > >>MythTV, time is *VERY* important. Imagine my surprise when I went to > >>watch the first day of the Olympics on to find out that my recordings > >>were off by over an hour and half. :) > >> > >>Thanks, > >> > >>Drew > > > > > > Drew, > > Please excuse me jumping in here. I have seen no other emails in > > this thread so maybe I'm wasting time. I hope not. > > > > I have a number of Gentoo machines. For some reason in the last > > week or 10 days my AMD64 machine stopped keeping time. I'd boot it in > > the morning and even the day would be off. It was horrible. > > > > With a little help from others I found that, at least in my case, I > > needed to start running ntp-client in the default run level. I never > > ran this before but there appears to have been change recently that > > has made it more important. Either that or I was just lucky before. > > > > I've since added ntp-client on all the machines and things are now > > dead on as far as I can tell. > > > > One other thing that was recommended to me was to remove the > > /etc/adjust file when doing this. I did that also. > > > > Again, if all of this has already been covered I apologize for > > taking up too much time. > > > > Good luck, > > Mark > >
Jeff, I realized over lunch I didn't give Drew all the ammo he might have wanted to go try out the fix for himself. (Not that he needs ammo from me.) If your problems are at all similar to the ones I was suffering through then you can test the fix by hand doing the following commands: /etc/init/ntpd stop /etcinit.d ntp-client start /etc/init.d ntpd start /etc/init.d/ntpd zap after the stop to clear up stuff left behind by the scripts or by ntpd crashing or stopping sometime unexpectedly. I did. After doing that my clocks were immediately back on time and I haven't hd trouble since then, although it;s only been a few days since the guys on the gentoo-amd64 list gave me the info. You might also have to optionally do I understand that the /etc/adjust file tells the system something about how much to adjust time and that it's better to allow that to be recreated or just let the system run without it. In my case I ran without on for a few days and magically I now have a new one created for me automatically: [EMAIL PROTECTED] ~ $ ls -la /etc/adjtime -rw-r--r-- 1 root root 44 Feb 13 08:35 /etc/adjtime [EMAIL PROTECTED] ~ $ Hope this helps, Mark -- [email protected] mailing list
