search for: send_file_entri

Displaying 20 results from an estimated 36 matches for "send_file_entri".

Did you mean: send_file_entry
2005 Apr 21
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From admin@exovian.com 2005-04-21 08:46 ------- root@xxxx [~]# rsync -avz -e ssh /home/ xxxx@xxxxx:xxxx building file list ... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) This method
2004 Oct 21
0
[Bug 1959] New: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:
2004 Dec 02
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From maarten@xolphin.nl 2004-12-01 17:59 ------- Created an attachment (id=817) --> (https://bugzilla.samba.org/attachment.cgi?id=817&action=view) Debug information on 'other' side -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because:
2005 Feb 27
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-02-27 13:54 ------- To diagnose this bug further, I need a system-call
2005 Aug 24
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From wejn@box.cz 2005-08-24 05:19 ------- Strange, got this error with 2.5.7 when the destination "module" was read-only. 2.6.6 prints user-friendly info that the module is not writeable. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because:
2006 Feb 24
0
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #14 from aim1@westnet.com.au 2006-02-24 08:39 MST ------- I also had the same problem ocurring randomly on large file transfers between an IDE disk and a disk attached via USB2.0 using RedHat FC4 and rsync version 2.6.4 protocol version 29. Error messages are: "rsync: writefd_unbuffered failed to write 4 bytes: phase
2007 Feb 25
1
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #15 from george@imagine-com.com 2007-02-25 04:41 MST ------- Created an attachment (id=2309) --> (https://bugzilla.samba.org/attachment.cgi?id=2309&action=view) log error file rsync command and error massage. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail
2008 May 13
0
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #17 from kde@ost.com.sg 2008-05-13 05:25 CST ------- I experienced the same error when rsync to an external usb ide drive. When it happened, the system hanged. Following Andrew Morris with --bwlimit=8192 --timeout=600 setting got rid of system hanging. However, it causes rsync to abort after 600 seconds. The problem is due to
2006 Jul 30
3
DO NOT REPLY [Bug 3979] New: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=3979 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.8 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:
2011 Jun 25
11
[Bug 8265] New: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1]
https://bugzilla.samba.org/show_bug.cgi?id=8265 Summary: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1] Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: core AssignedTo:
2004 Oct 21
5
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-10-21 15:19
2003 Jul 24
0
(no subject)
Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---
2004 Mar 10
4
HFS+ resource forks: WIP patch included
As you all know, rsync doesn't have any special handling for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX and rsync_hfs, to address this gap, but they only work when the destination filesystem is also HFS+. I haven't been able to find any references to an rsync that is capable of syncing from HFS+ to UFS (etc). The only solutions I've seen involve lots of preprocessing
2003 Jun 17
2
rsync error: error in rsync protocol data stream (Broken pipe)
I'm experiencing some unexpected behavior with rsync v2.5.6. After looking around it seems like several people have experienced similar problems in the past, but those appear to be old bugs that are solved now. Also doesn't appear to be any direct bugfixes made for this issue since 2.5.6. The strange thing is that things seem to work when I use ssh for transport. However now I need to
2004 May 29
1
[patch] Filename conversion
Hi, One feature missing from rsync, and requested on this list before, is on-the-fly conversion of filename character encoding. For example, I often need to sync files having Hebrew filenames from a UTF-8 system (Linux) to an ISO8859-8 system (Cygwin on Windows 2000 using the non-Unicode Win32 interface). Other circumstances surely abound. Attached is a patch against rsync 2.6.2 that adds an
2003 May 17
1
flist transmission and sorting
Wayne, I've been ruminating a bit on the qsorted flist and duplicate removal and have an idea. What if we removed end_file_entry() from send_file_name() and instead had a for(i=0; i < flist->count; ++i) send_file_entry(flist->files[i], f, ??) in send_file_list(). As near as i can tell this would be unnoticeable to the protocol. Once done the sort of the file list could be
2004 Sep 03
1
more filelist --stats
The attached diff causes rsync to show how much time it spends on building and sending its filelist. I'd appreciate if you could consider this change for inclusion in a future release. -------------- next part -------------- diff -ru rsync-2.6.3pre1/flist.c rsync-2.6.3pre1+tykhe/flist.c --- rsync-2.6.3pre1/flist.c 2004-08-12 14:20:07.000000000 -0400 +++ rsync-2.6.3pre1+tykhe/flist.c
2006 Nov 10
1
Internal error: wrong write used in receiver.
Hi, I'm using 2.6.9 but I get: recv_files phase=1 generate_files phase=2 recv_files phase=2 recv_files finished generate_files phase=3 deleting in home delete_in_dir(home) [generator] make_file(home/administ,*,2) Internal error: wrong write used in receiver. _exit_cleanup(code=2, file=io.c, line=1204): entered _exit_cleanup(code=19, file=main.c, line=1182): entered rsync error: received
2007 Mar 14
0
rsync failing after file list
I've taken on some rsync jobs created by someone else and below is a description of the problem. It's pretty straight forward. - both server and client and Windows 2003 servers - there is no ssh between the 2 nodes - the sync was working well up until recently - there are no known changes that would cause the sync to stop working - the job syncs files from a directory that contains
2007 Mar 28
1
rsync patch -flags fails to compile on Mac OSX
I am trying to compile rsync 3.0.0cvs with the flags.diff patch on a Mac OSX G4. It fails because the flags UF_NOUNLINK, and SF_NOUNLINK do not exist on this platform. sys/stat.h only gives the following flags * Definitions of flags stored in file flags word. * * Super-user and owner changeable flags. */ #define UF_SETTABLE 0x0000ffff /* mask of owner changeable flags */ #define