public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hiya Z <hiya.zyx@gmail.com>
To: cygwin@cygwin.com
Subject: Re: sshd issues on Windows 10 version 1803
Date: Tue, 26 Jun 2018 08:16:00 -0000	[thread overview]
Message-ID: <CAFcD33NUQh6OZmfanT3y3QMeaOuciBP1s2hQd+8KrT=+bpWOvw@mail.gmail.com> (raw)

>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

             reply	other threads:[~2018-06-25 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  8:16 Hiya Z [this message]
2018-06-26 16:03 ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2018-06-29  6:20 Hiya Z
2018-06-22 20:42 Hiya Z
2018-06-25 13:12 ` Corinna Vinschen
2018-06-25 18:59   ` Corinna Vinschen
2018-06-25 20:20     ` Corinna Vinschen

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='CAFcD33NUQh6OZmfanT3y3QMeaOuciBP1s2hQd+8KrT=+bpWOvw@mail.gmail.com' \
    --to=hiya.zyx@gmail.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).