> The only thing I noticed as I just telnetted to the machine was that
> cron was stealing all of the processor time, see the "top" output:
> 
> load averages:  1.33,  1.18,  1.11                                  14:30:47
> 11 processes:  1 runnable, 9 sleeping, 1 on processor
> CPU states: 18.0% user,  0.0% nice, 82.0% system,  0.0% interrupt, 0.0% idle
> Memory: 3252K Act, 4220K Inact, 116K Wired, 11M Free, 49M Swap free
> 
>   PID USERNAME PRI NICE   SIZE   RES STATE     TIME   WCPU    CPU COMMAND
>   181 root      64    0   116K  360K run     218:53 86.13% 86.13% cron
> 
> Is this a bug, or is cron always taking taking so long?

it looks like a bug.  please rebuild cron with -g and then gdb it (via /proc)
to see where it's looping.  it's possible that sleep() is returning 0 rather
than the number of seconds left to sleep...