[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Raq3 vs. realtime clock
- Subject: [cobalt-users] Raq3 vs. realtime clock
- From: "Jolley, Carl" <Carl.Jolley@xxxxxxx>
- Date: Fri Jul 5 10:51:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
I'm using a Raq3 that causing me problems every time
there's a reboot.
The time of the reboot shows up as being several days
earlier thatn the actual reboot. Several cron jobs are
initiated at the reboot and really clog things up. These
jobs start at the reboot when then should not be starting
for several hours later. In a couple of the cron jobs I've
actually put code in to check the time of day and exit if
the jobs were not initiated at the correct time but this
seem like a real PITA.
Due to tales I've heard about the problems with the realtime
clock, I've put a call to ntpdate near the end of
/etc/rc.d/rc.local but by the time it happens, several cron
jobs have already started. Can I put a call to ntpdate somewhere
in /etc/rc.d/rc.sysinit? I'm not getting mail messages saying
the clock is messed up but obvisously the clock is getting
set wrong at boot time. In addition to tweeking my startup
scripts, should I ask my co-loc vendor to replace the battery?
Will this do any good?