1and1 Help Centre Categories

print article

Manage 1&1 Virtual Server Processes

The System Processes page is displayed by clicking on the System Processes link on the 1&1 Virtual Server Services dashboard. It presents a table reflecting all the running processes and provides the following information:

PID The process ID
%CPU The percent of the CPU time the process is currently using
%MEM The percent of the RAM size the process is currently using
Command The command that is used to launch the process
Nice The relative priority of the process assigned to it by the user. The negative values mean that the user has manually increased the priority, the positive - that they have decreased it.
Pri The absolute priority of the process assigned to it by the process scheduler. On a Linux Node, the range is from 0 (the highest priority) to 39 (the lowest priority). The usual process priority is 30.
RSS The size of physical memory the process really uses(in Kilobytes).
Stat The state of the process
Time The total amount of time of the CPU time the process has used so far
User The user the process belongs to

To have the information in the table refreshed automatically with the current values, click the Enable Auto Refresh button. It is worthy to note that only the table on the current page is refreshed, which takes much less resources in comparison with refreshing the whole VZCC page.

You may select any number of processes by ticking the checkbox(es) against the corresponding process(es) and send them a standard signal. Choose the needed signal on the drop-down menu and press the Send Signal button. The following signals can be sent:

SIGHUP Hang-up signal. It is often used to ask a daemon process to re-read its configuration.
SIGTERM Sends the termination signal to the process. This is the best way to give the process a chance for an orderly shutdown and proper data saving. As the process might be able to catch this signal and stay alive, you may have to make use of the "sigkill” or "sigint” signals".
SIGCONT Continues the process causing it to resume.
SIGSTOP Stops/Suspends the process but leaves it on the task list.
SIGINT Causes the process to immediately interrupt. It can be caught by the process and ignored if the process gets out of hand. In this case you should send "sigkill” to shut down the process.
SIGKILL Unconditionally kills the process. Keep in mind that sending "sigkill"” to any process removes any chance for it to do a tidy cleanup and shutdown, which might have unfortunate consequences.