Date: Wed, 15 Sep 2010 10:18:00 +0200 From: Greg Byshenk <freebsd@byshenk.net> To: Doug Barton <dougb@freebsd.org> Cc: ports@freebsd.org, Ion-Mihai Tetcu <itetcu@freebsd.org>, Scot Hetzel <swhetzel@gmail.com>, Norikatsu Shigemura <nork@freebsd.org> Subject: Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons Message-ID: <20100915081800.GQ12467@core.byshenk.net> In-Reply-To: <4C901FD0.5000304@FreeBSD.org> References: <20100911222902.bb57444a.nork@FreeBSD.org> <20100911173359.68d71af6@it.buh.tecnik93.com> <AANLkTin0D13%2B9JQJ6wVD7_48Es6rvUJtu=rAx6M1xdjx@mail.gmail.com> <4C901FD0.5000304@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 14, 2010 at 06:22:24PM -0700, Doug Barton wrote: [...] > I can think of at least one more scenario off the top of my head. You > want to run the new version of the service the next time the box is > restarted for whatever reason, but the update is not so critical that it > justifies restarting the system immediately. Do 'you' (generic) -really- want to do this? 'This', in this case being making a change without testing what will happen when the machine or service is next restarted? One of the things I've learned is that things aren't always perfect, and, if I change service <X> in some way, then I want to test that .../rc.d/<X> actually does what I want/expect next time it runs. As I noted before, if by chance something is wrong, I want to know -now-, while the server/service is being maintained, not at some random later date. I am not coming down on either side of the 'automation' issue, as I think that I can see points on both sides; I'm just suggesting that this argument is not a good one. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100915081800.GQ12467>