On Thu, Feb 16, 2023 at 05:34:37PM -0500, joe a wrote: > Oh, of course. I installed as root initially, being foolish perhaps, but > did create a specific user "later" and adjusted permissions as needed. Or, > so I thought.
well, installing as root (especially with restrictive umask) manually (e.g. "make install" or "cpan" vs. "yum/rpm/dpkg") may often make problems, even if you later switch to packages (you need to look not only at final file permissions, but at directories leading up to it too). namei -l /path/to/file.pm is often helpful to quickly check ALL permissions needed to access file (+x on directories is a must) > Permissions are (almost) certainly the issue. Now having the impressive > locate/mlocate creature at my command, I might actually make progress. I usually troubleshoot those (if log is insufficient) with: strace -efile -o /tmp/sa.log spamassassin foobar then look at /tmp/sa.log to see which open/stat/access returned -1 EPERM or EACCES error. Then check all path components for that file using "namei -l" (or multiple "ls -ld"). Then try to su to that user and "cat" that file manually. If not regular DAC (chmod/chown) permissions, it might also be SELINUX restrictions or more rarely ACL (getfacl(1)). -- Opinions above are GNU-copylefted.
