Hi, li...@wrant.com wrote on Fri, Oct 16, 2015 at 03:38:25PM +0300:
> Is examples a good candidate for samples of everything etc that the > user may be wondering about compared to only contain examples for base > system daemons? Of course. For example, /etc/examples/pf.conf is not misplaced, even though pf(4) is not a daemon. > Would the user benefit from a sane starting point for other configs, > optionally when none are already in etc? Usually, no. We strive for "sane and secure by default", for all subsystems. Ideally, that works with no configuration file whatsoever. Ideally, if a user has one special need, they create a configuration file from scratch putting in just that one setting, so they get a configuration file of less than five lines. If five users have five different special needs, ideally, their configuration files won't have a single line in common. If a service needs a substantial configuration file for standard operation, it's ill-designed. Of course, there are exceptions for unusually complex services. For example, you can't possibly run bgpd(8) without providing a substantial amount of information in the configuration file about your site, your neigbors and peers. But having a file in /etc/examples/ ought to be the exception rather than the rule for a service. Yours, Ingo
