Incomplete log info

[klunde]

In my log I came across this line:

PHP Code:

[2007/1/3 20:00:39] PVSRecorder is restarting the recording because no data was received from the capture card for 30 seconds. This is restart 1 of 3 allowed restarts.

-- 


Why doesn't this entry tell me which capture card had the problem? At the time this occured I had 5 different recordings going.

[nanook105]

Originally Posted by klunde

In my log I came across this line:

PHP Code:

[2007/1/3 20:00:39] PVSRecorder is restarting the recording because no data was received from the capture card for 30 seconds. This is restart 1 of 3 allowed restarts.

-- 


Why doesn't this entry tell me which capture card had the problem? At the time this occured I had 5 different recordings going.

Look above that line to see which tuner the recording job was dispatched to

[klunde]

Off course I can look above, but it doesn't say anything about what tuner did the job. I'm sure I can figure it out by reading up and down the log, but thats not my point, my point is that I would suggest that when the program writes an entry that says that a tuner hasn't sent any signal, it should also say what tuner did it.

</Morten>

[nanook105]

Originally Posted by klunde

Off course I can look above, but it doesn't say anything about what tuner did the job. I'm sure I can figure it out by reading up and down the log, but thats not my point, my point is that I would suggest that when the program writes an entry that says that a tuner hasn't sent any signal, it should also say what tuner did it.

</Morten>

Umm - it's a log. From Wikipedia

Many operating systems and multitudinous computer programs include some form of logging subsystem. Some operating systems provide a syslog service (described in RFC 3164), which allows the filtering and recording of log messages to be performed by a separate dedicated subsystem, rather than placing the onus on each application to provide its own ad hoc logging system.

In many cases, the logs are esoteric and hard to understand; they need to be subjected to log analysis in order to make sense of them.

Could it be more informative/less curse ? Sure, but what you need is there. You don't need to look up and down the log, just up a few rows.

[klunde]

I'll refrase:

Suggestion for the next version: Include information about what tuner failes when logging info about tuner failure.

[bnflaherty]

realistically speaking... logging is meant to be sent to techsupport/developers to assist with issues happening with the system.

The particular message in question -- has several different meanings -- all depending on many factors -- of which I cannot go into at this time -- which Mostly are system-dependent.

As it IS -- the logs have been updated in recent versions to expose more data than before.... just see some of the 3.x logs... they were rather sparse...