[mythtv-users] Question on channel record removal

[Tom Dexter]

On Thu, Dec 26, 2013 at 11:19 AM, Bill Meek <keemllib at gmail.com> wrote:
> On 12/26/2013 09:41 AM, Tom Dexter wrote:
>>
>>
>> I've run into an issue when building with --disable-mythlogserver.  I
>> sent a separate email to the list on this with no replies as yet.  I
>> figured that since you build with that option you may know something
>> about this one:
>>
>> With that option enabled the logs are all getting written as I
>> expected (logging as with 0.25.3), but my logrotation isn't working
>> correctly.  After a weekly rotation I found my mythbackend process
>> actively logging to a file that had been rotated to the "old"
>> directory (/var/log/mythtv/old/mythbackend.20131213163424.1223.log.1).
>>   As far as I can tell looking briefly at the code I don't think
>> there's even any SIGHUP logic to re-open log files outside of
>> mythlogserver.  I'm I correct on that, and if so, it there any way in
>> 0.27 with --disable-mythlogserver. to handle log rotation in any
>> manner similar to that used with 0.25.3?
>
>
> Hi;
>
> I saw your post, but I suspect you run your backend as a 'real' server,
> where I use the shutdown/wakeup method.
>
> I do prefer the --logpath option and do use logrotate to manage the
> files. However, I have a cron job that moves the per-session logs into
> mythVariousProgramName.log files.
>
> This is the part where someone says there's an easier way, but here are
> the crontab/script, it really doesn't need to be hourly, I just set
> it up when --logpath was introduced and never changed it:
>
>     http://pastebin.com/ShZztrLw
>     http://pastebin.com/6yPdKx4U
>
> I does have the benefit of making zgreps for old log entries easy.
>
>
> --
> Bill

I'm a little confused when you refer to the "--logpath option".  That
just defaults to /var/log/mythtv correct?  By that are you simply
referring to the 0.25 change to write to the new process/timestamp
file names?

I actually like the idea of those scripts...that is getting everything
into a one file per processes format.  However in my case that would
remove the log files actively being written to...not sure how that'd
work out.

It seems though that for a true mythbackend server, there just aren't
any good options once --disable-mythlogserver has been used.  My
mythbackend process sometimes runs non-stop for months, and apparently
now has no mechanism for telling it to reopen the logs.  Up until 0.25
I used "copytruncate" in my mythtv logrotate configuration, but that
doesn't work out with the new file names at all.

If various distros are using the --disable-mythlogserver option, what
if anything are they doing about logrotate configurations?

I have a feeling I'm going to end up just using mythlogserver, which
I'd rather not do.

Tom