| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
'./configure --disable-probes' will disable these probes. Otherwise
they are autodetected as before.
The <sys/sdt.h> produces lots of errors when you try to compile with
these probes enabled under clang, so it is necessary to provide a way
to disable them for clang users.
|
| |
|
|
|
|
|
|
| |
Remove blkid tab cache in the guest.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
| |
|
| |
|
|
|
|
| |
It's not needed since we no longer use gettextize cruft.
|
| |
|
| |
|
|
|
|
|
|
| |
Remove the generated pam data in the guest.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(RHBZ#789504).
|
| |
|
| |
|
|
|
|
| |
This is just code motion.
|
|
|
|
|
| |
This also disables data and metadata duplication, which is not very
useful on a constructed filesystem on a virtual disk.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a tests/xml directory, and an LD_PRELOAD module which
can fake arbitrary libvirt XML from an external file (and is therefore
a much more flexible test than using the libvirt test:// driver
alone).
Also added is one regression test for:
https://bugzilla.redhat.com/show_bug.cgi?id=701814
Loading the given libvirt XML using Sys::Guestfs::Lib::open_guest
used to fail with the error:
format parameter is empty or contains disallowed characters at /home/rjones/d/libguestfs/perl/blib/lib/Sys/Guestfs/Lib.pm line 256.
Thanks to Tom Horsley for supplying the test data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(RHBZ#701814).
Old versions of libvirt allowed you to define disks like this:
<disk type='file' device='disk'>
<driver name='qemu'/>
...
Since the <driver> element does not have a 'type' attribute (which
defines the format), we are supposed to do autodetection, so the
format should be undefined.
However what actually happened was that the code in
Sys::Guestfs::Lib::open_guest received format as an empty string from
the xpath query, causing libguestfs to give an error.
If the xpath query returns the format as an empty string, undefine it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example:
><fs> glob echo /dev/*
/dev/vda
/dev/vda1
/dev/vda2
/dev/vda3
><fs> glob echo /dev/v*/*
/dev/vg_f16x64/lv_root
/dev/vg_f16x64/lv_swap
|
|
|
|
| |
This is just code motion.
|
|
|
|
|
|
| |
This commit tidies up the code for the 'glob' command. It also makes
the command return an error if malloc fails (previously it would just
print a message but not return any error indication).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(RHBZ#803533).
For a test case, see:
https://bugzilla.redhat.com/show_bug.cgi?id=803533
In guestfish, we use the gnulib closeout module which sets up an
atexit handler to detect if there were any errors on stdout when the
program exits. This is so we can fail correctly in out of disk space
cases like:
guestfish [...] > output
However the atexit handler just checks that there was any error on
stdout (using ferror). If a pipe command such as:
><fs> command_with_lots_of_output | head
ran at any time during the session, the error flag would be set
(because the underlying writes failed with EPIPE errors).
So the commit first adds a test for ferror (stdout) after each command
that we issue. This brings error handling closer to the point of
failure, and so is generally a good thing.
Secondly we reset the error flag after detecting and dealing with the
error, so that avoids the redundant 'guestfish: write error' message
produced by gnulib closeout.
Thirdly we add a --pipe-error flag which causes guestfish commands to
fail on pipe commands line the one above. The default is off for
backwards compatibility reasons.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Make the introduction in the man page shorter and punchier, so it
leads readers directly to other pages of interest.
|
| |
|
|
|
|
|
|
|
|
| |
Note that this support is optional: To enable it, install the
ocaml-gettext library from
http://forge.ocamlcore.org/projects/ocaml-gettext . If this library
is not installed, then configure detects this and inserts dummy
gettext functions that do nothing.
|
|
|
|
|
| |
Replace the sociopathic nonsense in gettextize with a simple
Makefile.am which does the same ... and is faster.
|
|
|
|
|
|
|
|
|
|
|
|
| |
gettextize provides a local file called "gettext.h". Remove this and
use <libintl.h> from glibc headers instead.
Most of this change is mechanical: #include <libintl.h> in every C
file which uses any gettext function. But also we remove the
gettext.h file, and adjust the "_" macros.
Note that this effectively removes the ./configure --disable-nls
option, although we don't know if that ever worked.
|
|
|
|
|
| |
virt-resize, virt-sparsify, virt-sysprep are all OCaml tools, so
change what is printed in the report.
|
| |
|
|
|
|
| |
Since it describes the C library, it's better in the src/ directory.
|
| |
|
|
|
|
|
|
| |
reasonable (RHBZ#816839).
Thanks Yuyu Zhou.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/include/optargs-add_domain.h
/usr/include/optargs-add_drive_opts.h
/usr/include/optargs-btrfs_filesystem_resize.h
/usr/include/optargs-compress_device_out.h
/usr/include/optargs-compress_out.h
/usr/include/optargs-copy_device_to_device.h
/usr/include/optargs-copy_device_to_file.h
/usr/include/optargs-copy_file_to_device.h
/usr/include/optargs-copy_file_to_file.h
/usr/include/optargs-e2fsck.h
/usr/include/optargs-inspect_get_icon.h
/usr/include/optargs-md_create.h
/usr/include/optargs-mkfs_btrfs.h
/usr/include/optargs-mkfs_opts.h
/usr/include/optargs-mount_9p.h
/usr/include/optargs-mount_local.h
/usr/include/optargs-ntfsclone_out.h
/usr/include/optargs-ntfsfix.h
/usr/include/optargs-ntfsresize_opts.h
/usr/include/optargs-set_e2attrs.h
/usr/include/optargs-test0.h
/usr/include/optargs-tune2fs.h
/usr/include/optargs-umount_local.h
/usr/include/session.h
/usr/include/struct-application.h
/usr/include/struct-btrfssubvolume.h
/usr/include/struct-dirent.h
/usr/include/struct-inotify_event.h
/usr/include/struct-int_bool.h
/usr/include/struct-isoinfo.h
/usr/include/struct-lvm_lv.h
/usr/include/struct-lvm_pv.h
/usr/include/struct-lvm_vg.h
/usr/include/struct-mdstat.h
/usr/include/struct-partition.h
/usr/include/struct-stat.h
/usr/include/struct-statvfs.h
/usr/include/struct-version.h
/usr/include/struct-xattr.h
/usr/include/tristate.h
We want to put these headers into the subdirectory, but not
guestfs-gobject.h. This isn't easy with automake.
|
| |
|
|
|
|
|
|
| |
Remove the data of dovecot.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
|
|
|
|
|
|
|
| |
Remove the logfiles configured by /etc/logrotate.d/*.
Omit the logfile of "samba" and "sssd" which we removed
them separately .
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
|
| |
|
|
|
|
| |
See: http://bugzilla.redhat.com/816346
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Originally this state was intended so that in some way you could find
out if the appliance was running a command. However there was never a
thread-safe way to access the state of the handle, so in effect you
could never do anything useful safely with this information.
This commit completely removes the BUSY state.
The only visible change is to the guestfs_is_busy API. Previously you
could never call this safely from another thread. If you called it
from the same thread it would always return false (since the current
thread can't be running a libguestfs command at that point by
definition). Now it always returns false.
|
|
|
|
| |
properly.
|