Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Dan Plimak <danp AT systematik DOT co DOT nz>
Date: Mon, 12 Feb 2001 17:43:35 +1300
To: cygwin AT cygwin DOT com
Subject: DuplicateHandle() failing under MS Telnet Server
Message-ID: <20010212174335.A5323@systematik.co.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i

Hi,

When trying to set up /bin/bash.exe as my default shell in MS Telnet Server
under Windows 2000, I'd encountered the following message: 

"... couldn't make stderr distinct from stdout"

Investigation revealed that you guys are bailing out on a DuplicateHandle()
failure when you notice that stdout is the same as stderr and attempt to
give stderr a different handle than stdout.

This patently won't work under MS Telnet server as from what I can tell (I
_may_ be wrong), they are using a kludge where they make a handle from a
socket fd, which is distinct from a regular Windows resource/file handle and
hence things that may be done with a handle fail.

I may be willing to look for a workaround for this problem--but first I need
to make sure that one does not already exist.

Again, I may be wrong (I had all of 5 minutes to think about this :-)), so
your response will give me a hint whether to proceed investigating this or
to drop it and get some more coffee.

  -- danp


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