similar to: Progress indication refreshes too often with --info=progress2

https://bugzilla.samba.org/show_bug.cgi?id=10580 Summary: Total file size reported wrong with --stats --info=progress2 Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org

Hi, I'm a bit new to rsync, and I recently learnt about the --info=progress2 flag to display complete transfer progress. However while transferring I encountered some unusually large transfer rates being displayed repeatedly. I used "rsync -av --info=progress2" to transfer a folder with several large files. Every time a new file was started , the initial transfer rate was unusually

https://bugzilla.samba.org/show_bug.cgi?id=10451 Summary: --info=progress2 with --bwlimit doesn't give correct value Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=10450 Summary: --info=progress2 increase % Product: rsync Version: 3.1.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: vania.toperich at gmail.com

https://bugzilla.samba.org/show_bug.cgi?id=10677 Summary: external zlib broken after update to 3.1.1 on FreeBSD Product: rsync Version: 3.1.1 Platform: x64 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: ehaupt at

Dear R-help, I would like to be able to run the following code sequence as a source routine. If I paste it into R via the clipboard it works as expected, but if I source the code instead then the last 3 statements fail. I've also tried writing to the file in place of the sink sequence, but that also hits a snag. R 1.6, w98e2, dfr is a data frame containing the content of Julian

https://bugzilla.samba.org/show_bug.cgi?id=11378 Nathan Neulinger <nneul at neulinger.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #2 from Nathan Neulinger <nneul

https://bugzilla.samba.org/show_bug.cgi?id=12940 Bug ID: 12940 Summary: rsync: -C/--cvs-exclude does not ignore SCM ignore files (patch) Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee:

Hi, I just stepped on a strange and very annoying bug in rsync-3.1.0 as shipped with SuSE Linux Enterprise 12, but verified the bug also with rsync-HEAD-20170123. I tried to copy some of my movie collection to a usb disk that our TV could read, so it was formatted with vfat. I forgot that vfat can't handle files > 4 GB, and some of the movies were larger. rsync worked for 3 hours copying

On Sun, Nov 03, 2019 at 06:37:57AM -0500, Michael Lueck via samba wrote: > I have Samba shares mounted to my Linux workstation. Mostly I access files on the Samba server over the Samba mount. I use mount.cifs to bring up these mounts. > > For a couple of special cases, I use scp to transfer files between the > server and workstation. Special characters in filenames give sending them

On Wed, 7 Nov 2018 12:21:17 +0100 Reindl Harald via samba <samba at lists.samba.org> wrote: > > > Am 07.11.18 um 12:07 schrieb Rowland Penny via samba: > > On Wed, 7 Nov 2018 11:44:28 +0100 > > Reindl Harald via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: > >>>

https://bugzilla.samba.org/show_bug.cgi?id=12769 Bug ID: 12769 Summary: error allocating core memory buffers (code 22) depending on source file system Product: rsync Version: 3.1.0 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: > On Wed, 7 Nov 2018 05:45:45 +0300 > Albert Berger via samba <samba at lists.samba.org> wrote: > >> I'm running a Samba server on Raspbian and observing that Samba >> during idle periods is constantly (every minute) writing to HDD >> (maybe doing some journaling?) what causes the HDD to constantly spin

On 03/11/2019 11:37, Michael Lueck via samba wrote: > Greetings Samba team, > > It has been a long time since I needed to ask a Samba technical question. > > Server and workstation are both running the latest Samba packages via > Ubuntu 16.04 LTS. I recently applied the security updates... actually > that was yesterday I applied them. > > >> samba

Am 07.11.18 um 12:07 schrieb Rowland Penny via samba: > On Wed, 7 Nov 2018 11:44:28 +0100 > Reindl Harald via samba <samba at lists.samba.org> wrote: > >> >> Am 07.11.18 um 09:54 schrieb Rowland Penny via samba: >>> On Wed, 7 Nov 2018 05:45:45 +0300 >>> Albert Berger via samba <samba at lists.samba.org> wrote: >>> >>>>

https://bugzilla.samba.org/show_bug.cgi?id=13423 Bug ID: 13423 Summary: Checksum option does not work as expected when append-verify is used Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD

I have a scenario where a "broken pipe" condition can happen on a fairly regular basis and in all honesty it is to be expected. We are working with satellite links to moving ship platforms (no it isn't military based) and depending on location, sea conditions, and a few dozen other factors, the data link can become somewhat unstable at times. That and the high-latency for IP

Hi, The man page for nsd.conf claims the following syntax is valid: provide-xfr: 0/0 NOKEY However, this gives the error: /var/dnsx/nsd.zones:9: error: Bad ip4 address '0' The following does work: provide-xfr: 0.0.0.0/0 NOKEY So either the code is wrong, or the man page :) Paul