similar to: ERROR: out of memory in flist_expand on Tru64 UNIX

Hello list, I get the following error using rsync 3.0.3 (both sides): ... data/xxxxxxxx/admin_docs/2/8/9/9/0/7/9/msg-75682-748.msg is uptodate data/xxxxxxxx/admin_docs/2/8/9/9/0/8/0/msg-75682-749.txt is uptodate ERROR: out of memory in flist_expand [generator] rsync error: error allocating core memory buffers (code 22) at util.c(117) [generator=3.0.3] rsync error: received SIGUSR1

Hi, I have been using rsync for years to perform my backups, but since a few days it crashes with an "out of memory" error. I am running Ubuntu 11.04/x86_64, which ships rsync-3.0.8, and I have also tried with the git version. I can see the following messages: [generator] expand file_list pointer array to 524288 bytes, did move [generator] expand file_list pointer array to 1048576

Hi, I have just downloaded the SunOS version of rsync from ftp://rsync.samba.org/pub/rsync/binaries/Sunos/ When I run it on my machines I get the following error message ./rsync -xr /usr /mnt ERROR: out of memory in flist_expand rsync error: error allocating core memory buffers (code 22) at util.c(232) There is free memory on the system. Thankis, joe. -------------- next part

Available now from samba.org and all mirrors. Please report bugs, compilation problems, etc. If there are no major issues I think I will put this out as 2.5.3 shortly, because it fixes a few serious issues. Thanks to everybody who contributed patches. rsync://samba.org/rsyncftp/preview/rsync-2.5.3pre1.tar.gz\* rsync 2.5.3 (not released yet) SECURITY FIXES: * Make sure that

We are experiencing problems with Adobe Photoshop and Samba, all versions up to 2.0.6. We run Samba off Compaq Alphaservers (ie 64 bit). Symptoms: 1) On doing a "Save As" in Photoshop, we intermittently get: "Could not save as F:\<filename> because the file is already in use or was left open". A zero length file is left on the Samba share. 2) Problem only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try also removing --delete-excluded. Without those two options there should be no reason for rsync to require gigs of RAM. Well, unless the other system has rsync 2.x. On 03/27/2015 07:29 AM, Aron Rotteveel wrote: > Yes, I removed "--no-inc-recursive", without success. > > -- Best regards / Met vriendelijke groet, > >

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try it without any --delete options. On 03/27/2015 09:31 AM, Aron Rotteveel wrote: > I am now running with --delete --numeric-ids --relative but the > problem still persists. > > -- Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net >

OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch to 3.4p1. Partial success, in that it now works for me for logins to "root". Logins to ordinary accounts fail after authentication, when trying to set tty characteristics. See the excerpt from the debug messages below. This is for Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time

Hello again, I encountered something amazing. First I thought there is not enough memory allowed through ulimit. ulimit is now set to (almost) 512MB but rsync still gets out fo memory at 8MB. Can anyone tell me why? That's my configuration: rsync version 2.6.2 from AIX 5.3 to SuSE Linux 9 (also has rsync 2.6.2) ulimit -a (AIX) ulimit -a AIX (source): -------------------------

Hi, I use previous 4.4 version on my two Compaq AlphaServer systems. Is there a chance that CentOS 5 will also become available for Alpha? Thanks, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hi- Since the tru64 patch was designed for -current, I thought I would try to build it with a recent snapshot before backporting to 3.4p1. So I downloaded openssh-SNAP-20020826.tar.gz frpm the portable snapshots, but it does not contain the 'configure' script. I tried copying the 'configure' from 3.4p1, but that does not create a Makefile from the Makefile.in. Where are the

We are using rsync to maintain a warm mirror of our boot disks. I just updated to rsync 2.6.0 and noticed that the rsync runs are now getting errors when copying sockets. The system is running Tru64 5.1A pk 4 on an AlphaServer 4100. Is this a bug? Is there some way to not copy sockets or should I find all of them and add them to the exclude file? rsync was built using a straight ./configure

Hi Toni, I'm sorry, I haven't had much time to work on this today. When I run sshd (from the patched snapshot) in a debugger, with a breakpoint early in setup_sia(), this is what I find after connecting with a client: (1) There are two sshd processes. One is running as root, and the other as the user I logged with using the client. The root process is the one in the debugger,

Hello. I'm hoping that you will provide some help with a Samba problem that I'm experiencing. We have an Alphaserver that has been functioning as the Samba-server in a Windows/NT Domain for about 5 years now. It was set up by an engineer here at Raytheon Missile Systems Company and he left the company about 2 years ago. I've inherited the administration of it. Last week

Hello, I'm building rsync on an AIX 6.1.9.6 host. I would like to build it so it has 64-bit inums enabled but have not been able to figure out how to enable this feature. Can someone please provide me with some guidance on how do do this? This is my current build: -bash-4.3$ /usr/local/bin/rsync --version rsync version 3.1.2 protocol version 31 Copyright (C) 1996-2015 by Andrew Tridgell,

I am just looking for a quick answer as to whether or not OpennSSH is compatible with Digital Unix Tru64 v 4.0F. Hing Fei Wong Systems Engineer Building 100, M1309 Valley Forge, PA Admin # 4-6242 -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Friday, June 23, 2006 3:53 AM To: Wong, Hing Fei Cc: www at openbsd.org Subject: Re: OpenSSH compatibility with

Hi, I am experiencing segfaults when transferring files via rsync though sudo. Setup: - Backupserver initiates the rsync command with --delete -vvv --no-inc-recursive --numeric-ids --delete-excluded --relative --rsync-path=/home/backupuser/rsync-wrapper.sh - rsync-wrapper.sh (on the client) contains /usr/bin/sudo /usr/bin/rsync "$@"; - user "backupuser" has sudo access to the

http://bugzilla.mindrot.org/show_bug.cgi?id=1104 Summary: Compile error "ldLL" not declared in strtonum.c under Tru64 Unix 4.0f Product: Portable OpenSSH Version: 4.2p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: critical Priority: P2 Component: Build system

I am now running with --delete --numeric-ids --relative but the problem still persists. -- Best regards / Met vriendelijke groet, Aron Rotteveel 2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Try also removing --delete-excluded. Without those two options there > should be no reason for rsync to require