public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygrunsrv does not start cygsshd at boot
Date: Wed, 29 Jan 2020 06:39:00 -0000	[thread overview]
Message-ID: <a96ecf34-216a-70d3-cf45-3f96dc12f689@SystematicSw.ab.ca> (raw)
In-Reply-To: <32e5fb73-7965-467d-8fe5-2ac08eb4e16e@SystematicSw.ab.ca>

On 2020-01-28 15:28, Brian Inglis wrote:
> On 2020-01-28 14:56, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>>> As the reg entries show, you can also do this by adding or setting registry
>>> entries using Cygwin regtool, Windows reg, or regedit commands.
>>
>> It is better and much safer to use native Windows service controller commands, than tweaking the registry:
>>
>> sc config cygsshd start= delayed-auto
> 
> Agreed, reg is useful for checking and doing in non-scripting languages.
> 
>> Also, you won't need (or generally want) to use service pre-shutdown, as it can cause a very long delay when Windows restarts.

If you mean by "delay when restarts" => "before shutdown", it may take up to
three (3) minutes by default before Windows times out preshutdown services, then
it may take up to two (2) minutes by default before Windows times out service
process shutdown.
Is that not better than abruptly terminating an sshd session, or abandoning
sending a large email?
I would expect UPS shutdown handlers to do whatever is required to expedite a
speedy shutdown within a a few tens of ms/a mains power cycle or two.

>> https://docs.microsoft.com/en-us/windows/win32/services/service-control-handler-function
> 
> Don't see where you read that?
> Preshutdown happens before regular service shutdown starts.
> Nothing to do with startup or restart!

-- 
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

  reply	other threads:[~2020-01-29  6:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-29 18:55 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-29 23:08 ` Brian Inglis
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
2020-01-23 15:54         ` Andrew J. Schorr

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=a96ecf34-216a-70d3-cf45-3f96dc12f689@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).