From owner-freebsd-ports@FreeBSD.ORG Thu Oct 27 09:15:01 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 51C391065673 for ; Thu, 27 Oct 2011 09:15:01 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from mx0.hoeg.nl (mx0.hoeg.nl [IPv6:2a01:4f8:101:5343::aa]) by mx1.freebsd.org (Postfix) with ESMTP id E1F308FC13 for ; Thu, 27 Oct 2011 09:15:00 +0000 (UTC) Received: by mx0.hoeg.nl (Postfix, from userid 1000) id 2FD8B2A28CE3; Thu, 27 Oct 2011 11:15:00 +0200 (CEST) Date: Thu, 27 Oct 2011 11:15:00 +0200 From: Ed Schouten To: ports@FreeBSD.org Message-ID: <20111027091500.GM63910@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sWvRP97dwRHm9fX+" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: 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 09:15:01 -0000 --sWvRP97dwRHm9fX+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, As crees@ suggested, I'm sending an email to ports@ about this. 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: - 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. - 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. My question is whether anyone has ever attempted to improve the integration with rc-scripts? In the PR I propose something along these lines: 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 Ed Schouten WWW: http://80386.nl/ --sWvRP97dwRHm9fX+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJOqSEUAAoJEG5e2P40kaK7+DsP/33geCXTrIKofHUTHXOYnmyp xwXKZpgJhhr4WlJBWF2I0LeMvahirnMm22VX1JvzzkTs2eXX8cE8QU1tVbTS5U/a 4ZYdR+rXEPEKXcuZPAEhsCZ/p1v2oCuBDFx1EhNjPiKOXB+HL30EceiYq4RS0TlJ YN0uM2mV7WoSbkQAc0PGX8+aim8g1i7Pva8mBPCo/TaHuJ6YREp/k53EAf7DqFgB +aq19G5Ybgvh8QvShzhEiIpXUYWObb9LDgL9Zqm2PNj8Qt4OMf8ftm2/HDLLEqc9 KzqNMBmRkV7+s9G64lG3m0k0rCm5plb8ZZl8OkhG/Az3ynyp328DqgHxO9A14O5T OZjHqL+q8lUab9zCgjZtagg8x52dX/WvlhQUa2tIYUs00o5HgHoq700eooqHjOee 8snLDPktZ/Ue0ETcphs/ZfFBD6gdPoY58WWmWMAgu+XqD3pQOnk0ZHdba4uCkqqQ gCa4fsYmoj4UlgEPjXh5CdVS6KFRKA3DZC86Im5vEGl26sDHkXmDdiAXvBxAq19S sRgFsDSg6Pa67GlzIaLbEHfeKbcdb/dOzf6IT4OvgH4nUxhnYPZpVNwEsBjRtPal Uk9he/eOkGpCU6jTxyL6K7DWKSjnMQemOtFsc05Z7n/L0X6JPi1sTV7+O50zXame knUyO8YURg3Zjm3bdPg6 =QibU -----END PGP SIGNATURE----- --sWvRP97dwRHm9fX+--