From owner-freebsd-ports@FreeBSD.ORG  Wed Sep 15 22:50:21 2010
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from hub.freebsd.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with SMTP id 4FD0F1065670;
	Wed, 15 Sep 2010 22:50:20 +0000 (UTC)
	(envelope-from nork@FreeBSD.org)
Date: Thu, 16 Sep 2010 07:50:19 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: ports@FreeBSD.org
Message-Id: <20100916075019.09dcb8ba.nork@FreeBSD.org>
In-Reply-To: <4C911117.7040600@FreeBSD.org>
References: <20100911222902.bb57444a.nork@FreeBSD.org>
	<20100911173359.68d71af6@it.buh.tecnik93.com>
	<AANLkTin0D13+9JQJ6wVD7_48Es6rvUJtu=rAx6M1xdjx@mail.gmail.com>
	<4C901FD0.5000304@FreeBSD.org>
	<20100915081800.GQ12467@core.byshenk.net>
	<4C911117.7040600@FreeBSD.org>
X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; i386-portbld-freebsd8.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Scot Hetzel <swhetzel@gmail.com>, Doug Barton <dougb@FreeBSD.org>,
	Ion-Mihai Tetcu <itetcu@FreeBSD.org>, nork@FreeBSD.org,
	Greg Byshenk <freebsd@byshenk.net>
Subject: Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 22:50:21 -0000

Hi.

On Wed, 15 Sep 2010 11:31:51 -0700
Doug Barton <dougb@FreeBSD.org> 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.

	I agree.

	And to disable '@unexec %D/etc/rc.d/isc-dhcpd forcestop', I wrote
	/etc/rc.conf.d/dhcpd in my machines like following:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
stop_precmd="nothing_to_do"
nothing_to_do () {
	[ x"${rc_force}" = x"yes" ] && exit 1
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

	If needed, we (administrators) can disable a mechanism such as thus.

-- 
Norikatsu Shigemura <nork@FreeBSD.org>