On 21:59, Larry Hall (Cygwin) wrote:
> On 8/2/2011 7:32 AM, Alexey Luchko wrote:
>>>> Cygwin Configuration Diagnostics atteched.
>> >
>> > Maybe crank up the debugging flags to maximum? I assume sshd is still
>> > stopped from your last run of sshd -d. If that doesn't sound right to
>> > you, you may want to investigate why it's not running now.
>>
>> sshd was stopped while that run because it did not login anyway. and still
>> don't.
>
> sshd will run even if you're having problems connecting to it. I'm just
> making sure that you are testing with a running server. If not, then
> you want to make sure the server is running first.

Yes, it's running.  Now it is set up as a service with automatic start up.


>> The messages
>> >>> debug1: Allocating pty.
>> >>> debug1: session_pty_req: session 0 alloc /dev/tty2
>> >>> chown(/dev/tty2, 11135, 10513) failed: Bad file descriptor
>> >>> debug1: do_cleanup
>> >>> debug1: session_pty_cleanup: session 0 release /dev/tty2
>> were got running sshd -d in console.
>
> I was suggesting that you run sshd with all the debug flags
> (i.e. "-d -d -d") to see if you'd get more useful information
> about your problem.

I've run it with -ddd.  There is nothing new around the tty allocation.
The full output is attached.  May be it can give some clue.


Thank you :)

--
Alex