I don't appreciate you implying I'm a stupid idiot. That and every bit
of your language has NO place on this forum, especially your reference
to my Lord and Savior!!!!
I had NOTHING to do with setting that folder, no matter how STUPID you
think I am. That's the folder that appeared in the log file when I ran
it out of the box. Why don't you read the full thread before INSULTING
people.
On 11/22/2019 5:17 PM, Reindl Harald wrote:
Am 22.11.19 um 23:06 schrieb Jerry Malcolm:
Well, I thought I finally had everything resolved. When I run
spamassassin -D --lint I get the lines:
Nov 22 21:57:57.954 [13813] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_toks
Nov 22 21:57:57.954 [13813] dbg: bayes: tie-ing to DB file R/O
/root/.spamassassin/bayes_seen
Nov 22 21:57:57.955 [13813] dbg: bayes: found bayes db version 3
So, I'm ready to start it up as a daemon and start using it... I checked
/var/log/maillog and see this instead:
Nov 22 21:58:21 ip-172-31-47-84 spamd[13780]: bayes: no dbs present,
cannot tie DB R/O: /tmp/spamd-13780-init/.spamassassin/bayes_toks
When running the same SA as a service, it's NOT looking for bayes in
/root/.spamassassin
jesus christ why should a service typically not running as root look in
roots home directory? why should it even can access it and if it can
which idiot ruined your permissions?
why the hell are you doing *anything* as root at all?
* train bays as the user spamd is running
* locate bayes in the homedirectory of that user
* done
