Yes -- SA itself does not communicate with syslog -- which is probably the Right
Thing. spamd is the thing which is detaching itself from the terminal and
therefore losing SA debug messages; it should properly not drop those messages,
but instead redirect them to wherever the output might usefully go -- in the
case of spamd, that's syslog, through the logmsg() function defined in spamd
C
Bryan Hoover wrote:
BH> Craig R Hughes wrote:
BH>
BH> > $SIG{__WARN__} = sub { logmsg($_[0]); }
BH> >
BH>
BH> I assume you would add the above to spamd? Would it make any difference
BH> if it were added to SA instead?
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
