From owner-freebsd-stable@freebsd.org Wed Aug 30 14:34:28 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08B5DE035F5; Wed, 30 Aug 2017 14:34:28 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D80066F618; Wed, 30 Aug 2017 14:34:27 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 380931389; Wed, 30 Aug 2017 14:34:27 +0000 (UTC) Date: Wed, 30 Aug 2017 16:34:27 +0200 From: Baptiste Daroussin To: Cassiano Peixoto Cc: Matthew Seaman , freebsd-stable@freebsd.org, "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830143426.r53pztrybmmvfy6c@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vcnzoghu4f62oozl" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 14:34:28 -0000 --vcnzoghu4f62oozl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote: > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > with when I need to restart a service without upgrading? Reaper > functionnality is a trouble for many administrators who made meta ports to > manage their servers. I really think it could be a option to be > enabled/disabled. Can you see this possibility? >=20 Yes I could add an option to disable the reaper functionnality (and will probably to unblock such use case as soon as I have time to do it.) However I still think this is not the right idea :) and a better one could = be found Bapt --vcnzoghu4f62oozl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmzOwACgkQY4mL3PG3 PloL3w/8C6qQd7JhPXERMD8QLSgFiRo4ZRp/yObh5igDZcIIs8hPQgGKviHFPSfr sgfi+2LyaTv6sNtblHlvaSNSjUlV8iUGdNEUpJ/uG4ELqYpgSP8+G/yuXbcZ8yh9 xfMUgwRsxH1KTdzRlIapAVgvWnfXB691D9AuJMs+6jhpYf3fgH7Qhrz+BWZjVS2o qZy/ga/aML+Xjs11ByButtjby3z9H/ASxEWxuTJQvkzcoyhX2H7MoqyoHN4oB2yC G0jZkSf4itwRtCHz1/pLZ3LjdoJSTB+EOK9gNKnbsEtD2RgXSARTo64PIdrzjJtj nBe877Fmwuqg+lRi3wpKfxYTiNOIL9Nyv4F7tfJy9k8FF5H/Oq+vt1jDRqrHQX8F C5YZuO/FwmQ7k6mIyfvwGSDRcBJ1bkDTN1V+zJJTB5Qlu9GgwC6Jq4zid2r0cnFq C9JXVPx7ug8BCLhDQWY1/9w2HG2VmBrF52YkyYkOwvIKmjMgEigu1rLJiANdVbaQ 4pJqEFD5vxNx3ArprCroEhK8PN5q4f9yuvK8VHY/unKJeLrWmPMO52eZyX7/qUki L6rVq1CZuQuX/Tsz9OQUqH/HouKtfgCsEyX4tzbGpywvTlBxbc9mjD0L0UI40MdS 1TRTKkpGOGYKyiWcVnkiwVrepNY5/GraQzuOoZkBnPBBv6m9JVM= =42m/ -----END PGP SIGNATURE----- --vcnzoghu4f62oozl--