Bryan Hoover wrote:
BH> Craig R Hughes wrote:
BH>
BH> > No, you can't just redirect STDERR, if you're using the -d flag, spamd
BH> > will
BH> > detach from the launching tty, and disconnect from that tty's STDERR,
BH> > STDIN and
BH> > STDOUT. If you specify -D and -d together, then spamd should
BH> > definitely install
BH> > a $SIG{__WARN__} handler which redirects to its logmsg() function.
BH> > Actually, it
BH> > should do this if you use -d whether or not you use -D.
BH> >
BH>
BH> Just seems to me that if a program's logging, e.g., SA, is set to go to
BH> the screen, then, unless it offers some sort of config. or switch,
BH> there's no need for another program to alter its behavior - though, as
BH> you mentioned, procmail does it.
It does offer some config. You can specify the facility to log to, and then
configure syslog to do anything you want with the logged info. SA when it was
first built was not expecting to be used in a detached-daemon environment where
its stderr was disconnected -- so when we disconnect it in spamd, it's only
polite to let SA continue to communicate with the outside world (unless the user
specifically tells it not to by modifying syslog to drop the messages).
C
_______________________________________________________________
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
