I'm also running spamd under supervise and just recently I asked this list why I couldn't get the -D option to work. Where were you guys then? ;-)
I wasn't here yet... so I have an excuse! ;-)
I solved it in the meantime by sending the debug output to a separate logfile via multilog. Otherwise, no problems with that setup and no need to worry about spamd crashing and mails getting deferred overnight.
Here's my current run scripts:
[EMAIL PROTECTED] spamd]# more /service/spamd/run
#!/bin/sh exec /usr/local/bin/softlimit -a 120000000 \ /usr/bin/spamd -s stderr -D -L 2>&1 # ^^^^^^^^^
[EMAIL PROTECTED] spamd]# more /service/spamd/log/run
#!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s8000000 n80 \ /var/log/qmail/spamd
=-=-=-=-=-=-=-=
What it took for the debugging info to make it to my logfile is adding the -s stderr (to tell SA to log everything to stderr) and then redirecting stderr to stdout, so the .../log/run script can catch it.
Works like a charm for me...
Prost, Roger "Merch" Merchberger
-- Roger "Merch" Merchberger --- sysadmin, Iceberg Computers [EMAIL PROTECTED]
Hi! I am a .signature virus. Copy me into your .signature to join in!
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
