https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #5 from Armin Mohring <armin_mohr...@web.de> ---
I think I have found the error:
the usb 3.0 Hdd must be mounted first and then it can be acessed.
--
You are receiving this mail because:
You are the QA Contact for t
> >rsync: writefd_unbuffered failed to write 8 bytes to message fd
[receiver]: Broken pipe
> >(32)
> >rsync error: error in rsync protocol data stream (code 12) at io.c(1532)
[receiver=3.0.9]
> >
receiver]:
Broken pipe
>(32)
>rsync error: error in rsync protocol data stream (code 12) at io.c(1532)
[receiver=3.0.9]
>
>
rite 8 bytes to message fd [receiver]:
Broken pipe
(32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1532)
[receiver
https://bugzilla.samba.org/show_bug.cgi?id=11215
--- Comment #1 from Shevek bugzi...@anarres.org ---
I think this bug is affecting us too, over multi-gigabyte files. There's one
specific file which is killing rsync, but it doesn't always kill it in the same
place.
--
You are receiving this mail
On Aug 17, 2015, at 5:03 PM, Wayne Davison way...@samba.org wrote:
The use of {} on the receiving (remote) side is superfluous -- just
specifying a destination dir (your .../Drive5/ path) is enough for rsync to
use the same name as the source file on the destination.
That is the case if
of syntactically
meaningful things.
That does not explain why bash is perfectly happy with the command line if it
is a locally mounted disk (the same disk, in fact). Despite the error, this is
not a bash problem.
So, at a minimum, you need to escape/quote *both* of your file references {}
- not just
to another
drive and ran across an error I haven’t seen before. Normally I do
this sync via a mounted file system, but this time I tried to do it
over ssh:
find . -type f -atime -1 -exec rsync -aP {}
10.0.0.11:/Volumes/Drive5/{} \; bash: -c: line 0: syntax error near
unexpected token
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It is true that you don't need the {} in the remote arg but due to the
syntax you probably want --relative instead.
On 08/17/2015 07:03 PM, Wayne Davison wrote:
On Sun, Aug 16, 2015 at 11:13 PM, @lbutlr krem...@kreme.com
mailto:krem...@kreme.com
the error, this is not a bash problem.
So, at a minimum, you need to escape/quote *both* of your file
references {} - not just the one.
Find’s {} is escaped, just doesn’t seem to be escaped properly via
ssh/rysnc.
As I said, this works:
find . -type f -atime -1 -exec rsync -aP
On Sun, Aug 16, 2015 at 11:13 PM, @lbutlr krem...@kreme.com wrote:
find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{}
\;
The use of {} on the receiving (remote) side is superfluous -- just
specifying a destination dir (your .../Drive5/ path) is enough for rsync to
use
On Aug 17, 2015, at 4:05 AM, Kevin Korb k...@sanitarium.net wrote:
If you want find to generate your list use --files-from:
find . -type f -atime -1 -print0 | rsync -aP --files-from=- --from0 .
10.0.0.11:/Volumes/Drive5/
This works:
find . -type f -atime -1 -exec rsync -aP {} /Drive5/{}
- as the file name so it uses the
output of the find command as input to rsync.
Once you get that sorted, any remaining errors should be a lot easier to
fix.
Joe
On 08/17/2015 02:13 AM, @lbutlr wrote:
I was trying to process a bunch of folders to sync them to another drive and
ran across an error I
I was trying to process a bunch of folders to sync them to another drive and
ran across an error I haven’t seen before. Normally I do this sync via a
mounted file system, but this time I tried to do it over ssh:
find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \;
bash
.
Backuppc uses RsyncArgs and RsyncRestoreArgs to create the rsync
'string' of commands to backup files. By adding the -A and -X to
the RsyncArgs list. When backups are run the log files contains: Got
fatal error during xfer (fileListReceive failed). Removing the -A and
the -X allows the backup
. When backups are run the log
files contains: Got fatal error during xfer (fileListReceive
failed). Removing the -A and the -X allows the backup to
proceed without errors. Is there another 'switch' that needs to be
added to allow the -A and -X to function without error? Anyone
familiar
contains: Got fatal error during xfer (fileListReceive failed). Removing the
-A and the -X allows the backup to proceed without errors. Is there another
'switch' that needs to be added to allow the -A and -X to function without
error? Anyone familiar with including acl and attr file permissions
. When backups are
run the log files contains: Got fatal error during xfer
(fileListReceive failed). Removing the -A and the -X
allows the backup to proceed without errors. Is there another
'switch' that needs to be added to allow the -A and -X to
function without error? Anyone familiar
the -A and -X to the
RsyncArgs list. When backups are run the log files contains: Got fatal
error during xfer (fileListReceive failed). Removing the -A and the -X
allows the backup to proceed without errors. Is there another 'switch' that
needs to be added to allow the -A and -X to function without
https://bugzilla.samba.org/show_bug.cgi?id=11215
Bug ID: 11215
Summary: compression/zlib errors discard the zlib error message
Product: rsync
Version: 3.1.0
Hardware: All
OS: All
Status: NEW
Severity
: rsync error: error allocating core memory buffers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should not be using rsync's --checksum during routine backups. It
is only for very rare use cases not every backup run.
On 04/09/2015 04:43 AM, Hans Kraus wrote:
Hi,
I've configured
checksums. Whith one of the shares I get the error (in
syslog):
-
robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender]
robbe rsyncd[2183]: rsync error: error allocating core memory
buffers (code 22) at util2.c(106
Hi,
I've configured 'backuppc' to transfer files via rsyncd, with enabled
checksums. Whith one of the shares I get the error (in syslog):
-
robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender]
robbe rsyncd[2183
message.
---
Desktop/OSme/Web-Site-Backups/backup-5.4.2014_15-11-43_linux014.tar.gz
4288446464 78% 32.15MB/s0:00:36
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken
pipe (32)
rsync: connection unexpectedly closed (1964386 bytes received so far) [sender]
rsync error
4288446464 78% 32.15MB/s0:00:36
rsync: writefd_unbuffered failed to write 4 bytes to socket
[sender]: Broken pipe (32) rsync: connection unexpectedly closed
(1964386 bytes received so far) [sender] rsync error: error in
rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9
https://bugzilla.samba.org/show_bug.cgi?id=10989
--- Comment #2 from Jim Avera jim.av...@gmail.com ---
A much more serious problem is that when unsafe symlinks are copied pursuant
to the --copy-unsafe-links option, they are all treated as I/O ERRORS.
This prevents --delete from ever working.
--
/tmp was actually on a tmpfs and no idea why this happens, but it doesn't
seem to be a rsync issue (though it's kinda scary). This fixes it:
diff -Nur a/testsuite/compare-dest.test b/testsuite/compare-dest.test
--- a/testsuite/compare-dest.test 2007-09-03 22:43:58.0 +0200
+++
On Wed, Dec 31, 2014 at 2:34 AM, Ingo Brückl i...@wupperonline.de wrote:
/tmp was actually on a tmpfs and no idea why this happens
Thanks for pointing that out. I couldn't reproduce the issue until I ran
the tests on a tmpfs mount, and discovered that rsync is optimizing away a
utimensat()
# The script would have aborted on error, so getting here means we've won.
-exit 0
+exit 99
in order to examine and preserve the data, I found:
2014-12-30 19:29:01.806934641 +0100
2014-12-30 19:29:01.820267972 +0100
in the test.log, e.g. the created file's mtime differs!
Surprisingly, the same
Resolution|--- |INVALID
--- Comment #2 from Wayne Davison way...@samba.org ---
Since the command-line you mentioned is completely valid, there's no error for
rsync to complain about. Your args specified --exclude --exclude (so that it
won't transfer a file named --exclude
https://bugzilla.samba.org/show_bug.cgi?id=10951
--- Comment #3 from Wayne Davison way...@samba.org ---
Let me also add that if the cause was a bash shell variable that ended up being
empty, then you should note that it is a bash-ism to require parameters to be
double-quoted in order for them to
, but no
error message
Product: rsync
Version: 3.1.0
Hardware: x64
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: core
Assignee: way...@samba.org
Reporter: st...@wis.no
https://bugzilla.samba.org/show_bug.cgi?id=10951
Bug ID: 10951
Summary: Emtpy parameter triggers unwanted behavior, but no
error message
Product: rsync
Version: 3.1.0
Hardware: x64
OS: Linux
https://bugzilla.samba.org/show_bug.cgi?id=10951
--- Comment #1 from Stian Ertvåg st...@wis.no ---
The --exclude without a value was of course a punshing error in our system,
but we think this should trigger an error instead of syncing to the folder
defined as excluded. The lack of output may
Hi,
I'm trying to use rsync to sync files between my desktop and a file server,
using my desktop as the client, and the file server as the remote side (or the
server side, of course), and I'm wondering how I can get the error code of
the remote/server side at the client side. For example
Does anyone know what this message is about? I keep getting this message
once in a while after my rsync command is run for some time.
rsync error: unexplained error (code 255) at rsync.c(541) [sender=3.0.4]
Regards
Jerry
HSBC Global
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't know what that error means as it is non-specific. However
3.0.4 is very old. Try upgrading your rsync and see if the problem
goes away.
On 08/10/2014 07:08 AM, jerrycww...@hsbc.com.hk wrote:
Does anyone know what this message is about? I
. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.
Internet communications cannot
, forward, disclose or
use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail. Internet communications cannot
be guaranteed to be timely, secure, error or virus-free. The sender
does
Thanks Kevin, I'll test it out. From the man page I saw -A implies -p,
that's why I thought I don't have to put -p.
From:
Kevin Korb k...@sanitarium.net
To:
rsync@lists.samba.org
Date:
07/23/2014 09:52 AM
Subject:
Re: Fw: rsync permission error
Sent by:
rsync-boun...@lists.samba.org
the man page I saw -A implies
-p, that's why I thought I don't have to put -p.
From: Kevin Korb k...@sanitarium.net To:rsync@lists.samba.org
Date: 07/23/2014 09:52 AM Subject:Re: Fw: rsync permission
error Sent by:rsync-boun...@lists.samba.org
https://bugzilla.samba.org/show_bug.cgi?id=10719
Summary: Error with cached effective process gid
Product: rsync
Version: 3.1.1
Platform: x64
OS/Version: FreeBSD
Status: NEW
Severity: major
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=10679
Summary: readlink_stat error results in deletion of mountpoints
Product: rsync
Version: 3.1.0
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
https://bugzilla.samba.org/show_bug.cgi?id=9594
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||FIXED
--- Comment #1 from Wayne Davison way...@samba.org 2014-05-25 23:02:03 UTC ---
I'm making rsync exit with the standard partial-transfer error code (which
always means that someone needs to check the error messages to see what
actually went wrong
https://bugzilla.samba.org/show_bug.cgi?id=10611
Summary: No error code returned when removing source file
failed
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: minor
https://bugzilla.samba.org/show_bug.cgi?id=10579
Summary: --xattr internal abbrev error
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Mac OS X
Status: NEW
Severity: major
Priority: P5
Component
https://bugzilla.samba.org/show_bug.cgi?id=9594
--- Comment #1 from Kuba Ober k...@mareimbrium.org 2014-04-30 01:20:39 UTC ---
I can reproduce under 3.1.1pre1. The cause of the problem is as follows:
Note that the rsync_xa list items contain the xattr name and value *but also*
an attribute
https://bugzilla.samba.org/show_bug.cgi?id=10567
Summary: --abort option to halt transfer on error(s)
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=10372
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #13 from mlus...@redhat.com 2014-04-15 15:11:51 UTC ---
I can confirm that this issue is caused by compiling rsync with system provided
zlib in F20. Archlinux package doesn't contain zlib in dependencies,and
therefore I suppose the
Has anyone ever seen this error with an rsync
rsync error: unexplained error (code 255) at rsync.c(543) [sender=3.0.7]
Gina Smith
NICS/System Administrator
Desk 256-961-9382
Cell 256-655-6531
You know, all that really matters is that the people you love are happy and
healthy.
Everything else
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #10 from Orion Poplawski or...@cora.nwra.com 2014-03-18 15:01:33
UTC ---
I get the same failure using the provided zlib in 3.1.1pre1.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #11 from Orion Poplawski or...@cora.nwra.com 2014-03-18 15:51:41
UTC ---
I take that back, this is caused by using the system zlib in Fedora 20. Still
poking around.
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=10372
Orion Poplawski or...@cora.nwra.com changed:
What|Removed |Added
CC||mlus...@redhat.com
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #7 from rudy.metz...@xs4all.nl 2014-03-15 08:22:31 UTC ---
(In reply to comment #5)
Please check if the version you're testing links against zlib or includes the
zlib that ships with rsync. I'd imagine that it is trying to use the
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #8 from Harvey h...@gmx.de 2014-03-15 12:03:16 UTC ---
I don't know how to test that either. I am on archlinux, the PKGBUILD is here:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/rsync
The
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #9 from Harvey h...@gmx.de 2014-03-15 12:05:23 UTC ---
Additional comment: Archlinux uses zlib 1.2.8
https://www.archlinux.org/packages/core/x86_64/zlib/
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
---
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #4 from Harvey h...@gmx.de 2014-03-14 17:33:15 UTC ---
I can confirm that the error only raises if compression is invoked. Doing the
same file transfer without -z in the commandline runs without errors.
--
Configure bugmail: https
https://bugzilla.samba.org/show_bug.cgi?id=10372
--- Comment #5 from Wayne Davison way...@samba.org 2014-03-14 23:25:27 UTC ---
Please check if the version you're testing links against zlib or includes the
zlib that ships with rsync. I'd imagine that it is trying to use the system's
zlib, and
https://bugzilla.samba.org/show_bug.cgi?id=10372
Wayne Davison way...@samba.org changed:
What|Removed |Added
CC||or...@cora.nwra.com
---
https://bugzilla.samba.org/show_bug.cgi?id=10445
Summary: flag to suppress link_stat error messages
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=10445
michele m...@bitchx.it changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
115440 at 28513680 offset=28513680
[sender] _exit_cleanup(code=10, file=io.c, line=837): entered
rsync error: error in rsync protocol data stream (code 12) at io.c(837)
[sender=3.1.0]
[sender] _exit_cleanup(code=10, file=io.c, line=837): about to call exit(12)
Does this help in any way?
--
Configure
https://bugzilla.samba.org/show_bug.cgi?id=10372
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1
https://bugzilla.samba.org/show_bug.cgi?id=10372
Summary: rsync 3.10 error in protocol data stream while rsync
3.0.9 runs through
Product: rsync
Version: 3.1.0
Platform: x64
OS/Version: Linux
Status: NEW
what it was
that rsync finished so quickly without an error.
Thanks
bye Fabi
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart
On Jan 06, 2014, at 04:14, Fabian Cenedese wrote:
sent 63 bytes received 2425 bytes ,')* bytes/sec
A! Squinty Blackbeard approves of this transfer speed, mateys!
John
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
might be interesting to know what it was
that rsync finished so quickly without an error.
Thanks
bye Fabi
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http
rsync has correctly terminated, but the shell
has not. On the lost host, rsync is still waiting for the remote to
finish. The local ssh client process (a subprocess of the local rsync)
is still running too.
What's going on here? I'd be expecting the local rsync to report some
error and exit on-zero
On Sat 17 Aug 2013 13:20:12 NZST +1200, Justin Pryzby wrote:
I saw something similar on a solaris machine. Do you know what kind of
redirection of file descriptors is going on ? I worked around my
problem by using tempfiles rather than sophisticated redirections [0].
The script snippet is
that Matt was going to post a
patch. I haven't been able to find the patch and wonder if one exists or anyone
can point me to the code where I can perhaps add at least the file path to the
error thrown. Also I would probably opt myself for keeping the file without the
acls, knowing the possible
https://bugzilla.samba.org/show_bug.cgi?id=9877
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #2
https://bugzilla.samba.org/show_bug.cgi?id=9877
Summary: target file deleted in error
Product: rsync
Version: 3.0.6
Platform: x64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
https://bugzilla.samba.org/show_bug.cgi?id=9877
--- Comment #1 from Jack Savage ja...@mid.org 2013-05-10 21:01:57 UTC ---
I meant to include this information in the original post.
[oracle@rh5-appsrvr99 oracle cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
, which file is
referred for checking the values of variable
“ac_cv_sizeof_uint32_t/checking size of uint16_t”
? As far as my study during this error debugging it seems the value is
looked from the cache file.
There should be no cache file present the first time you run configure
to
compilation error which I am facing with latest version of rsync.
I am compiling rsync-3.0.9 in my build system (which is for 2.6.10 linux
kernel. I am using windriver build system), compilation is failing due to
size of “uint32” and “uint16” was computed wrongly during configuration.
Output during
and examples well
enough, but obviously not.
Secondly, I am receiving an error 28 (ENOSPC) on the transfer of a large
file. I make sure the destination file system is double what the source
for the possibility of needing to keep copies of both during transfer, but
I assumed --delete-before would
, it appears that files were transferred
within the /gcse1/infor tree after all.
I naturally assumed that I followed documentation and examples
well enough, but obviously not.
Secondly, I am receiving an error 28 (ENOSPC) on the transfer of a
large file. I make sure the destination file system
On Mon 11 Feb 2013, scott.geo...@parker.com wrote:
Secondly, I am receiving an error 28 (ENOSPC) on the transfer of a large
file. I make sure the destination file system is double what the source
for the possibility of needing to keep copies of both during transfer, but
I assumed
https://bugzilla.samba.org/show_bug.cgi?id=9594
Summary: Error transferring user and non-user xattr using
--fake-super under Linux
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status: NEW
Hi all,
I have a script that rsyncs files from one machine to another as part of a
periodic backup. The source file system can be changing as the backup happens
and sometimes, I get 24 - Partial transfer due to vanished source files
errors. That error doesn't really bug me, so I mask it out
https://bugzilla.samba.org/show_bug.cgi?id=5811
--- Comment #10 from Stuart Longland stua...@longlandclan.yi.org 2012-12-11
20:47:47 UTC ---
Not sure if this is related, but I get more or less the same error message out
of rsync 3.0.9 on AMD64 Linux rsyncing from an internal XFS-formatted HDD
@lists.samba.org
Envoyé: Mardi 17 Juillet 2012 16:48:34
Objet: Re: Mac OS X : get_xattr_names: llistxattr(some/path/here, 1024)
failed error
Hi,
Sorry for re-opening this thread but I'm still trying to get rid of these
errors.
I tried to remove the -A and the -X options but it doesn't make
@lists.samba.org
Envoyé: Lundi 16 Janvier 2012 11:22:56
Objet: Re: Mac OS X : get_xattr_names: llistxattr(some/path/here, 1024)
failed error
Hi Henri, hi list,
Thanks a lot for your answer.
I did some testing during my spare time those last weeks and ended up compiling
rsync 3.0.9 (with additionnal
not to be required with 3.0.9.
Concerning the hard links error, however, I don't know what to do, since I'm
not good enough with programming to tinker with the rsync internals.
More specifically, backup bouncer test suite performs these actions:
echo testing 1 2 3 some-file
ln ./some-file link1
ln
Joris Korbeeck korbeeck at hotmail.com writes:
...
rsync error: unexplained error (code 129) at rsync.c(541) [sender=3.0.3]
Could anyone explain this error or suggest a solution?
Thanks in advance,
Joris
I received this error when using an Expect script to call a bash
script
Should I submit a bug? Will you take a patch?
On 03/24/2012 11:11:47 PM, Karl O. Pinc wrote:
Hi,
I'm having a problem using --link-dest and --hard-links when
the fs hits the hard link limit (link(2) returns EMLINK).
Using rsync 3.0.7 an error is thrown and the target file is
not created
Hi,
I'm having a problem using --link-dest and --hard-links when
the fs hits the hard link limit (link(2) returns EMLINK).
Using rsync 3.0.7 an error is thrown and the target file is
not created. Glancing at git head it _looks_ like things
could now be a little nicer. Perhaps the target file
.
the rsync update process on web server, always return code 23 error, the
complete error output like this:
(No batched update for /pictureShower/wallpaper/_info.php)
(No batched update for comm/js/log/cbaae969d4e258a9d6815a350d135982.txt)
(No batched update for /images/wallpaper/data.js
I am trying to figure out what happens in the following scenario:
I use rsync to copy files from hostA:/dir1 to hostB:/dir1
with the command (from hostB)
rsync -abvt --delete-after --suffix=~ hostA:/dir1 /dir1
So if fileA exists already on both boxes (it has previously been
rsynce-d) and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While a file is being updated it is stored as a temporary name
(.filename.string). When the file is complete the old version is
deleted and the temp file is renamed into place. If rsync aborts
during this process the temp file is deleted to ensure
https://bugzilla.samba.org/show_bug.cgi?id=7124
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1
/bar.txt - is that from Origin1 or origin2?
I know I can use the `--ignore-existing` option to make sure only the first
version is kept, or I could remove this option to keep the last one. But I
would like to be notified when this happens, either with a warning or an
error.
Is that possible with rsync
:
foo/bar.txt - is that from Origin1 or origin2?
I know I can use the `--ignore-existing` option to make sure only the first
version is kept, or I could remove this option to keep the last one. But I
would like to be notified when this happens, either with a warning or an
error
https://bugzilla.samba.org/show_bug.cgi?id=8659
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
read some doc about this error but it doesn't seem to fit my case and
I'm kinda stuck with it. It doesn't seem to be a serious issue but I'd like
to be sure about it and know if there is a way to get rid of them.
Do you guys have any clue of what's going wrong or what I may doing wrong
this error but it doesn't seem to fit my case and I'm
kinda stuck with it. It doesn't seem to be a serious issue but I'd like to be
sure about it and know if there is a way to get rid of them.
Do you guys have any clue of what's going wrong or what I may doing wrong ?
Thanks a lot !
--
Please use reply
https://bugzilla.samba.org/show_bug.cgi?id=8659
Summary: link-by-hash.diff: Fix error when running without
--link-by-hash
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=8090
Wayne Davison way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
101 - 200 of 1491 matches
Mail list logo
