Well, you guys are both right that there is already a logrotate facility for mythbackend -- I had not thought to look because I never saw it rotate. The problem is that it has the parameter size=10M. Why don't we just comment that out, then we should get weekly rotates similar to other log files?
Axel, I agree that in these days of near terabyte disks and HD-quality streams, that 10M is not a lot. On the other hand, as a matter of 'clean' Linux/Unix programming principles (vs. Microsoft bloatware), there is no reason to have multi-megabyte log files. In fact, the primary reason that I suggested a weekly rotate, is that when debugging using the mythbackend log, I had to page through nearly a megabyte of text dating back to October which was a pain in the neck. I can't imagine ever needing more than a week of log files (plus 4 other weeks of backups) to debug anything... Paulo Cavalcanti wrote at about 17:41:53 -0300 on Sunday, March 25, 2007: > On 3/25/07, Axel Thimm <[EMAIL PROTECTED]> wrote: > > > > On Sun, Mar 25, 2007 at 04:39:36PM -0300, Paulo Cavalcanti wrote: > > > On 3/25/07, Axel Thimm <[EMAIL PROTECTED]> wrote: > > > > > > > >On Sun, Mar 25, 2007 at 01:31:20PM -0400, Jeffrey J. Kosowsky wrote: > > > >> Just noticed that the /var/log/mythtv/mythbackend.log just continues > > > >> growing forever (so does /var/log/mythtfilldatabase but it seems to > > > >> collect much less information). Even worse, since mythbackend.log is > > > >> 'hidden' in the subdirectory /var/log/mythtv, casual users may not > > > >> notice how big the log file is getting... > > > >> > > > >> Would it be reasonable to add a logrotate facility for the mythtv > > > >> rpms? > > > > > > > >The rpms already have this for mythbackend.log since about mid-2003 > > (?). > > > > > > > > > > > > The log size has to reach 10M for anything to be done. > > > Mine is running since October and it is just a little bit over 1M now. > > > > > > Maybe a smaller size would be better? 512 K? > > > > Perhaps, but OTOH 10MB isn't much. It's for a system that uses up to > > 3-10 Mbit/sec for recording, e.g. 10MB are 10-30 seconds. :) > > > > But yours should be running since october, logrotate should be > > rotating it weekly irrespective of the size. > > > > I think not. There is only one file in /var/log/mythtv > > mythbackend.log > > The first lines are: > > 2006-10-28 08:30:03.379 Using runtime prefix = /usr > 2006-10-28 08:30:03.575 New DB connection, total: 1 > 2006-10-28 08:30:03.586 Connected to database 'mythconverg' at host: > localhost > 2006-10-28 08:30:03.610 Current Schema Version: 1160 > > ................. > > 2007-03-25 10:17:34.454 AutoExpire: Required Free Space: 3.1 GB w/freq: 10 > min > 2007-03-25 10:17:35.807 Reschedule requested for id -1. > 2007-03-25 10:17:36.642 Scheduled 0 items in 0.8 = 0.57 match + 0.27 place > 2007-03-25 10:17:36.996 Seem to be woken up by USER > > > Only messages about connections with entries for every day since > October. > > > -- > Paulo Roma Cavalcanti > LCG - UFRJ > _______________________________________________ > atrpms-users mailing list > [email protected] > http://lists.atrpms.net/mailman/listinfo/atrpms-users _______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
