DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Yw6aUncVPr93Gh74u09hz+DPcC7zJEJykJqO3yNwHznKHMSb/Xuvf
	3N1VkxCArXTlNxWv3NZ3UvMfPVixAlzFBIcBdMoXF2vqLpsYg8UqiJCC8l90bH5C
	hWb8iaxBchUkUmt5ZRXYAri93cMvJn9qkdOYGOUZTs+JGWE3h9IqS0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 26 Jun 2018 10:16:30 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd issues on Windows 10 version 1803
Message-ID: <20180626081630.GP28757@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAFcD33NUQh6OZmfanT3y3QMeaOuciBP1s2hQd+8KrT=+bpWOvw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="5VuzLDXibKSJvVYD"
Content-Disposition: inline
In-Reply-To: <CAFcD33NUQh6OZmfanT3y3QMeaOuciBP1s2hQd+8KrT=+bpWOvw@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

--5VuzLDXibKSJvVYD
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun 25 11:59, Hiya Z wrote:
> >Btw., I can't reproduce this problem.  Cygwin's sshd service always
> >starts for me at boottime as expected.
>=20
> >Did you check if the log file in /var/log contains any more info?
>=20
> I see nothing in /var/log/sshd.log. Windows event log shows following
> errors:
>=20
> --
> Error      6/20/2018 3:45:19 PM   Service Control Manager
> 7009      None
> A timeout was reached (30000 milliseconds) while waiting for the sshd
> service to connect.
>=20
> Error      6/20/2018 3:45:19 PM   Service Control Manager
> 7000      None
> The sshd service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> --
>=20
> Another odd behavior that I observe is that after a reboot, starting a
> Cygwin64 terminal (first time) takes a long time. Launching subsequent
> mintty terminals is quick as it should be. Could it be that sshd startup
> upon reboot is hitting the same delay as the 1st mintty?
>=20
> Will try removing %SystemRoot%\System32\OpenSSH from the PATH to see if it
> improves things.

I didn't remove it and it works fine for me.  The OpenSSH path is
pretty late in $PATH and should not affect starting with cygrunsrv
because it prepends /bin to $PATH before running the service...
unless you used the -e option to cygrunsrv to infuse your own $PATH.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--5VuzLDXibKSJvVYD
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlsx9l4ACgkQ9TYGna5E
T6At2Q//bwG8B6k8W1KZqUd0WS8KnxbPXWXblTosuEUxxZVaRcYOZaEPaOfLUQZt
8QYbXzHzGwC3jfNNPDTZejizZqjNLtq3zVdIboVBO9ZEjPOTy7uADmjUhyle5X1M
1aQEhEGubP9rXetFZ6p+kouw9VbY57pr+2wQ4t+HE5lkTMKaZnuXeoMph0eZM6Ua
0uAWqHpZ9jblldxyYckqxj7dR482EmeORFzsUZQsCoXW4T4Ek82eUSgCRouRx0Kg
VaBaDQRlcb30ICZwZEro4gmXmsOc5fizBELYDNWDYP0zjoWvufImr1+Z7TQ9/17l
ItMjRRDHr2Vw0sUi1JxPX0wciX6xqiMT4iMitRBo2pEOIlFElZz6P5pR5jA0+EcT
v/3ulQ6BzRcLyg+NLAX/CUQwxZIXArr+HBZCfjXv2fG8LR3vWaQJolXYhFF2csXt
qFsR/1/CBe79cxYgvBZrJgfo15tYzlodJi53PcVowKbkmGnEPoCYiGCUXPd7UVeW
o3ju03rq0VuY7OXQNGv5HyASAC3nYeyvo5aNdZdVbjkdqKOgVwoTf2Xy4qhW8f4G
f1dMRLZffrvwcXElVwn5TqCqaF7MdIo6FxYyn33rSiSUjFL3H/M3cM2Z/CT630SO
T/oo2fDmMfZKg0XsC4qRI+RgzhSs/cFtFzpIIsls58nIVkjqoEk=
=h0sF
-----END PGP SIGNATURE-----

--5VuzLDXibKSJvVYD--