On Sat Jun 7 19:22:41 EDT 2014, st...@quintile.net wrote:
> > - timesync. i saw this issue one in 2008, so i don't remember much about
> > it.
>
> I think this was a bug in cron. When the time lept forward as timesync
> corrected
> the time at boot cron would try to run all the intervening eve
> - timesync. i saw this issue one in 2008, so i don't remember much about it.
I think this was a bug in cron. When the time lept forward as timesync corrected
the time at boot cron would try to run all the intervening events and hang the
machine.
cron now ignores time changes if they are big.
On Sat, Jun 7, 2014 at 9:15 PM, erik quanstrom wrote:
> i don't think this has been mentioned in a while, so i wanted
> to quickly jot down a few tricks for looking at a "hung" machine.
>
> there are three main things that can hang things up on initial boot
> that aren't related to the kernel misb
i don't think this has been mentioned in a while, so i wanted
to quickly jot down a few tricks for looking at a "hung" machine.
there are three main things that can hang things up on initial boot
that aren't related to the kernel misbehaving
- unclean shutdown forcing a fs check. this can take 15
