[Bug 26520] New: Kill all wineserver option
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(a)winehq.org ReportedBy: andrew.millington(a)gmail.com Killing any and all winserver instances with a single command and regardless of WINEPREFIX environment variable. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26520 --- Comment #1 from Dmitry Timoshkov <dmitry(a)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? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26520 --- Comment #2 from Andrew Millington <andrew.millington(a)gmail.com> 2011-03-23 00:04:08 CDT --- More convenience if any as wineserver already has kill. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26520 --- Comment #3 from butraxz(a)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 ? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=26520 roger(a)mailinator.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger(a)mailinator.com --- Comment #4 from roger(a)mailinator.com --- abandon -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=26520 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- Still in 1.7.31. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=26520 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #6 from Sebastian Lackner <sebastian(a)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?). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=26520 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht(a)gmx.net Resolution|--- |WONTFIX --- Comment #7 from Anastasius Focht <focht(a)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 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=26520 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org