From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21394 invoked by alias); 25 Jun 2018 18:59:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 21384 invoked by uid 89); 25 Jun 2018 18:59:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.2 spammy=HX-HELO:sk:mail-ed, timely, 30000, Hx-languages-length:2118 X-HELO: mail-ed1-f51.google.com Received: from mail-ed1-f51.google.com (HELO mail-ed1-f51.google.com) (209.85.208.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Jun 2018 18:59:37 +0000 Received: by mail-ed1-f51.google.com with SMTP id a5-v6so6063377edt.5 for ; Mon, 25 Jun 2018 11:59:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=snXaq9n24pOwDPYxefZaYjmGn8E3NJs9hEBWt2t7xkY=; b=csKK4itXQIekmBUR3mdQEdyNSt/02AvYAmXwe1UqKUmdQsbuUP96soIDSagXWrMXTh SmUSorLmx22J6ixOqrF0gDlGPee8CPzdA1YrQy8UQZZJHnnqO4x2ngcbhUKPuJBk0bJN /ys5YD85NC1e90l/4XjRJJRMyLsUkWa5ytqryMPzY7Y1FmG8md6uuQlZOy/mVsXP+CK+ uX5trUnFwNAR8MSQsWek7xR2kQCKAiRWaTVV3N8nUzvRdiXEmAzwWvFhpp2uGDcY9o4x gIbf5WP/S3DdSsNhUPkkKzVX8AOiR6XCpMVdLEC+EBhFqoDyDGYAMty5vCC5S2IZLszo DbYg== MIME-Version: 1.0 Received: by 2002:a50:c385:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 11:59:35 -0700 (PDT) From: Hiya Z Date: Tue, 26 Jun 2018 08:16:00 -0000 Message-ID: Subject: Re: sshd issues on Windows 10 version 1803 To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-06/txt/msg00282.txt.bz2 >Btw., I can't reproduce this problem. Cygwin's sshd service always >starts for me at boottime as expected. >Did you check if the log file in /var/log contains any more info? I see nothing in /var/log/sshd.log. Windows event log shows following errors: -- 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. 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. -- 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? Will try removing %SystemRoot%\System32\OpenSSH from the PATH to see if it improves things. Thanks. -- 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