search for: guestfs_mount_local_run

Hi Richard! Maybe the function guestfs_mount_local_run shouldn't ACQUIRE_LOCK_FOR_CURRENT_SCOPE as it doesn't talk with the daemon and sits in the loop? What do you think? If I remove it from guestfs_mount_local_run (in lib/action-1.c, don't know how to properly remove it from ml generator), fuse_loop_mt works, but I still don't underst...

..., for example? If yes, how many threads it uses? Or every request starts its own thread? Thanks much, Maxim. On Oct 18, 2017 2:17 AM, "Maxim Kozover" <maximkoz@gmail.com> wrote: > Hi Richard! > Finally it seems it works after removing ACQUIRE_LOCK_FOR_CURRENT_SCOPE > in guestfs_mount_local_run and throwing away all directory cache code. > Although I didn't try to mix fuse libguestfs client with other clients, I > think guestfs_mount_local_run shouldn't take that specific lock as the > function won't exit until umount and will sit in the loop. I think it does > not...

Hi I`ve been trying this guestfs_mount_local api for quite a few days, but still can`t get over it. Now it seems to have enter the fuse loop but have some problems with 'mount'? and stops at guestfs_mount_local_run(g). Here`s corresponding code in the test program: ?? if(guestfs_mount_local(g,"/mnt/libg")==-1) exit(EXIT_FAILURE); else guestfs_mount_local_run(g); ?? Below is a part of the debug dump information, ?? version = 1.17.40.Root device: /dev/vda1 (this is test output) libguestfs: guestfs...

On Wed, Oct 18, 2017 at 01:33:49AM +0300, Maxim Kozover wrote: > Hi Richard! > Maybe the function guestfs_mount_local_run shouldn't > ACQUIRE_LOCK_FOR_CURRENT_SCOPE as it doesn't talk with the daemon and sits > in the loop? What do you think? The lock is needed for any access to the guestfs_h structure, so I'm pretty sure that is not safe. > If I remove it from guestfs_mount_local_run (in lib/ac...

On Mon, Jun 26, 2017 at 10:27:54AM +0300, Maxim Kozover wrote: > I'd like to ask you, please, about multithreading with libguestfs. > I'm using libguestfs 1.36.4 with Perl front-end. > > Should it be possible to have the same libguestfs appliance provide both > fuse interface and periodically perform some longer APIs like find0? > > I mean make one Perl thread do

Well, I get these error messages during the execution of guestfs_mount_local_run(). What can I do then ? On Wed, Jul 17, 2013 at 5:08 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Wed, Jul 17, 2013 at 04:43:34PM +0300, Or Goshen wrote: > > Hi, > > > > When I register a callback for events with this function call: > > eh = guestfs_set_...

...+ } + + if (guestfs_mount_local (sg, stempdir, -1) == -1) + exit (EXIT_FAILURE); + if (guestfs_mount_local (dg, dtempdir, -1) == -1) + exit (EXIT_FAILURE); + + spid = fork (); + if (spid == -1) { + perror ("fork"); + exit (EXIT_FAILURE); + } + if (spid == 0) { + if (guestfs_mount_local_run (sg) == -1) + exit (EXIT_FAILURE); + _exit (EXIT_SUCCESS); + } + + dpid = fork(); + if (dpid == -1) { + perror ("fork"); + exit (EXIT_FAILURE); + } + if (dpid == 0) { + if (guestfs_mount_local_run (dg) == -1) + exit (EXIT_FAILURE); + _exit (EXIT_SUCCESS); +...

2014-07-15 20:59 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > Not sure I understand the question, but the guestfish mount-local-run > command will block guestfish until another process runs > 'fusermount -u /mntpoint' (or better, 'guestunmount /mntpoint'). I understand that guestfish process will be locked. But in case of go that uses lightweight goroutines,

The existing mechanism was clunky, slow and used ~ 10 MB of local disk. Rich.

Hi, When I register a callback for events with this function call: eh = guestfs_set_event_callback(g, message_callback, GUESTFS_EVENT_ALL, 0, dev); Shouldnt it capture and redirect messages like this to message_callback(): "libguestfs: error: lstat: /.Trash: No such file or directory" I still get them in stderr .. Thanks, Or

The full description of this bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=838592 and the effect it has on OpenStack is described here: https://bugzilla.redhat.com/show_bug.cgi?id=835466#c9 Rich.

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

https://bugzilla.redhat.com/show_bug.cgi?id=836710 https://bugzilla.redhat.com/show_bug.cgi?id=836913 There are at least two related bugs going on: (1) Linux sync(2) system call doesn't send a write barrier to the disk, so in effect it doesn't force the hard disk to flush its cache. libguestfs used sync(2) to force changes to disk. We didn't expect that qemu was caching anything

...o_string (status, "test", - status_string, - sizeof status_string)); - goto error; + status_string, + sizeof status_string)); + goto error; } if (r == -1) /* guestfs_mount_local_run above failed */ diff --git a/tests/mountable/test-internal-parse-mountable.c b/tests/mountable/test-internal-parse-mountable.c index 0e0f8bf..c63c501 100644 --- a/tests/mountable/test-internal-parse-mountable.c +++ b/tests/mountable/test-internal-parse-mountable.c @@ -80,8 +80,7 @@ main (int argc,...

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

Split up the huge generator/actions.ml into several smaller files. Rich.