diff options
| author | Richard W.M. Jones <rjones@redhat.com> | 2009-11-13 14:47:32 +0000 |
|---|---|---|
| committer | Richard W.M. Jones <rjones@redhat.com> | 2009-11-13 14:50:39 +0000 |
| commit | c2cbf9cd082e2cca69481e31ebd9bafda879fa22 (patch) | |
| tree | a052cf99a669239247953bd0b5370fc9ae77d880 /guestfs.pod | |
| parent | 38d8943009e3a637e56af6adb43f6c12a7a357c7 (diff) | |
| download | libguestfs-c2cbf9cd082e2cca69481e31ebd9bafda879fa22.tar.gz libguestfs-c2cbf9cd082e2cca69481e31ebd9bafda879fa22.tar.xz libguestfs-c2cbf9cd082e2cca69481e31ebd9bafda879fa22.zip | |
Docs: Add section on using multiple threads.
This section was missing from the previous documentation.
Diffstat (limited to 'guestfs.pod')
| -rw-r--r-- | guestfs.pod | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/guestfs.pod b/guestfs.pod index 2ebcc090..bfd472e4 100644 --- a/guestfs.pod +++ b/guestfs.pod @@ -935,6 +935,15 @@ sort of connection control, when the daemon launches it sends an initial word (C<GUESTFS_LAUNCH_FLAG>) which indicates that the guest and daemon is alive. This is what C<guestfs_launch> waits for. +=head1 MULTIPLE HANDLES AND MULTIPLE THREADS + +All high-level libguestfs actions are synchronous. If you want +to use libguestfs asynchronously then you must create a thread. + +Only use the handle from a single thread. Either use the handle +exclusively from one thread, or provide your own mutex so that two +threads cannot issue calls on the same handle at the same time. + =head1 QEMU WRAPPERS If you want to compile your own qemu, run qemu from a non-standard |