search for: libguestfs_cat

.../22/using-rsync-with-libguestfs/ We are trying to get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the above example the "backup" rsync module name matches the script on Richard's wordpress.com blog page (above link). Typically in the rsync daemon log we see something like: receiving file list sent 17 bytes received 24 bytes total size 0 but no data is tr...

...s/ > > We are trying to get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: > > guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) > > surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the above > example the "backup" rsync module name matches the script on Richard's wordpress.com blog page (above link). > Typically in the rsync daemon log we see something like: > > receiving file list > sent 17 bytes received 24 bytes total...

...get the libguestfs API guestfs_rsync_out to work. We’ve tried combinations similar to: >>> >>> guestfs_rsync_out(g, “/HostShared”, “rsync://root@10.0.1.90:2999/backup/ -av”, -1) >>> >>> surrounding it with APIs as in the recipe examples, for example replacing libguestfs_cat(), with no luck. In the >>> above >>> example the "backup" rsync module name matches the script on Richard's wordpress.com blog page (above link). >>> Typically in the rsync daemon log we see something like: >>> >>> receiving file list &g...