Red Hat Bugzilla – Bug 114906
ccm-tools should provide a default /etc/conf/envars
Last modified: 2007-04-18 13:02:30 EDT
Description of problem:
The ccm-tools package should install a default set of envvars suitable
for a typical production install. Probably:
since this is suitable for all JDKs. We should also probably include
some commented out examples for other configs - such as the Sun JDK
garbage collector optimizations.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
what happens with the above if the machine has, say, 384MB of RAM?
Experiance has shown us that production servers will very quickly fall
over with OutOfMemoryExceptions if you allocate < 512m, particulary,
if they upload even moderately sized images / files. So running on a
machine with < 1 GB of RAM is not feasible.
Let me rephrase my question.
If I'm downloading this thing for evaluation, and I'm not running in
production, and my machine has 384MB of RAM, and I just want to click
around, will using these defaults preclude me from running at all?
/etc/ccm/conf/envvars is part of the ccm-tools package as of 40056.
The contents are:
## Environment variables to be set at ccm invocation
## Jave Runtime Environment parameters
# JAVA_OPTS=-Xms512m -Xmx512m
I prefer to leave the JAVA_OPTS settings commented out for the reason
that Richard Li mentioned. Plus, production installs should refer to
the deployment guide and use JVM settings corresponding to the