This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: serverside programs

From: Erik Poupaert <erik dot poupaert at skynet dot be>
To: Jeff Sturm <jsturm at one-point dot com>
Cc: java at gcc dot gnu dot org
Date: Thu, 18 Sep 2003 02:08:12 +0000
Subject: Re: serverside programs
Organization: Erik Poupaert
References: <20030917235055.77c9f6d6.erik.poupaert@skynet.be><Pine.LNX.4.44.0309172001350.24527-100000@ops2.one-point.com>

> ou can always the GC_MAXIMUM_HEAP_SIZE environment variable with libgcj
> to prevent a rogue program from consuming all system resources.

Ok.

Another strategy could be to start and exit the program for every request (like cgi
or xinetd programs). I was wondering, if the program has leaked memory during its
execution, will the OS always and fully reclaim the memory not freed by the program
after the program exits? Or in other words, is "exiting" always a full memory
cleanup?

Follow-Ups:
- Re: serverside programs
  - From: Jeff Sturm
- stripping libgcj.so.4
  - From: Erik Poupaert

References:
- serverside programs
  - From: Erik Poupaert
- Re: serverside programs
  - From: Jeff Sturm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]