[Top][All Lists]

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

RE: CVS Tagging Terminated with fatal signal 11

From: Krishnamoorthy, Balaji
Subject: RE: CVS Tagging Terminated with fatal signal 11
Date: Tue, 30 Apr 2002 15:39:52 -0400

Thanks once again , infact i tried ulimit -v for checking on the limit of 
virtual memory . Following is the output for ulimit -a for which most of them 
are specified as unlimited , would it be because of max open files or stack 
size ? But it works sometimes and fails sometimes, and this problem .
could you also suggest (if any change required) what the values should be for 
open files, pipe size , stack size and max user processes 

bash-2.03$ id
uid=302(cvsuser) gid=10(staff)
bash-2.03$ ulimit -a
core file size (blocks)     unlimited
data seg size (kbytes)      unlimited
file size (blocks)          unlimited
open files                  256
pipe size (512 bytes)       10
stack size (kbytes)         8192
cpu time (seconds)          unlimited
max user processes          15717
virtual memory (kbytes)     unlimited           


Balaji Krishnamoorthy
Senior Systems Analyst 
Architecture, IT
Standard & Poor's (S&P)
55 Water Street, 35th Floor
New York, NY 10041
Phone:  (212)-438-1118
Fax:       (212)-438-7482
Email:   balaji_krishnamoorthy@sandp.com 

-----Original Message-----
From: larry.jones@sdrc.com [mailto:larry.jones@sdrc.com]
Sent: Tuesday, April 30, 2002 3:28 PM
To: Balaji_Krishnamoorthy@standardandpoors.com
Cc: bug-cvs@gnu.org
Subject: Re: CVS Tagging Terminated with fatal signal 11

Krishnamoorthy, Balaji writes:
> Unix box is dedicated as CVS server and we do not have any other processes 
> running other than the very basic services of unix 
> the top command stats are as follows typically at any given point . and the 
> ulimit command returns "unlimited" as the output.
> Could you please write to me what else should i be looking at .

The man page for your shell to learn how the ulimit command works. 
ulimit with no arguments gives you the maximum allowable *file* size, it
doesn't have anything to do with memory limits.  If you can't be
bothered to read the man page, at least try "ulimit -a".

-Larry Jones

Let's pretend I already feel terrible about it, and that you
don't need to rub it in any more. -- Calvin

The information contained in this message is intended only for the recipient, 
may be privileged and confidential and protected from disclosure. If the reader 
of this message is not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, please be 
aware that any dissemination or copying of this communication is strictly 
prohibited. If you have received this communication in error, please 
immediately notify us by replying to the message and deleting it from your 

Thank you,
Standard & Poor's

reply via email to

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