From owner-freebsd-ports@freebsd.org  Tue Jan  9 18:24:22 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@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 6EAD7E689AF
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue,  9 Jan 2018 18:24:22 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net
 [IPv6:2001:41d0:401:2100::5:8a0e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 348D969850
 for <freebsd-ports@freebsd.org>; Tue,  9 Jan 2018 18:24:21 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from [IPv6:2003:8c:2e04:8901:d5b3:1562:cee8:c489]
 (p2003008C2E048901D5B31562CEE8C489.dip0.t-ipconnect.de
 [IPv6:2003:8c:2e04:8901:d5b3:1562:cee8:c489])
 by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 3zGLBb0QlRz4Ks;
 Tue,  9 Jan 2018 19:24:07 +0100 (CET)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at mail.enfer-du-nord.net
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Subject: Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd
From: Michael Grimm <trashcan@ellael.org>
In-Reply-To: <CAN6yY1vExnreT2mJ1cEKALZGwV4emS4fanSiEB_v4e5-BPU0tA@mail.gmail.com>
Date: Tue, 9 Jan 2018 19:24:04 +0100
Cc: Kevin Oberman <rkoberman@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C992D285-E5F3-49CA-902A-C2DDE9D3EEF9@ellael.org>
References: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org>
 <5A523873.2050001@quip.cz>
 <CAN6yY1vExnreT2mJ1cEKALZGwV4emS4fanSiEB_v4e5-BPU0tA@mail.gmail.com>
To: FreeBSD Ports ML <freebsd-ports@freebsd.org>
X-Mailer: Apple Mail (2.3445.5.20)
X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE,
 SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 18:24:22 -0000

Kevin Oberman <rkoberman@gmail.com> wrote:
> On Sun, Jan 7, 2018 at 7:10 AM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:

>> There are no consensus about what services should do on deinstall or
>> upgrade. That's why there is such a mess in ports / packages.
>> Some did nothing (my preferred way), some stop (but did not start) =
the
>> service,
[=E2=80=A6]
> Beg pardon, but I am aware of this being discussed twice on this list =
and
> both times there was a clear consensus in both cases that it was
> unacceptable or a port/package upgrade to touch running daemons.  =
There
> were arguments that some port might make changes in underlying files =
that
> could break a daemon in some way, though I can't recall any actual =
examples.
>=20
> The only real argument was that leaving a daemon with a serious
> vulnerability running was not acceptable. A competent admin should =
never
> let this happen, but I'm sure it has.

FTR: I have filed PR 225030 on this.

Thanks and regards,
Michael