Greetings, Brian Inglis! >>> The problem is, not all packages are prepared to deal with locked shared >>> objects (in truth, none are). Which may leave system in an inconsistent >>> state even after reboot.
> Cygwin setup uses standard Windows wininit processing to perform the > replacements on restart. Does it schedule a rebase after replacement? >> Server service like cygserver always start after windows re-start if it is >> registered. So restart does not always kill cygwin processes. I do not want >> to force to kill cygwin process by setupXX.exe but output the warning. > Only if a service is registered for Automatic startup: you can change this to > Manual, and restart services in a permanent last postinstall script prefix > e.g. > zp_zzz_services.dash, which can also be executed by a scheduled task, before > starting Cygwin from e.g. a XWin Server taskbar or Start Menu shortcut. > Cygwin setup could operate more consistently and transparently if setup > warned, > then shutdown running Cygwin services and noted them, and killed all remaining > processes, before beginning the install phase, then restarted previously noted > running services after the postinstall phase. Or it could rename the objects it failed to delete, and use wininit to cleanup. -- With best regards, Andrey Repin Monday, March 19, 2018 13:37:06 Sorry for my terrible english... -- 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
