Quote:
Originally Posted by lierduh
Ok, please list some examples of the file names and its contents. Without having the same problem. It can be hard for me to find the bug.
I honestly did not know what Triple_T was talking about though it makes more sense now.
|
I actually saw this today.
I couldn't get it to do it when I ran the cron manually from the admincp, but the scheduled task being run by the schedule did just this.
I had somewhere in the region of half a 100,00 files splattered around before I managed to kill the process (by nuking the MySql process and also restarting httpd). It took about 15 minutes running "rm -f *" against batches of 5,000 *.gz items at a time to delete them all.
I thought it was just me!
Anyhow... my cron job log output for this task is attached. Beware that the single logged job expands to 7.68mb of log file!
Fun