From 27146d368a4956a44c59d1a7fea4ab92685e080c Mon Sep 17 00:00:00 2001 From: Richard Jones Date: Thu, 2 Apr 2009 15:15:55 +0100 Subject: [PATCH] More documentation updates. --- guestfs.pod | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/guestfs.pod b/guestfs.pod index 1791545..a3ef84b 100644 --- a/guestfs.pod +++ b/guestfs.pod @@ -129,6 +129,12 @@ STATE MACHINE AND LOW-LEVEL EVENT API below. You should call these two functions after configuring the handle (eg. adding drives) but before performing any actions. +=head2 guestfs_kill_subprocess + + int guestfs_kill_subprocess (guestfs_h *handle); + +This kills the qemu subprocess. You should never need to call this. + =head1 CONFIGURATION MANAGEMENT The configuration functions allow you to configure which drive images @@ -189,7 +195,9 @@ handler using C. =head2 guestfs_set_error_handler - typedef void (*guestfs_error_handler_cb) (void *data, const char *msg); + typedef void (*guestfs_error_handler_cb) (guestfs_h *handle, + void *data, + const char *msg); void guestfs_set_error_handler (guestfs_h *handle, guestfs_error_handler_cb cb, void *data); @@ -205,7 +213,8 @@ message is completely discarded. =head2 guestfs_get_error_handler - guestfs_error_handler_cb guestfs_get_error_handler (guestfs_h *handle); + guestfs_error_handler_cb guestfs_get_error_handler (guestfs_h *handle, + void **data_rtn); Returns the current error handler callback. @@ -428,9 +437,6 @@ The callback function C will be called whenever a reply is received from the child process. (This corresponds to a transition from the BUSY state to the READY state). -Note (I) that high-level API calls overwrite this -callback. - =head2 guestfs_set_log_message_callback void guestfs_set_log_message_callback (guestfs_h *handle, -- 1.8.3.1