From: David W. Tamkin
Sent: Monday, 19 February 2001 6:15 PM
I gather you meant that if you don't specifically turn on the
abstracting, the logabstracts don't show up . . . .
If you don't define a logfile, stderr is probably going
into the bit bucket, but if stderr is going somewhere visible you
don't need to turn abstracts on to see LOG= assignments.
Okay, I didn't realize that your last clause was how it worked.
I'd somehow thought the LOG= assignments were not showing up
if I didn't set $LOGABSTRACT. (It wasn't an issue with
my logfile's being set; it was.)
I see that I can confirm the behavior in 3.11pre7.
Here is from my test-harness rc:
LOG="\$LOGABSTRACT is set to \"$LOGABSTRACT\" $NL"
LOGABSTRACT=no
LOG="\$LOGABSTRACT has been set to \"$LOGABSTRACT\" $NL"
Here is the relevant output:
$LOGABSTRACT is set to "all"
$LOGABSTRACT has been set to "no"
Thanks, David. And Don Hammond for running extensive
tests. And thanks also to Philip for clarifying
the native state of procmail vis-à-vis $LOGABSTRACT.
--
Dallman Ross <dman(_at_)nomotek(_dot_)com>
U.S. Voicemail/FAX: +1 (415) 276-2873
Residence Telephone: +49 (0) 6122 / 98 04 46
Cellular Telephone: +49 (0) 177 / 515 34 69
Fight Spam! Join CAUCE! == http://www.cauce.org/ or
http://www.euro.cauce.org/
N.B.: For no auto-reply, use <mailto:dman+noacks(_at_)nomotek(_dot_)com>
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail