similar to: rsync-2.5.5 memory eater problem

The first rsync-2.5.6 pre-release version is now available at: http://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz ftp://rsync.samba.org/pub/rsync/preview/rsync-2.5.6pre1.tar.gz rsync://rsync.samba.org/ftp/rsync/preview/rsync-2.5.6pre1.tar.gz There's also a corresponding '.sig' file that contains a gpg signature of the file; the public key is available on the

(I am not on the rsync mailing list, so if you send a response to this message to the list, please be sure to CC me.) I first reported this bug go Red Hat in <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>. If you run rsync with a subshell through ssh.com's ssh and sshd and then kill the client with ctrl-C, the rsync server process running on the remote machine grows

HI, patches/xattrs.diff repeats the man-page change from patches/slp.diff producing an error if you try to apply both patches. -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux Fatou 2.6.25-rc8-12-default #1 SMP 2008-04-02 01:36:51 +0200 x86_64 Key

HI, rsync-3.0.2 with patches/acls.diff,patches/xattrs.diff,patches/slp.diff fails (most of the time) in the itemize test: ----- itemize log follows Testing for symlinks using 'test -h' makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/foo makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/bar/baz cd+++++++++ ./ cd+++++++++ bar/

After upgrade from previous version I can't run rsync. 2004/05/09 10:40:54 [18630] rsyncd version 2.6.2 starting, listening on port 873 2004/05/09 10:40:54 [18630] rsync error: error in socket IO (code 10) at socket.c(466) strace shows that there is problem with listen() I've found patch on this lists: --- rsync-2.6.2/socket.c.orig 2004-05-08 23:25:11.979473336 +0200 +++

Hello, There is still a problem with the _exit_cleanup() function in cleanup.c despite the patch that was put in last week that prevented recursion. It turns out that sometimes multiple calls in close sequence are done and this causes rsync to spin out of control instead of exiting. This bug was found by Marc Espie and the patch I'm including is his as well. It hasn't been commited

seems the behavior of rsync has changed when dealing with output and using both -v and -q at the same time ... for example: $ mkdir test1 $ touch test1/foo $ rsync-2.6.0 -avq test1 test2 $ rm -r test2 $ rsync-2.6.8 -avq test1 test2 test1/ test1/fo $ rm -r test2 $ rsync-cvs -avq test1 test2 building file list ... test1/ test1/fo $ rm -r test2 the new output in 2.6.8 comes from the calls to

-----BEGIN PGP SIGNED MESSAGE----- I added the following code to log_exit(): void log_exit(int code, const char *file, int line) { static int error_count=0; if(error_count++ > 10) { abort(); } To force it to bail earlier instead of overflowing the stack. As you can see at frame #50, it is trying to log that the connection went away unexpectantly.

In case others find this of value, I wrote a patch to rsync 2.5.6 to give rsync in --daemon mode the ability to run a pre-transfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script =

Hello, we have the following problem: - a new Dell Optiplex 740 boots pxelinux.0 - loads the kernel - start to load the miniroot.gz and crashs after loading about 1/5 of the miniroot The tftpd messages are: Feb 21 14:48:32 srv006 atftpd[26225]: Advanced Trivial FTP server started (0.7) Feb 21 14:48:32 srv006 atftpd[26225]: Serving /linux/pxelinux.0 to 10.10.100.113:2070 Feb 21 14:48:32 srv006

We have a 100 number indial range and every so often get fax calls on our voice numbers (our fax number isn't in the 100 number range). If you just hang up the sending fax will often try a few times before finally giving up. Our outgoing fax is connected to the PBX (not asterisk), and we can do a blind transfer to that which will print it out, but right now the fax is printing a misdialled

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

Hi list, I have tried to reach Bradley (author of mongrel_cluster) by mail, but have not gotten a response. So I''ll try trough this channel: I have ''developed''[1] a small extension to mongrel_cluster that allows selective restart of any one listener in a configuration that contains more than one listener by using a command like mongrel_rails

Hi I'm using Debian woody. ii smbfs 2.2.3a-12.3 mount and umount commands for the smbfs... I want to mount a W2K share as user. Mount as root works fine. The entry in /etc/fstab looks like this: //NOTEBOOK/D /notebook/D: smbfs user,username=ernohl,noauto 0 3 If I try to mount: erno@flinker:~$ mount /notebook/D: Password: cannot mount on /notebook/D:: Operation not permitted smbmnt

I noticed that there once was a rename command but it was removed. Do you know why? And is there a way to do it manually? Thanks! -- OStR Dr. R. Kupper Kepler-Gymnasium Freudenstadt Am Mittwoch, April 12, 2023 17:11 CEST, schrieb Gilberto Ferreira <gilberto.nunes32 at gmail.com>: > I think gluster volume rename is not available anymore since version 6.5. > > --- >

I have attached a patch that supports a new "--direct-write" option. The result of using this option is to write directly to the destination files, instead of a temporary file first. The reason this patch is needed is for rsyncing to a device where the device is full or nearly full. Say that I am writing to a device that has 1 Meg free, and a 2 meg file on that device is out of date.

QueryParser fails badly allocating enormous amount of memory when processing query strings with special/accented characters. See: irb(main):002:0> require ''rubygems'' irb(main):003:0> require ''ferret'' irb(main):004:0> include Ferret irb(main):005:0> index = Index::Index.new irb(main):008:0> index << "something" # Now the error

There are cases when a user might have multiple keys in ssh-agent, but wants to use a specific one. Unless I'm mistaken, this is currently impossible. I've put together a proof of concept using the key's "filename" (the third column in the output of 'ssh-add -l') and it works. Is this a new feature that would be accepted? If so, should the key be identified with its

With python 3, we have a nicer way to handle socket.error with errno set to EPIPE (or ESHUTDOWN). This is also more correct since in some cases (that I could not reproduce yet with v2v), using e[0] with BrokenPipeError will fail with: >>> OSError(errno.EPIPE, "Broken pipe")[0] Traceback (most recent call last): File "<stdin>", line 1, in <module>

On Thu, Aug 31, 2023 at 11:12:59AM +0200, Laszlo Ersek wrote: > On 8/31/23 10:02, Richard W.M. Jones wrote: > > > > On Wed, Aug 30, 2023 at 05:21:19PM -0500, Eric Blake wrote: > >> I hit another transient failure in libnbd CI when a poorly-written > >> eval script did not consume all of stdin during .pwrite. As behaving > >> as a data sink can be a