From owner-freebsd-ports@freebsd.org Sun Jan 7 14:31:14 2018 Return-Path: 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 72C7FE6FC20 for ; Sun, 7 Jan 2018 14:31:14 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [IPv6:2001:41d0:302:1100::7:9a96]) (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 293226886E for ; Sun, 7 Jan 2018 14:31:14 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:8c:2e6d:3401:f18a:dc10:c0a2:3ced] (p2003008C2E6D3401F18ADC10C0A23CED.dip0.t-ipconnect.de [IPv6:2003:8c:2e6d:3401:f18a:dc10:c0a2:3ced]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3zF16l0GbTzDfv for ; Sun, 7 Jan 2018 15:31:10 +0100 (CET) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd Message-Id: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org> Date: Sun, 7 Jan 2018 15:31:08 +0100 To: freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=2.2 required=5.0 tests=RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 14:31:14 -0000 Hi, I am following 11-STABLE and therefore upgrading my system quite = frequently. During that process I do recompile all ports installed by = poudriere and upgrade all ports after reboot. Today I stumbled over an IMHO weird behaviour of the spamassassin's = installation process, that stops a running spamd daemon without = restarting. Even worse, the user will not be informed about that = procedure: mail> /usr/local/etc/rc.d/sa-spamd status spamd is running as pid 13859. mail> pkg upgrade -fy spamassassin Updating poudriere repository catalogue... poudriere repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: spamassassin-3.4.1_11 [poudriere] Number of packages to be reinstalled: 1 [mail] [1/1] Reinstalling spamassassin-3.4.1_11... =3D=3D=3D> Creating groups. Using existing group 'spamd'. =3D=3D=3D> Creating users Using existing user 'spamd'. [mail] [1/1] Extracting spamassassin-3.4.1_11: 100% [*] Stopping spamd. Waiting for PIDS: 13859, 13859. You may need to manually remove = /usr/local/etc/mail/spamassassin/local.cf if it is no longer needed. Message from spamassassin-3.4.1_11: = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D You should complete the following post-installation tasks: 1) Read /usr/local/share/doc/spamassassin/INSTALL and /usr/local/share/doc/spamassassin/UPGRADE BEFORE enabling SpamAssassin for important changes 2) Edit the configuration in = /usr/local/etc/mail/spamassassin, in particular = /usr/local/etc/mail/spamassassin/init.pre You may get lots of annoying (but harmless) error = messages if you skip this step. 3) To run spamd, add the following to /etc/rc.conf: spamd_enable=3D"YES" 4) If this is a new installation, you should run = sa-update and sa-compile. If this isn't a new installation, you should probably run those commands on a regular basis anyway. 5) Install mail/spamass-rules if you want some = third-party spam-catching rulesets SECURITY NOTE: By default, spamd runs as root (the AS_ROOT option). If you wish to change this, add the following to /etc/rc.conf: spamd_flags=3D"-u spamd -H /var/spool/spamd" = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D mail> /usr/local/etc/rc.d/sa-spamd status spamd is not running. Ok, one might notice that the daemon has been stopped [*], but section = "You should complete =E2=80=A6" fails to mention, that one needs to = restart the daemon after upgrading. Please correct me if I am wrong but I have always been under the = impression that stopping a daemon whilst upgrading violates conventions? Thanks and with kind regards, Michael