similar to: [Bug 2654] timeout is always triggered with 2.6.4

Displaying 20 results from an estimated 600 matches similar to: "[Bug 2654] timeout is always triggered with 2.6.4"

2003 Jul 31
2
rsync 2.5.6 timeout bug
I've been getting frequent io errors trying to synchronise a local CPAN mirror with the master on ftp.funet.fi, the symptoms being the dreaded rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) message at the client end. I've replicated this when mirroring from a local CPAN mirror, and the issue seems to
2005 Apr 25
2
How about a --min-size option, next to --max-size
There's a rather old bug report in Debian's bug tracking system (see http://bugs.debian.org/27126) about wanting to be able to specify the maximum file size, as well as the minimum file size. Here's the text: Sometimes, it's useful to specify a file size range one is interested in. For example, I'd like to keep an up-to-date mirror of Debian, but I currently
2002 Feb 14
1
unexpected EOF in read_timeout (was Re[2]: [Fwd: Re: meaning of "IO Error: skipping the delete...."]])
This is where it sets a sort of 60 second timeout if you don't set a timeout at all. As far as what it affects, I'm not that good with the code. I just know that my big syncs would die in almost exactly 1 minute unless I specified a timeout, and then would die at that timeout until i got it very large. +++++++++++++++++++++++++++++++++++++++++++++++++++++ Tools@willy
2003 Apr 15
1
Two --bwlimit issues
Hi, I have two issues with the --bwlimit parameter to rsync which are not mentioned in the FAQ (please correct me if I am wrong): 1. When both an rsync client and an rsync daemon specify the --bwlimit parameter, the client's value overrides the server's value. This could be used in a DOS attack if the client uses a larger value than the server intended. The documentation also is
2002 Jul 02
1
Rsync: Segmentation fault
Rsync 2.5.5; transfer via ssh; sparc-sun-solaris2.5 (Ultra 1); gcc 2.8.1. Every time rsync on this box causes boundary violation. I attached two strange examples. I have a few rsync's corefiles (100MB and above) and I can examine them. I will be grateful for any help. -Mirek <-------------------------------------------------------------------------> received 966761 names done
2005 Apr 01
3
Rsync 2.6.4 Multiplexing Overflows when File Name Too Long (cwRsync)
I installed the newly released version of cwRsync today on a few Windows machines and have noticed a new problem that I have not seen mentioned anywhere. When syncing to an NT machine used for backups, my rsync client exited at the end of the transfer with the following message to standard error: multiplexing overflow 1:296 [sender] rsync error: error in rsync protocol data stream (code 12)
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:
2006 Apr 28
1
imaptest, with options!
I hacked some command line options into imaptest. I dont think I broke it.. Place into dovecot-source root as usual and compile with: gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H src/lib/liblib.a As per Timo's instructions. # imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX] [clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO] USER = template for
2001 Sep 05
2
Feedback on 2.4.7pre1
FYI, We've been using the 2.4.7pre1 release for several days now, with nary a hang problem. We haven't seen the EOF bug at all, which was what we upgraded for. This is with transfers of as much as 50GB to set up an initial mirror. The only thing we did was set timeout=0 -- which I guess is unnecessary. The semantics of this flag are a bit unclear. We thought was 'time since
2005 May 12
2
help me understand keepalive..
I'm not sure keepalive is working the way I think it's supposed to. Here's my test. I've got a large file (approx 1 gig) on the rsync server, and I append a character on the end to make it slightly different. I fire up rsync on the client side and everything works fine until I hit the timeout value. I have this problems when I have a timeout of below 90 seconds. I've tried
2020 Oct 12
2
samba AD problem after re-join domain
On 10/12/2020 4:06 AM, Rowland penny via samba wrote: > On 12/10/2020 02:54, Jason Keltz via samba wrote: >> I've been working on a Samba AD setup with a bunch of test machines - >> the one DC, and a bunch of clients. Last night, I ended up switching >> the name of the test machines temporarily (except the DC), and >> re-joining the domain (that's for another
2006 May 02
2
flash not shown
I am using the following code (inspired by one of the books) to check if the user''s session should have timed out. # Check to see if the user has been inactive for longer than the # expiry period. If they have, reset the session. def check_timeout if session[:expires_at] != nil @time_left = (session[:expires_at] - Time.now).to_i unless @time_left > 0
2013 May 27
6
[PATCH 0/3] Xen related fixes
Hi all, I have few simple fixes for Xen for the next release: - the first one fixes a regression in qemu-char; - the second one is just a cleanup (that is needed to simplify preprocessor dependencies); - the last one avoids setting nonblocking on Xen (as is already done for KVM). The last two patches should be backported to older branches. Stefano Stabellini (3):
2019 Jul 16
2
samba 4.8 client and 4.9 AD DC: Reducing LDAP page size from 1000 to 500 due to IO_TIMEOUT
Hello, I have an issue as stated in topic. My samba 4.8.3 file server, which is AD member frequently shows winbind errors (pasted below). From user perspective it seems to work fine, but I'm worried that I have something misconfigured and in the long run, I might run into some errors. My AD DC are running on samba 4.9.x (two of them), compiled from source with BIND as DNS backend (running on
2016 Jun 29
0
Rsync hung when applying batch file
Hello. On rsync, version 3.0.9 got this trouble, rsync hung when applying batch file: Sync all files from batch to asr_billing install: - skelet/cfg/ install: - skelet/etc/ install: deleting usr/lib/python2.6/site-packages/IPython/external/Itpl.pyc - deleting install: 100% 9.83MB/s - 0 install: 100% 51.39kB/s - usr/lib/python2.6/site-packages/dbfpy/utils.pyc install: 100% 86.10kB/s -
2016 Jun 29
0
Rsync hung when applying batch file
Hello. On rsync, version 3.0.9 got this trouble, rsync hung when applying batch file: Sync all files from batch to asr_billing install: - skelet/cfg/ install: - skelet/etc/ install: deleting usr/lib/python2.6/site-packages/IPython/external/Itpl.pyc - deleting install: 100% 9.83MB/s - 0 install: 100% 51.39kB/s - usr/lib/python2.6/site-packages/dbfpy/utils.pyc install: 100% 86.10kB/s -
2020 Oct 12
1
samba AD problem after re-join domain
On 12/10/2020 16:11, Jason Keltz wrote: > >> Hi Rowland, >> >> I did not leave the domain, but I did delete the entry by either the >> Windows AD tool or "samba-tool computer delete" option.? I can't >> remember which one at this point.? I think that clears up all the >> bits.? Is that correct?? On the local host, I also deleted the >>
2005 Apr 06
2
backup option
Hi, I have question about the behavior of --backup-dir with --delete-after option. In my testing with version 2.6.4, it appears that the backup option only backups altered files. Files that will be deleted on the destination system will NOT be placed in --backup-dir location. I would like to back up deleted files. Is there a way to do this? Thanks
2006 Apr 11
1
Double redirect
I have two before_filters for my application that both redirect. The first checks whether there is an active session and if so, whether it has timed out (a la the recipes book). This is run from ApplicationController. The second filter is in use throughout most of the app and checks to see whether the user has the correct credentials to view the controller. This is run from individual
2004 Feb 13
1
possible bug?
A google search on this problem did not show any matches, so I'll take the chance that someone on this list might consider it an rsync problem. In a nutshell, if rsync forks a child process to handle the transport (rsh in this case) it can hang in wait_process() forever waiting for that child process to die. Normally this would not be a problem. However, if the wrong packet is dropped