Timer conflict detection logging when standby tuner enabled

[Grumpy_Geoff]

Any chance of toning down the debug logging when both settings 'Enable fallback remote receiver' (standby tuner) is enabled and 'Enable timer conflict detection' is enabled (its default)?
The debug log is filled with -

Code: Select all

[eDVBResourceManager] allocateFrontend, score=2

I've over 2,500 lines of the above in the T4 log that only started 5 hours ago. They appear in multiples of four, increasing as each [RecordTimer] entry is logged. 2,496 of them appeared at startup, when the existing timers were loaded.

The help text for 'Enable timer conflict detection' states -
"When you use the remote fallback tuner for recording, the timer conflict detection can't properly detect conflicts. This option allows you to turn off the timer conflict detection. This setting is for advanced users; the default is 'yes'."
... but you can't (_easily_) record from the standby tuner anyway,

When the timer conflict setting (config.usage.timer_sanity_check_enabled) is disabled, no debug logging occurs (but of course then there's no timer sanity checking, and that bit me in the bum on Monday night when the T4 silently tried to record from the T2 but failed).


Cheers,
Geoff

[Grumpy_Geoff]

Thanks peteru -

Code: Select all

		if (c)	/* if we have at least one frontend which is compatible with the source, flag this. */
 		{
-			eDebug("[eDVBResourceManager] allocateFrontend, score=%d", c);
+			//eDebug("[eDVBResourceManager] allocateFrontend, score=%d", c);
 			foundone = 1;
 		}

Is that coming to a firmware near me soon?


Cheers,
Geoff