Browsing Kashubian translation

53.

<qt>Change which processes are shown, and how they are shown. The processes can be further filtered by using the Quick Search text filter.<p>
<table>
<tr><td>All Processes</td><td>Show all the processes on the system.</td></tr>
<tr><td>All Processes, tree</td><td>Show all the processes on the system, in a hierarchical manner using the parent PID information.</td></tr>
<tr><td>System Processes</td><td>Show processes running as root and as a user who cannot login.</td></tr>
<tr><td>User Processes</td><td>Show processes running as a non-root user who can login.</td></tr>
<tr><td>Own Processes</td><td>Show processes owned by the same user that this process is owned by.</td></tr>
<tr><td>Programs Only</td><td>Show processes which are running as a user who can login and are either attached to a TTY or have at least one X11 Window.</td></tr>
</table>
<p>
<i>Technical Information:</i><br>
Processes with multiple threads are just shown as a single process, and not treated any differently.<br>
Kernel threads are shown as normal processes, but are actually running inside the kernel and are not real processes. As such, many of the fields (such as Username) do not apply.

114.

<qt><i>Technical information: </i>The kernel process name is a maximum of 8 characters long, so the full command is examined. If the first word in the full command line starts with the process name, the first word of the command line is shown, otherwise the process name is used.

115.

<qt>The user who owns this process. If the effective, setuid etc user is different, the user who owns the process will be shown, followed by the effective user. The ToolTip contains the full information. <p><table><tr><td>Login Name/Group</td><td>The username of the Real User/Group who created this process</td></tr><tr><td>Effective User/Group</td><td>The process is running with privileges of the Effective User/Group. This is shown if different from the real user.</td></tr><tr><td>Setuid User/Group</td><td>The saved username of the binary. The process can escalate its Effective User/Group to the Setuid User/Group.</td></tr><tr><td>File System User/Group</td><td>Accesses to the filesystem are checked with the File System User/Group. This is a Linux specific call. See setfsuid(2) for more information.</td></tr></table>

116.

<qt>This is the size of allocated address space - not memory, but address space. This value in practice means next to nothing. When a process requests a large memory block from the system but uses only a small part of it, the real usage will be low, VIRT will be high. <p><i>Technical information: </i>This is VmSize in proc/*/status and VIRT in top.

117.

<qt><i>Technical information: </i>This is the URSS - Unique Resident Set Size, calculated as VmRSS - Shared, from /proc/*/statm. This tends to underestimate the 'true' memory usage of a process (by not including i/o backed memory pages), but is the best estimation that is fast to determine.

119.

<qt><i>Technical information: </i>This is the Shared memory, called SHR in top. It is the number of pages that are backed by a file (see kernel Documentation/filesystems/proc.txt .)

121.

<qt><i>Technical information: </i>For each X11 window, the X11 property _NET_WM_PID is used to map the window to a PID. If a process' windows are not shown, then that application incorrectly is not setting _NET_WM_PID.

122.

<qt><i>Technical information: </i>This is the Process ID. A multi-threaded application is treated a single process, with all threads sharing the same PID. The CPU usage etc will be the total, accumulated, CPU usage of all the threads.

123.

<qt>This column shows the IO statistics for each process. The tooltip provides the following information:<br><table><tr><td>Characters Read</td><td>The number of bytes which this task has caused to be read from storage. This is simply the sum of bytes which this process passed to read() and pread(). It includes things like tty IO and it is unaffected by whether or not actual physical disk IO was required (the read might have been satisfied from pagecache).</td></tr><tr><td>Characters Written</td><td>The number of bytes which this task has caused, or shall cause to be written to disk. Similar caveats apply here as with Characters Read.</td></tr><tr><td>Read Syscalls</td><td>The number of read I/O operations, i.e. syscalls like read() and pread().</td></tr><tr><td>Write Syscalls</td><td>The number of write I/O operations, i.e. syscalls like write() and pwrite().</td></tr><tr><td>Actual Bytes Read</td><td>The number of bytes which this process really did cause to be fetched from the storage layer. Done at the submit_bio() level, so it is accurate for block-backed filesystems. This may not give sensible values for NFS and CIFS filesystems.</td></tr><tr><td>Actual Bytes Written</td><td>Attempt to count the number of bytes which this process caused to be sent to the storage layer. This is done at page-dirtying time.</td></table><p>The number in brackets shows the rate at which each value is changing, determined from taking the difference between the previous value and the new value, and dividing by the update interval.<p><i>Technical information: </i>This data is collected from /proc/*/io and is documented further in Documentation/accounting and Documentation/filesystems/proc.txt in the kernel source.