[Bug 12522] [PATCH] Send last error messages to sender

2020-05-26 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=12522 Ben RUBSON changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 12522] [PATCH] Send last error messages to sender

2018-02-13 Thread just subscribed for rsync-qa from bugzilla via rsync
solete|| --- Comment #3 from Ben RUBSON <ben.rub...@gmail.com> --- Created attachment 13959 --> https://bugzilla.samba.org/attachment.cgi?id=13959=edit Send last error messages to sender Modified patch to seamlessly suit rsync 3.1.3. Thx ! -- You are rece

[Bug 12522] [PATCH] Send last error messages to sender

2017-01-18 Thread samba-bugs
solete|| --- Comment #2 from Ben RUBSON <ben.rub...@gmail.com> --- Created attachment 12841 --> https://bugzilla.samba.org/attachment.cgi?id=12841=edit Send last error messages to sender Error correction on sender side. -- You are receiving this mail because:

[Bug 12522] New: [PATCH] Send last error messages to sender

2017-01-16 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=12522 Bug ID: 12522 Summary: [PATCH] Send last error messages to sender Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal

[Bug 10445] New: flag to suppress link_stat error messages

2014-02-13 Thread samba-bugs
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

[Bug 10445] flag to suppress link_stat error messages

2014-02-13 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10445 michele m...@bitchx.it changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: Error messages 3.0.6pre1

2009-07-23 Thread Warren Oates
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

Re: Error messages 3.0.6pre1

2009-07-22 Thread Mac User FR
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 with it.

Re: Error messages 3.0.6pre1

2009-07-21 Thread Warren Oates
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 a

re: Error messages 3.0.6pre1

2009-07-20 Thread Mark Cohen
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 for

Re: Error messages 3.0.6pre1

2009-04-25 Thread Wayne Davison
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

Error messages 3.0.6pre1

2009-04-17 Thread Warren Oates
I compiled 3.0.6pre1, including the crtimes and fileflags patches for use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here: http://www.bombich.com/mactips/rsync.html I want to use 3.0.6 because it seems that this bug: https://bugzilla.samba.org/show_bug.cgi?id=5365 has been

Error messages 3.0.6pre1

2009-04-17 Thread Warren Oates
[sorry if this appears twice -- I'm having trouble with my Gmail filters] I compiled 3.0.6pre1, including the crtimes and fileflags patches for use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here: http://www.bombich.com/mactips/rsync.html I want to use 3.0.6 because it seems

DO NOT REPLY [Bug 3245] improve rsync's error messages to make them clearer

2008-10-02 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3245 --- Comment #1 from [EMAIL PROTECTED] 2008-10-02 21:09 CST --- Yes, the code 23 message was bad. It has been improved: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1040) [sender=3.0.4]

Newbie can't figure out error messages

2007-01-16 Thread John Jason Jordan
copy the files to the /laptop folder on the USB drive. That is, Windows Explorer sees the files there, so I know I have copied the files there and not just to the /media/smb mount point. However, I get a lot of error messages like the following (chosen at random): rsync: mknod /media/smb/laptop/dev

Re: Newbie can't figure out error messages

2007-01-16 Thread Matt McCutchen
On 1/16/07, John Jason Jordan [EMAIL PROTECTED] wrote: I am trying to use rsync to create a mirror of my Linux laptop (Ubuntu Dapper amd-64) onto a USB drive hanging on a Windows 2000 desktop over ethernet. rsync: mknod /media/smb/laptop/dev/.static/dev/.static/dev/rfcomm74 failed: Operation

[Bug 3245] New: error messages not precise enough

2005-11-06 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3245 Summary: error messages not precise enough Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3

[Bug 3220] list of error messages

2005-10-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=3220 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

No error messages in rsyncd log in 2.6.1pre-1

2004-04-27 Thread John Van Essen
(As I was composing this, the 2.6.1 release notice on the rsync list rolled in. The quoted source, below, hasn't changed, so I'll leave the 'pre-1' references unchanged...) I have a situation where an error message seems to be sent from the daemon to the client, but none is logged in the

Re: No error messages in rsyncd log in 2.6.1pre-1

2004-04-27 Thread Wayne Davison
On Tue, Apr 27, 2004 at 05:15:25AM -0500, John Van Essen wrote: There was a change to rwrite() that seems to be preventing the error logging. Yes, you're right -- 2.6.0 changed this to make more errors go to the user and fewer to the log file. Neither the old behavior nor the new is really the

Error Messages

2002-05-31 Thread Scott Sipe
Hi, I'm using rsync to backup files from a file server at an office to a remote location. The office connection is a DSL line (fairly slow--40KB/s avg) that is NAT'd through an OpenBSD 3.1 box. The rsync server is behind the NAT box with a private address of 10.1.1.3. Using pf I expose the

Error messages

2002-05-06 Thread Jennifer Lu
Hi, We ran 2.5.5 rsync version between Sun-OS 5.8 and Sun-OS 5.6, and kept getting error messages - partial transfer (code 23) at main.c(925), The job completed, but with this error? Can you please help? Thanks, Jennifer -- To unsubscribe or change options: http://lists.samba.org

Re: Error messages

2002-03-08 Thread Dave Dykstra
area should work on all SunOS 5.5.1 and later, yes. - Dave Dykstra On Tue, Mar 05, 2002 at 01:55:58PM -0800, Jennifer Lu wrote: Hi, We got the following error messages when we ran rsync 2.5.2 from Solaris-5.5.1 to Solaris-5.8. vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/systop.v

List of rsync output / error messages

2002-02-06 Thread Joseph Annino
Is there a good place to get information about the list of all possible output and error messages rsync generates? Or should I just muck around the source code (which I haven't looked at yet) and find them? I am doing something where I would like to parse rsync's output using Perl into a set

Re: List of rsync output / error messages

2002-02-06 Thread Alberto Accomazzi
Joseph, check out the header file errcode.h in the rsync distribution. That file and the structure found in log.c map the system exit codes to the error messages you refer to, so the best way to programmatically catch errors is simply to check the exit status returned by rsync. -- Alberto

no error messages on I/O errors

2001-11-03 Thread Ian! D. Allen [NCFreeNet]
rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending