On 03/11/2016 07:06, Gerry Reno wrote:
in this case indicating Windows has not been (auto)restarted since
the update.
If you don't use mintty, you could do this in an ash or dash script
at Windows login, which does the rebase-trigger then exec rebaseall,
so no other process is running using Cygwin.
If you use Cygwin mintty you would have to do the equivalent from a
cmd or PowerShell script before launching any Cygwin process.
If your client systems run Windows Enterprise or Education or use
SCCM instead of Windows Update, details may need to be changed.
The users cannot do anything with Cygwin.
And the client machines are out in the field and not even connected to a
network.
What is needed is for Cygwin itself to detect and manage the situation.
than it was chosen the wrong system.
Instead of W10 + Cygwin a Linux system was more indicated.
Cygwin can not avoid that other programs, poorly written,
interfere with it.
https://cygwin.com/faq/faq.html#faq.using.bloda
You need to get rid of them.
Regards
Marco
--
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
