09-09-2012
I don't know well Red Hat, but here
What are the Red Hat Enterprise Linux limits? — Bull On-line Support Portal you can read:
Quote:
RHEL-5 kernels:
i686 - no PAE, no hugemem patches, can address up to 4GB of memory
i686-PAE - PAE, no hugemem patches, can reliably run with around 16GB
So, in summary, if customers need to use > 16GB of memory, the absolute best suggestion is to use RHEL-5 x86_64, which suffers from none of these limitations.
I didn't find anything about a RHEL-5 i686 SMP kernel, but the RHEL-4 i686 SMP kernel is limited to 16GB too.
So at least be careful with your OS. With as little as 4GB RAM and up, a 64bit OS would be a wise choice.
If you're concerned with you hardware capabilities too, apart from reading your hardware manual you could try:
# dmidecode -t 16
Read
man dmidecode for details.
--
Bye
10 More Discussions You Might Find Interesting
1. Programming
Sir,
How can i get the RAM size .Is there is any predefined function ..Howsir???
Thanks In advance,
ArunKumar (6 Replies)
Discussion started by: arunkumar_mca
6 Replies
2. UNIX for Dummies Questions & Answers
I need to have fast access to some of my files (like 5 Gb).
Im on:
Linux franklin3 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 i686 i386 GNU/Linux
How can I load my files in my RAM ?
Thank you in advance! (0 Replies)
Discussion started by: Gab
0 Replies
3. HP-UX
hi,
while i am working in hpux 11.23 using a telnet connection how do i check the RAM size and hard disk size? (4 Replies)
Discussion started by: sekar sundaram
4 Replies
4. AIX
hello, we have a aix 5.2 server with 8GB of ram. is it possible, without actually removing the hardware, to have the O/S think it has only 4GB of ram? We would like to see how the handles and responds if it only had 4Gb instead of the 8GB. Any ideas or suggestions? Thanks
Looks like i found... (6 Replies)
Discussion started by: zuessh
6 Replies
5. 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
6. 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
7. Solaris
Hi all,
The environment we're using is a T5440 running Solaris 10 LDOMs and zones configured within the LDOM. The LDOM has 32Gb of RAM and 32Gb of swap.
Last week, we had an issue where the MQ server on zone 3 crashed as it ran out of swap, apparently caused by zone 2 usage. I understand that... (7 Replies)
Discussion started by: JerryHone
7 Replies
8. Windows & DOS: Issues & Discussions
Hello All
Is there a way I can find out the type of RAM (DDR1 or DDR2 or DDR3), I'm using withoout opening the cabinet?
Any Windows command?
Thanks in advance. (5 Replies)
Discussion started by: tenderfoot
5 Replies
9. 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
10. Red Hat
Hi,
I have a server (BL460c) with 32G of physical RAM.
It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications.
If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies
LEARN ABOUT MOJAVE
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)