Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision |
Your text |
Line 186: |
Line 186: |
| to create more than 200–300 <code>numiptent</code>. | | to create more than 200–300 <code>numiptent</code>. |
| | | |
− | == swappages ==
| + | I went to tons of links before this, what was I thiknnig? |
− | | |
− | The amount of swap space to show in container.
| |
− | | |
− | {{Note|this parameter is only available in RHEL5-based kernel since version 028stab060.2, in 2.6.27 since kiprensky.}}
| |
− | | |
− | The configuration of this parameter doesn't affect security and
| |
− | stability of the whole system or isolation between containers.
| |
− | Its configuration only affects the way OpenVZ kernel reports about
| |
− | available swap in a container. This is needed for some applications
| |
− | which refuse to run inside a container unless the kernel
| |
− | report that no less than some specific amount of swap is available.
| |
− | | |
− | If <code>limit</code> is set, its value is reported as the amount
| |
− | of total swap space in a container. | |
− | | |
− | If the <code>limit</code> is set to [[LONG_MAX]] (which is the
| |
− | in-kernel default for this parameter), all the swap space values
| |
− | parameters (total, used, free) are reported as 0.
| |
− | | |
− | The value of <code>barrier</code> for this beancounter is ignored.
| |
− | | |
− | The value of <code>held</code> shows how much swap space
| |
− | is currently being used for this container.
| |