Re: Mythtv logging

John Pilkington wrote at about 16:30:15 +0000 on Thursday, November 29, 2012:
 > On 29/11/12 13:45, Duncan Brown wrote:
 > > Hello All
 > >
 > > I'm not a huge fan of the current mythtv logging method which results in
 > > huge amounts of separate log files, so I've changed to using syslog.
 > >
 > > This involves changing the command in init.d/mythbackend to "--syslog
 > > local7" instead of "--logpath /var/log/mythtv/"
 > >
 > > This works great, but every time I upgrade the init.d file is
 > > overwritten. Is there anyway of stopping that file being overwritten by
 > > the upgrade each time?
 > >
 > > cheers
 > >
 > > Dunc
 > >
 > 
 > I probably ought to let someone with a /good/ suggestion come in here, 
 > but I keep copies of foo_distrib.bar and foo_my.bar
 > 
 > After an upgrade, if diff foo.bar foo_distrib.bar is null,
 > cp foo_my.bar foo.bar
 > 
 > If the diff isn't null, some investigation is needed.
 > 
 > I doubt that it's rigorously correct but it seems to work.
 > 

I do a similar thing but I go a step further.
Whenever I modify a config file, I copy the original to
config_file.xorig.
Then I edit a copy of it as config_file.xnew.
Finally, I symbolically link config_file -> config_file.xnew

Whenever a new install occurs, it will write over the link.
So, all I need to do is search for places where config_file.xnew is no
longer linked to config_file and I know that some new version has
overwritten my config files.

I have written a script that goes through my /etc tree (and other
relevant places) looking for such broken links. Actually, my script
also checks to make sure that the permissions, ownership, and SELinux
parameters are consistent across the versions...

Hope this is helpful...