David Merrill:
> Oh, wait. Brain fart. /etc/cron.* don't run by magic. They are
> executed via /etc/crontab which holds:
>
> # run-parts
> 01 * * * * root run-parts /etc/cron.hourly
> 02 4 * * * root run-parts /etc/cron.daily
> 22 4 * * 0 root run-parts /etc/cron.weekly
> 42 4 1 * * root run-part
Yes, it makes perfect sense. And, yes, cronjobs can run sumultaneously.
Just as you can run more than one thing from a command line at once. The
only snafu would be if one job depends on the output of another job.
Setting it up the way you outlined would definately address the risk of
things bu
On Tue, May 29, 2001 at 01:03:26PM -0700, Nancy Corbett wrote:
>
> It depends on how the cron is set up. The exact hour of the day is set
> in the crontab file. You can check it out yourself by entering crontab -e
> at the command line. It will bring up the list of scheduled cron jobs.
> Below
It depends on how the cron is set up. The exact hour of the day is set
in the crontab file. You can check it out yourself by entering crontab -e
at the command line. It will bring up the list of scheduled cron jobs.
Below I have an example of how crons are scheduled. There are 3 cron jobs
set
I'm configuring webalizer on my machine and am scheduling a cron job
to process the web logs. I need to make sure the processing of web
logs happens *before* the log rotator. The log rotator is called from
a script in cron.monthly, and the log processor is going to be in
cron.hourly (for now).
Ca
