=head2 COMMUNICATIONS DIRECTORY
The guest writes various static, mostly unchanging, information into
-its own directory. On Linux the directory is C</var/lib/virt-tools/>
-and under Windows it is C<%systemroot%\virttool\>. In the discussion
-below, this communications directory is referred to as
-C<$GUESTCOMMSDIR>.
+its own directory. On Linux the directory is
+C<@LOCALSTATEDIR@/lib/virt-tools/> and under Windows it is
+C<%systemroot%\virttool\>. In the discussion below, this
+communications directory is referred to as C<$GUESTCOMMSDIR>.
The host is able to read files out of this directory using
L<libguestfs(3)> (without any cooperation needed by the guest).
C<virt-tools-get-key> caches the keys of guests that it has seen
before so it doesn't have to read them each time. The cache is in
-C</var/lib/virt-tools/keys/> (in the host).
+C<@LOCALSTATEDIR@/lib/virt-tools/keys/> (in the host).
You can just delete the files in this directory at any time, I<or> you
can drop a file in here which contains the key of a guest.
-To do this, create a file C</var/lib/virt-tools/keys/E<lt>UUIDE<gt>>
-where E<lt>UUIDE<gt> is the guest's UUID as displayed by this command:
+To do this, create a file
+C<@LOCALSTATEDIR@/lib/virt-tools/keys/E<lt>UUIDE<gt>> where
+E<lt>UUIDE<gt> is the guest's UUID as displayed by this command:
virsh domuuid <name>
C<virt-tools-get-transport> caches the transports of guests that it
has seen before so it doesn't have to determine them each time. The
-cache is in C</var/lib/virt-tools/transports/> (in the host).
+cache is in C<@LOCALSTATEDIR@/lib/virt-tools/transports/> (in the
+host).
As for the L</KEY CACHE>, this directory is just some files that are
named after the UUID of the guest, containing the transport.
git.annexia.org / virt-tools.git / blobdiff