Date: Wed, 15 Sep 2010 11:31:51 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Greg Byshenk <freebsd@byshenk.net> 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: <4C911117.7040600@FreeBSD.org> In-Reply-To: <20100915081800.GQ12467@core.byshenk.net> References: <20100911222902.bb57444a.nork@FreeBSD.org> <20100911173359.68d71af6@it.buh.tecnik93.com> <AANLkTin0D13%2B9JQJ6wVD7_48Es6rvUJtu=rAx6M1xdjx@mail.gmail.com> <4C901FD0.5000304@FreeBSD.org> <20100915081800.GQ12467@core.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/15/2010 1:18 AM, Greg Byshenk wrote: > 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? Once again, it's an area where the intelligence of the admin is expected to be applied. :) If you're thinking in terms of one machine, you're right, this probably isn't a good idea. However if you're thinking of a server farm with 1,000's of identical systems, a good QA process (so it's a known-good change), and monitoring in place to detect a failed reboot and take that box out of the pool; not only is what I described reasonable, it's commonplace. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C911117.7040600>