> Else how would you stop them in the first place?
Restarting the OS was the way (post install, to restart with the new DLL),
but that no longer works anymore with Win10.
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: https://cygwin.com/problems.html
FAQ: ht
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]!
>> for svc in cygserver $( cygrunsrv --list | grep -v cygserver ); do net start
>> "$svc"; done
>> and you're golden!
> Not so fast, you must have admin rights to start any Windows services,
> including cygserver.
> So maybe just bronze, and not
> for svc in cygserver $( cygrunsrv --list | grep -v cygserver ); do net start
> "$svc"; done
> and you're golden!
Not so fast, you must have admin rights to start any Windows services,
including cygserver.
So maybe just bronze, and not so golden
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Greetings, Brian Inglis!
> restart them in a late local permanent postinstall script
> /etc/postinstall/zp_z0_l_start_services.dash after setup.
It never occured to me that I can use postinstall tasks to restart services :D
Just add a line
for svc in cygserver $( cygrunsrv --list | grep -v cygs
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
Anton,
Interesting problems these days.
Thank you again!
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Keith,
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
Anton,
There were two cygserver instances listed, one had a PID and the other
one had N/A for the PID.
I terminated both of them and now I can launch Cygwin64 term.
Are there any configs I should check for cygserver to make sure there
aren't two of them running?
I've never seen this problem befor
> Click the Cygwin64 Terminal icon on the desktop, opens briefly then closes.
> Suggested troubleshooting steps?
Try to completely stop and then re-start Cygserver (found in "windows
services").
HTH,
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: https://cygwin.com/problem
Downloaded the latest setup-x64.exe from the Cygwin website, ran a
normal Cygwin update this morning on my Windows 10 system, rebooted
after updates.
Click the Cygwin64 Terminal icon on the desktop, opens briefly then closes.
Suggested troubleshooting steps?
Thanks, everyone.
--
Problem reports:
10 matches
Mail list logo
