Open forum for end-user questions about Wine
. Before asking questions, check out the Wiki
as a first step.
- Level 1
- Posts: 7
- Joined: Thu Mar 14, 2019 10:07 pm
I find wine lacks process managing feature. Why not set a public accessible IPC (unix socket or dbus) which can return wine and wine programs' status?
For example, people may use "wineserver --list" to list all running wine and wine programs:
Code: Select all
PID in unix WINEPREFIX wine binary file WINEARCH windows command
1233 ~/.wine /usr/bin/wineserver win32 -
1234 ~/.wine /usr/bin/wine win32 notepad.exe c:\xxxxx.txt
12344 ~/wine-foo /usr/bin/wineserver win64 -
12345 ~/wine-foo /usr/bin/wine win64 foo.exe
And users use "wineserver --kill-prefix ~/.wine" to kill (SIGTERM or SIGKILL) a bunch of processes.
Wine programs often freeze. Or programs seems to be exited but actually not (process still there), causing wineserver or explorer.exe or service.exe refuse to quit.
I believe users need that feature.
- Level 8
- Posts: 1058
- Joined: Tue Nov 22, 2016 5:39 pm
Feel free to open a feature request ticket, I guess?
- Level 1
- Posts: 8
- Joined: Sat Jul 20, 2019 2:47 am
I also agree that it would be a nice to have feature when wine behaves unexpectedly.
Its not critical because its possible to manually kill the associated sub processes using -7 or -9 signals for the then defunct processes.
A feature like this would make it a lot easier for users to cleanup/recover in some cases where wineserver was killed and there are still processes left open.