Philip Guenther wrote:
Michael J Wise <mjwise(_at_)kapu(_dot_)net> writes:
b) the nslookup command being invoked sends error messages to stdout;
Doesn't do that when I invoke sh and feed it the same command.
When procmail is run to process incoming message, is it running on the
same host?
Yes.
3) Therefore, if a message is getting from nslookup to the logfile, then
either
a) procmail is leaving open fds above 2 that point to the logfile
and nslookup sends its error message to that fd; or
b) nslookup sends it error message to the value of the LOGFILE
environment variable; or
c) statement (1) is incorrect -- procmail is opening STDOUT = fd 1
to the logfile -- and nslookup sends its error message to fd 1
d) statement (2) is incorrect and your shell is broken
So, which of (a), (b), (c), and (d) do you think is the most likely?
Quite frankly? e. I'm a little worried about the following code:
pipes.c: if(!(pidchild=sfork())) /* connect stdout to
stderr before exec */
What happens when you change the assignment to
NSLOOKUP=`nslookup ${REVERSED}.correct.domain.here 2>nslookup.err`
I don't know. I'll find out and get back to you.
Aloha mai Nai`a!
--
"Please have your Internet License http://kapu.net/~mjwise/
and Usenet Registration handy..."
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail