search for: select_timeout

...a timeout, and then would die at that timeout until i got it very large. +++++++++++++++++++++++++++++++++++++++++++++++++++++ Tools@willy /users/Tools/encap/src/rsync-cvs>grep -i timeout *.c |grep -i select io.c:/* if no timeout is specified then use a 60 second select timeout */ io.c:#define SELECT_TIMEOUT 60 io.c: tv.tv_sec = io_timeout?io_timeout:SELECT_TIMEOUT; io.c: tv.tv_sec = io_timeout?io_timeout:SELECT_TIMEOUT; Tools@willy /users/Tools/encap/src/rsync-cvs> +++++++++++++++++++++++++++++++++++++++++++++++++++++ I last tested and saw the problem with a 2.4.6 with a bunch...

...to the client but before the client has started transferring files. Despite what the documentation says about the default IO timeout being infinite (0), inspection of the code would seem to indicate otherwise: [io.c] /** If no timeout is specified then use a 60 second select timeout */ #define SELECT_TIMEOUT 60 : tv.tv_sec = io_timeout?io_timeout:SELECT_TIMEOUT; tv.tv_usec = 0; I haven't crawled through the initialisation code to find out exactly how io_timeout gets set, but examination of rsync in daemon mode with a debugger reveals that it is using a timeout of 60 seconds when no --timeout is...

...20 PM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: rsync@lists.samba.org Subject: Re: Re[2]: unexpected EOF in read_timeout (was Re[2]: [Fwd: Re: meaning of "IO Error: skipping the delete...."]]) Classification: I'm not sure whether the SELECT_TIMEOUT issue is relevant to this thread or another one, but it's good to know that you haven't seen the problem since 2.5.0 where Tridge put in a fix. It is still waking up from select every 60 seconds, but it doesn't exit now if --timeout is 0. I'm not sure why it bothers wake up, but...

I have just been upgrading my Samba servers from 1.9.18p10 to 2.0.6 So far as I can tell users have been happy (or at least not noticed!). Our clients are almost exclusively NT 4.0 (most at SP5). Our servers are Suns running Solaris 2.5.1 and 7. On upgrading 2 of our busier servers (for admin - home directories and NT binaries), I observed a considerable increase in server load. Home server

Hi I use rsync to perform backup on disk on a SunFire 880 with Solaris 8. For performance issues, we launch simultaneously 5 rsyncs on 5 different fliesystems and about 150-200 "cp -p" commands on as many database files. We have been using the same scripts for about 2 months, without problems. The backup is performed on the same server (from filesystem to filesystem on the same

...SCII test page" command from the printer utility: I [11/Nov/2005:12:58:36 +0100] [Job 5] Connecting to dymo-labelwriter.local on port 631... I [11/Nov/2005:12:58:36 +0100] [Job 5] Unable to connect to dymo-labelwriter.local, queuing on next printer in class... d [11/Nov/2005:12:58:37 +0100] select_timeout: 86400 seconds to browse timeout a printer Soooo, the issue obviously resided in CUPS not being able to connect to port 631 on the MacOSX machine. This is where it got interesting, as I checked the MacOSX machine and that port was open (listing "IPP" as port-listener). Doing a remote...

Howdy, We occassionally get the following error when running our nightly backups: rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) This happens more on one or two machines than on any of the others. We've looked high and low to see if we're mistakenly sending these signals, but nothing is that we can find. Does anyone know what this might be from? Is it the server

Hi, I have some files size 400MB+ that my rsync ends on, error message is : "Write failed: Broken pipe". Without this "big files" everything works smoothe. I searched to find anything about this problem but so far without any luck. Source machine : Solaris 8, rsync-2.4.6 Destination machine : FreeBSD 4.1.1, rsync 2.4.6 Command run(from source machine): rsync

https://bugzilla.samba.org/show_bug.cgi?id=5478 Summary: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32) Product: rsync Version: 3.0.3 Platform: Other URL: https://bugzilla.samba.org/show_bug.cgi?id=1959 OS/Version: Linux Status: NEW Severity: normal

...3:09 -0000 1.131 --- io.c 12 Jul 2004 00:37:48 -0000 *************** *** 56,61 **** --- 56,63 ---- extern int eol_nulls; extern char *remote_filesfrom_file; extern struct stats stats; + extern int batch_fd; + extern int write_batch; const char phase_unknown[] = "unknown"; int select_timeout = SELECT_TIMEOUT; *************** *** 674,679 **** --- 676,688 ---- total += ret; } + if (write_batch && !am_sender) { + if (write(batch_fd, buffer, total) < 0) { + close(batch_fd); + exit_cleanup(RERR_FILEIO); + } + } + stats.total_read += total; } ******...

