Browsing Occitan (post 1500) translation

19.

<qt>This is the amount of real physical memory that this process is using by itself, and approximates the Private memory usage of the process.<br>It does not include any swapped out memory, nor the code size of its shared libraries.<br>This is often the most useful figure to judge the memory use of a program. See What's This for more information.</qt>

20.

<qt>This is approximately the amount of real physical memory that this process's shared libraries are using.<br>This memory is shared among all processes that use this library.</qt>

27.

<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.

28.

<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>

29.

<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.

30.

<qt><i>Technical information: </i>This is an approximation of the Private memory usage, calculated as VmRSS - Shared, from /proc/*/statm. This tends to underestimate the true Private memory usage of a process (by not including i/o backed memory pages), but is the best estimation that is fast to determine. This is sometimes known as URSS (Unique Resident Set Size). For an individual process, see "Detailed Memory Information" for a more accurate, but slower, calculation of the true Private memory usage.

32.

<qt>The total system and user time that a process and all of its threads have been running on the CPU for. This can be greater than the wall clock time if the process has been across multiple CPU cores.

33.

<qt><i>Technical information: </i>This is an approximation of 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). For an individual process, see "Detailed Memory Information" for a more accurate, but slower, calculation of the true Shared memory usage.

35.

<qt><i>Technical information: </i>This is the amount of memory used by the Xorg process for images for this process. This is memory used in addition to Memory and Shared Memory.<br><i>Technical information: </i>This only counts the pixmap memory, and does not include resource memory used by fonts, cursors, glyphsets etc. See the <code>xrestop</code> program for a more detailed breakdown.

37.

<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.