mirror of
git://source.winehq.org/git/wine.git
synced 2024-10-06 18:37:19 +00:00
Modify the wineserver documentation for the new location of the socket
and add a warning.
This commit is contained in:
parent
e9e6db870a
commit
7500111cc9
|
@ -24,7 +24,7 @@
|
||||||
used for "Windows Emulator". In a way, both meanings are
|
used for "Windows Emulator". In a way, both meanings are
|
||||||
correct, only seen from different perspectives. The first
|
correct, only seen from different perspectives. The first
|
||||||
meaning says that Wine is not a virtual machine, it does not
|
meaning says that Wine is not a virtual machine, it does not
|
||||||
emulate a CPU, and you are not supposed to install neither
|
emulate a CPU, and you are not supposed to install
|
||||||
Windows nor any Windows device drivers on top of it; rather,
|
Windows nor any Windows device drivers on top of it; rather,
|
||||||
Wine is an implementation of the Windows API, and can be
|
Wine is an implementation of the Windows API, and can be
|
||||||
used as a library to port Windows applications to Unix. The
|
used as a library to port Windows applications to Unix. The
|
||||||
|
@ -82,8 +82,8 @@
|
||||||
What is its function in Wine? Well, to be brief, it provides
|
What is its function in Wine? Well, to be brief, it provides
|
||||||
Inter-Process Communication (IPC), synchronization, and
|
Inter-Process Communication (IPC), synchronization, and
|
||||||
process/thread management. When the wineserver launches, it
|
process/thread management. When the wineserver launches, it
|
||||||
creates a Unix socket for the current host in your home
|
creates a Unix socket for the current host based on (see below)
|
||||||
directory's <filename>.wine</filename> subdirectory (or
|
your home directory's <filename>.wine</filename> subdirectory (or
|
||||||
wherever the <constant>WINEPREFIX</constant> environment
|
wherever the <constant>WINEPREFIX</constant> environment
|
||||||
variable points) - all Wine processes launched later
|
variable points) - all Wine processes launched later
|
||||||
connects to the wineserver using this socket. (If a
|
connects to the wineserver using this socket. (If a
|
||||||
|
@ -92,6 +92,22 @@
|
||||||
the wineserver will then terminate itself once the last Wine
|
the wineserver will then terminate itself once the last Wine
|
||||||
process has terminated).)
|
process has terminated).)
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
In earlier versions of Wine the master socket mentioned
|
||||||
|
above was actually created in the configuration directory;
|
||||||
|
either your home directory's <filename>/wine</filename>
|
||||||
|
subdirectory or wherever the <constant>WINEPREFIX</constant>
|
||||||
|
environment variable points>. Since that might not be possible
|
||||||
|
the socket is actually created within the <filename>/tmp</filename>
|
||||||
|
directory with a name that reflects the configuration directory.
|
||||||
|
This means that there can actually be several separate copies of
|
||||||
|
the wineserver running; one per combination of user and
|
||||||
|
configuration directory. Note that you should not have several
|
||||||
|
users using the same configuration directory at the same time;
|
||||||
|
they will have different copies of the wineserver running and
|
||||||
|
this could well lead to problems with the registry information
|
||||||
|
that they are sharing.
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Every thread in each Wine process has its own request
|
Every thread in each Wine process has its own request
|
||||||
buffer, which is shared with the wineserver. When a thread
|
buffer, which is shared with the wineserver. When a thread
|
||||||
|
|
Loading…
Reference in a new issue