From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv does not start cygsshd at boot
Date: Tue, 28 Jan 2020 22:21:00 -0000 [thread overview]
Message-ID: <b40abb5b-3f4b-fb6e-8984-4185b2ea1685@SystematicSw.ab.ca> (raw)
In-Reply-To: <916514140.20200129002639@yandex.ru>
On 2020-01-28 14:26, Andrey Repin wrote:
>> $ cygrunsrv -VQ cygsshd
>> Service : cygsshd
>> Display name : CYGWIN sshd
>> Current State : Running
>> Controls Accepted : Stop, Preshutdown
>> Command : /usr/sbin/sshd -D
>> stdin path : /dev/null
>> stdout path : /var/log/cygsshd.log
>> stderr path : /var/log/cygsshd.log
>> Process Type : Own Process
>> Startup : Manual
>> Dependencies : dnscache, cygserver, syslog-ng
>
> I strongly suggest adding "tcpip" here.
No - causes problems as tcpip is a kernel driver which is early and low level
BOOT_START - other BOOT_START and SYSTEM_START kernel drivers and services
depend on tcpip, and later AUTO_START services like dhcp and dnscache depend on
those - once those are available, we have a gateway, resolver, and the other
network services which we need available to use the network, which is why we
need to start Cygwin network services as Delayed auto start
(HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/cygsshd Start=2
DelayedAutostart=1) and Preshutdown (cygrunsrv -O, --preshutdown
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/cygsshd/Parameters
Preshutdown=1).
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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-28 22:21 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
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 [this message]
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=b40abb5b-3f4b-fb6e-8984-4185b2ea1685@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).