Editing Reporting OpenVZ problem
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 49: | Line 49: | ||
== Access to the node == <!--T:8--> | == Access to the node == <!--T:8--> | ||
− | In some cases, a remote access to the problem node is the fastest way to diagnose and fix a problem, so sometimes an OpenVZ developer can request such access from you. Note that in should be root access | + | In some cases, a remote access to the problem node is the fastest way to diagnose and fix a problem, so sometimes an OpenVZ developer can request such access from you. Note that in should be a root access (either directly, or via <code>sudo</code>) to the [[hardware node]]. |
<!--T:9--> | <!--T:9--> | ||
− | In case you can provide access, post login information via forum PM or e-mail, or ask for a public SSH key. | + | In case you can provide an access, post login information via forum PM or by e-mail, or ask for a public SSH key. |
<!--T:10--> | <!--T:10--> |