On Wed, 24 Sep 1997, era eriksson wrote:
On Wed, 24 Sep 1997 01:03:55 -0700 (MST), Wotan <wotan(_at_)netcom(_dot_)com>
wrote:
>> practice, of course, you're doomed as soon as the size exceeds LINEBUF
>> but that will hit you slightly later, when you want to say $VAR1.
> This is what brought the question to mind. Some of my test messages
> generated output well above default LINEBUFF (what I use) with no problem.
> (8-9K characters stored).
You should see LINEBUF exceeded in the log, but like I said, only when
you actually try to +use+ the variable (is this not happening?),
Not happening.
Here is what is happening in test.a:
procmail: Assigning "BODY="
procmail: Executing " sed -e 's/^/>/'"
procmail: Executing " ($FORMAIL -r -I"Precedence: junk" \
-i"Subject: qazwsx"; \
echo "twit fodder$N$N$BODY")|$SENDMAIL -oi -t"
test.b is an almost identical filter which writes output to a file using
echo. And it gives me similar output in a verbose log.
The output has been pretty much what I wanted, minus formatting errors on
my part.
and
start getting core dumps when you exceed LINEBUF by too much. (OK,
"should" has the wrong connotations here. That is what will happen,
anyway.)
Apparently not yet. :) But this is Netcom I'm testing on...
--
Bumper sticker:
"All the parts falling off this car are of the very finest British
manufacture"