In-process wine server (a.k.a., "Dirty Speed Hack")
danielfsantos at att.net
Wed Jan 25 00:38:54 CST 2012
oops, sorry I missed this one earlier Stefan. On my first mailing, all
remaining processes simply stayed in memory waiting on the pipe, which
also still existed (I ran a simple kill script to clean it up).
However, I added a new atexit function that shuts down the master socket
and all other programs terminate (as when you run wineserver -k).
However, the socket & lock files still aren't cleaned up, so that issue
is still outstanding.
So, in essence, termination of the primary application terminates the
On 01/20/2012 02:31 PM, Stefan Dösinger wrote:
> Am Freitag, 20. Januar 2012, 11:47:11 schrieb Daniel Santos:
>> This hack builds a libwineserver.so that the primary application (i.e.,
>> the one you first launch) will spawn a thread and run the wine server in
>> the same process,
> What happens when this process exits normally, but other processes still run?
More information about the wine-devel