Date: Sun, 7 Jan 2018 10:05:26 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Michael Grimm <trashcan@ellael.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd Message-ID: <CAN6yY1vExnreT2mJ1cEKALZGwV4emS4fanSiEB_v4e5-BPU0tA@mail.gmail.com> In-Reply-To: <5A523873.2050001@quip.cz> References: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org> <5A523873.2050001@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
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, some modify user edited config files (removing / disabling modules > in httpd.conf so Apache is broken on each upgrade of module(s)). > > Miroslav Lachman 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. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vExnreT2mJ1cEKALZGwV4emS4fanSiEB_v4e5-BPU0tA>