http://bugs.winehq.org/show_bug.cgi?id=26520
Summary: Kill all wineserver option Product: Wine Version: 1.3.16 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wineserver AssignedTo: wine-bugs@winehq.org ReportedBy: andrew.millington@gmail.com
Killing any and all winserver instances with a single command and regardless of WINEPREFIX environment variable.
http://bugs.winehq.org/show_bug.cgi?id=26520
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2011-03-22 23:52:33 CDT --- Is there any reason why do you need that? Why 'killall' doesn't work for you?
http://bugs.winehq.org/show_bug.cgi?id=26520
--- Comment #2 from Andrew Millington andrew.millington@gmail.com 2011-03-23 00:04:08 CDT --- More convenience if any as wineserver already has kill.
http://bugs.winehq.org/show_bug.cgi?id=26520
--- Comment #3 from butraxz@gmail.com 2013-09-15 07:45:24 CDT --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.2 or higher ?
https://bugs.winehq.org/show_bug.cgi?id=26520
roger@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |roger@mailinator.com
--- Comment #4 from roger@mailinator.com --- abandon
https://bugs.winehq.org/show_bug.cgi?id=26520
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #5 from Austin English austinenglish@gmail.com --- Still in 1.7.31.
https://bugs.winehq.org/show_bug.cgi?id=26520
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- I think this is basically a WONTFIX. It is right that it would be convenient in some situations, but there is no good way to enumerate which wineserver instances are running.
Each wineserver runs with its own server_dir, and the user can specify arbitrary WINEPREFIXes. How is the wineserver executable supposed to know what exactly is running (besides enumerating processes with the name 'wineserver', which could also match other unrelated processes?).
https://bugs.winehq.org/show_bug.cgi?id=26520
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht@gmx.net Resolution|--- |WONTFIX
--- Comment #7 from Anastasius Focht focht@gmx.net --- Hello folks,
indeed, killing wineserver is an exceptional situation anyway. There are very few situations where one wants to kill *all* wineserver processes.
Killing the active server process with apps under investigation (debugging, development) is a more common use case. I don't want to kill off the other instances though, running legit apps. People wanting this can spend the 5 seconds typing the command required to achieve what is requested here.
Resolving 'WONTFIX' unless Alexandre decides otherwise.
Regards
https://bugs.winehq.org/show_bug.cgi?id=26520
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org