https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7924
Bill Cole <billc...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |billc...@apache.org
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Bill Cole <billc...@apache.org> ---
This is a problem with how SA and the cron job running sa-update were
installed. This is handled by the packager for a specific distribution (e.g.
RedHat, Debian, etc. ) or by the user themselves if installed from source.
SpamAssassin itself does not install any sa-update cron job, but rather
documents the available choices for packagers and users in the README, INSTALL,
and PACKAGING files.
The most common solution chosen by packagers is to install SA as root and run
the sa-update script as root. You could also install it as another user (e.g.
spamd) so that directories created based on Makefile.PL arguments (e.g.
LOCALSTATEDIR, which is usually /var/lib/spamassassin) are owned by that user
and then you can run any maintenance scripts like sa-update as that user.
Because the core SA distribution is designed to work on any system that can run
Perl, for installations by privileged or unprivileged users, the distribution
build system does not set ownership and permissions of the update directory or
of the other configurable directories to a user that may not exist on a
specific system.
--
You are receiving this mail because:
You are the assignee for the bug.
