Request: Get path to task log buffer file

I’d like to request an API method to reliably retrieve the full path to the log file Deadline uses to buffer the current task’s output streams (e.g. /var/log/Thinkbox/Deadline7/deadlineslave_renderthread_0-rd-041-0000.log) from within a plugin.

In the meantime, in order to (hackily) engineer the path myself, I’d like to know what the “0000” in the file name represents, as that’s the only piece I can’t easily identify.

Thanks.

Hello,

I will have to verify this, but in the case of our other logs, it’s the version of the log based on the other data. For instance, if you have restarted Deadline Slave 3 times in a day, you will have 0000, 0001, 0002 and 0003. I don’t know if there is any way to code for the current version of log, only to code that there is logs.

Hi Dwight,

The numbering makes sense for things like launcher or slave logs, but I guess I don’t quite understand how that would apply to the ‘renderthread’ logs. Maybe it’s just a carry-over naming convention that is being reused, and the numbering will never increment past 0, but if there are cases where that could happen, it would be good to know about it.

Thanks.

Hello Nathan,

Sorry for not answering sooner, I completely lost the tab your post was in. I would think that it’s just reuse of logging code between all the different types of logging, which denotes the 0000. I couldn’t find any situation where that log would go above 0000, based on the type of log.

Thanks Dwight, that’s what I was hoping to hear.