From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv does not start cygsshd at boot
Date: Wed, 22 Jan 2020 18:18:00 -0000 [thread overview]
Message-ID: <87muafs6bk.fsf@Otto.invalid> (raw)
In-Reply-To: <20200122160541.GA28483@ti129.telemetry-investments.com> (Andrew J. Schorr's message of "Wed, 22 Jan 2020 11:05:41 -0500")
Andrew J. Schorr writes:
>> Try to set the service to "delayed start" instead and see if that helps.
>
> Thanks for the suggestion; that seems to fix the issue. Is this a known
> problem due to some updates to Windows 10 and/or Cygwin? I have not had
> this problem in the past.
Win10 is better at starting fast (including parallelization of startup
across the available cores) and just the fact that TCP/IP is up seems
not enough for sshd to function correctly.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
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
next prev parent reply other threads:[~2020-01-22 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:02 Andrew J. Schorr
2020-01-21 20:37 ` Achim Gratz
2020-01-22 16:05 ` Andrew J. Schorr
2020-01-22 18:18 ` ASSI [this message]
2020-01-22 22:08 ` Brian Inglis
2020-01-22 22:23 ` Brian Inglis
2020-01-28 21:35 ` Andrey Repin
2020-01-28 22:21 ` Brian Inglis
2020-01-23 15:54 ` Andrew J. Schorr
2020-01-28 21:56 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-28 22:28 ` Brian Inglis
2020-01-29 6:39 ` Brian Inglis
2020-01-29 18:55 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-29 23:08 ` Brian Inglis
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=87muafs6bk.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).