Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
wine
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Johnny Cai
wine
Commits
7500111c
Commit
7500111c
authored
21 years ago
by
Bill Medland
Committed by
Alexandre Julliard
21 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Modify the wineserver documentation for the new location of the socket
and add a warning.
parent
e9e6db87
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
documentation/architecture.sgml
+19
-3
19 additions, 3 deletions
documentation/architecture.sgml
with
19 additions
and
3 deletions
documentation/architecture.sgml
+
19
−
3
View file @
7500111c
...
...
@@ -24,7 +24,7 @@
used for "Windows Emulator". In a way, both meanings are
correct, only seen from different perspectives. The first
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,
Wine is an implementation of the Windows API, and can be
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
Inter-Process Communication (IPC), synchronization, and
process/thread management. When the wineserver launches, it
creates a Unix socket for the current host
in your home
directory's <filename>.wine</filename> subdirectory (or
creates a Unix socket for the current host
based on (see below)
your home
directory's <filename>.wine</filename> subdirectory (or
wherever the <constant>WINEPREFIX</constant> environment
variable points) - all Wine processes launched later
connects to the wineserver using this socket. (If a
...
...
@@ -92,6 +92,22 @@
the wineserver will then terminate itself once the last Wine
process has terminated).)
</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>
Every thread in each Wine process has its own request
buffer, which is shared with the wineserver. When a thread
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment