[mythtv] ringbuffer.cpp

[Bill Meek]

On 03/02/2014 11:22 PM, Jean-Yves Avenard wrote:
> On 3 March 2014 15:26, Bill Meek <keemllib at gmail.com> wrote:
>> Is this message supposed to be loglevel debug?
>>
>> 2014-03-02 22:08:02.032226 I [4857/4891] MythSocketThread(-1)
>> mythcorecontext.cpp:1151 (readyRead) - MythCoreContext: Received remote
>> 'FILE_WRITTEN /srv/mythtv-0/recordings/2615_20140303040000.mpg' request
>> 2014-03-02 22:08:02.239430 I [4857/4891] MythSocketThread(-1)
>> mythcorecontext.cpp:1151 (readyRead) - MythCoreContext: Received remote
>> 'FILE_WRITTEN /srv/mythtv-1/recordings/1021_20140303030000.mpg' request
>>
>> I've had over 5300 (with various channels) in the last 10 hours. None
>> were from LiveTV, they were scheduled recordings.
>>
>> They were all on a FE which is running: v0.28-pre-931-g2c71895.
>>
>> The message appears in: commit fafc658.
>
> Yes, those messages appear with loglevel=debug like all messages sent
> by the backend.
> FILE_WRITTEN is sent by the backend whenever a new file is created in
> write mode, and following that, no more than every 10s whenever a file
> is being written to.

I worded that poorly. My frontend was not running with --loglevel=debug,
and since they're currently LOG_INFO, I was wondering if they should be
changed to LOG_DEBUG.

They were printing every 10 seconds, as you mentioned.

...

-- 
Bill