From c6547ec22d31d2388579bea1602c3ead2bce2a3f Mon Sep 17 00:00:00 2001 From: mprpic@REDHAT.COM Date: Mar 14 2011 09:36:24 +0000 Subject: fixed silly typos, restructured a sentence into an ordered list, incremented pubsnumber --- diff --git a/6-trunk/en-US/Book_Info.xml b/6-trunk/en-US/Book_Info.xml index 36b8e77..d75c822 100644 --- a/6-trunk/en-US/Book_Info.xml +++ b/6-trunk/en-US/Book_Info.xml @@ -9,7 +9,7 @@ Red Hat Enterprise Linux 6 1.0 - 7 + 8 Managing system resources on &MAJOROSVER; diff --git a/6-trunk/en-US/Subsystems_and_Tunable_Parameters.xml b/6-trunk/en-US/Subsystems_and_Tunable_Parameters.xml index f83840f..d230f9c 100644 --- a/6-trunk/en-US/Subsystems_and_Tunable_Parameters.xml +++ b/6-trunk/en-US/Subsystems_and_Tunable_Parameters.xml @@ -395,7 +395,22 @@ - To suspend a specific process, first, you must move that process to a cgroup in a hierarchy which has the freezer subsystem attached to it. Consequently, freeze that particular cgroup to suspend the task contained in it. It is not possible to move a task into a suspended (frozen) cgroup. + To suspend a specific process: + + + + + Move that process to a cgroup in a hierarchy which has the freezer subsystem attached to it. + + + + + Freeze that particular cgroup to suspend the process contained in it. + + + + + It is not possible to move a process into a suspended (frozen) cgroup. Note that while the FROZEN and THAWED values can be written to freezer.state, FREEZING cannot be written, only read. diff --git a/6-trunk/en-US/Using_Control_Groups.xml b/6-trunk/en-US/Using_Control_Groups.xml index 8aaf5d7..f67c65a 100644 --- a/6-trunk/en-US/Using_Control_Groups.xml +++ b/6-trunk/en-US/Using_Control_Groups.xml @@ -642,7 +642,7 @@ CGROUP_DAEMON="cpuset:daemons/sql" Note - Using the mount command to create cgroups (as oposed to creating them using the cgconfig service) results in the creation of an entry in the /etc/mtab file (the mounted file systems table). This change is also reflected into the /proc/mounts file. However, the unloading of cgroups with the cgclear command, along with other cgconfig commands, uses a direct kernel interface which does not reflect it's changes into the /etc/mtab file and only writes the new information into the /proc/mounts file. Thus, after unloading cgroups with the cgclear command, the unmounted cgroups may still be visible in the /etc/mtab file, and, consequently, displayed when the mount command is executed. It is advisable to refer to the /proc/mounts file for an accurate listing of all mounted cgroups. + Using the mount command to create cgroups (as opposed to creating them using the cgconfig service) results in the creation of an entry in the /etc/mtab file (the mounted file systems table). This change is also reflected into the /proc/mounts file. However, the unloading of cgroups with the cgclear command, along with other cgconfig commands, uses a direct kernel interface which does not reflect its changes into the /etc/mtab file and only writes the new information into the /proc/mounts file. Thus, after unloading cgroups with the cgclear command, the unmounted cgroups may still be visible in the /etc/mtab file, and, consequently, displayed when the mount command is executed. It is advisable to refer to the /proc/mounts file for an accurate listing of all mounted cgroups.