search for: fg_utimens

guestmount.c: In function 'fg_utimens': guestmount.c:537: error: 'UTIME_NOW' undeclared (first use in this function) guestmount.c:537: error: (Each undeclared identifier is reported only once guestmount.c:537: error: for each function it appears in.) guestmount.c:539: error: 'UTIME_OMIT' undeclared (first use in thi...

...issing then just don't implement it in the FUSE layer. --- fuse/guestmount.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/fuse/guestmount.c b/fuse/guestmount.c index baf2b66..05cacef 100644 --- a/fuse/guestmount.c +++ b/fuse/guestmount.c @@ -534,14 +534,22 @@ fg_utimens (const char *path, const struct timespec ts[2]) time_t mtsecs = ts[1].tv_sec; long mtnsecs = ts[1].tv_nsec; +#ifdef UTIME_NOW if (atnsecs == UTIME_NOW) atnsecs = -1; +#endif +#ifdef UTIME_OMIT if (atnsecs == UTIME_OMIT) atnsecs = -2; +#endif +#ifdef UTIME_NOW if (mtnsecs...

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

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