Date: Sat, 12 Sep 2015 08:02:11 -0700 (PDT) From: Roger Marquis <marquis@roble.com> To: RW <rwmaillists@googlemail.com> Cc: ports@freebsd.org Subject: Re: rc script problem - pidfile not being recognised In-Reply-To: <20150912122759.412ea139@gumby.homeunix.com> References: <20150911161850.402b3d5a@gumby.homeunix.com> <853047065.182.1441986957380.JavaMail.Kevin@Thoth> <20150911171930.59e67cc2@gumby.homeunix.com> <0NUI007RMV24EUD0@hades.sorbs.net> <55F367CF.2080507@sorbs.net> <20150912122759.412ea139@gumby.homeunix.com>
| previous in thread | raw e-mail | index | archive | help
RW via freebsd-ports wrote: > You'd rather an rc script fails at run-time and shuts down the wrong > daemon than fail when the script is being developed? It's not so much where the script fails than that it fails in the first place. Neither a pidfile nor a command_interpreter needs to be required for an rc scripts to work. These are nice features but making them mandatory is at best a sort of premature optimization. The freebsd rc script environment is already far too OS-specific and un-editable, often containing no readable shell code at all. What if your interpreter changes from say python2.7 to python for example? Does that mean you have to reinstall all the associated packages or edit their rc scripts? Neither shouldn you have to parse who knows how many hundred of lines of shell code included by /etc/rc.subr or rewrite an rc script from scratch to make a simple change. We appreciate the features this subsystem provides and the work devs have put into it but not when it's made mandatory. The value of KIS needs to be emphasized here. IMO, Roger Marquis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>