:> ram and 512MB of swap (4MB of swap in use), but the kernel reports over
:> 3 GB of VM assigned to processes. That's a fairly lightly loaded machine.
:
:What you say is generally true; however, the problem is that *you*
:are making implicit assumptions about what applications *I* might
:have in mind. I just think that's a presumptous thing to do unless
:you can read minds..
:
:For example:
:
:- I might be creating a very limited embedded system with just a few
: small processes that are all written to *handle* out of memory situations.
Really? Then setting resource limits from within each program is not
a problem now is it? Then it will get a nice malloc failure instead
of getting killed by the kernel.
:- I could be creating a "Java OS" that is going to have a single process,
: ie, the Java VM, that can handle ENOMEM (which translates into an
: OutOfMemoryException, which can be caught) but otherwise *must not die*.
.... just one process? Set a resource limit! If you have 64MB of swap,
then limit the size of the Java OS process to 50MB. Now the java
process will get a nice malloc failure instead of getting killed by
the kernel.
:...
:-Archie
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:___________________________________________________________________________
:Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
:
:
:To Unsubscribe: send mail to [EMAIL PROTECTED]
:with "unsubscribe freebsd-hackers" in the body of the message
:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
