Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Process started by Perl "open3" not taking input from write fd
From: dkarr AT tcsi DOT com (David M. Karr)
Date: 04 Jan 2001 12:59:36 -0800
Message-ID: <uypui3ghjb.fsf@tcsi.com>
Lines: 28
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I'm having some trouble with some Perl ClearCase triggers which try to
internally use "open3" to start a "cleartool" process to communicate
with whenever it needs a subcommand executed and data returned.

I have a small test case that just tries to execute a single cleartool
subcommand, then exit.

When I execute it on Unix, it executes the subcommand, makes the
output available for reading, and exits.  When I execute it on NT, it
seems to be blocked on the "read" for the output from "cleartool".  I
found that when I execute the script at the console, when it gets to
the point where it blocks, I can type at the console, and the line
that I type gets sent to "cleartool", and I can then read the output
from that.

It seems as if the read file descriptor is not connected to the
process, but to my console.

My Perl versions on each platform are somewhat different.  On NT, I'm
using the latest Cygwin-built version, which I believe is 5.6.1.  On
Unix, I'm executing 5.005_03.

Can someone give me some idea of what could be going wrong here?

-- 
===================================================================
David M. Karr     ; w:(425)487-8312     ; TCSI & Best Consulting
dkarr AT tcsi DOT com    ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple