From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Updated cygwin this morning, mintty window flashes briefly and quits
Date: Fri, 21 Jan 2022 00:45:19 -0700 [thread overview]
Message-ID: <59cdd990-5b36-7cc8-8d97-4f3c1f042535@SystematicSw.ab.ca> (raw)
In-Reply-To: <SJ0PR09MB71023C5EF158E30414727266A55A9@SJ0PR09MB7102.namprd09.prod.outlook.com>
On 2022-01-20 13:24, Lavrentiev, Anton wrote:
> There should be only one of them running, unless you have multiple Cygwin installations,
> then there can be per-installation instances. Restart of all Cygwin processes was always
> required (because the main DLL may not be properly replaced while it's in use by
> any process) -- but a reboot usually took care of that quite well...
>
> Honestly, this was new for me, too. Formerly, install with a following reboot was all I needed
> to do (since I'm not a power user on my work PC, that was the only way for me to "restart"
> the service, anyways). But now the reboot alone does not seem to help anymore: looks like
> Win10 loads up services in a different (fast) fashion, like a wake-up from hibernate.
> So an explicit restart of cygserver is now required (and now I have to ask sysadmin
> to do that for me at work -- sigh).
I have modified my Cygwin services definitions to do Delayed Autostart
and Preshutdown, with appropriate Windows service and
inter-dependencies, shut them down and restart them in local scheduled
tasks run under SYSTEM account on appropriate events and on demand, and
restart them in a late local permanent postinstall script
/etc/postinstall/zp_z0_l_start_services.dash after setup.
Some combination of these techniques may allow your sysadmin to set
things up for you to control these services without their intervention.
--
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.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-01-21 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 16:15 Keith Christian
2022-01-20 16:41 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-20 18:33 ` Keith Christian
2022-01-20 20:24 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-20 23:02 ` Keith Christian
2022-01-21 7:45 ` Brian Inglis [this message]
2022-01-26 14:50 ` Andrey Repin
2022-01-26 20:23 ` services startup postinstall scripts Brian Inglis
2022-01-28 8:18 ` Andrey Repin
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=59cdd990-5b36-7cc8-8d97-4f3c1f042535@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).