QBox User Posted November 8, 2011 Posted November 8, 2011 It would be useful if the log file for a recording would include the original timer information. At present, this information is destroyed with no record, making it hard to debug faulty recordings. Users are left wondering whether they set the timer wrongly, or there's a possible bug. Some of us have posted problems with suspected incorrect timer operation (possibly related to time-zone correction) but have no timer data unless we took a manual copy of svctimers.xml. An alternative or additional option would be to include the information in svcdebug.log, though this may be less useful than having it in the recording log.
Lars_MQ Posted November 8, 2011 Posted November 8, 2011 the important info for a recording is already logged to the svcdebug.log.
QBox User Posted November 8, 2011 Author Posted November 8, 2011 svcdebug.log gives actual times when recordings start and stop - when the timers execute. It doesn't help when the timer was set for something different, or the recording didn't take place (maybe because the times were mis-interpreted). Of course, sometimes this can be user error, but we can't tell without the original timer setting. A debug capability showing both original timer entry and actual timer execution would help track these issues down. At present, we only have half the information.
Recommended Posts