From d72a617a262e000ce7bc97838ad1f0d640dc66ec Mon Sep 17 00:00:00 2001 From: "Richard W.M. Jones" Date: Fri, 24 Sep 2010 19:28:01 +0100 Subject: [PATCH 1/1] Document accurately how supermin appliance uses /tmp as a cache. --- fish/guestfish.pod | 6 +++--- src/guestfs.pod | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/fish/guestfish.pod b/fish/guestfish.pod index 181a053..285d901 100644 --- a/fish/guestfish.pod +++ b/fish/guestfish.pod @@ -866,9 +866,9 @@ set, it uses C. Location of temporary directory, defaults to C. -If libguestfs was compiled to use the supermin appliance then each -handle will require rather a large amount of space in this directory -for short periods of time (~ 80 MB). You can use C<$TMPDIR> to +If libguestfs was compiled to use the supermin appliance then the +real appliance is cached in this directory, shared between all +handles belonging to the same EUID. You can use C<$TMPDIR> to configure another directory to use in case C is not large enough. diff --git a/src/guestfs.pod b/src/guestfs.pod index de5e254..c235383 100644 --- a/src/guestfs.pod +++ b/src/guestfs.pod @@ -1684,9 +1684,9 @@ has the same effect as calling C. Location of temporary directory, defaults to C. -If libguestfs was compiled to use the supermin appliance then each -handle will require rather a large amount of space in this directory -for short periods of time (~ 80 MB). You can use C<$TMPDIR> to +If libguestfs was compiled to use the supermin appliance then the +real appliance is cached in this directory, shared between all +handles belonging to the same EUID. You can use C<$TMPDIR> to configure another directory to use in case C is not large enough. -- 1.8.3.1