similar to: [Bug 13241] New: A problem with test for xattrs transfer

Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -------------------------------------------------------------- #! /bin/sh # # set -x DIR="/var/tmp/rsync_$(date +%s)/" mkdir "${DIR}/" # Preparing dir_A mkdir

Hello list, When rsync dir_A to dir_B, I hope I wont make any change to the original dir_B unless the rsync procedure end withour errors, therefore, I hope there's somethig like rsync -av dir_A dir_B_tmp && \ mv dir_B dir_B.bkup && mv dir_B_tmp dir_B This small script can ensure the minimal change time between 2 versions of archive. Is this built in the native rsync

https://bugzilla.samba.org/show_bug.cgi?id=10357 Summary: make check fails for xattr tests Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: psimerda at redhat.com

Hi, I have tried to make a recursive scp from a ReliantUNIX machine to an other UNIX machine and got an infinite loop on the source machine. A "normal" scp works well. Also strange is, that the first two letters of the directory respectively file name are missing in the output below. The destination machine produces a directory structure with growing subdirectory names. Below you can

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

https://bugzilla.samba.org/show_bug.cgi?id=13320 Bug ID: 13320 Summary: file contents cause rsync to fail (with certains args and dir structure) Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

On 3/22/23 12:45, Laszlo Ersek wrote: > On 3/22/23 12:42, Daniel P. Berrang? wrote: >> On Wed, Mar 22, 2023 at 12:13:49PM +0100, Laszlo Ersek wrote: >>> On 3/22/23 11:42, Laszlo Ersek wrote: >>> >>>> Now the "podman build -f ci/containers/alpine-edge.Dockerfile -t >>>> libnbd-alpine-edge" command is failing with a different error

http://bugs.freedesktop.org/show_bug.cgi?id=13241 Summary: This particular flash file cycles between "loaded" and "loading" Product: swfdec Version: 0.5.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Kudos all that maintain this awesome and enduring piece of software. Awesome job, many thanks. I’ve come across a use case that would greatly benefit form a —delete-older-than <secs> argument. This would behave the same as —delete only sparing files dest that have a creating time less than <secs> ago. How hard would this be to implement? Where would I start ? TIA, Francois

On Mon, May 18, 2020 at 11:12:29AM +0200, Pino Toscano wrote: > On Tuesday, 5 May 2020 17:44:15 CEST Richard W.M. Jones wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=1828952#c2 > > I think we need to do a different approach than this patch. > > The biggest thing is that currently we check only SELINUXTYPE for the > actual policy, however we do not check SELINUX

On Thursday, 24 September 2020 12:15:29 CEST Richard W.M. Jones wrote: > On Wed, Sep 23, 2020 at 05:57:50PM +0200, Pino Toscano wrote: > > Do not attempt to relabel a guest in case its SELinux enforcing mode is > > not "enforcing", as it is either pointless, or it may fail because of an > > invalid policy configured. > > --- > >

https://bugzilla.samba.org/show_bug.cgi?id=13609 Bug ID: 13609 Summary: rsync can be crazy slow on os x 10.13.6 when copying via usb drives Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=13433 Bug ID: 13433 Summary: out_of_memory in receive_sums on large files Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

https://bugzilla.samba.org/show_bug.cgi?id=13321 Bug ID: 13321 Summary: Rsync --copy-dest issue Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: Anatoly.Penkov at

On Thu, Sep 24, 2020 at 12:39:02PM +0200, Pino Toscano wrote: ... > There are various cases when, even of an enforcing system, labels are > not kept up-to-date: > > $ getenforce > Enforcing > $ touch /tmp/test > $ ls -lZ /tmp/test > -rw-rw-r--. 1 ptoscano ptoscano unconfined_u:object_r:user_tmp_t:s0 0 Sep 24 12:26 /tmp/test > $ mv /tmp/test ~/var/ > $ ls -lZ

https://bugzilla.samba.org/show_bug.cgi?id=12820 Bug ID: 12820 Summary: rsync always try change owner and group of symlink in --fake-super mode Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

I run a sshd host solely to allow employees to tunnel secure connections to our internal hosts. Some of which do not support encrypted protocols. These connections are chroot'ed via the following in /etc/ssh/sshd_config Match Group !wheel,!xxxxxx,yyyyy AllowTcpForwarding yes ChrootDirectory /home/yyyyy X11Forwarding yes Where external users belong to group yyyyy (primary). We

https://bugzilla.samba.org/show_bug.cgi?id=10496 Summary: --itemize-changes always reports xattr changes with --xattrs --fake-super Product: rsync Version: 3.1.1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

Hello! The following code triggered by syzbot r = get_user_pages_fast(log, 1, 1, &page); if (r < 0) return r; BUG_ON(r != 1); Just looking at get_user_pages_fast's documentation this seems impossible - it is supposed to only ever return # of pages pinned or errno. However, poking at code, I see at least one path that might cause this: