Re: Strange SSH behaviour after updating to Cygwin 2.0.1

2015-05-15 Thread Achim Gratz
Takashi Yano writes: > Try: ssh -t user@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

Re: Strange SSH behaviour after updating to Cygwin 2.0.1

2015-05-15 Thread Takashi Yano
On Thu, 14 May 2015 09:23:34 +0200 Achim Gratz wrote: > 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. Try:

Re: Strange SSH behaviour after updating to Cygwin 2.0.1

2015-05-14 Thread Achim Gratz
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

Re: Strange SSH behaviour after updating to Cygwin 2.0.1

2015-05-07 Thread Stephen John Smoogen
On 7 May 2015 at 01:15, Achim Gratz wrote: > I'm seeing strange behaviour from SSH after updating both sides to Cygwin > 2.0.1. The symptoms, logging in via a 32bit client into a 32bit or 64bit > sshd instance on the server: > I have replicated this using Cygwin ssh to a Linux server. However I

Strange SSH behaviour after updating to Cygwin 2.0.1

2015-05-07 Thread Achim Gratz
I'm seeing strange behaviour from SSH after updating both sides to Cygwin 2.0.1. The symptoms, logging in via a 32bit client into a 32bit or 64bit sshd instance on the server: (1005)~ > ssh gratz@server -- tcsh -l Warning: no access to tty (Bad file descriptor). Thus no job control in this shell.