Joe--
Indeed it does...there appears to have been a change made to
Pending.py sometime after 0.82. These lines were added, but I'm not
too sure what their purpose is:
# re-open stdin on the tty
sys.stdin.close()
sys.stdin = open('/dev/tty', 'r')
This seems to affect the way tmda-pending operates when reading its
input from STDIN inside a script. In an interactive shell,
piping data to tmda-pending works fine...inside a script, it seems to
fail with a "No such device or address: /dev/tty" error.
Perhaps someone can shed some light on the reason for these two lines,
especially since there's no guarantee tmda-pending will always be
reading in from /dev/tty...
In the meantime, commenting out these two lines in Pending.py seems to
fix tmda-pending, which might be the cause of your broken pipe. I'll
keep digging...
--Brian
On Fri, Jun 11, 2004 at 09:02:05PM -0700, Joe wrote:
> There was not too much info searching the net. I'm running tmda 1.0.3 and trying to
> get the tmda-ezplm utility running. This seems to be a TMDA error??
>
> Here's the error:
> failure delivering message to command
> "/usr/local/var/qmail/bin/processPending.pl" ([Errno 32] Broken pipe)
>
> Here's the delivery line in the incoming filter file
>
> to [EMAIL PROTECTED] deliver=|/usr/local/var/qmail/bin/processPending.pl
>
> Here's the executable
> [EMAIL PROTECTED] pwd
> /usr/local/var/qmail/bin
> [EMAIL PROTECTED] ll processPending.pl
> -rwxr-xr-x 1 root vmail 5143 Jun 7 18:44 processPending.pl
>
>
> Any suggestions.
>
> --
> Joe S.
> ------------
> praxis makes perfect.
> - anon
>
> ps. Brian, I owe you some mods, I haven't forgotten but got distracted with other
> things. I went back to this work with release 1.0.3 and actually read the install
> instructions.
>
> _____________________________________________
> tmda-users mailing list ([EMAIL PROTECTED])
> http://tmda.net/lists/listinfo/tmda-users
>
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
