execline's pipeline (and forbacktickx) with closed stdin

From: Guillermo <gdiazhartusch_at_gmail.com>
Date: Fri, 8 May 2015 20:13:36 -0300


It appears that if the pipeline program is run with a closed stdin,
like when being part of an execline script that does a previous
"fdclose 0", the program it execs into will get a "bad file
descriptor" error. For example, if I do something like "pipeline {
some-program } grep $regex" I get a "grep: (standard input): Bad file
descriptor". And if I do something like "forbacktickx file { ls
$directory } some-program", I get a "forstdin: fatal: unable to
skagetlnsep: Bad file descriptor". The documentation says forbacktickx
is a wrapper around pipeline and the forstdin program, so I guess this
would be the same pipeline thing.

Are we not supposed to use pipeline or forbacktickx with a closed
stdin, or is this something that needs fixing?

Received on Fri May 08 2015 - 23:13:36 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:38:49 UTC