On Thu, 26 Jul 2001 Jenny_Hopkins@toby-churchill.com wrote:
Alexis said:
(who's had plenty of fun with cron before...)
Ah! I also am surprised that the file didn't simply replace itself, why did it build up to size 33241453?
The file should of replaced itself, but I am guessing that what happened was that the backup took more than 1 minute to complete and so the second one started and took more resources from the machine ad infinitum and you ended up with lots and lots of processes that were all stealing CPU cycles while waiting for each other to complete and reduced the machine to the overall speed of a windows box.
Adam