On Wed, Oct 20, 2004 at 04:18:10PM +0100, Werner Schalk quoth: > Oct 20 17:10:30 knoxville spamd[19984]: info: setuid to qmailq > succeeded > Oct 20 17:10:30 knoxville spamd[19984]: Cannot open > bayes_path /var/qmail/.spamassassin/bayes R/O: > > Any ideas of what might be wrong here?
Permissions. > The directory /var/qmail/.spamassassin looks like this: > > knoxville:/home/sebastian# ls /var/qmail/.spamassassin/ -la > total 10192 > drwxr-xr-x 2 qmailq qmail 4096 Oct 20 17:04 . > drwxr-xr-x 13 root qmail 4096 Oct 20 16:43 .. > -rw-r--r-- 1 qmailq qmail 0 Sep 16 12:43 bayes > -rw------- 1 qmailq qmail 2039615 Sep 16 11:30 bayes_journal > -rw------- 1 qmailq qmail 2172 Sep 16 11:30 bayes_msgcount > -rw------- 1 qmailq qmail 5230592 Sep 16 10:57 bayes_seen > -rw------- 1 qmailq qmail 5431296 Sep 16 10:57 bayes_toks > -rw-r--r-- 1 qmailq qmail 1218 Feb 3 2004 user_prefs > > I changed the ownership of those files to nobody.nogroup, root.root, > qmailq.qmail but that did not change anything. Any ideas? Google did not > really help me... The process that opens those files is the spamd process. Therefore, the files must be useable by the user the spamd process is running as. You can either check your spamd scripts to see who is running it, or you can do a 'ps aux | grep spamd' to find out what user is running spamd. Then, make sure that user can edit those files. It's quite likely not qmailq unless you explicitly set it up that way. ~Kyle -- I have an existential map; it has `you are here' written all over it. -- Steven Wright
signature.asc
Description: Digital signature
