08-12-2012
Quote:
Originally Posted by
neutronscott
overall the easiest solution is adding RAM, unless you find you've improperly configured services, or non-essential ones, wasting your memory.
I agree with this. RAM is cheap; cheaper than hours of analysis. Heck, I have 4GB of RAM on my MBA which I only use for web and email; basically. Our basic server is now at 32 GB RAM...... so a running a server with an Oracle DB with only 4 GB of RAM seems "overly economical" to me..... It is cheaper to just put in more RAM than trying to analyze the issue to death... IMHO..
10 More Discussions You Might Find Interesting
1. Solaris
What command should I be using on Solaris 9 to get an accurate representation of the available physical RAM? (4 Replies)
Discussion started by: dangral
4 Replies
2. Solaris
folks, hows everyone?
just upgraded my laptop running on solaris 10 by adding some extra RAM. I did notice some improvement (increase in speed) but could not be certain the new RAM has been accepted and all is well (was concerned a bit as i almost broke it while installing :-)) and didnt get any... (4 Replies)
Discussion started by: alikun
4 Replies
3. UNIX for Dummies Questions & Answers
Hi
can anyone please help me, how to know RAM specification in unix? (4 Replies)
Discussion started by: palash2k
4 Replies
4. Red Hat
Hi,
On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb
can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Linux
Hi All,
I installed CentOs on my PC (it has 1 GB of RAM). I see that only 200MB of RAM is being utilized on average but its very slow. Please let me know how do I improve the performance. Is there a way to set the RAM utilization/usage on CentOS.
Thank you (2 Replies)
Discussion started by: jayfriend
2 Replies
6. Linux
Hi
one of our applications that runs on our Linux server leaks memory resulting in Ram that was used by the program not being released back to the operating system once a file has been processed. the result is over a very short period virtual all the memory has been used. an example currently
... (8 Replies)
Discussion started by: treds
8 Replies
7. Solaris
our sparc server has only 1Gb RAM. Since RAM is not very expensive anymore, it seems like a good idea to upgrade it.
will it make server (and database on it) faster?
I hope it would less 'abuse' hard drive.. (6 Replies)
Discussion started by: orange47
6 Replies
8. Red Hat
Dear All,
I have linux Servers where all are having at present 12 Gig RAM.
At present my need is to increase the RAM for atleast another 12 G . ie 12G +12 G ===24 Gig RAM.
But how does i can find out whether my server will support for 24 GiG RAM or is there any way of finding out how... (4 Replies)
Discussion started by: jegaraman
4 Replies
9. Solaris
is there a way to thoroughly test RAM in Solaris10 (SPARC)?
or is boot test good enough? (5 Replies)
Discussion started by: orange47
5 Replies
10. UNIX for Dummies Questions & Answers
hi,
i m working on my ubuntu 12.10 i wanted to update my desktop's RAM. so
kindly let me know how i get below details (thru commands in terminal)
1) what is the processor am using currently
2) what is the RAM am using currently
3) max how much i can upgrade my RAM (4 Replies)
Discussion started by: anandpasunoori
4 Replies
LEARN ABOUT DEBIAN
systemd-cryptsetup-generator
SYSTEMD-CRYPTSETUP-GENERATOR(8) systemd-cryptsetup-generator SYSTEMD-CRYPTSETUP-GENERATOR(8)
NAME
systemd-cryptsetup-generator - Unit generator for /etc/crypttab
SYNOPSIS
/lib/systemd/system-generators/systemd-cryptsetup-generator
DESCRIPTION
systemd-cryptsetup-generator is a generator that translates /etc/crypttab into native systemd units early at boot and when configuration of
the system manager is reloaded. This will create systemd-cryptsetup@.service(8) units as necessary.
systemd-cryptsetup-generator implements systemd.generator(7).
KERNEL COMMAND LINE
systemd-cryptsetup-generator understands the following kernel command line parameters:
luks=, rd.luks=
Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.luks= is honored only by initial RAM disk
(initrd) while luks= is honored by both the main system and the initrd.
luks.crypttab=, rd.luks.crypttab=
Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any devices configured in /etc/crypttab
(luks.uuid= will still work however). rd.luks.crypttab= is honored only by initial RAM disk (initrd) while luks.crypttab= is honored
by both the main system and the initrd.
luks.uuid=, rd.luks.uuid=
Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in
/etc/crypttab. This option may be specified more than once in order to set up multiple devices. rd.luks.uuid= is honored only by
initial RAM disk (initrd) while luks.uuid= is honored by both the main system and the initrd.
If /etc/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the
device will have the name "luks-UUID".
If /etc/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.
luks.name=, rd.luks.name=
Takes a LUKS super block UUID followed by an "=" and a name. This implies rd.luks.uuid= or luks.uuid= and will additionally make the
LUKS device given by the UUID appear under the provided name.
rd.luks.name= is honored only by initial RAM disk (initrd) while luks.name= is honored by both the main system and the initrd.
luks.options=, rd.luks.options=
Takes a LUKS super block UUID followed by an "=" and a string of options separated by commas as argument. This will override the
options for the given UUID.
If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in
/etc/crypttab.
rd.luks.options= is honored only by initial RAM disk (initrd) while luks.options= is honored by both the main system and the initrd.
luks.key=, rd.luks.key=
Takes a password file name as argument or a LUKS super block UUID followed by a "=" and a password file name.
For those entries specified with rd.luks.uuid= or luks.uuid=, the password file will be set to the one specified by rd.luks.key= or
luks.key= of the corresponding UUID, or the password file that was specified without a UUID.
rd.luks.key= is honored only by initial RAM disk (initrd) while luks.key= is honored by both the main system and the initrd.
SEE ALSO
systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8), systemd-fstab-generator(8)
systemd 237 SYSTEMD-CRYPTSETUP-GENERATOR(8)