search for: guestfs_int_fadvise_sequenti

...internal-frontend.h +++ b/src/guestfs-internal-frontend.h @@ -87,6 +87,11 @@ extern int guestfs_int_is_true (const char *str); extern const char *guestfs_int_ovmf_i386_firmware[]; extern const char *guestfs_int_ovmf_x86_64_firmware[]; extern const char *guestfs_int_aavmf_firmware[]; +extern void guestfs_int_fadvise_sequential (int fd); +extern void guestfs_int_fadvise_random (int fd); +extern void guestfs_int_fadvise_noreuse (int fd); +extern void guestfs_int_fadvise_dontneed (int fd); +extern void guestfs_int_fadvise_willneed (int fd); /* These functions are used internally by the CLEANUP_* macros. * Don't c...

The way we used posix_fadvise was wrong, and yet right! Rich.

More posix_fadvise stuff, and document what Linux really does with these calls. Also fixes a nasty bug in virt-builder. Rich.

..._t guestfs_int_drive_index (const char *); extern int guestfs_int_is_true (const char *str); +extern bool guestfs_int_string_is_valid (const char *str, size_t min_length, size_t max_length, bool alpha, bool digit, const char *extra); //extern void guestfs_int_fadvise_normal (int fd); extern void guestfs_int_fadvise_sequential (int fd); extern void guestfs_int_fadvise_random (int fd); diff --git a/src/unit-tests.c b/src/unit-tests.c index 06d4d27..e22a61e 100644 --- a/src/unit-tests.c +++ b/src/unit-tests.c @@ -433,6 +433,45 @@ test_stringsbuf (void) guestfs_close (g); } +/* Use the same macros as in src/drives....

As discussed in the thread on validating $TERM, it would be good to have a common function to do this. This is such a function. The main advantage is it includes unit tests which the previous functions did not. Rich.