Very Computer

by **John Olive** » Wed, 17 Jan 2001 12:16:50

An old machine that's been chugging along for years... looks like it
rebooted this AM. Since, cron jobs haven't run. I changed /etc/crontab
a little, touched it, kill -1 the crond PID, etc. with no results. What
else might kick it in the *and get it going again? It's an older
Red Hat, if that makes a difference... probably 5.1 or 5.2

--
John Oliver, System Administrator http://www.veryComputer.com/
ConnectNet, an Allegiance Telecom company http://www.veryComputer.com/
6370 Lusk Blvd. Ste F103 (858) 638-2020
San Diego, CA. 92121 FAX: (858) 623-1505

by **Doug O'Lear** » Thu, 18 Jan 2001 01:49:59

> What else might kick it in the *and get it going again?

You could completely kill the cron process and restart it.
That's worked for me on other nixes...

Doug

--
------------------------
Douglas K. O'Leary
Senior System Administrator

by **Chip Pille** » Thu, 18 Jan 2001 05:30:48

Perhaps crond did not get started when the machine rebooted, did you look
for that?
Check the processes running on the machine, "ps ax | grep cron".
To start crond do as root, "/etc/rc.d/init.d/cron start". This or
something similar should work on RH5.x.

Then add crond to your list of services that get started by default during
system bootup.

If that's not it I would probably use rpm to verify the cron package, and
possibly reinstall cron if it has been corrupted.

Hope this helps,
Chip

Quote:> An old machine that's been chugging along for years... looks like it
> rebooted this AM. Since, cron jobs haven't run. I changed /etc/crontab
> a little, touched it, kill -1 the crond PID, etc. with no results. What
> else might kick it in the *and get it going again? It's an older
> Red Hat, if that makes a difference... probably 5.1 or 5.2

> --
> John Oliver, System Administrator http://www.veryComputer.com/
> ConnectNet, an Allegiance Telecom company http://www.veryComputer.com/
> 6370 Lusk Blvd. Ste F103 (858) 638-2020
> San Diego, CA. 92121 FAX: (858) 623-1505

Very Computer

cron jobs aren't running :-(

cron jobs aren't running :-(

cron jobs aren't running :-(

cron jobs aren't running :-(