[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Named update/Reboot/Logs dead/Get's me Red
- Subject: Re: [cobalt-users] Named update/Reboot/Logs dead/Get's me Red
- From: "Scott w" <webbcite@xxxxxxxxxxx>
- Date: Wed Nov 14 22:10:06 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
<BIG DAVE SAID>
When Tech Support was in the box they stated that the Raq3's had an issue
when rebooted and the clocks not syncing. What I feel is happening is that
once the clock is wrong the cron thinks it has already ran that date (Nov
16th) I argued with the tech stating this is what I think has happened and
they said no way. Well after looking at it he stated it looks like the cron
thinks it ran. So anyone else have this happen and then waited the required
days for the system to "Catch Backup" and all work okay. I really don't want
to pay them again and then wait to be credited back, when this is an on
going problem.
</BIG DAVE SAID>
This is correct...I have run into this myself with log check. After a
reboot my clock was set forward approx 24 hrs. I just waited and it started
back up after it caught up. It has happened several times...actually every
time they put out an update that requires a reboot :)
Webbcite
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp