Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: From: "LeGardeur Michel (external)" To: "'cygwin AT cygwin DOT com'" Subject: CYGWIN on W2K Telnet Server. Solution "to couldn't make stderr di stinct from stdout" Date: Fri, 20 Jul 2001 12:02:26 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Hallo, for information the instruction "ECHO blablabla >NUL" before starting any CYGWIN tool within a Telnet session on the W2K Telnet Server is sufficient to get rid of this error. M. Le Gardeur * To: cygwin * Subject: Re: Error: couldn't make stderr distinct from stdout * From: Corinna Vinschen * Date: Tue, 19 Dec 2000 13:02:57 +0100 * References: <90F3E2EF5221D411AAF5006008A8451601AAE980 AT server DOT pixsci DOT com > On Tuesday 19 December 2000 01:55, Don Bowman wrote: > installer. When invoked via telnet, bash quits with the > same "couldn't make stderr distinct from stdout" message. > My other windows2000 box with the same setup but cygwin1.dll > of ts=1998/12/3 23:39 works well with the telnet server. Fine. There's has been made a change in Cygwin which tries the following on init: - Get the stdin, stdout and stderr handles from the system. - If stdout handle == stderr handle then try to separate them into two _different_ handles. This is important to allow separate redirection of stdout and stderr. - If this failes (The Win32 system call `DuplicateHandle') the above system error output is forced. The problem is that the W2K telnet server doesn't allow duplicating the handle for some strange reason which only Microsoft knows of. Try using telnet from the inetutils package. Corinna -- 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/