public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Strange SSH behaviour after updating to Cygwin 2.0.1
Date: Thu, 14 May 2015 07:44:00 -0000	[thread overview]
Message-ID: <87siazei6h.fsf@Rainer.invalid> (raw)
In-Reply-To: <CANnLRdhFETB0boh4MXF--+v0=aC99=fKRTzX9gcVBN2ts3RTNA@mail.gmail.com>	(Stephen John Smoogen's message of "Thu, 7 May 2015 15:19:47 -0600")

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

  reply	other threads:[~2015-05-14  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  8:12 Achim Gratz
2015-05-08  6:48 ` Stephen John Smoogen
2015-05-14  7:44   ` Achim Gratz [this message]
2015-05-15 10:29     ` Takashi Yano
2015-05-15 11:58       ` Achim Gratz

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=87siazei6h.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).