[mythtv-users] Different mythfilldatabase commands for different sources

[Ian Evans]

On Wed, Feb 10, 2016 at 5:15 PM, Bill Meek <keemllib at gmail.com> wrote:

> On 02/10/2016 04:05 PM, Ian Evans wrote:
> ...
>
>>
>> The source for OTA has:
>>
>> <Grabber>schedulesdirect1</Grabber>
>>
>> The source for the HLS channel has:
>>
>> <Grabber>/bin/true</Grabber>
>>
>
> That's good. Now, in the log for the HLS mythfilldatabase run file,
> I'd expect that the following *wouldn't* appear:
>
> CoreContext datadirect.cpp:1070 (GrabNextSuggestedTime) - DataDirect:
> Grabbing next suggested grabbing time
> CoreContext datadirect.cpp:1112 (GrabNextSuggestedTime) - Suggested Time
> data: 613 bytes
> CoreContext datadirect.cpp:1141 (GrabNextSuggestedTime) - DataDirect:
> nextSuggestedTime is: 2016-02-11T23:51:24Z
>
> and, if they don't, then is the HLS grabber modifying the setting
> MythFillSuggestedRunTime directly, and is there an option to
> prevent it?
>
>
The "next suggested grabbing time" is not appearing in the log.

The HLS grabber is simply the tv_grab_uk_atlas grabber. I looked at the
source and can't see anything about MythFillSuggestedRunTim.

It's being run from a file like this as the mythtv user:

tv_grab_uk_atlas  --config-file /home/mythtv/.mythtv/HLS.xmltv --output
/tmp/ukxmltv
mythfilldatabase --refresh 0-99 --file --xmlfile /tmp/ukxmltv --sourceid 4
--syslog local7
rm /tmp/ukxmltv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160210/34e1fb0a/attachment.html>