search for: io_error_fd

Displaying 6 results from an estimated 6 matches for "io_error_fd".

2002 May 22
2
rsync: race condition can cause loss of diagnostic output
...h the end result being that they are seen by the user running rsync). - select() is used to call read_error_fd() only if there is stuff waiting to be read by it. - The select()/read_error_fd() combo is checked when the child reads and writes. - read_error_fd() only reads a single message from io_error_fd. The end result is that if multiple messages have accumulated, waiting and unread, on io_error_fd at the time the write_int() and io_flush() are called at the end of do_recv(), then only the first is handled by read_error_fd(). The rest get discarded. --------------------------------------------...
2003 Jan 10
5
working on a 2.5.6pre1 release
I'm working on trying to get rsync 2.5.6pre1 available for people to test more widely. I'm out of time for today, and I'm stuck on a problem that some machines on build.samba.org are showing on the 'chgrp' test. I can reproduce this on my home redhat 7.3 system too. It appears to be a timing problem because when I do strace -F -f on it the problem goes away. Everything seems
2003 Oct 03
2
Cygwin/rsync Hang Problem Testing Results
People of cygwin & rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a "get" (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going
2002 Jan 13
0
rsynd-2.5.1 / io.c patches
...2 +++ lcl_src:io.c Sat Jan 12 18:29:18 2002 @@ -1,3 +1,4 @@ +/* Converted by prj_src:unix_c_to_vms_c.tpu AND PRJ_SRC:IO.TPU on 12-JAN-2002 18:29:18.32 OPENVMS_AXP */ /* -*- c-file-style: "linux" -*- Copyright (C) 1996-2001 by Andrew Tridgell @@ -49,7 +50,7 @@ static int io_error_fd = -1; -static void read_loop(int fd, char *buf, int len); +static void read_loop(int fd, void *buf, int len); static void check_timeout(void) { @@ -163,9 +164,11 @@ * give a better explanation. We can tell whether the connection has * started by looking e.g. at whether the remote versi...
2001 Aug 22
1
@RSYNC EXIT / @RSYNC EOF
...t_io; -static int eof_error=1; +static int no_flush; + +extern int bwlimit; extern int verbose; extern int io_timeout; extern struct stats stats; + +/** Ignore EOF errors while reading a module listing if the remote + version is 24 or less. */ +int kludge_around_eof = False; + + static int io_error_fd = -1; static void read_loop(int fd, char *buf, int len); @@ -106,9 +113,46 @@ static void read_error_fd(void) } -static int no_flush; +static void whine_about_eof (void) +{ + /** + It's almost always an error to get an EOF when we're trying + to read from the network, because...
2005 Nov 18
12
[Bug 3271] New: Rsync instances stay in memory when using in daemon mode
https://bugzilla.samba.org/show_bug.cgi?id=3271 Summary: Rsync instances stay in memory when using in daemon mode Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: