From: dumser@rtis.ray.com (James Dumser)
Subject: Re: ssh/sshd and /dev/tty
6 Jan 1998 05:58:11 -0800
Message-ID: <34B235A5.A2513A8D.cygnus.gnu-win32@rtis.ray.com>
References: <Pine.SGI.3.96.980105144003.28250F-100000@kent.acl.lanl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Derek Young <derek@biddersedge.com>
Cc: "Patrick J. Fay" <pfay@acl.lanl.gov>, chuck@ethereal.ru,
        gnu-win32@cygnus.com

On Mon, 5 Jan 1998 14:58:48 -0700 (MST), Patrick J. Fay
  <pfay@acl.lanl.gov> wrote:
>Let's try this all on your PC.
>Try:
>1st window
>./sshd -d
>2nd window
>env|grep HOST
>(for bash)
>export CYGWIN_TITLE=1
>export CYGWIN_TTY=1
>export DISPLAY='yourhost:0.0'
>export TERM=linux #this may not be necessary
>./ssh -v yourhost

I'm not using ssh/sshd, but from the conversation that's been going on,
I believe CYGWIN_TTY=1 is the important one. Sergey's DLL does not
support pseudo terminals without it (or if it's set to 0).

It's important to have CYGWIN_TTY set before cygwin.dll loads. Also, if
you eventually want to run sshd as a service, remember that the user it
will run as also needs to have CYGWIN_TTY set. I'd recommend putting
CYGWIN_TTY=1 in your global environment and then rebooting.

-- 
James Dumser    972.462.5335    dumser@rtis.ray.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