.../io.c 2009-03-13 18:46:39.000000000 +0200 +++ rsync-3.0.6.fast/io.c 2009-09-23 12:26:40.000000000 +0300 @@ -29,6 +29,7 @@ #include "rsync.h" #include "ifuncs.h" +#include <linux/socket.h> /** If no timeout is specified then use a 60 second select timeout */ #define SELECT_TIMEOUT 60 @@ -1722,6 +1723,82 @@ writefd(f, str, len); } +int send_fd(int socket, int fd_to_send) +{ + struct msghdr message; + struct iovec iov[1]; + struct cmsghdr *control_message = NULL; + char buffer[CMSG_SPACE(sizeof(int))], data[1]; + int ret; + + memset(&message, 0, sizeof(struct msghdr)...

This is my first post so first of all I will say hello to everyone. I have rsync configured and working properly on my local network however when I try to connect from a remote host (one located in a different state) the connection times out. I was wondering if there was another way to set the timeout besides in the rsyncd.conf file? As I said the connection works fine on the internal lan, but

...ght (C) 2001 by Martin Pool <mbp@samba.org> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -28,18 +29,24 @@ /* if no timeout is specified then use a 60 second select timeout */ #define SELECT_TIMEOUT 60 -extern int bwlimit; - static int io_multiplexing_out; static int io_multiplexing_in; static int multiplex_in_fd; static int multiplex_out_fd; static time_t last_io; -static int eof_error=1; +static int no_flush; + +extern int bwlimit; extern int verbose; extern int io_timeout; extern...

...ss.c:797 type = 37 outsize = 0 msg_type = 0 #22 0x080d618b in process_smb (inbuf=0x40483008 "", outbuf=0x404a4008 "") at smbd/process.c:897 trans_num = 28 msg_type = 0 len = 1176 nread = 1180 #23 0x080d6f05 in smbd_process () at smbd/process.c:1328 deadtime = 604800 select_timeout = 60000 num_echos = 0 last_timeout_processing_time = 1075937457 num_smbs = 28 total_buffer_size = 132161 #24 0x08256fd7 in main (argc=2, argv=0xbffffe04) at smbd/server.c:887 is_daemon = 1 interactive = 0 Fork = 1 log_stdout = 0 ports = 0x0 opt = -1 pc = 0x82f3f38 long_options = {{longN...

Hi: I'm in the middle of recoverying from a tactical error copying around an Mac OS X 10.10.5 Time Machine backup (turns out Apple's instructions aren't great...), and I had rsync running for the past 6 hours repairing permissions/acls on 1.5 TB of data (not copying the data), and then it just died in the middle with: .L....og.... 2015-03-11-094807/platinum-bar2/usr/local/mysql

...'ve heard of others running much larger distributions. Incidentally, from this test, it's plain that the old false timeout problem, where one process waiting for another to finish its work would timeout and stop the run, even though the other threads were still working, at the 60-second select_timeout value that is set when no io_timeout is set, is fixed in this version. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ starting /bildmax/bildmax2 at Wed Oct 31 02:42:46 PST 2001 readlink b...

...0] [Job 9] GIMP-PRINT: Image_width 3060 I [28/Dec/2004:12:05:40 -0500] [Job 9] Ready to print. I [28/Dec/2004:12:05:40 -0500] [Job 9] Attempting to connect to host 192.168.0.1 9 for printer raw d [28/Dec/2004:12:05:40 -0500] PID 7523 exited with no errors. d [28/Dec/2004:12:05:41 -0500] select_timeout: 11 seconds to process active jobs And here are some packets from the end of the Shorewall log just AFTER I tried to print (above). Note that the rejected packets occurred before the print job, and none during or after. Dec 28 11:54:38 rfc1918:DROP:IN=eth0 OUT= SRC=10.0.0.1 DST=255.255.255....

...tsize = 0 msg_type = 0 #17 0x807bc85 in process_smb (inbuf=0x81c9271 "", outbuf=0x81d96b9 "") at smbd/process.c:856 outbuf = 0x81d96b9 "" trans_num = 65 msg_type = 0 len = 268 nread = 272 #18 0x807c43f in smbd_process () at smbd/process.c:1240 deadtime = 604800 select_timeout = 60000 num_echos = 0 last_timeout_processing_time = 994072883 num_smbs = 62 #19 0x804c40a in main (argc=2, argv=0xbffffd34) at smbd/server.c:801 argc = 2 argv = (char **) 0xbffffd34 is_daemon = 1 specified_logfile = 0 port = 139 opt = 0 #20 0x40056790 in __libc_start_main (main=0x804be10...