From: tom arnall <kloro2006@gmail.com>
To: linux-admin@vger.kernel.org
Subject: Re:
Date: Wed, 3 May 2006 14:28:04 -0700 [thread overview]
Message-ID: <200605031428.05017.kloro@cox.net> (raw)
In-Reply-To: <4457BC2F.4010208@tessco.com>
my system freezes when I try to run an application that handles a large file
in a variable. I have set ulimits as follows:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 256000
max memory size (kbytes, -m) 256000
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
Physical memory on the system is 512MB, yet when the application runs -
despite the limits shown above - linux hands almost all of memory to the
application.
Tom Arnall
north spit, ca
next prev parent reply other threads:[~2006-05-03 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:36 (unknown), Kirkwood, David A
2006-05-02 20:08 ` Tom Callahan
2006-05-02 20:23 ` ipforward Adrian C.
2006-05-03 21:28 ` tom arnall [this message]
2006-05-03 21:50 ` memory problems tom arnall
2006-05-02 21:48 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 12:36 (unknown) terry white
2010-03-16 14:05 ` Adam T. Bowen
2010-03-16 14:15 ` Re: Lars
2010-03-16 14:35 ` Re: Ben Kevan
2010-03-16 14:40 ` Re: Yuri Csapo
2010-03-16 14:22 ` Re: Yuri Csapo
2010-03-16 14:31 ` Re: James Grimwood
2010-03-16 18:06 ` Re: Yuri Csapo
2006-09-28 15:59 (unknown), Kirkwood, David A
2006-09-28 16:19 ` Alexandre Mulatinho
2006-09-29 16:32 ` Re: Glynn Clements
2004-08-08 9:00 File size Anindya Mozumdar
2004-08-08 15:45 ` (unknown) Debian UserJens Suelwald
2004-08-09 13:21 ` Adam Lang
2002-04-16 20:51 (unknown), Greg Kilfoyle
2002-04-16 21:10 ` James Kelty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605031428.05017.kloro@cox.net \
--to=kloro2006@gmail.com \
--cc=kloro@cox.net \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).