Ok, nearly there. :) I start spamd 3.1.6 as follows: /usr/local/bin/spamd -D -x -q -d -m 16 -r /var/run/spamd.pid -i 127.0.0.1 -A 127.0.0.1 -u spamd -s mail.crit
I get: [11581] dbg: logger: adding facilities: all [11581] dbg: logger: logging level is DBG [11581] dbg: logger: successfully opened file mail.crit [11581] dbg: logger: successfully added file method [11581] dbg: spamd: creating INET socket: [11581] dbg: spamd: Listen: 128 "successfully opened file mail.crit"?? Say what? :) I specified the syslog facility "mail.crit", not a file! Far as I can tell, -s is still used to set the syslog facility. How do I get SA to log to syslog again? These are more worrisome, though: Fri Oct 6 09:04:18 2006 [11583] dbg: prefork: new lowest idle kid: 11585 Fri Oct 6 09:04:18 2006 [11583] dbg: prefork: child reports idle Fri Oct 6 09:04:18 2006 [11583] info: prefork: child states: II Fri Oct 6 09:04:18 2006 [11585] dbg: prefork: sysread(7) not ready, wait max 300 secs Fri Oct 6 09:04:28 2006 [11586] dbg: prefork: periodic ping from spamd parent Fri Oct 6 09:04:28 2006 [11586] dbg: prefork: sysread(8) not ready, wait max 300 secs Fri Oct 6 09:04:28 2006 [11585] dbg: prefork: periodic ping from spamd parent Fri Oct 6 09:04:28 2006 [11585] dbg: prefork: sysread(7) not ready, wait max 300 secs That does not look good. What does it mean, and how can I solve it? Thanks, - Mark
