Date: Wed, 10 Nov 2004 12:06:10 +0100 From: Alexander@Leidinger.net To: Volker Stolz <stolz@i2.informatik.rwth-aachen.de> Cc: freebsd-ports@freebsd.org Subject: Re: rc.subr extensions Message-ID: <1100084770.4191f6222333d@netchild.homeip.net> In-Reply-To: <20041109080124.GA59253@i2.informatik.rwth-aachen.de> References: <20041109040834.GA8940@k7.mavetju> <20041109080124.GA59253@i2.informatik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Zitat von Volker Stolz <stolz@i2.informatik.rwth-aachen.de>:
> In gmane.os.freebsd.devel.ports, you wrote:
> > - define RC_FILES, which contain a list of all the files to be
> > stored in /usr/local/etc/rc.d. This file may contain macros like
> > %%LOCALBASE%% and %%RC_SUBR%%.
>
> Excellent! While we discussed this at the ports BOF at EuroBSDCon, it
> was suggested to have a knob for deciding whether to run
> "${RC_SCRIPT} restart" on updating a port -- it has to be configurable
> since the administrator might want fine-grained control. Any chance of
> adding this as sugar on top?
Do we really want to do that? Personally I agree with "stop" before the
deinstall (in some cases...), but not with a "restart". I may want to
make changes of the configuration in between, or I need to make changes
because the application has an incompatible change in the configuration
between versions. Ideally the administrator knows best what to do at an
update, so he should explicitly start, stop or restart a service.
Bye,
Alexander.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1100084770.4191f6222333d>