Piping input from subprocess loses track of temp file

Piping input from subprocess loses track of temp file

[David Karr]

I believe the relevant part of my cygwin version info is "3.0.7(0.338/5/3)"
(from uname -a output).

I'm working on a script where one step executes a process where the input
is taking from a subprocess, like this:

    someprocess <(cat $outfile | sed -e "s/${property}[
]*=.*$/${property}=${newValue}/")  ...

When I run this, I see:

    error: error reading /dev/fd/62: The system cannot find the path
specified.

I tried running the exact same command line and script in Ubuntu 16.04, and
it works fine.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Piping input from subprocess loses track of temp file

[Ken Brown]

On 7/19/2019 2:27 PM, David Karr wrote:
> I believe the relevant part of my cygwin version info is "3.0.7(0.338/5/3)"
> (from uname -a output).
> 
> I'm working on a script where one step executes a process where the input
> is taking from a subprocess, like this:
> 
>      someprocess <(cat $outfile | sed -e "s/${property}[
> ]*=.*$/${property}=${newValue}/")  ...
> 
> When I run this, I see:
> 
>      error: error reading /dev/fd/62: The system cannot find the path
> specified.

I just ran into a possibly similar problem:

   https://cygwin.com/ml/cygwin/2019-07/msg00230.html,

although in my case I could only reproduce it under X11.  Are you running under 
X11 when you see your problem?  And can you boil it down to a simple test case 
or, barring that, send your script and reproduction instructions?

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Piping input from subprocess loses track of temp file

[David Karr]

On Sat, Jul 27, 2019 at 8:40 AM Ken Brown wrote:

> On 7/19/2019 2:27 PM, David Karr wrote:
> > I believe the relevant part of my cygwin version info is
> "3.0.7(0.338/5/3)"
> > (from uname -a output).
> >
> > I'm working on a script where one step executes a process where the input
> > is taking from a subprocess, like this:
> >
> >      someprocess <(cat $outfile | sed -e "s/${property}[
> > ]*=.*$/${property}=${newValue}/")  ...
> >
> > When I run this, I see:
> >
> >      error: error reading /dev/fd/62: The system cannot find the path
> > specified.
>
> I just ran into a possibly similar problem:
>
>    https://cygwin.com/ml/cygwin/2019-07/msg00230.html,
>
> although in my case I could only reproduce it under X11.  Are you running
> under
> X11 when you see your problem?  And can you boil it down to a simple test
> case
> or, barring that, send your script and reproduction instructions?
>
> Ken
>

Well, what's curious is that I thought I was running under X11, but now I
see that I'm not running the server.

What's even stranger is that this isn't happening anymore, or at least it's
not happening today.  I guess that means there's some sort of race
condition in play here, which is really annoying.

I'm even running the exact same command line that I was running before
(that is, passing the same parameters to the script that calls the process
that had this problem).

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple