Matt Kettler wrote:
At 10:02 AM 10/18/2004, Rick Macdougall wrote:
Hi,
No, they keep running as root all the time.
98160 root 62 0 49992K 41208K RUN 0:09 18.49% 17.53% perl5.8.2
It's a large bug here that affects the permissions of the bayes_journal file etc since it gets owned by root instead of the -u user on the spamd command line.
Hmm, IMNSHO it's a large bug in SA configuration to set a bayes_path in your local.cf without setting the mode to 777 in your local.cf as well.
Don't try to rely on every instance of SA, including command-line as well as spamc/spamd, running as one and only one, user. It's not going to happen that way in reality.
That said, are you seeing this log message out of spamd (check syslog):
logmsg( "Still running as root: user not specified with -u, " . "not found, or set to root. Fall back to nobody." );
Hi,
Why would one not rely on SA running as one and only one user when writing to bayes and auto_whitelist files ? Is that not the whole reason behind having a separate user to run spamd as ?
I have no errors in my logfiles about it still running as root, but I do see the debug lines telling me that the user has changed
debug: user has changed
but of course, it is still writing the journal file and auto_whitelist as root.
Anything else you'd like me to check on, I'd be more than happy to check and test.
Regards,
Rick
