1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="ts_linux-host-vboxsvc">
<title>VBoxSVC IPC Issues</title>
<body>
<p>
On Linux, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of a custom version of
Mozilla XPCOM (cross platform component object model) for
interprocess and intraprocess communication (IPC). The process
<userinput>VBoxSVC</userinput> serves as a communication hub between
different <ph conkeyref="vbox-conkeyref-phrases/product-name"/> processes and maintains the global
configuration, such as the XML database. When starting an
<ph conkeyref="vbox-conkeyref-phrases/product-name"/> component, the processes
<userinput>VBoxSVC</userinput> and <userinput>VBoxXPCOMIPCD</userinput>
are started automatically. They are only accessible from the
user account they are running under. <userinput>VBoxSVC</userinput>
owns the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration database which normally
resides in <filepath>~/.config/VirtualBox</filepath>, or the
appropriate configuration directory for your operating system.
While it is running, the configuration files are locked.
Communication between the various <ph conkeyref="vbox-conkeyref-phrases/product-name"/> components and
<userinput>VBoxSVC</userinput> is performed through a local domain
socket residing in
<filepath>/tmp/.vbox-<varname>username</varname>-ipc</filepath>.
In case there are communication problems, such as an
<ph conkeyref="vbox-conkeyref-phrases/product-name"/> application cannot communicate with
<userinput>VBoxSVC</userinput>, terminate the daemons and remove the
local domain socket directory.
</p>
</body>
</topic>
|
