public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: DuplicateHandle() failing under MS Telnet Server
Date: Sat, 10 Feb 2001 20:58:00 -0000	[thread overview]
Message-ID: <20010210235834.A7140@redhat.com> (raw)
In-Reply-To: <20010212174335.A5323@systematik.co.nz>

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

  reply	other threads:[~2001-02-10 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 20:51 Dan Plimak
2001-02-10 20:58 ` Christopher Faylor [this message]
2001-02-12  4:44 ` Warren Young
2001-02-13  0:33   ` Dan Plimak
2001-02-10 21:05 Dan Plimak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010210235834.A7140@redhat.com \
    --to=cgf@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).