[mythtv-users] can't find mythfilldatabase logs after 0.25 to 0.27 upgrade

[Bill Meek]

On 10/01/2013 05:39 AM, Jean-Yves Avenard wrote:
> On 1 October 2013 05:44, Bill Meek <keemllib at gmail.com> wrote:
>
>> That's what I use and I don't get logging either. So, I don't
>> believe it will help. In your case, I think it's the --daemon
>> that's causing the issue (not sure if this is a problem that
>> needs something in Trac or just an entry in the  0.27 Release
>> Notes.) But logging mythfilldatabase started from the backend has
>> definitely changed.
>>
>> If is weren't for waiting 24 hours for each test, this would
>> probably be easy to solve.
>
> the backend starts mythfilldatabase (and any other myth utilities for
> that matter) with exactly the same logging option as how you started
> the backend.
>
> so if you started the backend with -quiet, then mythfilldatabase will
> be started with -quiet too.
> syslog, dblog etc... same deal.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>

Sorry, no. mythsystemlegacy sees the -quiet I have always used and
appends an additional --quiet to the mythfilldatabase command line.
Two --quiets shuts down logging, as promised in myth* --help.

     http://code.mythtv.org/cgit/mythtv/tree/mythtv/libs/libmythbase/mythsystemlegacy.cpp#n146

I removed --quiet from my BE startup yesterday and when MFDB ran last
night, it created a log as it used to. I haven't tested --daemon, but
believe it causes the same loss of logging.

Running the BE with -v system showed the command line in the BE logs with
the --quiet --quiet.

It looks like the original housekeeping rewrite used mythsystem and
sometime later it was switched to ...legacy. I can't find the 2nd
commit.

-- 
Bill