DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=db5
	rkwoBJyWclatYUritjD99dsBVZ4ycfK3THPjzGX7ItLx3eq3lK/8UgVXjMDVK2PJ
	Zb+g4etNGOCotloz1sv6tApITtk2+Nc0IqTovWue9HpnDXoa3ZqAvfVpqqXZvlnq
	bJVKU9rwEtWa/3FsZg5XNEaGDiNpv/muiWkicplg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@NexGo.DE>
Subject: Configure second sshd on the same machine
Date: Thu, 14 Aug 2014 16:27:11 +0000 (UTC)
Lines: 16
Message-ID: <loom.20140814T182028-687@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

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.


Regards,
Achim.


--
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