'pkg upgrade -f spamassassin' stops but doesn't restart spamd

Michael Grimm trashcan at ellael.org
Tue Jan 9 18:24:22 UTC 2018


Kevin Oberman <rkoberman at gmail.com> wrote:
> On Sun, Jan 7, 2018 at 7:10 AM, Miroslav Lachman <000.fbsd at 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,
[…]
> 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.
> 
> 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




More information about the freebsd-ports mailing list