The slave logs for the REDLine job are too verbose and fill up hard drives.
This gets printed for every frame:
2013-06-05 09:59:26: 0: STDOUT: [06-05-09-59-25-131] TEST_DBG_1 R3DClip::getCineImage - Cache Hit! 324
2013-06-05 09:59:26: 0: STDOUT: [06-05-09-59-25-131] R3DClip Requested Frame: 325 -> 325 Track: 0 Final Track: 0
As a result if you render off an hour long (60 * 24 * 60) magazine of footage you end up with 86,000 lines of log data. Which apparently is about 1GB of txt file data 
Hello,
I was wondering if you are running 6.0 yet, as we do compress the logs in 6.0. That is a massive file, with 2 lines per frame.
Cheers,
We are passing the “–verbose” flag, but I that’s needed to support progress reporting for the job. Maybe we need to make the verbose flag optional?
Cheers,
Yep, deadline 6.0. I would like verbose progress bars etc but would it be possible to just not save it to the log file?
Actually, yeah, we should be able to suppress the line of output that would be used to report progress. However, I just checked our REDLine.py plugin file, and the current movie progress handler we have doesn’t match either of those two lines in the original post. Is progress reporting working for your REDLine jobs? Could you maybe send us a bigger chunk of the output to look at?
Out plan is to do some work on the REDLine plugin for the next release (based on the feedback you provided in another thread), and we can definitely add the output problem to this list.
Thanks!