From owner-freebsd-ports@FreeBSD.ORG Thu Oct 27 18:13:18 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF6F8106564A for ; Thu, 27 Oct 2011 18:13:17 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id B80758FC17 for ; Thu, 27 Oct 2011 18:13:17 +0000 (UTC) Received: from 184-78-197-203.war.clearwire-wmx.net ([184.78.197.203] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RJTv0-0007ve-0N; Thu, 27 Oct 2011 10:38:43 -0700 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Thu, 27 Oct 2011 10:39:03 -0700 Date: Thu, 27 Oct 2011 10:39:03 -0700 From: Chip Camden To: ports@FreeBSD.org Message-ID: <20111027173903.GC1058@libertas.local.camdensoftware.com> Mail-Followup-To: ports@FreeBSD.org, Ed Schouten References: <20111027091500.GM63910@hoeg.nl> <20111027162715.GB1012@sysmon.tcworks.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="32u276st3Jlj2kUU" Content-Disposition: inline In-Reply-To: <20111027162715.GB1012@sysmon.tcworks.net> User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Cc: Ed Schouten Subject: Re: ports/162049: The Ports tree lacks a framework to restart services X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 18:13:18 -0000 --32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Scott Lambert on Thursday, 27 October 2011: > On Thu, Oct 27, 2011 at 11:15:00AM +0200, Ed Schouten wrote: > > Hi folks, > >=20 > > As crees@ suggested, I'm sending an email to ports@ about this. > >=20 > > What really bothers me when I use the FreeBSD Ports tree on one of my > > systems, is that the behaviour of dealing with services is quite > > inconsistent.=20 > >=20 > > My question is whether anyone has ever attempted to improve the > > integration with rc-scripts? In the PR I propose something along these > > lines: > >=20 > > We know exactly which ports install rc scripts (USE_RC_SUBR). > > Why not run `/usr/local/etc/rc.d/${FOO} status' and > > `/usr/local/etc/rc.d/${FOO} stop' prior to installation. Based > > on the return value of the first, we can run > > `/usr/local/etc/rc.d/${FOO} start' after installation. >=20 > If all of that is contingent upon a boolean knob the admin can set, > something like NO_RESTART_SERVICES, I suspect everyone could get > what they want and the bikeshed would be limitted to what the default > for that boolean should be. >=20 > The people who don't want the services restarted automagically can > set it and, once things use the new ports framewoork properly, not > have to worry about suprises. The people who want everything to > restarted as soon as possible can set the knob the other way. =20 >=20 > It could help keep our less sophisticated users from continuing to > run vulerable versions of software after they think they have done > what is needed to get the patched software. The sophisticated users > would still be free to choose which foot to shoot. >=20 > A side effect might, eventually, be to encourage ports maintainers > to analyse their ported software for incompatible config changes > so that they can programatically halt the install and output a > warning message before attempting to stop the old daemon then > upgrading while a likely un-usable config is in place. >=20 > I see it as win, win, if there is a knob. >=20 > I do not like either option without a knob, depending on the box > we are talking about. >=20 +1 for this idea. +10 for "The sophisticated users would still be free to choose which foot to shoot." --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --32u276st3Jlj2kUU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOqZc3AAoJEIpckszW26+R534IAKfkUdIQtDymWuQ16iMwA110 JUkXqoLMuOdrTQe5CiIECnDzwEch38D8IyBVoq3EDktsVlisliTcBsnLukeFxJdK HfVpylcGuP+N+UdQbmNF+PIWxAcXqA5XcU9Tyg71s4UXGcDC1K5OwpSD+3uqFR7p qIkLUqWaOLxEAhYrGqQAqIsi3zbbrK2rRyeLbYpacKox1IZudmUTvIh5eW8+rvwX hQNYCV7yD9E9QmQSnnXp6Te9Zr7ixFuH/AqTU1I07xcnVVybWcUzyq5K0yYtNo04 7aSiQ8M6GYRGu+Tm1PtKisUG5VdUy1SqVS5bYbRjiheuBoIb+R3ZICL7nGYdsBc= =MEUn -----END PGP SIGNATURE----- --32u276st3Jlj2kUU--