search for: progress_hint

...tderr, - "guestfsd: main_loop: new request, len 0x%" PRIx32 "\n", - len); - /* Cancellation sent from the library and received after the * previous request has finished processing. Just ignore it. */ @@ -175,6 +170,13 @@ main_loop (int _sock) progress_hint = hdr.progress_hint; optargs_bitmask = hdr.optargs_bitmask; + if (verbose) + fprintf (stderr, + "guestfsd: enter: %s (0x%x) request length %" PRIu32 " bytes\n", + proc_nr >= 0 && proc_nr <= GUESTFS_MAX_PROC_NR + ? f...

...file. + * Return 0 on success, -1 on error. + */ +static int +write_callback (void *data_vp, const void *buf, size_t len) +{ + int ret; + struct write_callback_data *data = data_vp; + + ret = xwrite (data->fd, buf, len); + if (ret == -1) + return -1; + + data->written += len; + + if (progress_hint > 0) + notify_progress (data->written, progress_hint); + + return 0; +} + +int +optgroup_libyara_available (void) +{ + return 1; +} + +#else /* !HAVE_LIBYARA */ + +OPTGROUP_LIBYARA_NOT_AVAILABLE + +#endif /* !HAVE_LIBYARA */ diff --git a/generator/actions.ml b/generator/actions.ml ind...

...file. + * Return 0 on success, -1 on error. + */ +static int +write_callback (void *data_vp, const void *buf, size_t len) +{ + int ret; + struct write_callback_data *data = data_vp; + + ret = xwrite (data->fd, buf, len); + if (ret == -1) + return -1; + + data->written += len; + + if (progress_hint > 0) + notify_progress (data->written, progress_hint); + + return 0; +} + +/* Yara compilation error callback. + * Reports back the compilation error message. + * Prints compilation warnings if verbose. + */ +static void +compile_error_callback(int level, const char *name, int line, +...

This rather complex set of patches allow non-optargs functions to gain optional arguments, while preserving source and binary backwards compatibility. The problem is that we cannot add an optional argument to an existing function. For example, we might want to add flags to the 'lvresize' API which currently has no optional arguments.

..."", x_handy = 0} buf = <optimized out> lenbuf = "\000\000\000(" len = 40 hdr = {prog = 536933877, vers = 4, proc = GUESTFS_PROC_INTERNAL_AUTOSYNC, direction = GUESTFS_DIRECTION_CALL, serial = 1192960, progress_hint = 0, optargs_bitmask = 0, status = GUESTFS_STATUS_OK} *#2 0xb76d3190 in main (argc=2, argv=0xbfedcf34) at guestfsd.c:342* options = <synthetic pointer> long_options = {{name = 0xb77448b2 "help", has_arg = 0, flag = 0x0, val = 63}, {name = 0xb7745fb9 &qu...

Hello, So in ubuntu1204 guest This is what i got : *(gdb)* bt full * #0* 0x005a9fc0 in exit () from /lib/i386-linux-gnu/libc.so.6 No symbol table info available. * #1* 0x0805f7dd in ?? () No symbol table info available. * #2* 0x0804aedf in ?? () No symbol table info available. *#3* 0x005904d3 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 No symbol

Without this option, configure will fail when there is no display. Signed-off-by: Masami HIRATA <msmhrt at gmail.com> --- configure.ac | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configure.ac b/configure.ac index de8a064..61d6f69 100644 --- a/configure.ac +++ b/configure.ac @@ -593,16 +593,16 @@ working. AC_MSG_FAILURE([$QEMU version must be >=

This change refactors guestfs___has_windows_systemroot to guestfs___get_windows_systemroot. The new function returns a dynamically allocated char * which must be freed. The new function is no less efficient than before, as it returns the result of guestfs___case_sensitive_path_silently, which is required anyway. The new code is slightly more efficient than before, as it re-uses the result of this

Yara is a rule based scanning engine aimed to help malware analysts in finding and classifying interesting samples. https://github.com/VirusTotal/yara This series adds Yara support to Libguestfs allowing to upload sets of rules and scanning files against them. Currently provided APIs: - yara_load: loads a set of rules - yara_destroy: free resources allocated by loaded rules - yara_scan:

...= trace_return name style "r"; ); pr "\n"; + pr " RELEASE_LOCK (g);\n"; pr " return r;\n"; pr "}\n"; pr "\n" @@ -1699,6 +1707,7 @@ and generate_client_actions hash () = pr " const uint64_t progress_hint = 0;\n"; pr "\n"; + pr " ACQUIRE_LOCK (g);\n"; enter_event name; check_null_strings c_name style; reject_unknown_optargs c_name style; @@ -1721,6 +1730,7 @@ and generate_client_actions hash () = (* This is a daemon_function so check the applia...

From: "Richard W.M. Jones" <rjones at redhat.com> --- generator/generator_gobject.ml | 4 ++-- gobject/Makefile.am | 14 +++++++++----- gobject/Makefile.inc | 4 ++-- 3 files changed, 13 insertions(+), 9 deletions(-) diff --git a/generator/generator_gobject.ml b/generator/generator_gobject.ml index 17c6c36..3096501 100644 ---

v2: - Fix yara dependency in packagelist - Use pkg-config where available - Improve longdesc of yara_load API - Fix libyara initialization and finalization - Import CLEANUP_FCLOSE - Add custom CLEANUP_DESTROY_YARA_COMPILER - Add rules compilation error callback - Other small fixes according to comments Matteo Cafasso (6): appliance: add yara dependency New API: yara_load New API:

...ent in pr "%sif (trace_flag)\n" indent; @@ -1876,7 +1878,7 @@ and generate_client_actions actions () = (* Send the main header and arguments. *) if args_passed_to_daemon = [] && optargs = [] then ( pr " serial = guestfs_int_send (g, GUESTFS_PROC_%s, progress_hint, 0,\n" - (String.uppercase name); + (String.uppercase_ascii name); pr " NULL, NULL);\n" ) else ( List.iter ( @@ -1913,7 +1915,7 @@ and generate_client_actions actions () = fun argt -> let n = name_of...

Tested with 'make check-release'. tests/parallel (in check-slow) failed, although it does regularly and that seems to be because of libvirt. Rich.

This patch isn't ready to go upstream. In fact, I think we might do a quick 1.30 release soon, and save this patch, and also the extensive changes proposed for the test suite[1], to after 1.30. Currently it is not safe to use the same handle from multiple threads, unless you implement your own mutexes. See: http://libguestfs.org/guestfs.3.html#multiple-handles-and-multiple-threads These

libguestfs has used double and triple underscores in identifiers. These aren't valid for global names in C++. (http://stackoverflow.com/a/228797) These large but completely mechanical patches change the illegal identifiers to legal ones. Rich.

...rray, sizeof array / sizeof array[0]); + array, sizeof array / sizeof array[0]); } /* Connection modules call us back here when they get a log message. */ @@ -201,8 +201,8 @@ check_daemon_socket (guestfs_h *g) int guestfs_int_send (guestfs_h *g, int proc_nr, - uint64_t progress_hint, uint64_t optargs_bitmask, - xdrproc_t xdrp, char *args) + uint64_t progress_hint, uint64_t optargs_bitmask, + xdrproc_t xdrp, char *args) { struct guestfs_message_header hdr; XDR xdr; @@ -633,9 +633,9 @@ guestfs_int_recv_from_daemon (guestfs_h *g, uint32_t *size_rtn, vo...

I've been taking a long hard look at the protocol layer. It has evolved over a long time without any particular direction, and the result is, to say the least, not very organized. These patches take a first step at cleaning up the mess by abstracting out socket operations from the rest of the code. The purpose of this is to allow us to slot in a different connection layer under the

Result of earlier copy and paste. --- align/scan.c | 35 ++++++++++--------- cat/cat.c | 39 +++++++++++---------- cat/filesystems.c | 69 +++++++++++++++++++------------------- cat/log.c | 35 ++++++++++--------- cat/ls.c | 61 +++++++++++++++++---------------- df/main.c | 43 ++++++++++++------------ diff/diff.c | 67

In the kernel and qemu communities it is routine for patches that will be backported to stable branches to be posted for review. I'm proposing we do the same for libguestfs stable branches. All of the attached have been tested with 'make check-release'. Rich.