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=kEhvD
	yMwYAPtIvBg+uAqHAnllzXqglASg1BUHx9pZO8vHjimFoX9Hki1GShy709meqpiM
	ZQV2fo6Q35kd4M6qViTiwfQAQa4ncjGAY0frEW432qHLjN6lQZl3d/plGy6XaNkc
	FmfkIBFiqej17wOhrJ1rmku58p1WXxLYxH5k/I=
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=R1U8AMICQYE
	PlfRPQOjbQE2F8ws=; b=ZvQQ+scgaCOci9feittRu3nG3+t82R8JZ3wfo5ErQCJ
	kpyUvuNcToi6miG5JqJnIEkga9PhYpABs0HJ9P+pMF+fq023xP5IEQW/yAP9eMt8
	ubHjV4Pnp9ONniNytLTMR4kolQm6Gqy3deCsqTfrMerpDZNhktHAXggf6o8PYmO4
	=
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-10.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-08.arcor-online.net 3lp73T04NZzY59r
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>	<87siazei6h DOT fsf AT Rainer DOT invalid>	<20150515184100 DOT 2c2590c9b1b49b3d8617f334 AT nifty DOT ne DOT jp>
Date: Fri, 15 May 2015 13:35:59 +0200
In-Reply-To: <20150515184100.2c2590c9b1b49b3d8617f334@nifty.ne.jp> (Takashi	Yano's message of "Fri, 15 May 2015 18:41:00 +0900")
Message-ID: <87617ukr8g.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

Takashi Yano writes:
> Try: ssh -t user AT hostname -- tcsh -l
>
> With option -t, it should work as you expected.

Yes it does, thank you very much!  One more problem crossed off the
list.

Meanwhile after another update I actually had that happen when
connecting from the 64bit client also, btw.  So the original question of
why the behaviour was different between a 32bit and 64bit client was
probably due to the phases of the moon or something like that anyway.


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

Factory and User Sound Singles for Waldorf Blofeld:
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