Date: Thu, 21 Jun 2012 00:22:55 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Michael Ross <gmx@ross.cx> Cc: Daniel Robbins <drobbins@funtoo.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Replacing rc(8) (Was: FreeBSD Boot Times) Message-ID: <alpine.BSF.2.00.1206210017400.1403@wojtek.tensor.gdynia.pl> In-Reply-To: <op.wf70vswbg7njmm@michael-think> References: <4FDF6177.5050608@unsane.co.uk> <4FDFB44D.9090308@gentoo.org> <4FE0ADCD.9010109@FreeBSD.org> <4FE0C123.8030301@gentoo.org> <CAGH67wRidMZrzjzTSdwud%2BZ5V--wOTN8CHXOWcOr%2BE5XHYo2rA@mail.gmail.com> <4FE0F773.1080403@gentoo.org> <CAGH67wQdb-c0Kf=60rkaJSH8Hd0OjwCi=rQQMzGq8xfp2q7b=Q@mail.gmail.com> <4FE100F9.2050009@funtoo.org> <20120620073920.GA5300@lonesome.com> <alpine.BSF.2.00.1206201618560.75278@wojtek.tensor.gdynia.pl> <CAPDOV49kkOdeV%2B6LVW5j5PO6VYrrNVqWZEksc_GzvWHjbufoAQ@mail.gmail.com> <alpine.BSF.2.00.1206201722520.1856@wojtek.tensor.gdynia.pl> <CAPDOV4_ufNGyheDAhPxfndJ7WtH_u=5z7mrLtW-5-a9BMbCswg@mail.gmail.com> <alpine.BSF.2.00.1206201745040.1949@wojtek.tensor.gdynia.pl> <CAPDOV4_Fsj_QCLDWSs3o5qiDKS2hTH4qBf8fwJftne8KJNXy1Q@mail.gmail.com> <op.wf7v5el5g7njmm@michael-think> <CAPDOV4_x2T7p_3puD6AKpjoTwFCRPeP6mvvLxRVv_ZrgCTmU3g@mail.gmail.com> <alpine.BSF.2.00.1206202228530.3289@wojtek.tensor.gdynia.pl> <op.wf70vswbg7njmm@michael-think>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>> >>> # rc maintenance >>> # rc online >> >> this functionality seems useful. > > That's... not the word I'd have used. > I'm sort-of-emulating this using custom scripts quite often, true. custom script that do lots of start or stops are good. But with N>2 "runlevels" without this subsystem you would need to run multiple of them or have N*(N-1) scripts. But i don't like the idea of executing commands to add new "runlevels", configure it etc. I like the idea of single config file, or POSSIBLY integrating it in rc.conf service_enable=YES could be replaced by service1_enable=YES service1_disable="maintenance blah" service2_enable="maintenance" which means service1 should be stopped at "runlevels" maintenance and blah, and service2 enabled only at "runlevel" maintenance.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206210017400.1403>