|
2.
|
|
|
The program '%1' (PID: %2) is being monitored for input and output through any file descriptor (stdin, stdout, stderr, open files, network connections, etc.). Data being written by the process is shown in red and data being read by the process is shown in blue.
|
|
|
|
(no translation yet)
|
|
|
|
41.
|
|
|
Could not find setscheduler executable. This should have been installed alongside system monitor.
|
|
|
|
(no translation yet)
|
|
|
|
49.
|
|
|
If this is checked then ANSI escape sequences will be interpreted and not displayed. Useful for when monitoring bash.
|
|
|
|
(no translation yet)
|
|
|
|
52.
|
|
|
Follow fork and clone commands to monitor child processes
|
|
|
|
(no translation yet)
|
|
|
|
55.
|
|
|
Stop reading the output from the process. This will cause the process to be blocked, effectively pausing it. The process can be resumed by resuming, detaching or closing the dialog.
|
|
|
|
(no translation yet)
|
|
|
|
142.
|
|
|
<qt><p style='white-space:pre'>Process status: %1 %2<br />User CPU usage : %3%<br />System CPU usage: %4%</qt>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
ProcessModel.cc:911
|
|
151.
|
|
|
<qt>Your system does not seem to have this information available to be read.</qt>
|
|
|
|
(no translation yet)
|
|
|
|
Located in
ProcessModel.cc:954
|