I have two questions on Linux's free command. Below, I have provided output from my home laptop (fedora 26 ) which has 16GB Physical RAM and a production server (RHEL 7.4) which has 24GB RAM.
Question1. What exactly does the buffer/cache column say in free command's output ? buffer/cache is only 1GB in my home laptop but it is 18GB in production server below.
Question2. To know the free RAM available to the system, Can I trust the 'available' column rather than the 'free' column ?
In my home laptop, the 'free' column shows 13GB and available shows 14GB
But, in my production server, when the free command shows just 2GB , the available command shows 9 GB
My Home Laptop with 16 GB RAM (Fedora 26)
A production Server (VM) with 24GB RAM (RHEL 7.4)
I know that free command displays memory usages however I like to know how the option and the results when I use this command..
PLease respond ASAP
thanx... I am a newbie.. :D (1 Reply)
Hi there again,
Running Solaris 10 with built-in Java. Seems to compile and run fine.
Problem is: Say I want to see contents of current directory. In a shell, I'd just write "ls" and it outputs the content.
When I write a Java file, I have the following line:
System.out.println("ls");
... (1 Reply)
Hi All
I have something that from the outset seems really trivial but in practice is not quite working.
I have the following code sample in my shell script which illustrates the problem
echo "enter home directory"
read home
mkdir $home/newdir
The user then enters a logical $HOME... (3 Replies)
hi all,
when I run-
wcars1j5#netstat -an | grep 8090
127.0.0.1.8090 *.* 0 0 49152 0 LISTEN
wcars1j5#
1. does this mean that no one is connected to this port?
Regards,
akash (1 Reply)
I am having trouble figuring this one out.....Is this a 2CPU or a 4CPU v490 with 16GB? I think it is a 2CPU system, looking for confirmation.
$ prtdiag
System Configuration: Sun Microsystems sun4u Sun Fire V490
System clock frequency: 150 MHz
Memory size: 16384 Megabytes
... (1 Reply)
Hello, I need some help to interpret the below output...
What is -/+ buffers/cache?
My understanding is, total RAM is 3986152 Bytes, used RAM is 3950904 bytes.
What is buffers and cached?? Can any one please interpret this output? It would be great help if some one can help me on this?
... (2 Replies)
Hi Friends,
I am really confused with the output of "free" command on redhat linux.
I can see caching and buffer output on two different areas on the output.
Please let me know whats the difference of these two different outputs.
Here I am pasting the command output of my server.
# free... (3 Replies)
Hi. I wonder what the equal sign in front of the answer means.
I have read man pages and googled but found no answer.
xntpdc -p
=15.5.64.3 15.5.2.51 3 512 377 0.02060 0.057426 0.04965Thanks.
Jan (1 Reply)
Hi All,
I have a file with name
Is there a LINUX command that will help me to output the word after the 9th Underscore(_).
ie the output should be DLY in this case.
Can anybody pls help me.
Thanks much in advance,
Freddie (4 Replies)
I wanted to know the concept of free -m command as there are different rows of Mem, -/+ buffers/cache & Swap in the output. As an example, it is showing 195 as free Mem in my server but 13850 in the free section of the -/+ buffers/cache row. The output needs in depth knowledge of the different... (7 Replies)
Discussion started by: RHCE
7 Replies
LEARN ABOUT SUNOS
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 237SYSTEMD-CRYPTSETUP-GENERATOR(8)