samba-bugs at samba.org
2014-Jan-01 15:00 UTC
[Bug 10356] New: Include rsync-no-vanished support script
https://bugzilla.samba.org/show_bug.cgi?id=10356 Summary: Include rsync-no-vanished support script Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jakobunt at gmail.com QAContact: rsync-qa at samba.org Bug 3653 discussed how "file has vanished" warnings can be silenced. Code changes did not make it in, but Matt McCutchen wrote the rsync-no-vanished bash wrapper script, whose final version seems to handle it correctly, using advanced bash features: #!/bin/bash ignoreexit=24 ignoreout='^(file has vanished: |rsync warning: some files vanished before they could be transferred)' set -o pipefail rsync "$@" 2>&1 | (egrep -v "$ignoreout" || true) a=$? if [ $a == $ignoreexit ]; then exit 0 else exit $a fi What is missing is to make that script accessible to users. I suggest to include it in the support directory in the rsync tarball. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2014-Jan-01 18:37 UTC
[Bug 10356] Include rsync-no-vanished support script
https://bugzilla.samba.org/show_bug.cgi?id=10356 Wayne Davison <wayned at samba.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #1 from Wayne Davison <wayned at samba.org> 2014-01-01 18:37:39 UTC --- Good idea -- thanks. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2014-Jun-26 04:39 UTC
[Bug 10356] Include rsync-no-vanished support script
https://bugzilla.samba.org/show_bug.cgi?id=10356 --- Comment #2 from Dmitry Yu Okunev <xaionaro at gmail.com> 2014-06-26 04:39:41 UTC --- IMHO, this's wrong by design solution. There should be an option in rsync itself, but not a hacky wrapper. BTW. couldn't there be a situation, that rsync got two errors (one of which is "24") and exited with the exitcode "24", that will be suppressed by the script. So the other error will be unnoticed? -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2014-Jun-26 15:22 UTC
[Bug 10356] Include rsync-no-vanished support script
https://bugzilla.samba.org/show_bug.cgi?id=10356 --- Comment #3 from Wayne Davison <wayned at samba.org> 2014-06-26 15:22:47 UTC --- Rsync doesn't exit with error code 24 if a more important error happens (which is basically any other error). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Seemingly Similar Threads
- Should I worry about the "vanished files" warning?
- [Bug 10081] New: Multiple rsync instances conflict
- [Bug 10681] New: Add an option to delete non-existent files in --files-from
- Should I worry about the "vanished files" warning?
- rsync: Please add an option to ignore vanished files