info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory error while committing...


From: James Depaul
Subject: Re: Memory error while committing...
Date: Tue, 29 May 2007 16:02:05 -0600

I've asked the Unix Admin to bump up the security limits file for us as follows:

data = ""> rss = 131072
stack = 131072

I've tried it again after re-logging and the same error persists - giving up.

Is there another way: could I delete the file OUTSIDE of cvs and do some cleanup afterwards?! I really think the unusually large size of the file is the culprit here.

Advice will be welcome -

thanks,
james







-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Depaul <address@hidden> writes:

> We are using CVS 1.11.17 (client/server) on AIX 5.3
>
> I spoke with the server admin and he tells me that the OS is in good
> shape in case of heap size - see below. Do we need to specify some CVS
> admin parameters to increase the heap size that CVS is using on the
> system?
>
> Could someone comment please - we are still getting the same error
> while commiting:
> cvs [commit aborted]: out of memory; can not reallocate 33894405 bytes
>
> Here is the memory status on the box itself:
...elided...
>
> Suggestions would be welcome.
...elided...

Hi James,

It is my recollection that under AIX, there are per-user limits as to
how much memory a single process may consume. It may be that the user(s)
running. You may wish to have your system admin look at
/etc/security/limits but my recollection was that 256MB was the maximum
possible for data and stack to grow.

I don't have easy access to an AIX 5.x box right now, but a FreeBSD 4.11
box I have around here has an /etc/login.conf file wherein there are
attributes for various classes of users as to the cputime, datasize,
stacksize, memoryuse, openfiles, vmemoryuse and other similar knobs.

So, I would need to ask you if the problem is that your user is running
into a problem with allocating an additional 32MB because that user is
running close the the per-user limits imposed by the defaults set by
your administrator.

-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFGXFbBCg7APGsDnFERAniBAJ9hXraVM8A5JMClpkoh/lCptP9vEgCfRSxw
NAGVT4Mse3koT4qhaxNZUIY=
=vrhn
-----END PGP SIGNATURE-----


reply via email to

[Prev in Thread] Current Thread [Next in Thread]