This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: ssh/sshd and /dev/tty
- To: Derek Young <derek at biddersedge dot com>
- Subject: Re: ssh/sshd and /dev/tty
- From: James Dumser <dumser at rtis dot ray dot com>
- Date: Tue, 06 Jan 1998 07:46:13 -0600
- CC: "Patrick J. Fay" <pfay at acl dot lanl dot gov>, chuck at ethereal dot ru, gnu-win32 at cygnus dot com
- Organization: Raytheon Systems Company
- References: <Pine.SGI.3.96.980105144003.28250F-100000@kent.acl.lanl.gov>
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".