||INVALID
--- Comment #2 from way...@samba.org 2009-09-05 10:52 CST ---
If rsync starts a child process, it can set its exit code based on what that
process returned. If that process didn't exit cleanly, the code can be out of
the normal list of error codes that rsync
On Sat, 2009-09-05 at 14:25 +0200, Gilles-Alexandre wrote:
I think IMHO that the description of the option --checksum-seed
should be :
--checksum-seed=NUM spécifie le grain de sable pour la somme de
contrôle
The rsync project does not maintain a French manpage. Please report
this to
On Tue, 2009-09-01 at 09:09 -0500, Mike Bombich wrote:
Rsync shouldn't be converting UUID to uid/gid *for ACL entries*
(because Mac OS X stores those ACEs with a reference to a UUID, not a
uid/gid). For file ownership, etc., it should maintain its current
behavior.
My point is that
a Directory Service, I would want it to preserve the UUID. In
that case, upon the restore the then-valid UUID would be properly
restored. Personally, I'd prefer the ACE was always preserved, and
perhaps have a message printed that reports the error. For example:
if (verbose 1 mbr_uuid_to_id(*uup
Rsync shouldn't be converting UUID to uid/gid *for ACL entries*
(because Mac OS X stores those ACEs with a reference to a UUID, not a
uid/gid). For file ownership, etc., it should maintain its current
behavior.
On Aug 31, 2009, at 10:08 PM, Matt McCutchen wrote:
On Mon, 2009-08-31 at
Hi,
Since upgrading to Snow Leopard, my backup script throws an error msg :
rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
This happened both with 3.0.5 and 3.0.6 that I just installed.
Can someone tell me what it means ? I have no clue on what/where to
look for.
Thanks
That error occurs when rsync tries to set an ACE specifying a user
that does not exist. Here's what happens:
1) Read ACE on source file -- on Mac OS X, the user or group of the
ACE is stored using the user or group's UUID
2) Convert UUID to uid/gid using mbr_uuid_to_id, also store which
On Mon, 2009-08-31 at 16:59 -0500, Mike Bombich wrote:
Regardless, rsync shouldn't be converting uuid to uid/gid for Mac OS
X, it's unnecessary.
This is really a question of whether Mac users expect users/groups to be
preserved by uid/gid or by uuid. Are you saying it makes more sense to
On comparing file sizes I noted that the 2.6.8 versions of rscynd and rsync
are the same file. I backed those up and copied the /usr/local/bin/rsync
3.0.6 version as /usr/sbin/rsyncd and /usr/bin/rsync. I no longer get the
--xattrs requires protocol 30... error.
Cheers,
Kirk
On Sat, Aug
Hi there,
We are using rsync 3.0.6 on two identical SLES 10.2 servers. The
destination server is running rsyncd. When I include the -X switch in the
rsync command from the source I get the following:
--xattrs requires protocol 30 or higher (negotiated 29).
rsync error: protocol incompatibility
On Sat, Aug 22, 2009 at 11:22:40AM +0100, Kirk Maule wrote:
Both rsync versions are 3.0.6 protocol version 30.
You'll undoubtedly find that there is an older rsync on the $PATH on one
of the machines. e.g, try this:
ssh hostname rsync --version
Either get rid of the old version, or specify
Good call. I observed rsyncd 2.6.8 starting up in the /var/log/rsyncd.log.
Should the rsync*.tar.gz install procedure replaced rsyncd 2.6.8 as well as
rsync 2.6.8 with the 3.0.6 version?
Stopped the rscyncd and re-ran the install of the tar.gz but no change. The
install was done as root.
On Sat, Aug 22, 2009 at 08:49:10PM +0100, Kirk Maule wrote:
Should the rsync*.tar.gz install procedure replaced rsyncd 2.6.8 as
well as rsync 2.6.8 with the 3.0.6 version?
Depends on how the package was built. Rsync is just one executable, so
be sure to put it in a consistent spot. For your
The local folder contained the text file, which was confirmed by the command
ls ./
When I go to the remote machine and repeat this command, the file is
not shown which means that transfer failed.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
On 18/08/2009, Wayne Davison way...@samba.org wrote:
On Mon, Aug 17, 2009 at 09:02:42PM +0100, e-letter wrote:
rsync -t *.txt u...@remote.machine:
No response from the command terminal, except for a new prompt
Then it succeeded. If you want it to be more verbose, tell it to be
verbose.
I
Tue, 18 Aug 2009 12:53:28 +0100, inpost wrote:
I repeat: I connect to the remote machine in a separate command terminal to
see
if the text file was transferred and there was no transfer.
I repeated the command with the verbose command:
rsync -vt *.txt u...@remote.machine:
sent 39 bytes
Readers,
I have tried the following command:
rsync -t *.txt ssh u...@remote.machine:
and receive the following error:
rsync: link_stat local/machinepath/ssh failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at
main.c(1031) [sender=3.0.2]
My
the following command:
rsync -t *.txt ssh u...@remote.machine:
and receive the following error:
rsync: link_stat local/machinepath/ssh failed: No such file or
directory (2)
rsync error: some files could not be transferred (code 23) at
main.c(1031) [sender=3.0.2]
My understanding of the manual
On Mon 17 Aug 2009, e-letter wrote:
I have tried the following command:
rsync -t *.txt ssh u...@remote.machine:
and receive the following error:
rsync: link_stat local/machinepath/ssh failed: No such file or directory (2)
Does:
ssh u...@remote.machine
actually work to give you
?
and receive the following error:
rsync: link_stat local/machinepath/ssh failed: No such file or directory
(2)
Your current working directory is local/machinepath ?
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
).
This failed, command terminal response:
ssh: *.txt: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(635) [receiver=3.0.2]
--
Please use reply-all for most replies to avoid
On 17/08/2009, Paul Slootman paul+rs...@wurtel.net wrote:
On Mon 17 Aug 2009, e-letter wrote:
I have tried the following command:
rsync -t *.txt ssh u...@remote.machine:
and receive the following error:
rsync: link_stat local/machinepath/ssh failed: No such file or directory
(2)
Does
On 17/08/2009, Paul Slootman p...@wurtel.net wrote:
On Mon 17 Aug 2009, Paul Slootman wrote:
I have tried the following command:
rsync -t *.txt ssh u...@remote.machine:
I removed the ssh from the command:
rsync -t *.txt u...@remote.machine:
No response from the command terminal, except
https://bugzilla.samba.org/show_bug.cgi?id=6573
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Wed, Jul 22, 2009 at 2:52 AM, Mac User FRmacuse...@free.fr wrote:
This is a malloc (memory allocation) error.
It shows that a non-aligned pointer (pointer that doesn't start on an
address multiple of 4 in a 32-bit machine) is being freed. As pointers must
always be aligned, this indicates
https://bugzilla.samba.org/show_bug.cgi?id=6573
Summary: Documentation Error: Section with exact title doesn't
exist
Product: rsync
Version: 3.0.6
Platform: Other
URL: http://samba.anu.edu.au/ftp/rsync/rsyncd.conf.html
https://bugzilla.samba.org/show_bug.cgi?id=6573
--- Comment #1 from bugzilla.samba@krystian.net 2009-07-23 18:02 CST
---
I updated this to severity minor since this may be a minor issue or even
trivial compared with other issues. I'm just trying to help the QA efforts.
The way
This is a malloc (memory allocation) error.
It shows that a non-aligned pointer (pointer that doesn't start on an
address multiple of 4 in a 32-bit machine) is being freed. As pointers
must always be aligned, this indicates an error and the function
free() doesn't know how to deal
On Mon, Jul 20, 2009 at 4:20 AM, Mark Cohenmarkco...@mac.com wrote:
I too have the same issue (reported by Warren) - in that 3.06 backups appear
valid, but the terminal shows the following errors:
rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer being
freed
*** set
I too have the same issue (reported by Warren) - in that 3.06 backups
appear valid, but the terminal shows the following errors:
rsync(18819) malloc: *** error for object 0xf305c: Non-aligned pointer
being freed
*** set a breakpoint in malloc_error_break to debug
I'm looking
After a large transfer, when I see an error at the end like:
sent 2077917 bytes received 9290799087 bytes 2232523.00 bytes/sec
total size is 11868499780 speedup is 1.28
rsync error: some files could not be transferred (code 23) at
main.c(1385) [generator=2.6.9]
rsync
https://bugzilla.samba.org/show_bug.cgi?id=6461
Summary: rsync occassionally issues the message rsync error:
unexplained error (code 255) at main.c(1506)
[generator=3.0.4]
Product: rsync
Version: 3.0.4
Platform
https://bugzilla.samba.org/show_bug.cgi?id=6461
--- Comment #1 from james.pur...@ny.frb.org 2009-06-10 09:03 CST ---
I should mention that we are using rsync in conjunction with ssh. Please let
me know if there are additional details you would like.
--
Configure bugmail:
or (if already redoing) exit code 23 that sending a bad
checksum normally would.
--
Matt
On Wed, May 20, 2009 at 8:32 AM, Matt McCutchen
m...@mattmccutchen.netwrote:
On Tue, 2009-05-19 at 15:49 +0530, Jignesh Shah wrote:
Hi, I am wondering how rsync-3.0.6 react if it encounters ESTALE
error
https://bugzilla.samba.org/show_bug.cgi?id=6405
Summary: Error parsing commandline in version 3.0.6
Product: rsync
Version: 3.0.6
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=6405
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Dear List,
I'm using rsync to sync my data, see below command. And I met this
error?
I think it might be due to 2.6.9 and 3.0.5 compatible issue. So how to
solve the problem? Thanks.
rsync -vrtopg --progress --delete
--password-file=rsync-password /path/on/pc
r...@192.168.0.202::destination
met this
error?
I think it might be due to 2.6.9 and 3.0.5 compatible issue. So how to
solve the problem? Thanks.
rsync -vrtopg --progress --delete
--password-file=rsync-password /path/on/pc
r...@192.168.0.202::destination
building file list ...
151804 files to consider
rsync: push_dir#1
mai 09 à 13:01, Daniel.Li a écrit :
Dear List,
I'm using rsync to sync my data, see below command. And I met this
error?
I think it might be due to 2.6.9 and 3.0.5 compatible issue. So how to
solve the problem? Thanks.
rsync -vrtopg --progress --delete
--password-file=rsync
Hi, I am wondering how rsync-3.0.6 react if it encounters ESTALE error while
synching? If I remember correctly then the rsync-2.6.0 skipping that
file/dir in case of ESTALE error.
Jignesh.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
On Tue, 2009-05-19 at 15:49 +0530, Jignesh Shah wrote:
Hi, I am wondering how rsync-3.0.6 react if it encounters ESTALE error
while synching? If I remember correctly then the rsync-2.6.0 skipping
that file/dir in case of ESTALE error.
If rsync encounters any kind of error reading a source file
, Jignesh Shah wrote:
Hi, I am wondering how rsync-3.0.6 react if it encounters ESTALE error
while synching? If I remember correctly then the rsync-2.6.0 skipping
that file/dir in case of ESTALE error.
If rsync encounters any kind of error reading a source file, it will
report the error
Hi, we have been getting this errors frequently.
ERROR: DoRsync(): rsync had errors or failed
rsync return code: 12
unexpected tag -7
rsync error: error in rsync protocol data stream (code 12) at
io.c(469)
rsync: connection unexpectedly closed (7087269 bytes read so
far
Hi All;
I keep getting Bad file descriptor (9), error in file IO (code 11) at
receiver.c(720) [receiver=3.0.5] from the following:
rav...@bubu:~/bin$ rsync -vvv \
--modify-window=1 \
--progress --stats --compress \
--recursive --times --perms --links --delete \
--exclude
the same sort of error when RSync tries to process anything with
an extended character set. TM symbols, apostrophes, anything aside from
standard Alphabet, by the look of it.
2009/05/06 19:33:11 [1] readlink DATA:\/USERS/JSAWERS/Favorites/Morrell r in
Christchurch - White PagesT New Zealand.url
On Fri, Apr 17, 2009 at 03:03:02PM -0400, Warren Oates wrote:
I compiled 3.0.6pre1, including the crtimes and fileflags patches for
use on Intel OS X 10.5.6
I just compiled rsync with those patches on an Intel OS X 10.5.6 system,
and didn't see any such errors. I did see an issue with make
-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes, file-flags
-
However, now I'm getting these kinds of messages throughout my output:
-
rsync(68321) malloc: *** error for object
This looks like an application is running where the backup is
to be made. The application opens and locks the files
with an exclusive lock and the rsync program must then wait
until it is freed by the application or times out.
This is a typical problem under Windows. Can you ask the
Hy people, where could this be coming from?
rsync: send_files failed to open Alfredo Polti
SA/wz_ALFREDO_POLTI_SA.ac0 (in Winway_z-32): Device or resource busy
(16)
rsync: send_files failed to open Alfredo Polti
SA/wz_ALFREDO_POLTI_SA.ac3 (in Winway_z-32): Device or resource busy
(16) rsync error
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #3 from anorho...@gmail.com 2009-04-01 12:32 CST ---
I am on AIX 6.1 TL02. Been using older version and encountered the file too
large error (27) so I downloaded and tried 3.0.5 but encountered the same error
but ~10GB has
Hi I'm using rsync (ver 3.0.5) to sync a local folder with a folder on a
server using SSH and encrypted key files. It works fine on Windows
2000/XP/2003/Vista but not Windows 2008 Server.
I get an error like the following:
ssh _cygtls::handle_exceptions Error while dumping state (probably
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #2 from way...@samba.org 2009-03-13 12:11 CST ---
File too large is an OS error, so you need to figure out why your OS is
returning that. I'd imagine that rsync was not compiled with large-file
support. If so, let me know
https://bugzilla.samba.org/show_bug.cgi?id=6183
Summary: rsync error file too large (27)
Product: rsync
Version: 3.0.4
Platform: Other
OS/Version: AIX
Status: NEW
Severity: normal
Priority: P3
Component
https://bugzilla.samba.org/show_bug.cgi?id=6183
--- Comment #1 from bros...@gmail.com 2009-03-11 11:38 CST ---
Justed tested using rsync 3.0.2, and it works fine (same file, same servers)
so the problem occursd using rsync 3.0.4
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=6175
Summary: write last transfer status when timeout or other error
happens
Product: rsync
Version: 3.0.5
Platform: Other
OS/Version: Linux
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #1 from ar...@maven.pl 2009-03-08 06:14 CST ---
Ah, that was rsync -avPc.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #2 from m...@mattmccutchen.net 2009-03-08 20:05 CST ---
Rsync does leave the progress line on the screen, but ssh is printing the
Timeout, server not responding message that overwrites it. Rsync could
simply reprint the
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #3 from way...@samba.org 2009-03-08 21:52 CST ---
3.1.0 keeps the cursor at the end of the line, so ssh can't overwrite it. Is
there something else to fix here?
--
Configure bugmail:
https://bugzilla.samba.org/show_bug.cgi?id=6175
--- Comment #4 from m...@mattmccutchen.net 2009-03-08 22:03 CST ---
(In reply to comment #3)
3.1.0 keeps the cursor at the end of the line, so ssh can't overwrite it. Is
there something else to fix here?
You're right. Looking at
https://bugzilla.samba.org/show_bug.cgi?id=6169
Summary: Syntax Error in runtests.sh ssh-basic.test script
Product: rsync
Version: 3.0.5
Platform: x86
OS/Version: Other
Status: NEW
Severity: minor
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=6169
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Mon, Feb 16, 2009 at 02:54:36PM +0100, dr...@wp.pl wrote:
overflow: xflags=0x7a l1=255 l2=779
This is the error rsync gives when the file and path exceed the
MAXPATHLEN size for your system. The receiver updates all the files
from the base of the transfer, so the names need to fit within
/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations
dr...@wp.pl [receiver]
dr...@wp.pl ERROR: buffer overflow in recv_file_entry [receiver]
dr...@wp.pl rsync error: error allocating
/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations/animations
[receiver]
ERROR: buffer overflow in recv_file_entry
: rename /home/.aquota.user.cXUky1 - home/aquota.user:
Operation not permitted (1)
Could this error be the cause of the problem ?
If so, how can I overcome this ?
Thank you :)
Joao
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
: rename /home/.aquota.user.cXUky1 - home/aquota.user:
Operation not permitted (1)
Could this error be the cause of the problem ?
If so, how can I overcome this ?
Thank you :)
Joao
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
rsync error on two test www.dwhs.net servers
rsync error: error in rsync protocol data stream (code 12) at io.c(359)
Also both of these two servers have locked out all root access remitly. I
dont think they have been hacked, but I can seem to get access without going
in single user and adding
https://bugzilla.samba.org/show_bug.cgi?id=6027
--- Comment #6 from m...@mattmccutchen.net 2009-02-05 21:14 CST ---
Looks good.
As for comment #3: on Linux, each filesystem implements independent
follow_link and readlink functions, so when you follow a symlink, the
filesystem can
the check to where it would
only affect the sending of the file list to the receiver.
I have checked in a fix to prevent a fatal error for a 0-length symlink.
As for you comment #3, I am missing what you are driving at. If readlink()
doesn't work on a symlink, how can something read the link
https://bugzilla.samba.org/show_bug.cgi?id=6027
--- Comment #4 from m...@mattmccutchen.net 2009-01-31 00:17 CST ---
Thoughts on comment #3?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA
/
or
rsync /cygdrive/c/
--
Stuart Halliday
-Original Message-
From: Jignesh Shah jignesh.shah1...@gmail.com
To: Stuart Halliday stua...@ecs-tech.com
Date: Tue, 20 Jan 2009 16:18:25 +0530
Subject: Re: find out the meaning of rsync error code
Thanks Sven and Stuart
-
From: Jignesh Shah jignesh.shah1...@gmail.com
To: Stuart Halliday stua...@ecs-tech.com
Date: Tue, 20 Jan 2009 16:18:25 +0530
Subject: Re: find out the meaning of rsync error code
Thanks Sven and Stuart for reply.
They both are running at the same version 2.6.0 but still it gives
same
I'd recommend that you do a search on the failing systems for duplicate or
old copies of Rsync. It just takes a PATH variable to include another old
copy of rsync to make it fail.
I'd also check your firewall or router aren't the problem. If you need to,
temporary disable the firewall or any AV
On Tue, Jan 20, 2009 at 10:16:37AM +, Stuart Halliday wrote:
I suggest that this may be caused by you using two different versions of
Rsync? Please check that the daemon and client are running the same version.
The only known issues of cross-version incompatibility have been fixed.
If you
On Tue, Jan 20, 2009 at 03:25:05PM +0530, Jignesh Shah wrote:
In rsync return code: 12 error, what 12 indicates?
The error code is pretty inconsequential compared to the errors that
come before it. See what rsync is actually complaining about, and make
sure you know if there is an issue
Hi,
Please let me know what what could be the cause of below error:
ERROR: DoRsync(): rsync had errors or failed
rsync return code: 12
unexpected tag -7
rsync error: error in rsync protocol data stream (code 12) at io.c(469)
rsync: connection unexpectedly closed (3941538 bytes
Hi,
Could anyone please tell me how to get the meaning of rsync error codes.
In rsync return code: 12 error, what 12 indicates?
Thanks,
Jignesh
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman
Tue, 20 Jan 2009 15:25:05 +0530, jignesh.shah1980 wrote:
Could anyone please tell me how to get the meaning of rsync error codes.
In rsync return code: 12 error, what 12 indicates?
Please use the archive:
http://www.mail-archive.com/rsync@lists.samba.org/msg22890.html
pgpEalpvdwL2E.pgp
See bottom of Man page @ http://www.samba.org/ftp/rsync/rsync.html
EXIT Values 12 is:
Error in rsync protocol data stream
I suggest that this may be caused by you using two different versions of
Rsync? Please check that the daemon and client are running the same version.
--
Stuart Halliday
/
--
Stuart Halliday
-Original Message-
From: Jignesh Shah jignesh.shah1...@gmail.com
To: Stuart Halliday stua...@ecs-tech.com
Date: Tue, 20 Jan 2009 16:18:25 +0530
Subject: Re: find out the meaning of rsync error code
Thanks Sven and Stuart for reply.
They both are running
...@gmail.com
To: Stuart Halliday stua...@ecs-tech.com
Date: Tue, 20 Jan 2009 16:18:25 +0530
Subject: Re: find out the meaning of rsync error code
Thanks Sven and Stuart for reply.
They both are running at the same version 2.6.0 but still it gives
same error. It was working fine since months
https://bugzilla.samba.org/show_bug.cgi?id=6032
--- Comment #4 from m...@mattmccutchen.net 2009-01-15 18:02 CST ---
That is strange, but the output does seem to indicate pretty clearly that rsync
is not the thing closing the connection. It's possible that the file is
triggering a
https://bugzilla.samba.org/show_bug.cgi?id=6027
Summary: Error when rsync encounters empty symlinks
Product: rsync
Version: 3.0.4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=6027
--- Comment #1 from way...@samba.org 2009-01-13 13:53 CST ---
Created an attachment (id=3872)
-- (https://bugzilla.samba.org/attachment.cgi?id=3872action=view)
Don't send a symlink with an empty target name
This patch should fix the
https://bugzilla.samba.org/show_bug.cgi?id=6032
Summary: error in rsync protocol data stream
Product: rsync
Version: 3.0.4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
https://bugzilla.samba.org/show_bug.cgi?id=6032
--- Comment #1 from rm...@lexiconn.com 2009-01-13 22:06 CST ---
Created an attachment (id=3875)
-- (https://bugzilla.samba.org/attachment.cgi?id=3875action=view)
rsync-debug output (last 200 lines)
This is the last 200 lines from the
different patch:
https://mattmccutchen.net/rsync/rsync.git/commitdiff/7c18847f1608618134ffd166d97952177502d998
The place where the code is hooked is a matter of taste; I preferred to catch
the invalid data as soon as possible to avoid any potential surprises. On the
other hand, the error message
. More generally, what if readlink returns an error but the symlink
can be followed?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the QA contact for the bug, or are watching the QA contact.
--
Please use reply
https://bugzilla.samba.org/show_bug.cgi?id=6032
m...@mattmccutchen.net changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=6032
--- Comment #3 from rm...@lexiconn.com 2009-01-13 23:26 CST ---
ok, just seems strange that the rsync fails every time on the same
dovecot.patched.tar.gz file. Any pointers on how to t/s would be appreciated.
--
Configure bugmail:
=/nslu2/rsync.log line is present.
BTW; how can an error such as this be 'unexpected'? The tag '93' must
mean something? Why can't the error handler be more specific about
what caused this? At least some information in a client-server
environment on which side generated the protocol error would help
/rsync-files
/share/hdd/data/public/Ernst/ 192.168.1.69::rsync-nslu2 /nslu2/rsync.log
(i.e. omit the --log-file= parameter and generate a log by redirection)
all is well again. The moment I add the --log-file= parameter, the error pops
up again.
The weird thing is that a search with Google
On Thu, 2008-12-11 at 23:19 +0100, Matthias Meyer wrote:
Where I can find a list of the error codes and their meanings?
Especially I have troubles because of:
pre-xfer exec returned failure (32256) in Win XP SP3
pre-xfer exec returned failure (65280) in Vista
Those codes are coming from your
Hi,
Where I can find a list of the error codes and their meanings?
Especially I have troubles because of:
pre-xfer exec returned failure (32256) in Win XP SP3
pre-xfer exec returned failure (65280) in Vista
Thanks
Matthias
--
Don't panic
--
Please use reply-all for most replies to avoid
task fails to transfer a file with compress (z) but
doesn't fail without this argument. My frame of time for transfers is
reduced and, at this moment, I'd need compress.
Anybody knows why or how to solve it? Is compress the random problem? Could
be a programming bug?
This error happen with compress
be a programming bug?
This error happen with compress but not always.
Where can I find values for --compress-level parameter?
I hope to have explained it.
Thanks in advance, Miguel.
I've this feature too.
In my experience you have no chance. -c did not work on windows clients
Good Afternoon,
I have been looking for a comprehensive list of error codes that are returned
by rsync for a script that I am writing. I have searched Ggoogle and Yahoo!
and I have found out the following:
4 = action not supported
5 = wrong password
10 = socket IO error
11 = file IO error
12
will return 255 if an error occurred and I have seen this
exit code returned by rsync when there is an ssh error. Can anyone
confirm whether rsync is actually passing through the error code from
ssh, or if there is some other undocumented reason for it returning
255? Are there any other codes that might
2008/11/19 John Macon [EMAIL PROTECTED]:
Good Afternoon,
I have been looking for a comprehensive list of error codes that are
returned by rsync for a script that I am writing. I have searched Ggoogle
and Yahoo! and I have found out the following:
4 = action not supported
5
or half an hour and returns the following error
message:
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
_
Express yourself
301 - 400 of 1491 matches
Mail list logo
