similar to: [PATCH 1/4] daemon: upload: fix fd leak on lseek failure

Allows other modules to use the same logic for uploading files. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/daemon.h | 3 +++ daemon/upload.c | 70 ++++++++++++++++++++++++++++++++------------------------- 2 files changed, 42 insertions(+), 31 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index 2379e31..1723b68 100644 --- a/daemon/daemon.h +++

Allows other modules to use the same logic for uploading files. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/daemon.h | 3 +++ daemon/upload.c | 70 ++++++++++++++++++++++++++++++++------------------------- 2 files changed, 42 insertions(+), 31 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index 793074dea..bc89f78dd 100644 --- a/daemon/daemon.h +++

Allows other modules to use the same logic for uploading files. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/daemon.h | 3 +++ daemon/upload.c | 70 ++++++++++++++++++++++++++++++++------------------------- 2 files changed, 42 insertions(+), 31 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index abec087cd..797ec2dd9 100644 --- a/daemon/daemon.h +++

Allows other modules to use the same logic for uploading files. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- daemon/daemon.h | 3 +++ daemon/upload.c | 66 ++++++++++++++++++++++++++++++++------------------------- 2 files changed, 40 insertions(+), 29 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index 5137e2c2a..75af5246e 100644 --- a/daemon/daemon.h +++

On Sun, Apr 23, 2017 at 07:49:56PM +0300, Matteo Cafasso wrote: > + if (r == -1) { /* write error */ > + err = errno; > + r = cancel_receive (); You need to use ignore_value here, and it needs to be in a separate commit, as discussed previously. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog:

Hi, I just figured FreeBSD will happily write data (disk blocks) from byte #0 even after successful lseek(fd, 17, SEEK_SET) returned 17, at least on da(4) partitions such as rda0s1f. Tested on 4.9-PRERELEASE checked out early Sep 5th. I'd suggest that lseek to a non-sector boundary returns either (off_t)-1 and EINVAL (preferred) or at least returns the actual position (though few

Exposing file upload logic as suggested in previous patch: https://www.redhat.com/archives/libguestfs/2016-November/msg00109.html Matteo Cafasso (1): daemon: expose upload logic daemon/daemon.h | 3 +++ daemon/upload.c | 70 ++++++++++++++++++++++++++++++++------------------------- 2 files changed, 42 insertions(+), 31 deletions(-) -- 2.10.2

Simply a file rename, no other change. --- daemon/Makefile.am | 2 +- daemon/command.c | 319 ----------------------------------------------------- daemon/sh.c | 319 +++++++++++++++++++++++++++++++++++++++++++++++++++++ po/POTFILES | 2 +- 4 files changed, 321 insertions(+), 321 deletions(-) delete mode 100644 daemon/command.c create mode 100644 daemon/sh.c diff --git

Hi folks, Shouldn't the lseek macros (SEEK_SET, etc) go to unistd.h? Regards Harri -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature Url : http://www.vas.nu/pipermail/klibc/attachments/20050213/9790028c/signature.bin

On Wed, Dec 02, 2015 at 02:00:57PM +0100, Pino Toscano wrote: > - add a flag to request chroot for the process, which is done only as > very last (before chdir) operation before exec'ing the process in the > child: this avoids using CHROOT_IN & CHROOT_OUT around command* > invocations, and reduces the code spent in chroot mode > - add failure checks for dup2 and open

- add a flag to request chroot for the process, which is done only as very last (before chdir) operation before exec'ing the process in the child: this avoids using CHROOT_IN & CHROOT_OUT around command* invocations, and reduces the code spent in chroot mode - add failure checks for dup2 and open done in child, not proceeding to executing the process if they fail - open /dev/null

GCC has two warnings related to large stack frames. We were already using the -Wframe-larger-than warning, but this reduces the threshold from 10000 to 5000 bytes. However that warning only covers the static part of frames (not alloca). So this change also enables -Wstack-usage=10000 which covers both the static and dynamic usage (alloca and variable length arrays). Multiple changes are made

Hi Volker and many thanks for your response According to your questions >Please remove the SO_RCVBUF and SO_SNDBUF entries. >Oh, that's ancient. Do you have any possibility to move to >"security=user"? The smb.conf file was inherited from HP-UX system. Ok, I'll remove them >Did you try "posix locking = no"? That is mostly criticial >if

Dears, I'm faced with the above mentionned problem. System is a HP Proliant DL380 with HP SmartArray 5304-256 Controller and a HP StorageWorks 4300 disk shelf. OS is Debian/testing with kernel 2.6.3 and LVM2. I've created a new LV and when I try to create the FS on it, it fails when saying "Writing superblocks and filesystem accounting information:" sar output shows that CPU

On 03/01/15 16:31, Robert Hartmann wrote: > Hi, > > i am really depressed at this moment. I set up an domain controller > using samba4 and an raspberry pi. > > I can join the domain and everything works BUT kerberos has some > strange problems resolving my raspberry hostname. > > First of all some information: > > Raspberry pi is DHCP Server and DNS-Server

On 03/01/15 18:45, Robert Hartmann wrote: > > Hi, > > /etc/resolv.conf looks exactly like this: > > domain family.rapsberry.local > search family.rapsberry.local > nameserver 192.168.178.222 > > So to answer your question: yes the only Nameserver the raspberry has > is itself. > Hi, firstly, you might as well remove the 'domain' line, it will be

GUESTFSD_EXT_CMD was used by OpenSUSE to track which external commands are run by the daemon and package those commands into the appliance. It is no longer used by recent SUSE builds, so remove it. Thanks: Pino Toscano, Olaf Hering. --- daemon/9p.c | 3 +- daemon/available.c | 7 +-- daemon/base64.c | 6 +-- daemon/blkid.c | 10 ++---

GUESTFSD_EXT_CMD is used by OpenSUSE to track which external commands are run by the daemon and package those commands into the appliance. However because this uses linker trickery it won't work from OCaml code. Replace it with a [nearly] standard C mechanism. Files still have to declare the external commands they will use, eg: DECLARE_EXTERNAL_COMMANDS ("btrfs",

Hi, thank you so! much. Turning off avahi daemon was the solution! rapsberry instead of raspberry is a typo during porivision actually. Thank you again :) I will write an entry on my blog to make sure that does not happen again. One last time for google bots. IF you receive kinit: Cannot contact any KDC for realm while getting initial credentials make sure you don't run avahi However

For Device parameters we expect a block device name. However we were only testing for "/dev/..." and so chardevs (from the appliance) could be passed here, resulting in strange effects. This adds a function is_device_parameter which tests for a valid block device name. For Dev_or_Path parameters much the same, except we can also use the is_device_parameter function elsewhere in the