Re: Fwd: Improved configuration hierarchy

Markus Lude <[email protected]>
Newsgroups gmane.comp.log.logwatch.devel
Message-ID <[email protected]>
On Thu, Feb 14, 2008 at 10:25:18AM -0800, Mike Tremaine wrote:
> Kirk Bauer wrote:
> > Not sure if we want to separate default and dist... but if we weren't
> > treating all directories equally I think we should.
> > 
> > Unfortunately these days it is all I can do to forward these to the
> > list, I'm not doing as much pre-screening as I normally do.  Hopefully
> > this is a useful patch.
> > 
> > 
> > ---------- Forwarded message ----------
> > From: Chris O'Regan <[email protected]>
> > Date: Tue, Feb 12, 2008 at 3:40 PM
> > Subject: Improved configuration hierarchy
> > To: [email protected]
> > 
> > 
> > Hello,
> > 
> >  I am adapting LogWatch to our environment. Fortunately a lot of the work
> >  has been done to help customize the configuration but I have made some
> >  changes. In particular, the HOWTO states that the configuration
> >  structure is the same for all three directories, but in practice this is
> >  not always true. This patch ensures that logwatch.pl will look in all
> >  three places for its configuration, and in the proper order.
> > 
> >  Also, I found it useful to separate the "default" and "dist"
> >  configuration directories. I associate the "default" with what comes
> >  with this particular version of logwatch and it should refer to the
> >  package installation directory. The "dist" directory contains
> >  modifications that affect all my servers. They should reside in a shared
> >  directory outside of the package so that it is easy to upgrade. I have
> >  also changed the naming convention to fit my environment.
> > 
> >  Not sure if these are of interest to you but I figured I would share
> >  them anyway.
> > 
> 
> 
> This one is confusing to me. I would normally think that the 
> /etc/logwatch/conf would be enough since the RPM spec says not to 
> upgrade these files? I might be missing the point. I'm going to pass on 
> this for now, Bjorn can weigh in if he has the time since the dist/ was 
> his baby.

As I understood it,

default.conf/ -> default logwatch configuration
dist.conf/    -> changes made for some distribution (usually from the
                 package maintainer)

Both of the above usually in /usr/share/logwatch or some similar
directory.

/etc/logwatch/conf/ -> local changes

It should be enough to touch the stuff in /etc/logwatch/conf/. Unless of
course you are a package maintainer. The OP should better move his
changes from "dist" to "etc".

HTH,
Markus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.