There's also simplicity of implementation. Even a few more
lines means more bugs. Having the parameters as one and
checking for less cases means simpler software, and simple
is reliable.
________________________________________
From: owner-m...@openbsd.org [owner-m...@openbsd.org] on behalf of Raf Czlonka
[rczlo...@gmail.com]
Sent: January 29, 2015 8:03 PM
To: misc@openbsd.org
Subject: Re: Wouldn't `daemon_enable=YES` make more sense than
`daemon_flags=""` in rc.conf.local?
On Thu, Jan 29, 2015 at 11:16:41PM GMT, openda...@hushmail.com wrote:
> Indeed, don't get me wrong, I use flags all the time as well. I'm just
> arguing for a cleaner separation between startup and configuration for
> a slightly more semantic (and better looking) `rc.conf.local`, ie.:
>
> ftpd_enable=YES
> ftpd_flags="-llSA"
> mountd_enable=YES
> nfsd_enable=YES
> nfsd_flags="-tun 4"
> ntpd_enable=YES
> portmap_enable=YES
> rsyncd_enable=YES
> slowcgi_enable=YES
> unbound_enable=YES
Semantic? Maybe. Better looking? Most certainly not!
Configuration == Startup
Basically, if you are configuring a daemon, that is by using
${daemon_flags}, then you *intend* to *run* it. If you *don't* intend to
run it, *don't* configure it (or hash it out)!
Simple? Simple!
> Thanks for your feedback!
You're welcome :^)
Regards,
Raf
