X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=jFTis
	KzDFFfCUR48ceNCzFI8OhnAVAUVnMX/W5bXvxvtu+/3KIhEdWXGQ/aru3uj8Yj6x
	K00wG7emMpi+vMBYUKso4Y2dSRPX9Iy0wgv6McbWJfu+uzRB/5bJiLwPhb8MDIRp
	QhFG3or0I8o20gx+W9VV7cpmAajquQGiRXVdjE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=0NxlEZX0YI2
	qvvNlI4j75AKZ46g=; b=xmb3JIg8+RQAYxJqpxKJG59QLUoXgMZUCuKJhGrYxjx
	0kf47MgvaGy5xThHsXcnmJfNY6p8CToOuTXAmGv4+2mhCKd1zEtCQ8u9oza4aZaE
	W0h7+dpIY/ccKPWQSGt3i4uf+IsvaUir9Pa14uDxzC2l8tm9CPdBN5u3JYghRl8I
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-in-11.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-04.arcor-online.net 3lnPVb0nNPz5FMD
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Strange SSH behaviour after updating to Cygwin 2.0.1
References: <loom DOT 20150507T085653-79 AT post DOT gmane DOT org>	<CANnLRdhFETB0boh4MXF--+v0=aC99=fKRTzX9gcVBN2ts3RTNA AT mail DOT gmail DOT com>
Date: Thu, 14 May 2015 09:23:34 +0200
In-Reply-To: <CANnLRdhFETB0boh4MXF--+v0=aC99=fKRTzX9gcVBN2ts3RTNA@mail.gmail.com>	(Stephen John Smoogen's message of "Thu, 7 May 2015 15:19:47 -0600")
Message-ID: <87siazei6h.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Stephen John Smoogen writes:
> I have replicated this using Cygwin ssh to a Linux server. However I
> also replicated it using Linux -> Linux

That I already knew, and it's indeed fixed by making tcsh your default
shell over on Cygwin.  I can't do that in the case I mentioned since I
still haven't been able to convince our AD administrators to fill the
respective fields.

> So it might be a 'works as it is supposed to now' even if it is not
> the same behaviour as before. Doing a bunch of google hunting.. pretty
> much all the places it comes up with are "set your shell to tcsh by
> default so the tty is setup by login" or "use bash then go into tcsh".

The interesting part is why it seems to depend on the client while
accessing the same server, all on the same version of Cygwin (login
isn't involved anyway).  Cygwin clearly has the /dev/tty file present,
but for some reason it's not accessible in any way when that happens.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple