public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: Cygwin List <cygwin@cygwin.com>
Subject: Re: Configure second sshd on the same machine
Date: Thu, 14 Aug 2014 16:43:00 -0000	[thread overview]
Message-ID: <53ECE70C.4090908@cygwin.com> (raw)
In-Reply-To: <loom.20140814T182028-687@post.gmane.org>

On 08/14/2014 12:27 PM, Achim Gratz wrote:
> For building 32bit packages I've set up an additional installation on the
> same server.  To use it from the outside (like) I'm trying to configure a
> second sshd on the server.  So I've installed a cygserver23 and sshd32
> service with otherwise identical setup to their 64bit brethren and bumped
> the port sshd listens on to 3222.  The services are starting without any
> hitch, the port is listening and I can log in via public key or password as
> I chose.  The only problem: after sending the command to the new ssh
> session, the server closes the connection, claiming that the client had
> disconnected.  the client gets an exit code 5.  Does that ring a bell with
> anyone?   I can't find any error in the config.  Even when I shut down the
> 64bit installation completely and let sshd run on the standard port I'm
> getting the same result.

The only time I've seen that is when I start the server in debug mode.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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:[~2014-08-14 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 16:27 Achim Gratz
2014-08-14 16:43 ` Larry Hall (Cygwin) [this message]
2014-08-14 16:55   ` Achim Gratz
2014-08-14 18:50     ` Andrey Repin
2014-08-14 19:18       ` Achim Gratz
2014-08-15  6:32 ` 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=53ECE70C.4090908@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).