Editing User Guide/Managing Resources
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 523: | Line 523: | ||
Any CT is configured by means of its own configuration file. You can manage your CT configurations in a number of ways: | Any CT is configured by means of its own configuration file. You can manage your CT configurations in a number of ways: | ||
<ol> | <ol> | ||
− | <li>Using configuration sample files shipped with OpenVZ. These files are used when a new Container is being created (for details, see the [[#Creating and Configuring New Container]] section). They are stored in (<code>/etc/vz | + | <li>Using configuration sample files shipped with OpenVZ. These files are used when a new Container is being created (for details, see the [[#Creating and Configuring New Container]] section). They are stored in (<code>/etc/vz/</code> and have the <code>ve‑''name''.conf-sample</code> mask. Currently, the following configuration sample files are provided: |
* light – to be used for creating “light” CTs having restrictions on the upper limit of quality of service parameters; | * light – to be used for creating “light” CTs having restrictions on the upper limit of quality of service parameters; | ||
− | * basic – to be used for common CTs. | + | * vps.basic – to be used for common CTs. |
{{Note|Configuration sample files cannot contain spaces in their names.}} | {{Note|Configuration sample files cannot contain spaces in their names.}} |