The attached patch applied over current init.d for spamd (from spamassassin ebuild) makes it require to be started after syslog (or any other logger) if present. If it's not used, and it's started before syslog, it throws up some errors at console about being unable to access syslog socket (but still starts). HTH, Diego
Created attachment 53410 [details, diff] Patch for spamd init.d script
News about this? It's trivial and I can commit it in case.
If "use" is no "need" (spamd also runs without syslog) it looks fine for me.
I'll get this in tonight - i'm mucking around with a docs bug for spamassassin right now, easy enough to commit (i'm back :)