[2.3.6] Excessive logging or unexpected behaviour?

[gEd]

it seems odd that every second, npvr should be trying to prevent my screensaver from starting. Especially as I don't have a screensaver.

2012-01-18 18:28:23.815 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:24.835 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:25.847 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:26.860 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:27.874 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:28.888 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:29.898 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:30.918 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:31.930 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:32.940 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:33.960 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:34.973 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:35.983 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:37.003 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:38.015 [DEBUG][1] Stopping windows screen saver from starting...
2012-01-18 18:28:39.029 [DEBUG][1] Stopping windows screen saver from starting...


And this message every 5 seconds.

2012-01-18 22:01:52.350 [DEBUG][19] Asking NDigitalHost to start: LIVE&R:\Temp\live-BBCTWO-11540-2.ts
2012-01-18 22:01:52.897 [DEBUG][19] Live TV handle: 0x1A0002
2012-01-18 22:01:59.956 [DEBUG][19] Renew lease ok (0x1A0002)
2012-01-18 22:02:04.964 [DEBUG][19] Renew lease ok (0x1A0002)
2012-01-18 22:02:09.970 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:15.014 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:20.083 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:25.099 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:30.143 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:35.236 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:40.310 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:45.363 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:50.400 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:02:55.411 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:00.519 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:05.591 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:10.595 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:15.602 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:20.674 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:25.716 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:30.788 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:35.803 [DEBUG][3] Renew lease ok (0x1A0002)
2012-01-18 22:03:40.900 [DEBUG][3] Renew lease ok (0x1A0002)

I can;t seem to find a way to reduce the logging level. Is there a setting to reduce the logging level to "Error" like we used to have back in the old days?

[sub]

I dont think either of those are new. I'll leave the Renew Lease message in, because its a useful diagnostic message for me, but I've commented out the other message for the next build of nextpvr.exe

There isnt a setting to reduce the logging level, since I found that people used to post useless logs and I was forever having to ask them to set the logging level back to debug. I decided to avoid that problem with NextPVR.