Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <02c301c21b6f$a62249e0$6132bc3e@BABEL> From: "Conrad Scott" To: References: <007001c21b66$a39dff10$651c440a@BRAMSCHE> <13211610364.20020624123852@syntrex.com> Subject: Re: pipe connection problem in recent cvs release Date: Mon, 24 Jun 2002 12:09:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Pavel Tsekov" 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 ? 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. // Conrad -- 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/