Stan Ryckman <stanr(_at_)sunspot(_dot_)tiac(_dot_)net> writes:
Can't one avoid writing *any* of the header or body? Something like:
:0c:log.gz.lock # now I think you need to name the lock
{
JUNK="`/usr/local/gnu/bin/date +'%e/%m/%y, %k:%M'`"
JUNK="`echo $VAR8 lines, $JUNK, $VAR9, $VAR10 | gzip >> log.gz`"
}
or am I missing something? (Quite possible :)
procmail provides the entire message on stdin of programs started via
backquotes, so no, this doesn't help. The only way to have procmail
write nothing is to cheat and execute the program from a *condition*
which has a "var ??" special on it that refers to an empty variable.
HOWEVER, you then lose the locking, so I would *not* do this. You
aren't saving yourself anything.
Anyway, procmail stops writing as soon as it gets a write error, so I
probably wouldn't bother even putting the 'h' flag on the recipe, as it
will probably only save the copying of something like
PIPE_BUF-sizeof(header) bytes inside the kernel, and that's nothing.
Sorry David.
If someone really cares about this, they should appeal to Stephen to add
a new flag, say, 'I', that causes procmail to not write anything at all.
Philip Guenther