This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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.
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.
-- Alex
Attachment:
sshd-ddd.log
Description: Text document
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |