tmpfiles.d became a thing when /run became a temporary filesystem, so
it is relatively new. And most of the time packages install the
necessary files in /usr/lib/tmpfiles.d, so admins may have never run up
against this issue since it became a thing.
As John says, you can file a bug report with RedHat. Technically that
directory is only necessary when you're running spamd on a socket, so
they may not consider it a bug. For what it's worth, there's no
tmpfiles.d entry on my Ubuntu or Gentoo systems (Gentoo does its
thing in the init script).
I wonder if it's worth adding a note to the wiki, or even the
--socketpath section of the spamd man-page?
On Mon, 27 Nov 2017, John Hardin wrote:
On Mon, 27 Nov 2017, Colony.three wrote:
> I suspect you need an entry in /etc/tmpfiles.d so that directory gets
> created at boot time.
Indeed there is no tmpfiles in the spamassassin package. (I've never heard
of this in 22 years) How can this be, in the 21st Century? As I'd
suspected, everyone is settling for the tcp:port.
What should I do about this, if anything? Fix it just for myself, or let
someone else know?
Report it to the RedHat bugzilla. The SA team doesn't handle distro-specific
packaging issues.
--
Public key #7BBC68D9 at | Shane Williams
http://pgp.mit.edu/ | System Admin - UT CompSci
=----------------------------------+-------------------------------
All syllogisms contain three lines | sha...@shanew.net
Therefore this is not a syllogism | www.ischool.utexas.edu/~shanew
