Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "cygwin" <cygwin AT cygwin DOT com>
Subject: RE: pipe connection problem in recent cvs release
Date: Mon, 24 Jun 2002 14:24:17 +0200
Message-ID: <008b01c21b7a$0f2ef190$651c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <02c301c21b6f$a62249e0$6132bc3e@BABEL>

> "Pavel Tsekov" <ptsekov AT syntrex DOT com> wrote:
> > RH> The strace log is appended. The only unusal behavior I can see,
> is a pipe
> > RH> opening error".
> >
> > RH> 368   43330 [main] echo 2408 transport_layer_pipes::connect:
> Error opening the
> > RH> pipe (2)
> >
> > It looks like you're using cygserver - am I right ?
>
I haven't started cygserver.

> In the current cygwin setup, you'll get this strace line if you're
> *not* using cygserver, i.e. this is what the code spits out shortly
> after startup when it tries to connect to cygserver and discovers that
> there isn't one running. This is the message for NT; for win 95 et al,
> there's a similar message about a socket connection, something like
> "client connect failure". Now, if you *were* running cygserver and you
> got this message, that's a problem :-)
>
> BTW, the message refers to NT named pipes, not cygwin pipes.
>
Thanks for this hints.
I've looked again in the strace file , but found only one point for further
analysing and that is, that the echo command does not got any input:

cvs build
     build_argv: argv[0] = 'echo'
     build_argv: argc 1
     normalize_posix_path: src /dev/conin

cygwin 1-3.10
     build_argv: argv[0] = 'echo'
     build_argv: argv[1] = 'habacker'
     build_argv: argc 2

The next check was the influence of the shell, so I tried to avoid a subshell

$exec echo `basename $PWD`
habacker

Okay, the result is printed as expected, so basename seems to work, but after
printing the line the bash window was closed immediatly. The same behavior with
cygwin 1.3.10

Then I tried to use another application to see, if the problem is in basename:

echo `ls $PWD`
CVS Desktop Mail bzip2.strace calendar.html ....

it works.

Trying

$ exec echo `ls $PWD`
CVS Desktop Mail bzip2.strace calendar.html ....

the result is okay, but bash was immediatly closed.

Okay, another try:

habacker AT BRAMSCHE ~
$ sh -c "exec echo `ls $PWD`"
CVS

habacker AT BRAMSCHE ~
$ bash -c "exec echo `ls $PWD`"
CVS

.. oh, there should be more results , but at least it does not let sh/bash
crashing.

No I'm completly confused. Does anyone an idea, where to look now ?

Ralf














--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/