On Tue, 10 Apr 2001, Ben Ocean wrote:

> Hi;
> Every so often, my server reboots automatically. I looked in
> /var/log/boot.log to find the last time it did this, then looked in
> /var/log/cron and found this:
>  >>>
> CRON (04/10-12:05:32-393) STARTUP (fork ok)
> root~ (04/10-12:05:32-393) ORPHAN (no passwd entry)
> <<<
> I assume the *393* is a PID, so I ran ps aux|less and got this:
>  >>>
> root       393  0.0  0.2  1304  640 ?        S    12:06   0:00 crond
> <<<
> What's crond? Should I kill it? The time is actually a minute past when the
> system rebooted. The actual time it rebooted, the ps aux gave this:
>  >>>
> root         6  0.0  0.0     0    0 ?        SW<  12:05   0:00 [mdrecoveryd]
> <<<
> What's mdrecoveryd? For the record, here's the full story if I missed
> something:
>  >>>
> root         1  0.0  0.1  1104  380 ?        S    12:04   0:05 init [3]
> root         2  0.0  0.0     0    0 ?        SW   12:04   0:00 [kflushd]
> root         3  0.0  0.0     0    0 ?        SW   12:04   0:00 [kupdate]
> root         4  0.0  0.0     0    0 ?        SW   12:04   0:00 [kpiod]
> root         5  0.0  0.0     0    0 ?        SW   12:04   0:00 [kswapd]
> root         6  0.0  0.0     0    0 ?        SW<  12:05   0:00 [mdrecoveryd]
> root       350  0.0  0.2  1156  528 ?        S    12:06   0:00 syslogd -m 0
> root       361  0.0  0.2  1428  756 ?        S    12:06   0:00 klogd
> daemon     377  0.0  0.1  1128  484 ?        S    12:06   0:00 /usr/sbin/atd
> root       393  0.0  0.2  1304  640 ?        S    12:06   0:00 crond
> root       413  0.0  0.1  1120  480 ?        S    12:06   0:00 inetd
> root       451  0.0  0.4  2124 1160 ?        S    12:07   0:00 sendmail:
> accepti
> <<<
> TIA,
> BenO
>
crond is the daemon that takes care of the assorted houskeeping tasks
that are done at specific times.  Things like rotating the logs,
building the locate database, etc.  You do not want to kill it on a
server!  To get an idea of the type of things run by crond, check out
/etc/crontab, and the /etc/cron.d, cron.daily, cron.weekly, and
cron.monthly directories.  You might also want to read the crond man
page.

mdrecoveryd is part of the software RAID package.  If you are not using
software RAID, you do not need it.  But it doesn't do any harm.

Now, as far as the system rebooting, does it do it at the same time, or
at random times?  If it does it at about the same time, say every Sunday
at 4:35am, it may be a cron job that is causing the reboot.  If it does
it at random times, I would consider a hardware or power problem,
especialy if it is not on a UPS.

Mikkel
-- 

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to