[mythtv-users] Logging Best Practices?

[Tom Dexter]

On Sat, Jul 19, 2014 at 10:31 AM, Jean-Yves Avenard <jyavenard at gmail.com> wrote:
> On 19 July 2014 23:05, Rich Freeman <r-mythtv at thefreemanclan.net> wrote:
>
>> What would be the best default, especially considering things like:
>> 1.  Console logging is apparently not desirable for bug reports.
>> 2.  Logging without logserver apparently isn't logrotate-friendly.
>
> and why not ?
>
> if you build mythtv with --disable-mythlogserver or run standard but
> with --nologserver
>
> it is functionally identical to using mythlogserver, it's just how the
> logs are handled internally that changes. From the user point of view
> it makes no difference.
>
> myth doesn't do any rotation, that's up to syslogd or other utilities to do so
>

Well...the issue I ran into is described here:

https://bugs.gentoo.org/show_bug.cgi?id=493396#c5

When it comes to using logrotate, as far as I can see, the logic in
mythtv to re-open logs via a HUP signal now exists *only* in
mythlogserver, so you can no longer directly HUP the frontend or
backend for that purpose.  The only other option I'm aware of with
logrotate is to use copytruncate, which isn't viable because of the
complex log file naming.

Tom