From owner-freebsd-ports@FreeBSD.ORG Thu Oct 27 16:15:11 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 95226106566C for ; Thu, 27 Oct 2011 16:15:11 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6496A8FC12; Thu, 27 Oct 2011 16:15:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9RGFBrD039032; Thu, 27 Oct 2011 16:15:11 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9RGFBxL039031; Thu, 27 Oct 2011 16:15:11 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Thu, 27 Oct 2011 18:15:01 +0200 From: Baptiste Daroussin To: Ed Schouten Message-ID: <20111027161501.GB4600@azathoth.lan> References: <20111027091500.GM63910@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oLBj+sq0vYjzfsbl" Content-Disposition: inline In-Reply-To: <20111027091500.GM63910@hoeg.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org 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 16:15:11 -0000 --oLBj+sq0vYjzfsbl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. As mentioned in the PR: >=20 > - If I upgrade Apache, MySQL or PostgreSQL, it does not restart the > service, meaning it won't use the freshly installed daemon. This has > potential security issues. >=20 > - If I upgrade Dovecot, it shuts it down during the upgrade, but won't > restart it. This means that I have to watch portmaster to complete and > must not forget to restart Dovecot afterwards. >=20 imho the consistency should be done by removing the autostopping stuff and auto-upgrading stuff. we have no way to be sure it will be safe at all as we don't know from which version of the previous software it has been upgraded, I can't imagine how = much data corruption it would lead to. restarting the services is the goal of the system administrator it shouldn't been automated at all. I would hate that freebsd-update automatically reboot my box because it upg= raded the kernel, the same way I don't want packages to restart my services, it c= an leads to more problem that it can solve. Administrators should know what they do, the only thing that maybe can be d= one is a recommandation to tell the upgrader that he should restart some servic= es. My 2cts, Bapt --oLBj+sq0vYjzfsbl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk6pg4UACgkQ8kTtMUmk6EzdFwCfXX2x90Zodg6LxSGrgrbM8RzF 4KAAn1lJWdVL+xZwV8jaw7NHX36nx+0y =3vHN -----END PGP SIGNATURE----- --oLBj+sq0vYjzfsbl--