Reply to thread

Message

<blockquote data-quote="T^2" data-source="post: 1060132" data-attributes="member: 145022">Another capture just for good measure.... MP logs and Wireshark capture attached.Relevant sections of the HDHR log for time and channel info for both captures...[DOUBLEPOST=1391186681][/DOUBLEPOST]One other thing... If I remember right... LogVerbosity was set to 3 (info) before I made changes to the .ini file (changed LogVerbosity to 5). So I set it back to 3 after I was done getting the captures. I also stopped and restarted the TVServer service (don't know if this was necessary, but just in case). However, I noted (with MP running and Live TV playing) that the MPIPTVSource.log file was still incrementing at what appears to be the same rate as when LogVerbosity was set to 5. I also noted in the .ini file that the log file max size is set to 10485760. So I guess it doesn't really matter - I won't end of with a huge drive consuming file. My guess is that it wraps around when the max file size is reached. Anyway, just out of curiosity, I set LogVerbosity to 0 and restarted the service to see what would happen the next time I ran MP with live TV. The file size didn't change (what I expected). I've now have reset LogVerbosity to 3 (as - if memory serves - it was before I started messing around).&nbsp; Please advise if I got something that I need to be concerned about.</blockquote>

[QUOTE="T^2, post: 1060132, member: 145022"] Another capture just for good measure.... MP logs and Wireshark capture attached. Relevant sections of the HDHR log for time and channel info for both captures... [DOUBLEPOST=1391186681][/DOUBLEPOST]One other thing... If I remember right... LogVerbosity was set to 3 (info) before I made changes to the .ini file (changed LogVerbosity to 5). So I set it back to 3 after I was done getting the captures. I also stopped and restarted the TVServer service (don't know if this was necessary, but just in case). However, I noted (with MP running and Live TV playing) that the MPIPTVSource.log file was still incrementing at what appears to be the same rate as when LogVerbosity was set to 5. I also noted in the .ini file that the log file max size is set to 10485760. So I guess it doesn't really matter - I won't end of with a huge drive consuming file. My guess is that it wraps around when the max file size is reached. Anyway, just out of curiosity, I set LogVerbosity to 0 and restarted the service to see what would happen the next time I ran MP with live TV. The file size didn't change (what I expected). I've now have reset LogVerbosity to 3 (as - if memory serves - it was before I started messing around). Please advise if I got something that I need to be concerned about. [/QUOTE]

Verification