similar to: [PATCH] fuse/RHEL: Don't require UTIME_{NOW, OMIT} to be defined.

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

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 this function) I'm not sure what's the best thing to

- fix names of arguments & optional arguments in C<..> markers - use https for URLs where possible - fix links to other guestfs APIs - use more C<..> markers for special tests, shell commands, values of arguments, and names of fields - link to command man pages where an explicit command is mentioned - fix few incorrect documentation bits --- generator/actions_augeas.ml

On Thu, 2016-10-13 at 20:08 -0400, Kevin Korb wrote: > I don't remember whether or not you said you were running rsync over > ssh but if you are you can also debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the

https://bugzilla.samba.org/show_bug.cgi?id=12742 Bug ID: 12742 Summary: a proposal: fix bogus nanosecond mtimes on transfer (patch included) Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core

I'm currently working on gobject bindings for libguestfs. I haven't got as far as compiling anything yet, but I've attached the C header for initial review. Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 -------------- next part -------------- An embedded and

Very large but mechanical change to the generator. Rich.

Release Announcements ===================== This is the first release candidate of Samba 4.12. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.12 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

https://bugzilla.samba.org/show_bug.cgi?id=10925 Bug ID: 10925 Summary: non-atomic xattr replacement in btrfs => rsync --read-batch random errors Product: rsync Version: 3.1.0 Hardware: All URL: http://article.gmane.org/gmane.comp.file-systems.btrfs /40013 OS: All

Release Announcements ===================== This is the second release candidate of Samba 4.12. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.12 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.12. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.12 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Dear All I try to migration a kvm guest os to another host failed server: ubuntu 11.04 server virsh:migrate --live --tunnelled vm1 qemu+ssh://192.168.10.3/system error:Requested operation is not valid:cannot perform tunnelled migration without using peer2peer flag

Hi, (I'm not subscribed to the list, so please CC me on reply.) I'd like to request adding a feature to OpenSSH: Task: ~~~~~ It is quite sometime useful to invoke a program prior to connecting to an ssh server. The most common use case will probably be port knocking. That is a small program sends certain packets to a server and the server reacts to this by unlocking the ssh port, which

Dear All, Along with the files that suddenly disappear, we have a bit of a problem with these that do not. Namely, in my test runs I can see a small but stable set of files, that rsync is repeatedly trying to transfer, and then repeatedly fails to updates their times ; and then the story repeats itself. The situation is illustrated by the log snippet below, where I have changed file names to

Full_Name: Ralph Mac Nally Version: 1.40 OS: MacOS9x/Windows98 Submission from: (NULL) (130.194.13.180) I'm using a simple glm in which the dependent variable may have missing data (coded 'NA') as usual. Both the default na.action (na.omit) and explicit 'na.action=na.omit' do not seem to ignore the missing data as I expect, generating an error to that effect (NA passed to

https://bugzilla.samba.org/show_bug.cgi?id=7668 Summary: Add --omit-symlink-times option, same purpose as --omit- dir-times Product: rsync Version: 3.0.7 Platform: All OS/Version: FreeBSD Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at

Dear r-devel list, dear Ben I came across a post of Ben Bolker from Feb 2012 (see below) on handling NA values in prcomp(). As I faced the same issue and found Ben's suggestions interesting, I was wondering whether this led to further discussions I might have missed? I understand handling NA values is far from trivial, but would it be possible to add a warning in the documentation, and/or

Dear all, I have a series of variables that looks roughly like the sample data below and I'm trying to conduct a factor analysis. I've omitted cases with missing values for the factor analysis, but now I'd like to use the scores on each component as new variables in the *original* data set for analysis. That is, I'd like to take the scores on each of the two factors and see how