Date: Tue, 2 Oct 2007 15:25:04 -0700 (PDT) From: Doug Barton <dougb@FreeBSD.org> To: Pietro Cerutti <gahr@gahr.ch> Cc: freebsd-rc@FreeBSD.org Subject: Re: conf/105568: [patch] Add more flexibility to rc.conf, to choose "_enable" values at startup Message-ID: <alpine.BSF.0.9999.0710021522150.23009@ync.qbhto.arg> In-Reply-To: <47022870.7030607@gahr.ch> References: <200710012040.l91KeC2t097859@freefall.freebsd.org> <alpine.BSF.0.9999.0710011753400.1408@ync.qbhto.arg> <47022870.7030607@gahr.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Oct 2007, Pietro Cerutti wrote:
> Doug Barton wrote:
>> What do you feel is the need/benefit of adding this? I read your PR, and
>> I don't find your reasoning very compelling. You can easily start or
>> stop services after the system enters multi-user mode by simply changing
>> the _enable variable and running /etc/rc.d/foo start|stop as needed.
>> There are precious few services that depend on being started at boot time.
>
> 1) enter multi user mode
That's going to happen anyway, so this is a red herring.
> 2) edit rc.conf
> 3) /etc/rc.d/foo [start|stop]
Or just do: /etc/rc.d/foo onestart
> 1) choose yes or no before entering multi user mode
>
> It's just a matter of comfort, cleanness and easy of handling.
I certainly see that you believe this to be true, but I'm sorry to say
that I don't agree with you. I didn't see anything in the list of examples
you gave that convinces me that what you're proposing is dramatically
better than simply using onestart where needed.
Perhaps others will have different opinions.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.9999.0710021522150.23009>