Frank Bax wrote:
Chris Bennett wrote:
steve szmidt wrote:


Just off hand, are there not too many time parameters?

Probably, I just threw in some * to fill in extra ones.
I was just trying to show that I was purposefully running at a certain time during testing.
Too lazy to count them correctly :)



So how many asterisks are in your crontab? An extra * will attempt to "run" every file in current directory. Your script files wouldn't happen to be in the default directory would they?


$ crontab -l
#minute hour    mday    month   wday    command

57 3 * * * mv /home/chris/vprod* /home/chris/psqldump/ 46 2 * * * /usr/local/bin/pg_dump -U ben -d prod | gzip > /home/chris/prod_dump`date +\%m\%d\%Y`.sql.gz
03      3       *       *       1       /home/chris/LWP4.pl;
03      4       *       *       1       /home/chris/LWP5.pl;
33      4       *       *       1       /home/chris/LWP_lowes10.pl;
03      5       *       *       1       /home/chris/LWP6.pl;
03      6       *       *       1       /home/chris/LWP_hd.pl;
03      7       *       *       1       /home/chris/LWP_lowes11.pl;
30 * * * * /home/chris/LWP4.pl; /home/chris/LWP5.pl; /home/chris/LWP6.pl;

I don't have the original line from crontab that I used.
I decided to try this again, as you can see on the last line.
THIS time, all is running normally!

At the time, only those three scripts (and one that would have done nothing) were present in the default directory.

It does seem likely now that I may have gotten the number of * wrong.
I am very careful with editing crontabs, I can see that I need to be even more careful. Running all the scripts could be very bad!

Thanks,
Chris Bennett

Reply via email to