On 05/18/2017 05:56, Rodney W. Grimes wrote: >> Author: ngie >> Date: Thu May 18 06:25:39 2017 >> New Revision: 318441 >> URL: https://svnweb.freebsd.org/changeset/base/318441 >> >> Log: >> Handle the cron.d entry for MK_AT in cron conditionally >>
> > The thread on the newsyslog clearly shows that this is a contriversial change. > > I strongly object to further splitting of /etc/FOO into /etc/foo.d/FOO files > to suite Dell/EMC/Isilon's needs. It is in conflict with the needs and > desires of others. > I'm not an appliance vendor and am not affiliated with Dell/EMC/Isilon and this change served my needs and desires. When automating configuration management, templating a file instead of conditionally installing/removing configuration snippets is: 1) less performant because you can't just check mtime of the expanded template vs. the source file to figure out whether to expand it again, which affects practical frequency of configuration runs 2) couples logic from unrelated configuration modules, making working on different configuration with different people more difficult I really wish we had /etc/fstab.d/ :) > I especially object to it being done on a 1 of case, either completly split > the file or make it 1 file, but making it this miss match is just adding to > the work load of ansible and puppet task writting. You now have to mange > 2 config files rather than 1 for cron, and 7 for newsyslog instead of 1. > I agree that inconsistencies are bad, but I think we can get there incrementally, unbundling configuration of one MK_* thing at a time. - Nikolai Lifanov
signature.asc
Description: OpenPGP digital signature
