Date: Sun, 7 Jan 2018 15:31:08 +0100 From: Michael Grimm <trashcan@ellael.org> To: freebsd-ports@freebsd.org Subject: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd Message-ID: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76627A89-D7E9-4010-910B-5F25886E7E7E>