Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 10 Feb 2001 23:58:34 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: DuplicateHandle() failing under MS Telnet Server Message-ID: <20010210235834.A7140@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010212174335.A5323@systematik.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010212174335.A5323@systematik.co.nz>; from danp@systematik.co.nz on Mon, Feb 12, 2001 at 05:43:35PM +1300 On Mon, Feb 12, 2001 at 05:43:35PM +1300, Dan Plimak wrote: >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. Why not use the cygwin telnetd? Then you won't have these problems. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple