> On May 13, 2017, at 9:39 AM, Warner Losh <i...@bsdimp.com> wrote:
> 
> On Sat, May 13, 2017 at 10:32 AM, Ngie Cooper <yaneurab...@gmail.com 
> <mailto:yaneurab...@gmail.com>> wrote:
>> 
>>> On May 13, 2017, at 09:29, Ngie Cooper <yaneurab...@gmail.com> wrote:
>>> 
>>> On May 13, 2017, at 08:37, Rodney W. Grimes 
>>> <free...@pdx.rh.cn85.dnsmgr.net> wrote:
>>> 
>>>>> Author: ngie
>>>>> Date: Sat May 13 03:10:50 2017
>>>>> New Revision: 318250
>>>>> URL: https://svnweb.freebsd.org/changeset/base/318250
>>>>> 
>>>>> Log:
>>>>> Handle the logfiles in newsyslog and syslogd conditionally, based on
>>>>> src.conf(5) knobs
>>>>> 
>>>>> This will allow consumers of FreeBSD to use the unmodified configuration
>>>>> files out of the box more than previously.
>>>> 
>>>> What about simply generating proper newsyslog.conf and syslog.conf based
>>>> on the the MK_ values rather than change the visible administration
>>>> interface that has finger memory, ansible, and puppet support?
>>> 
>>> - My employer doesn't use puppet on its appliances.
>>> - Files snapshotted in time bitrot (which was the case with our configs, 
>>> which is part of the reason behind this change.
> 
> couldn't you have an Isilion config file in the appropriate directory
> instead? And use the default newsyslog / syslog config files?

I’m not sure I’m in disagreement with this statement, but the fact is that 
there are a handful of config files, about 200 lines each, which drive 
newsyslog/syslogd on OneFS, with a fair amount of duplication. I’m trying to 
simplify the mess I’m presented with at work, one bit at a time.

>>> - 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 don’t follow. Could you please restate this paragraph?
Thanks,
-Ngie

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to