On Tue, May 28, 2002 at 10:07:10PM -0500, David W. Tamkin wrote:
Reread the logfile excerpt in Marek's original post; it said it was executing
./tester and that it encountered an error while writing (not a failure to
write) to the script:
"Error while writing to" and "failure to write to" mean the same thing in my
book. And the fact that it said "executing ./tester" means nothing as far as
the the reason for the error. To test this, I created a procmailrc that pipes
to "./tester". This line appeared in the log regardless if the tester script
existed or not, or was executable or not, or if the path to the script was
relative or absolute. The only difference was the presence of "No such file or
directory" when the file didn't exist or when the path was relative. When I
gave it an absolute path this line went away. However since "No such file or
directory" doesn't appear in Marek's log, we can rule this out.
My point being simply that just because it says 'Executing "./tester"' doesn't
mean it's actually successfully finding and executing anything at all. Perhpas
that line should be more accuratly read as "Attempting to execute..." One must
read the next few lines to determine what happened.
I will however concede that the cause of his problem is in fact, as you said,
that his test script is not reading from STDIN, and he therefor needs to use i
in his recipe invocation to tell procmail to ignore the resulting write error.
--
Andre Edelstein - http://andrew.pure-chaos.com/resume.txt
Please do not reply directly to me, or Cc: me on a reply to a list message.
I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail