svn commit: r318250 - in head: etc etc/newsyslog.conf.d etc/syslog.d tools/build/mk

[Ian Lepore]

On Mon, 2017-05-15 at 10:13 -0700, John Baldwin wrote:
> On Saturday, May 13, 2017 10:39:15 AM Warner Losh wrote:
> > 
> > > 
> > > > 
> > > > - It's really easy to screw up a mergemaster call if you edit
> > > > the files, and install the stock version which removes the
> > > > edits.
> > > Also, programmatically removing the entries means you have to
> > > bake the metadata into etc/Makefile, which is already complicated
> > > enough as-is.
> > Why do you care about removing them at all? They are no-ops if the
> > files don't exist. Why not just always install all these files is
> > where I'm going with this...
> I think this is actually the bigger question.  I think it is
> perfectly
> sensible to support conf.d/* files for ports to use and as a way to
> manage logs for application logs on an appliance, etc.  However, this
> shuffling is a bit of a merge nightmare for anyone using mergemaster
> or etcupdate, and the biggest cost is that newsyslog will create a
> one-line file in /var/log for entries with 'C'.
> 

That's only a good argument for keeping the lines in the monolithic
file if those lines will be ignored when a file in the .conf.d
directory provides conflicting config.  Otherwise my embedded product
that drops different rules for rotating /var/log/messages into .conf.d
STILL has to programmatically edit the monolithic file to remove the
standard rule(s).

-- Ian