diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 17:59:44 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 17:59:44 +0000 |
| commit | fb31765cbe33890f325a87015507364156741321 (patch) | |
| tree | 0c5cd12aee0a0a6a6e2d542520df5846859bd40d /help/C | |
| parent | Initial commit. (diff) | |
| download | gnome-system-monitor-fb31765cbe33890f325a87015507364156741321.tar.xz gnome-system-monitor-fb31765cbe33890f325a87015507364156741321.zip | |
Adding upstream version 42.0.upstream/42.0upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'help/C')
32 files changed, 1862 insertions, 0 deletions
diff --git a/help/C/commandline.page b/help/C/commandline.page new file mode 100644 index 0000000..b3960fa --- /dev/null +++ b/help/C/commandline.page @@ -0,0 +1,72 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="commandline"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#other" group="other" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Information in System Monitor can also be found using command line + tools.</desc> + </info> + + <title>Get the same information from the command line</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Briefly list a few useful command line tools which can provide some of + the same information as System Monitor. Don't go into too much detail.</p> + </comment> + + <p>Most of the information displayed by System Monitor can also be obtained + using these command line tools.</p> + +<table rules="rows" frame="top bottom"> + + <tr> + <td><p><cmd>top</cmd></p></td> + <td><p>provides a continually updated list of running processes, and + allows you to manipulate them.</p></td> + </tr> + + <tr> + <td><p><cmd>lsof</cmd></p></td> + <td><p>provides a list of open files and the processes that opened + them.</p></td> + </tr> + + <tr> + <td><p><cmd>free -m</cmd></p></td> + <td><p>shows you how much memory is available.</p></td> + </tr> + + <tr> + <td><p><cmd>vmstat</cmd></p></td> + <td><p>provides information about current virtual memory use.</p></td> + </tr> + + <tr> + <td><p><cmd>df -h</cmd></p></td> + <td><p>displays available disk space on mounted filesystems.</p></td> + </tr> + + <tr> + <td><p><cmd>pmap</cmd></p></td> + <td><p>displays the memory map of a process.</p></td> + </tr> + +</table> + +</page> diff --git a/help/C/cpu-check.page b/help/C/cpu-check.page new file mode 100644 index 0000000..faaf89d --- /dev/null +++ b/help/C/cpu-check.page @@ -0,0 +1,31 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="cpu-check"> + <info> + <revision version="0.1" date="2014-01-28" status="review"/> + <link type="guide" xref="index#cpu" group="cpu" /> + <link type="seealso" xref="process-identify-hog" /> + <link type="seealso" xref="process-priority-change" /> + <link type="seealso" xref="cpu-mem-normal" /> + <link type="seealso" xref="cpu-multicore" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>The amount of CPU being used tells you how much work the computer is trying to do.</desc> + </info> + + <title>Check how much processor (CPU) capacity is being used</title> + + <p>To check how much of your computer's processor is currently being used, go to the <gui>Resources</gui> tab and look at the <gui>CPU History</gui> chart. This tells you how much work the computer is currently doing.</p> + + <p>Many computers have more than one processor (sometimes called <em>multi-core</em> systems). Each processor is shown separately on the chart. If you want, you can change the color used for each processor by clicking one of the colored blocks below the chart.</p> + + <p>You can also change how rapidly the chart is updated (the update interval), and how the lines for each processor are displayed (e.g. as a stacked area chart). Change the relevant options by clicking <gui>System Monitor</gui>, then select <gui>Preferences</gui>, and then the <gui>Resources</gui> tab.</p> + +</page> diff --git a/help/C/cpu-mem-normal.page b/help/C/cpu-mem-normal.page new file mode 100644 index 0000000..1dca1d5 --- /dev/null +++ b/help/C/cpu-mem-normal.page @@ -0,0 +1,35 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="cpu-mem-normal"> + <info> + <revision version="0.1" date="2014-01-28" status="review"/> + <link type="guide" xref="index#cpu" group="cpu" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>If the computer is doing a lot of work, it will use more processor time and more memory.</desc> + </info> + + <title>Is it normal for my computer to be using this much CPU or memory?</title> + + <p>All of the programs running on your computer share CPU (processor) time and memory. If you run many programs at once, or if some programs are doing a lot of work, a higher percentage of both of these things will be used.</p> + + <p>If the CPU usage is around 100%, this means that your computer is trying to do more work than it has the capacity for. This is usually OK, but it means that programs may slow down a little. Computers tend to use close to 100% of the CPU when they are doing computationally-intensive things like running games.</p> + + <p>If the processor is running at 100% for a long time, this could make your computer annoyingly slow. In this case, you should <link xref="process-identify-hog">find out which program is using up so much CPU time</link>.</p> + + <p>If the memory usage is close to 100%, this can slow things down a lot. This is because the computer will then try to use your hard disk as a temporary memory store, called <link xref="mem-swap">swap memory</link>. Hard disks are much slower than the system memory.</p> + + <p>You can try to free up some system memory by closing some programs. If things get too slow, try restarting the computer.</p> + + <note> + <p>The memory shown in the <gui>Resources</gui> tab is <em>system memory</em> (also called RAM). This is used to hold programs temporarily, while they are running on the computer. This is not the same as a hard disk or other kinds of memory, which are used to store files and programs more permanently.</p> + </note> + +</page> diff --git a/help/C/cpu-multicore.page b/help/C/cpu-multicore.page new file mode 100644 index 0000000..8deee1e --- /dev/null +++ b/help/C/cpu-multicore.page @@ -0,0 +1,27 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="cpu-multicore"> + <info> + <revision version="0.1" date="2014-01-28" status="review"/> + <link type="guide" xref="index#cpu" group="cpu" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Computers with more processors find it easier to run many programs at the same time.</desc> + </info> + + <title>Why do I have more than one processor?</title> + + <p>Many computers have more than one processor (CPU). These are sometimes referred to as multi-core systems.</p> + + <p>The workload of running all of the programs on your computer is shared between the processors. The more processors you have, the more the work can be shared out. This reduces the load on each processor, which can help make the computer run faster.</p> + + <p>The computer automatically decides how best to share the work between processors; you don't need to do this yourself.</p> + +</page> diff --git a/help/C/figures/org.gnome.SystemMonitor.svg b/help/C/figures/org.gnome.SystemMonitor.svg new file mode 100644 index 0000000..844525d --- /dev/null +++ b/help/C/figures/org.gnome.SystemMonitor.svg @@ -0,0 +1,290 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + width="128" + height="128" + id="svg11300" + version="1.0" + style="display:inline;enable-background:new" + viewBox="0 0 128 128"> + <title + id="title4162">Adwaita Icon Template</title> + <defs + id="defs3"> + <linearGradient + id="linearGradient1076"> + <stop + style="stop-color:#d5d3cf;stop-opacity:1" + offset="0" + id="stop1064" /> + <stop + id="stop1066" + offset="0.03571428" + style="stop-color:#e4e1de;stop-opacity:1" /> + <stop + style="stop-color:#d5d3cf;stop-opacity:1" + offset="0.07142857" + id="stop1068" /> + <stop + id="stop1070" + offset="0.9285714" + style="stop-color:#d5d3cf;stop-opacity:1" /> + <stop + style="stop-color:#e4e1de;stop-opacity:1" + offset="0.96428573" + id="stop1072" /> + <stop + style="stop-color:#d5d3cf;stop-opacity:1" + offset="1" + id="stop1074" /> + </linearGradient> + <linearGradient + xlink:href="#linearGradient1076" + id="linearGradient1444-2-3-2" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.25,0,0,0.25,-22,109.00903)" + x1="120" + y1="619.96387" + x2="568" + y2="619.96387" /> + <linearGradient + xlink:href="#linearGradient985" + id="linearGradient1106-8" + x1="335.86829" + y1="33.559235" + x2="112.13174" + y2="33.559235" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.25,0,0,0.25,-12,225)" /> + <linearGradient + id="linearGradient985"> + <stop + id="stop981" + offset="0" + style="stop-color:#f9f06b;stop-opacity:1" /> + <stop + id="stop983" + offset="1" + style="stop-color:#f9f06b;stop-opacity:0" /> + </linearGradient> + <radialGradient + xlink:href="#linearGradient1020" + id="radialGradient1030" + cx="64.846146" + cy="194.19048" + fx="64.846146" + fy="194.19048" + r="44" + gradientTransform="matrix(-4.7272726,1.1058296e-6,-3.0301491e-7,-1.2272727,250.54547,-21.6754)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient1020"> + <stop + style="stop-color:#ffffff;stop-opacity:1;" + offset="0" + id="stop1016" /> + <stop + style="stop-color:#ffffff;stop-opacity:0.09411765" + offset="1" + id="stop1018" /> + </linearGradient> + <linearGradient + y2="619.96387" + x2="568" + y1="619.96387" + x1="120" + gradientTransform="matrix(0.25,0,0,0.25,-22.00001,-50.99097)" + gradientUnits="userSpaceOnUse" + id="linearGradient1444-2-3-3" + xlink:href="#linearGradient1076" /> + <radialGradient + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(-4.1363634,1.2532736e-6,-2.6513804e-7,-1.3909091,319.22728,170.63455)" + r="44" + fy="194.19048" + fx="63.999996" + cy="194.19048" + cx="63.999996" + id="radialGradient1030-8" + xlink:href="#linearGradient1020" /> + <linearGradient + gradientTransform="matrix(0.25,0,0,0.25,-2.00001,61)" + gradientUnits="userSpaceOnUse" + y2="33.559235" + x2="104" + y1="33.559235" + x1="301" + id="linearGradient1106-2" + xlink:href="#linearGradient985" /> + </defs> + <metadata + id="metadata4"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:creator> + <cc:Agent> + <dc:title>GNOME Design Team</dc:title> + </cc:Agent> + </dc:creator> + <dc:source /> + <cc:license + rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/" /> + <dc:title>Adwaita Icon Template</dc:title> + <dc:subject> + <rdf:Bag /> + </dc:subject> + <dc:date /> + <dc:rights> + <cc:Agent> + <dc:title /> + </cc:Agent> + </dc:rights> + <dc:publisher> + <cc:Agent> + <dc:title /> + </cc:Agent> + </dc:publisher> + <dc:identifier /> + <dc:relation /> + <dc:language /> + <dc:coverage /> + <dc:description /> + <dc:contributor> + <cc:Agent> + <dc:title /> + </cc:Agent> + </dc:contributor> + </cc:Work> + <cc:License + rdf:about="http://creativecommons.org/licenses/by-sa/4.0/"> + <cc:permits + rdf:resource="http://creativecommons.org/ns#Reproduction" /> + <cc:permits + rdf:resource="http://creativecommons.org/ns#Distribution" /> + <cc:requires + rdf:resource="http://creativecommons.org/ns#Notice" /> + <cc:requires + rdf:resource="http://creativecommons.org/ns#Attribution" /> + <cc:permits + rdf:resource="http://creativecommons.org/ns#DerivativeWorks" /> + <cc:requires + rdf:resource="http://creativecommons.org/ns#ShareAlike" /> + </cc:License> + </rdf:RDF> + </metadata> + <rect + style="display:inline;opacity:1;vector-effect:none;fill:#f6f5f4;fill-opacity:1;stroke:none;stroke-width:0.01129821px;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + id="rect929-36-9-9" + width="112" + height="86" + x="8" + y="28" + rx="7.9999995" + ry="7.999999" /> + <rect + rx="3.9999998" + style="display:inline;opacity:1;vector-effect:none;fill:#241f31;fill-opacity:1;stroke:none;stroke-width:0.01129821px;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + id="rect946-0-7-4" + width="92" + height="76" + x="12" + y="32" + ry="4" /> + <path + style="display:inline;opacity:1;vector-effect:none;fill:url(#linearGradient1444-2-3-3);fill-opacity:1;stroke:none;stroke-width:0.01129821px;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + d="m 7.99999,104 v 4 c 0,4.432 3.568,8 8,8 h 96 c 4.432,0 8,-3.568 8,-8 v -4 c 0,4.432 -3.568,8 -8,8 h -96 c -4.432,0 -8,-3.568 -8,-8 z" + id="rect929-3-6-3-9" /> + <rect + y="-104" + x="16" + height="68" + width="84" + id="rect968-2" + style="display:inline;opacity:0.05;vector-effect:none;fill:url(#radialGradient1030-8);fill-opacity:1;stroke:none;stroke-width:0.01121096px;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + transform="scale(1,-1)" /> + <path + id="path1092-6-1-3-7-5-5" + style="display:inline;opacity:0.23600003;fill:none;stroke:#e5a50a;stroke-width:4;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:10;stroke-dasharray:none;stroke-opacity:1;enable-background:new" + d="m 15.99999,74 h 26 l 10,-23 6,39 8,-16 h 34" /> + <path + id="path1092-6-1-3-7-5-1-0" + style="display:inline;opacity:1;fill:none;stroke:url(#linearGradient1106-2);stroke-width:4;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:10;stroke-dasharray:none;stroke-opacity:1;enable-background:new" + d="m 15.99999,74 h 26 l 10,-23 6,39 8,-16 h 6" /> + <g + transform="translate(0,-170)" + id="g1063"> + <path + style="display:inline;opacity:1;vector-effect:none;fill:#949390;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + d="m 115.99999,232 v 4 c 0,2.20914 -1.79086,4 -4,4 -2.20914,0 -4,-1.79086 -4,-4 v -2 l 4,-2 z" + id="path1066" /> + <path + id="path1074" + d="m 115.99999,248 v 6 h -4 c -2.216,0 -4,-1.784 -4,-4 v -2 z" + style="display:inline;opacity:1;vector-effect:none;fill:#949390;fill-opacity:1;stroke:none;stroke-width:4;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" /> + <path + id="path1076" + d="m 115.99999,252 v -4 a 4,3.9999998 0 0 0 -4,-4 4,3.9999998 0 0 0 -4,4 4,3.9999998 0 0 0 4,4 z" + style="display:inline;opacity:1;vector-effect:none;fill:#d5d3cf;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" /> + <ellipse + ry="1.0000002" + rx="1" + cy="250" + cx="-113.99997" + id="ellipse1078" + style="display:inline;opacity:1;vector-effect:none;fill:#68676b;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + transform="scale(-1,1)" /> + <path + style="display:inline;opacity:1;vector-effect:none;fill:#d5d3cf;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + d="m 115.99999,230 v 4 a 4,3.9999998 0 0 1 -4,4 4,3.9999998 0 0 1 -4,-4 4,3.9999998 0 0 1 4,-4 z" + id="path1080" /> + <ellipse + transform="scale(-1)" + style="display:inline;opacity:1;vector-effect:none;fill:#68676b;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + id="ellipse1082" + cx="-113.99997" + cy="-232" + rx="1" + ry="1.0000002" /> + <path + id="path1084" + d="m 107.99999,218 v 4 c 0,2.20914 1.79086,4 4,4 2.20914,0 4,-1.79086 4,-4 v -2 l -4,-2 z" + style="display:inline;opacity:1;vector-effect:none;fill:#949390;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" /> + <path + id="path1086" + d="m 107.99999,216 v 4 a 4,3.9999998 0 0 0 4,4 4,3.9999998 0 0 0 4,-4 4,3.9999998 0 0 0 -4,-4 z" + style="display:inline;opacity:1;vector-effect:none;fill:#d5d3cf;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" /> + <ellipse + ry="1.0000002" + rx="1" + cy="-218" + cx="109.99997" + id="ellipse1088" + style="display:inline;opacity:1;vector-effect:none;fill:#68676b;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + transform="scale(1,-1)" /> + <path + style="display:inline;opacity:1;vector-effect:none;fill:#949390;fill-opacity:1;stroke:none;stroke-width:4;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + d="m 115.99999,206 v 6 h -4 c -2.216,0 -4,-1.784 -4,-4 v -2 z" + id="path1090" /> + <path + style="display:inline;opacity:1;vector-effect:none;fill:#d5d3cf;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + d="m 115.99999,210 v -4 a 4,3.9999998 0 0 0 -4,-4 4,3.9999998 0 0 0 -4,4 4,3.9999998 0 0 0 4,4 z" + id="path1092" /> + <ellipse + transform="scale(-1,1)" + style="display:inline;opacity:1;vector-effect:none;fill:#68676b;fill-opacity:1;stroke:none;stroke-width:3.99999952;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1;marker:none;marker-start:none;marker-mid:none;marker-end:none;paint-order:normal;enable-background:new" + id="ellipse1094" + cx="-113.99997" + cy="208" + rx="1" + ry="1.0000002" /> + </g> +</svg> diff --git a/help/C/fs-device.page b/help/C/fs-device.page new file mode 100644 index 0000000..ded6f06 --- /dev/null +++ b/help/C/fs-device.page @@ -0,0 +1,31 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="fs-device"> + + <info> + <revision version="0.1" date="2014-01-26" status="review"/> + <link type="guide" xref="index#filesystems" group="filesystems" /> + <link type="seealso" xref="fs-info" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Each device corresponds to a <em>partition</em> on a hard disk.</desc> + </info> + + <title>What are the different devices in the File Systems tab?</title> + + <p>Each device listed under the <gui>File Systems</gui> tab is a storage disk (like a hard drive or USB memory stick), or a disk partition. For each device, you can see what its total capacity is, how much of its capacity has been used, and some technical information about what <link xref="fs-info">type of filesystem it is</link> and <link xref="fs-info">where it is "mounted"</link>.</p> + + <p>The disk space on a single physical hard disk can be split up into multiple chunks, called <em>partitions</em>, each of which can be used as if it were a separate disk. If your hard disk has been partitioned (perhaps by you or the computer manufacturer), each partition will be listed separately in the File Systems list.</p> + + <note> + <p>You can manage disks and partitions and see more detailed disk information with the <app>Disks</app> application.</p> + </note> + +</page> diff --git a/help/C/fs-diskusage.page b/help/C/fs-diskusage.page new file mode 100644 index 0000000..0314d86 --- /dev/null +++ b/help/C/fs-diskusage.page @@ -0,0 +1,43 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="fs-diskusage"> + <info> + <revision version="0.1" date="2014-01-27" status="review"/> + <link type="guide" xref="index#filesystems" group="filesystems" /> + <link type="seealso" xref="fs-info" /> + <link type="seealso" xref="units" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>The <gui>File Systems</gui> tab shows how much space is being used on each hard disk.</desc> + </info> + + <title>Check how much disk space is being used</title> + + <p>To check how much space is available on a disk, go to the <gui>File Systems</gui> tab and look at the <gui>Used</gui> and <gui>Available</gui> columns.</p> + + <p>If several devices are shown, and you are looking for the one that has your Home folder on it, look for the disk that has <file>/</file> or <file>/home</file> listed under <gui>Directory</gui>. This is usually (but not always) the disk where your personal files are stored.</p> + + + <section id="free-space"> + <title>Freeing-up disk space</title> + + <p>If you don't have much disk space left, there are a few things you can do to try and free up some space.</p> + + <p>One is to delete unwanted files manually. You can use the <app>Disk Usage Analyzer</app> application to tell you which files and folders are taking up the most space. After deleting some files, you should then empty the <gui>Trash</gui> to make sure they are fully removed from the computer.</p> + + <p>You can also remove temporary files in various applications. For example, web browsers and software managers often keep sizeable temporary files around. (How you remove them depends on the application.)</p> + + <p>You can also try uninstalling some unwanted applications. Use your usual software manager to do this.</p> + + <p>Another way of freeing disk space is to "archive" old files by moving them to an external hard disk or online "cloud" storage, for example.</p> + + </section> + +</page> diff --git a/help/C/fs-info.page b/help/C/fs-info.page new file mode 100644 index 0000000..22d577a --- /dev/null +++ b/help/C/fs-info.page @@ -0,0 +1,47 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="fs-info"> + <info> + <revision version="0.1" date="2014-01-27" status="review"/> + <link type="guide" xref="index#filesystems" group="filesystems" /> + <link type="seealso" xref="fs-device" /> + <link type="seealso" xref="units" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Explanations of all of the fields shown in the <gui>File System</gui> tab.</desc> + </info> + + <title>Learn what the File Systems information means</title> + + <p>The File Systems tab lists which disks are attached to the computer, what they are named, and how much disk space is available on them.</p> + + <list> + <item> + <p><gui>Device</gui> lists the name that the operating system has assigned to the disk. Every bit of computer hardware that is attached to the computer is given an entry in the <file>/dev</file> directory that is used to identify it. For hard disks, it will usually look something like <file>/dev/sda</file>.</p> + </item> + + <item> + <p><gui>Directory</gui> tells you where the disk or partition is <em>mounted</em>. Mounting is the technical term for making a disk or partition available for use. A disk can be physically connected to the computer, but unless it is also mounted, the files on it cannot be accessed. When a disk is mounted, it will be linked to a folder that you can then go to in order to access the files on the disk. For example, if the <gui>Directory</gui> is listed as <file>/media/disk</file>, you can access the files by going to the <file>/media/disk</file> folder on your computer.</p> + </item> + + <item> + <p><gui>Type</gui> tells you the type of <em>filesystem</em> that is used on the disk or partition. A filesystem specifies how the computer should store files on the disk. Some operating systems can only understand some filesystem types and not others, so it can be useful to check which filesystem an external hard disk uses, for example.</p> + </item> + + <item> + <p><gui>Total</gui> shows the total capacity of the disk and <gui>Available</gui> shows how much of that capacity is available to use for files and programs. <gui>Used</gui> shows how much disk space is already being used.</p> + </item> + + </list> + + <p>The sum of Used and Available will not necessarily add up to the Total. This is because some disk space might be reserved for use by the system. The important number to look at is the Available column, as this tells you how much disk space you can actually use.</p> + <p>You might also find that the Total doesn't match up with the advertised capacity of your hard disk. This is normal, and happens for a couple of reasons. One is that hard disk manufacturers use a slightly different way of counting disk capacity to everyone else. Another is that some disk space might be reserved for use by the operating system. If there is a big difference from the capacity you expect, it might be because your disk has been split up into multiple partitions.</p> + +</page> diff --git a/help/C/fs-showall.page b/help/C/fs-showall.page new file mode 100644 index 0000000..1806cc2 --- /dev/null +++ b/help/C/fs-showall.page @@ -0,0 +1,27 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="fs-showall"> + <info> + <revision version="0.1" date="2014-01-27" status="review"/> + <link type="guide" xref="index#filesystems" group="filesystems" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>There are hidden file systems that the operating system uses.</desc> + </info> + + <title>Show all file systems, including hidden and system ones</title> + + <p>By default, the <gui>File Systems</gui> tab only shows disks and partitions that hold your files and applications. There are also a number of special filesystems that the operating system uses, but these are hidden by default.</p> + + <p>To see these special filesystems, click <guiseq><gui>System Monitor</gui><gui>Preferences</gui></guiseq>, and under the <gui>File Systems</gui> tab, check <gui>Show all file systems</gui>.</p> + + <p>Most of the entries in the list are "virtual" filesystems. These are not real disks or partitions. Instead, they are used by the operating system as a convenient layer of abstraction for various things, like managing hardware devices and storing temporary files. The system manages these automatically, so there is rarely any need for you to look at them yourself.</p> + +</page> diff --git a/help/C/index.page b/help/C/index.page new file mode 100644 index 0000000..5537a15 --- /dev/null +++ b/help/C/index.page @@ -0,0 +1,70 @@ +<page xmlns="http://projectmallard.org/1.0/" + xmlns:its="http://www.w3.org/2005/11/its" + type="guide" + id="index"> + <info> + <revision pkgversion="3.11" date="2014-01-27" status="review"/> + <title type='link' role='trail'>System Monitor</title> + <title type='link'>System Monitor</title> + <title type='text'>System Monitor</title> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <credit type="editor"> + <name>Patrick Pace</name> + <email>patrickqpace@gmail.com</email> + <years>2017</years> + </credit> + + <desc>System Monitor shows you what programs are running and how much processor time, memory, and disk space are being used.</desc> + + </info> + +<title> +<media src="figures/org.gnome.SystemMonitor.svg" width="48px" height="48px" its:translate="no" /> + System Monitor +</title> + +<p><app>System Monitor</app> shows you what programs are running and how much processor time, memory, and disk space are being used.</p> + +<section id="cpu"> + <title>Monitoring the CPU</title> + <links type="topic" style="toronto" groups="cpu"></links> +</section> + +<section id="memory"> + <title>Memory usage</title> + <links type="topic" style="toronto" groups="memory"></links> +</section> + +<section id="processes-info"> + <title>Questions about processes</title> + <links type="topic" style="toronto" groups="processes-info"></links> +</section> + +<section id="processes-tasks"> + <title>Common tasks with processes</title> + <links type="topic" style="toronto" groups="processes-tasks"></links> +</section> + +<section id="filesystems"> + <title>Information about file systems</title> + <links type="topic" style="toronto" groups="filesystems"></links> +</section> + +<section id="net"> + <title>Network information</title> + <links type="topic" style="toronto" groups="net"></links> +</section> + +<section id="other"> + <title>Miscellaneous</title> + <links type="topic" style="toronto" groups="other"></links> +</section> +</page> diff --git a/help/C/legal.xml b/help/C/legal.xml new file mode 100644 index 0000000..aa36246 --- /dev/null +++ b/help/C/legal.xml @@ -0,0 +1,8 @@ +<license xmlns="http://projectmallard.org/1.0/" + href="http://creativecommons.org/licenses/by-sa/3.0/"> + + <p>This work is licensed under a + <link href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons + Attribution-ShareAlike 3.0 Unported License</link>.</p> + +</license> diff --git a/help/C/mem-check.page b/help/C/mem-check.page new file mode 100644 index 0000000..c30de1b --- /dev/null +++ b/help/C/mem-check.page @@ -0,0 +1,97 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="mem-check"> + + <info> + <revision pkgversion="3.11" date="2014-01-28" status="candidate"/> + <link type="guide" xref="index#memory" group="memory" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <credit type="editor"> + <name>Ekaterina Gerasimova</name> + <email>kittykat3756@gmail.com</email> + </credit> + + <desc>The <gui>Resources</gui> tab tells you how much of your computer's + memory (RAM) is being used.</desc> + </info> + + <title>How much memory is being used?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Go to the Resources tab and look at the graph/indicators (short topic). + Point to resources about memory problems. Maybe mention how you can find + which processes are using the most memory.</p> + </comment> + + <p>To check the current memory usage of your computer:</p> + + <steps> + <item> + <p>Click the <gui>Resources</gui> tab.</p> + </item> + </steps> + + <p><gui>Memory and Swap History</gui> displays a running line graph for + memory and swap as a percentage of the total available. These are plotted + against time, with the current time at the right.</p> + + <note style="tip"> + <p>The color of each line is indicated by the pie graphs below. Click the + pie graph to change the color of the line graph.</p> + </note> + + <p>The <gui>Memory</gui> pie graph shows memory usage in + <link xref="units">GiB</link> and as a percentage of the total available.</p> + + <p>To change the <gui>update interval</gui>:</p> + + <steps> + <item> + <p>Click + <guiseq><gui>System Monitor</gui><gui>Preferences</gui></guiseq>.</p> + </item> + <item> + <p>Click the <gui>Resources</gui> tab.</p> + </item> + <item> + <p>Enter a value for <gui>Update interval in seconds</gui>.</p> + </item> + </steps> + +<section id="highusage"> + <title>Which processes are using the most memory?</title> + + <p>To check which processes are using the most memory:</p> + + <steps> + <item> + <p>Click the <gui>Processes</gui> tab.</p> + </item> + <item> + <p>Click the <gui>Memory</gui> column header to sort the processes + according to memory use.</p> + <note> + <p>The arrow in the column header shows the sort direction; click again + to reverse it. If the arrow points up, the processes using the most + memory appear at the top of the list.</p> + </note> + </item> + </steps> +</section> + +</page> diff --git a/help/C/mem-swap.page b/help/C/mem-swap.page new file mode 100644 index 0000000..2176c08 --- /dev/null +++ b/help/C/mem-swap.page @@ -0,0 +1,60 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="mem-swap"> + + <info> + <revision pkgversion="3.11" date="2014-01-28" status="final"/> + <link type="guide" xref="index#memory" group="memory" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Swap memory allows your computer to run more applications at the same + time than will fit into the system memory (RAM).</desc> + </info> + + <title>What is "swap" memory?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain what swap is and how it helps. Explain that the computer may run + slowly if it's swapping too much.</p> + </comment> + + <p>Swap memory or <em>swap space</em> is the on-disk component of the virtual + memory system. It is pre-configured as a <em>swap partition</em> or a + <em>swap file</em> when Linux is first installed, but can also be added + later.</p> + + <note> + <p>Disk access is <em>very</em> slow compared to memory access. The system + runs more slowly if there is excessive swapping, or <em>thrashing</em>, + when the system is unable to find enough free memory. In this situation the + only solution is to add more RAM.</p> + </note> + + <p>To see whether swapping, or <em>paging</em>, has become a performance + issue:</p> + + <steps> + <item> + <p>Click the <gui>Resources</gui> tab.</p> + </item> + <item> + <p>The <gui>Memory and Swap History</gui> graph shows memory and swap use + as percentages.</p> + </item> + </steps> + +</page> diff --git a/help/C/memory-map-use.page b/help/C/memory-map-use.page new file mode 100644 index 0000000..b2f03e4 --- /dev/null +++ b/help/C/memory-map-use.page @@ -0,0 +1,174 @@ +<page xmlns="http://projectmallard.org/1.0/" + xmlns:ui="http://projectmallard.org/ui/1.0/" + type="topic" style="task" + id="memory-map-use"> + + <info> + <revision pkgversion="3.11" date="2014-01-28" status="candidate"/> + <link type="guide" xref="index#memory" group="memory" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>View the memory map of a process.</desc> + </info> + + <title>Using memory maps</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how to use the Memory Map feature.</p> + </comment> + + <p><gui>Virtual memory</gui> is a representation of the combined + <gui>physical memory</gui> and <link xref="mem-swap">swap space</link> in a + system. It enables running processes to access <em>more</em> than the + existing physical memory by <gui>mapping</gui> locations in physical memory + to files on disk. When the system needs more pages of memory than are + available, some of the existing pages will be <em>paged out</em> or written + to the swap space.</p> + + <p>The <gui>memory map</gui> displays the total virtual memory use of the + process, and can be used to determine the memory cost of running a single or + multiple instances of the program, to ensure the use of the correct shared + libraries, to see the results of adjusting various performance tuning + parameters the program may have, or to diagnose issues such as memory + leaks.</p> + + <p>To display the <link xref="memory-map-what">memory map</link> of a + process:</p> + + <steps> + <item><p>Click the <gui>Processes</gui> tab.</p></item> + <item><p>Right click the desired process in the <gui>process list</gui>.</p></item> + <item><p>Click <gui>Memory Maps</gui>.</p></item> + </steps> + +<section id="read"> + <title>Reading the memory map</title> + + <list> + <item> + <p>Addresses are displayed in hexadecimal (base 16).</p> + </item> + <item> + <p>Sizes are displayed in <link xref="units">IEC binary + prefixes</link>.</p> + </item> + <item> + <p>At runtime the process can allocate more memory dynamically into an + area called the <em>heap</em>, and store arguments and variables into + another area called the <em>stack</em>.</p> + </item> + <item> + <p>The program itself and each of the shared libraries has three entries + each, one for the read-execute text segment, one for the read-write data + segment and one for a read-only data segment. Both data segments need to + be paged out at swap time.</p> + </item> + </list> + +<table shade="rows" ui:expanded="false"> +<title>Properties</title> + <tr> + <td><p>Filename</p></td> + <td><p>The location of a shared library that is currently used by the + process. If this field is blank, the memory information in this row + describes memory that is owned by the process whose name is displayed above + the memory-map table.</p></td> + </tr> + <tr> + <td><p>VM Start</p></td> + <td><p>The address at which the memory segment begins. VM Start, VM End and + VM Offset together specify the location on disk to which the shared library + is mapped.</p></td> + </tr> + <tr> + <td><p>VM End</p></td> + <td><p>The address at which the memory segment ends.</p></td> + </tr> + <tr> + <td><p>VM Size</p></td> + <td><p>The size of the memory segment.</p></td> + </tr> + <tr> + <td><p>Flags</p></td> + <td><p>The following flags describe the different types of memory-segment + access that the process can have:</p> + <terms> + <item> + <title><gui>p</gui></title> + <p>The memory segment is private to the process, and is not accessible + to other processes.</p> + </item> + <item> + <title><gui>r</gui></title> + <p>The process has permission to read from the memory segment.</p> + </item> + <item> + <title><gui>s</gui></title> + <p>The memory segment is shared with other processes.</p> + </item> + <item> + <title><gui>w</gui></title> + <p>The process has permission to write into the memory segment.</p> + </item> + <item> + <title><gui>x</gui></title> + <p>The process has permission to execute instructions that are + contained within the memory segment.</p> + </item> + </terms> + </td> + </tr> + <tr> + <td><p>VM Offset</p></td> + <td><p>The location of the address within the memory segment, + measured from VM Start.</p></td> + </tr> + <tr> + <td><p>Private, Shared, Clean, Dirty</p></td> +<!-- <td><p>Text pages are flagged read-execute in memory and don't need to + be written to swap since they can be re-loaded from their original location + on disk. Data pages have read-write permissions, and if modified when in + memory, they are labeled <em>dirty</em>, and when designated for swapping, + must be paged out.</p></td> +--> + <td><list><item><p><em>private</em> pages are accessed by one + process</p></item> + <item><p><em>shared</em> pages can be accessed by more than + one process</p></item> + <item><p><em>clean</em> pages have not yet been modified + while in memory and can be discarded when designated to be swapped + out</p></item> + <item><p><em>dirty</em> pages have been modified while in + memory and must be written to disk when designated to be swapped + out</p></item></list></td> + </tr> + <tr> + <td><p>Device</p></td> + <td><p>The major and minor numbers of the device on which the shared + library filename is located. Together these specify a partition on the + system.</p></td> + </tr> + <tr> + <td><p>Inode</p></td> + <td><p>The inode on the device from which the shared library location + is loaded into memory. An inode is the structure the filesystem uses to + store a file, and the number assigned to it is unique.</p></td> + </tr> +</table> + +</section> +</page> diff --git a/help/C/memory-map-what.page b/help/C/memory-map-what.page new file mode 100644 index 0000000..73bd0bd --- /dev/null +++ b/help/C/memory-map-what.page @@ -0,0 +1,79 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="memory-map-what"> + + <info> + <revision pkgversion="3.11" date="2014-01-28" status="candidate"/> + <link type="guide" xref="index#memory" group="memory" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>The memory map of a process can help diagnose certain memory + issues.</desc> + </info> + + <title>What is a memory map?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Difficult conceptual topic. Explain how to use memory maps to do + whatever the hell you're supposed to use them for.</p> + </comment> + + <comment> + <cite date="2014-01-28" href="mailto:kittykat3756@gmail.com">Kat</cite> + <p>TODO: check gui tags.</p> + </comment> + + <p><gui>Virtual memory</gui> is a representation of the combined + <gui>physical memory</gui> and <link xref="mem-swap">swap space</link> in a + system. It enables running processes to access <em>more</em> than the + existing physical memory by <gui>mapping</gui> locations in physical memory + to files on disk.</p> + + <p>When a program is launched, the system assigns it a unique process ID + (PID) and its <em>instructions</em> and <em>data</em> are loaded into memory + in <em>pages</em>. The page table of each process maps the correspondence + between its pages in virtual memory and their location in physical memory. + The <gui>memory map</gui> displays the total virtual memory use of the + process, and can be used to determine the memory cost of running a single or + multiple instances of the program, to ensure the use of the correct shared + libraries, to see the results of adjusting various performance tuning + parameters the program may have, or to diagnose issues such as memory + leaks.</p> + + <p>If multiple copies of a program are running, the instructions (or + <em>text</em>) of the program only need to be loaded once into physical + memory. Each time a new instance of the program is launched (as a unique + process with its own virtual memory pages), its page table maps the location + of the text in virtual memory to those instructions in the original real + memory location. In addition, any dynamic shared libraries used by the + process appear as distinct in virtual memory, but are shared references to a + single copy of the library's text segment in real memory. When accounting for + the total memory use of a process, it is important to note that the cost of + shared libraries loaded into memory can be spread across all processes + currently using them.</p> + + <p>When the system needs more pages of memory than are available, some of the + existing pages will be <em>paged out</em> or written to the <gui>swap + space</gui>. Text pages are flagged read-execute in memory and don't need to + be written to swap since they can be re-loaded from their original location + on disk. Data pages have read-write permissions, and if modified when in + memory, they are labeled <em>dirty</em>, and when designated for swapping, + must be paged out. When a page in swap space is required by a running + process, it needs to be swapped back in before use, perhaps causing another + page to be paged out.</p> + +</page> diff --git a/help/C/net-bits.page b/help/C/net-bits.page new file mode 100644 index 0000000..5722b4d --- /dev/null +++ b/help/C/net-bits.page @@ -0,0 +1,45 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="net-bits"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#net" group="net" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Choose the units to display your network speed.</desc> + </info> + + <title>Show the network speed in bits instead of bytes per second</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Brief topic. Explain how to do this, and why you might want to do it.</p> + </comment> + + <p>Network speed is often shown in bits per second, rather than bytes per + second. This is called the <em>bit rate</em>, or <em>data rate</em>.</p> + + <p>To display the network speed in bits:</p> + + <steps> + <item><p>Click + <guiseq><gui>System Monitor</gui><gui>Preferences</gui></guiseq>.</p> + </item> + <item><p>Click the <gui>Resources</gui> tab.</p></item> + <item><p>Select <gui>Show network speed in bits</gui>.</p></item> + </steps> + +</page> diff --git a/help/C/net-check.page b/help/C/net-check.page new file mode 100644 index 0000000..ca3cac0 --- /dev/null +++ b/help/C/net-check.page @@ -0,0 +1,58 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="net-check"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="incomplete"/> + <link type="guide" xref="" group="net" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>The <gui>Resources</gui> tab shows you the volume of data that's + passing over your network connections. + </desc> + </info> + + <title>Check network usage and connection speed</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how to check network usage and what all the numbers mean. Why + might there be spikes?</p> + </comment> + + <p>To check the current network usage of your computer:</p> + + <steps> + <item><p>Click the <gui>Resources</gui> tab.</p> + </item> + </steps> + <list> + <item><p><gui>Network History</gui> displays a running line graph for the + volume of data passing over your network connections, split up into data + received and sent. These are plotted against time, with the current time at + the right.</p> + <note style = "tip"><p>The color of each line is indicated by the down and + up arrows (for <gui>Receiving</gui> and <gui>Sending</gui> respectively) + underneath the graph. Click an arrow to change the color of the + corresponding line graph.</p> + </note> + </item> + <item><p>Below the graph is shown <gui>Receiving</gui> and <gui>Sending</gui> + <link xref="net-bits">bit rate</link> or connection speed, as well as + total data transferred in each direction.</p> + </item> + </list> + +</page> diff --git a/help/C/process-columns.page b/help/C/process-columns.page new file mode 100644 index 0000000..ec58778 --- /dev/null +++ b/help/C/process-columns.page @@ -0,0 +1,42 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-columns"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-29" status="incomplete"/> + <link type="guide" xref="" group="processes-tasks" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Various other columns can be shown in the <gui>Processes</gui> tab.</desc> + </info> + + <title>Display different information about processes</title> + + <p>To display different or additional information in the process list:</p> + + <steps> + <item><p>Click + <guiseq><gui>System Monitor</gui><gui>Preferences</gui></guiseq>.</p></item> + <item><p>Click the <gui>Processes</gui> tab.</p></item> + <item><p>Select the desired headings in the <gui>Information Fields</gui> + list.</p></item> + </steps> + + <p>For each process listed in the <gui>Processes</gui> tab, + <app>System Monitor</app> provides information in a number of categories. + For detailed descriptions of what the columns mean, check the + <link href="man:ps"><cmd>ps</cmd> man page</link>.</p> + +</page> diff --git a/help/C/process-explain.page b/help/C/process-explain.page new file mode 100644 index 0000000..3ab8fbf --- /dev/null +++ b/help/C/process-explain.page @@ -0,0 +1,45 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-explain"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#processes-info" group="processes-info" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>A process can be manipulated from the process list.</desc> + </info> + + <title>What is a process?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain, in simple terms, what a process is, how they relate to + applications, how some are 'system processes', and what you can do with a + process.</p> + </comment> + + <p>A <gui>process</gui> is a program or application being executed by the + system. When an application is launched, the system assigns a unique process ID + (PID), and its instructions and data are loaded into memory.</p> + + <p>The <gui>Processes</gui> tab displays information on processes, and allows + you to <gui>Stop</gui>, <gui>Continue</gui>, <gui>End</gui>, <gui>Kill</gui>, + or change the priority of a process. If you choose to display + <gui>All Processes</gui>, the process list will include + <em>system processes</em>, which run in the background providing various + services that keep a computer running.</p> + +</page> diff --git a/help/C/process-files.page b/help/C/process-files.page new file mode 100644 index 0000000..f6413b3 --- /dev/null +++ b/help/C/process-files.page @@ -0,0 +1,31 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-files"> + <info> + <revision version="0.1" date="2014-01-25" status="review"/> + <link type="guide" xref="index#processes-tasks" group="processes-tasks" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>View files being accessed by processes.</desc> + </info> + + <title>List which files a process has open</title> + + <p>Processes sometimes need to keep files open. They could be files that you are viewing or editing, or temporary or system files that the process needs to work properly.</p> + + <p>To see which files a process has open:</p> + <steps> + <item><p>Find the process in the <gui>Processes</gui> tab and click once to select it.</p></item> + <item><p>Right-click the process and select <gui>Open Files</gui>.</p></item> + </steps> + + <p>In the list of open files that appears, you might find some special files called <em>sockets</em>. These are actually a way for processes to communicate with one another, and are not normal files that you can view or edit.</p> + +</page> diff --git a/help/C/process-forcequit.page b/help/C/process-forcequit.page new file mode 100644 index 0000000..56c5a5f --- /dev/null +++ b/help/C/process-forcequit.page @@ -0,0 +1,36 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-forcequit"> + <info> + <revision version="0.1" date="2011-08-28" status="stub"/> + <link type="guide" xref="..." group="processes-tasks" /> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <desc>If an application has frozen, you can force it to close by "killing" it.</desc> + </info> + + <title>Close an application that's not responding</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how to force an application to quit using the System Monitor.</p> + </comment> + + <comment> + <cite date="2011-08-28" href="mailto:ksinnott5ht@gmail.com">Kelly Sinnott</cite> + <p>I think that this page is not necessary because process-end-kill.page covers it well.</p> + </comment> + <p>Short introductory text...</p> + + <steps> + <item><p>First step...</p></item> + <item><p>Second step...</p></item> + <item><p>Third step...</p></item> + </steps> + +</page> diff --git a/help/C/process-identify-file.page b/help/C/process-identify-file.page new file mode 100644 index 0000000..a1d7b78 --- /dev/null +++ b/help/C/process-identify-file.page @@ -0,0 +1,53 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-identify-file"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#processes-tasks" group="processes-tasks" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Search for a file that's open to display which process is using it.</desc> + </info> + + <title>Find which program is using a specific file</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how you can search for a file (or part of a filename) and it will + show which processes are using it. Explain why this might be useful.</p> + </comment> + + <p>Sometimes an error message will tell you a device (like the sound device or + the DVD ROM) is busy, or the file you want to edit is in use. To find the + process or processes responsible:</p> + + <steps> + <item><p>Click + <guiseq><gui>System Monitor</gui><gui>Search for Open Files</gui></guiseq>.</p> + </item> + <item><p>Enter a filename or part of a filename. This could be + <file>/dev/snd</file> for the sound device or <file>/media/cdrom</file> + for the DVD ROM.</p> + </item> + <item><p>Click <gui>Find</gui>.</p> + </item> + </steps> + + <p>This will display a list of running processes that are currently accessing + the file or files that match the search. Quitting the program should allow you + to access the device or edit the file.</p> + +</page> diff --git a/help/C/process-identify-hog.page b/help/C/process-identify-hog.page new file mode 100644 index 0000000..d7f0d95 --- /dev/null +++ b/help/C/process-identify-hog.page @@ -0,0 +1,62 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-identify-hog"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#processes-tasks" group="processes-tasks" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Sort the list of processes by <gui>% CPU</gui> to see which + application is using up the computer's resources.</desc> + </info> + + <title>Which program is making the computer run slowly?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how the System Monitor can be used to find + misbehaving/resource-hogging processes. (A lot of process use 100% CPU or + similar if they hang, for example.)</p> + </comment> + + <p>A program that is using more than its share of the CPU may slow down the + whole computer. To find which process could be doing this:</p> + + <steps> + <item> + <p>Click the <gui>Processes</gui> tab.</p> + </item> + <item> + <p>Click the <gui>% CPU</gui> column header to sort the processes + according to CPU use.</p> + <note> + <p>The arrow in the column header shows the sort direction; click again + to reverse it. The arrow should point up.</p> + </note> + </item> + </steps> + + <p>The processes at the top of the list are using the highest percentage CPU. + Once you identify which one might be using more resources than it should, you + can decide whether to close the program itself, or close other programs to + try to reduce the CPU load.</p> + + <note style = "tip"> + <p>A process that has hung or crashed might use 100% CPU. If this happens + you may need to <link xref="process-kill">kill</link> the process.</p> + </note> + +</page> diff --git a/help/C/process-kill.page b/help/C/process-kill.page new file mode 100644 index 0000000..0ff95bd --- /dev/null +++ b/help/C/process-kill.page @@ -0,0 +1,29 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-kill"> + <info> + <revision version="0.1" date="2014-01-28" status="review"/> + <link type="guide" xref="index#processes-info" group="processes-info" /> + <link type="seealso" xref="process-identify-hog" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>If a program stops working or freezes, you can force it to close.</desc> + + </info> + + <title>Kill (close) a program immediately</title> + + <p>If a program stops working or freezes, you can force it to close ("kill" it) using <app>System Monitor</app>. Go to the <gui>Processes</gui> tab and click to select the process you want to kill. Then, click <gui>End Process</gui>.</p> + + <p>If the process does not close after a few seconds, right-click it and select <gui>Kill</gui> from the menu that appears.</p> + + <p>Using <gui>End Process</gui> tries to close the process properly, giving it time to save files and so on, whereas <gui>Kill</gui> forces it to close straight away. For some programs, this might mean that you lose unsaved files. You should always try <gui>End Process</gui> first.</p> + +</page> diff --git a/help/C/process-loadaverage.page.stub b/help/C/process-loadaverage.page.stub new file mode 100644 index 0000000..6b21b9a --- /dev/null +++ b/help/C/process-loadaverage.page.stub @@ -0,0 +1,50 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-loadaverage"> + <info> + <revision version="0.1" date="2011-08-19" status="stub"/> + <link type="guide" xref="index" group="processes-info" /> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011</years> + </credit> + + <desc>The <em>load average</em> tells you how much work your computer has + been doing over the past few minutes.</desc> + </info> + + <title>What is the load average?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how to interpret the load averages quoted on the Processes tab.</p> + </comment> + + <p>The <gui>load average</gui> shows the load on the CPU over three different + time intervals, one minute, five minutes and fifteen minutes. These are displayed + on the <gui>Processes</gui> tab above the process list, and are an indicator of + system processing capacity.</p> + + <p>The <em>load</em> is the number of processes currently running plus the + number of processes <em>queued</em> to run on the system's CPU(s). A load + showing a utilization of 100% would be roughly 1.0 times the number of CPUs or + <link xref="cpu-multicore">cores</link> in the system; load averages constantly + hitting this number would indicate that the system is fully-loaded with no + processes waiting for processor time. Lower numbers indicate that the system's + processing power is sufficient for the processes being run, while numbers that + are consistently higher might mean more processing power is needed.</p> + + <p>Three intervals are shown so that spikes and trends in the numbers can be + taken into account: if the load average spikes higher in the one- or + five-minute intervals, but settles down below the 100% mark over the + fifteen-minute interval, system processing capacity is probably sufficient.</p> + +</page> diff --git a/help/C/process-many.page b/help/C/process-many.page new file mode 100644 index 0000000..baa5a85 --- /dev/null +++ b/help/C/process-many.page @@ -0,0 +1,23 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-many"> + <info> + <revision version="0.1" date="2014-01-25" status="review"/> + <link type="guide" xref="index#processes-info" group="processes-info" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Lots of system processes run automatically in the background.</desc> + </info> + + <title>Why are there processes listed that I did not start?</title> + + <p>There are usually lots of processes listed under the <gui>Processes</gui> tab. Only a few of these will be programs that you started yourself. The others are mostly processes that are needed by the operating system to make the computer run correctly. These are started automatically when you log in, and typically run quietly in the background.</p> + +</page> diff --git a/help/C/process-priority-change.page b/help/C/process-priority-change.page new file mode 100644 index 0000000..b6ae128 --- /dev/null +++ b/help/C/process-priority-change.page @@ -0,0 +1,45 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-priority-change"> + <info> + <revision version="0.1" date="2014-01-26" status="review"/> + <link type="guide" xref="index#processes-tasks" group="processes-tasks" /> + <link type="seealso" xref="cpu-check" /> + <link type="seealso" xref="process-identify-hog" /> + <link type="seealso" xref="process-priority-what" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>Decide whether a process should get a bigger or smaller share of the processor's time.</desc> + </info> + + <title>Change the priority of a process</title> + + <p>You can tell the computer that certain processes should have a higher priority than others, and so should be given a bigger share of the available computing time. This can make them run faster, but only in certain cases. You can also give a process a <em>lower</em> priority if you think it is taking up too much processing power.</p> + + <steps> + <item><p>Go to the <gui>Processes</gui> tab and click on the process you want to have a different priority.</p></item> + <item><p>Right-click the process, and use the <gui>Change Priority</gui> menu to assign the process a higher or lower priority.</p></item> + </steps> + + <p>There is typically little need to change process priorities manually. The computer will usually do a good job of managing them itself. (The system for managing the priority of processes is called <link xref="process-priority-what">nice</link>.)</p> + + + <section id="faster"> + <title>Does higher priority make a process run faster?</title> + + <p>The computer shares its processing time between all of the running processes. This is normally shared intelligently, so programs that are doing more work automatically get a bigger share of the resources. Most of the time, processes will get as much processing time as they need, and so will already be running as fast as possible. Changing their priority won't make a difference.</p> + + <p>If your computer is running several computationally-intensive programs at once, however, its processing time may be "over-subscribed" (that is, the <link xref="process-identify-hog">processor's full capacity</link> will be in use). You may notice that other programs run slower than usual because there is not enough processing time to share between all of them.</p> + + <p>In this case, changing the priority of processes can be helpful. You could lower the priority of one of the computationally-intensive processes to free up more processing time for other programs. Alternatively, you could increase the priority of a process that is more important to you, and that you want to run faster.</p> + + </section> + +</page> diff --git a/help/C/process-priority-what.page b/help/C/process-priority-what.page new file mode 100644 index 0000000..4b2f949 --- /dev/null +++ b/help/C/process-priority-what.page @@ -0,0 +1,36 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-priority-what"> + <info> + <revision version="0.1" date="2014-01-26" status="stub"/> + <link type="guide" xref="" group="processes-info" /> + <link type="seealso" xref="process-priority-change" /> + <link type="seealso" xref="cpu-multicore" /> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011</years> + </credit> + + <desc>The <em>nice</em> value of a process is used to adjust its priority.</desc> + </info> + + <title>What is the <em>nice</em> value of a process?</title> + + <p>The priority of a process determines the share of time the process is + alotted on a system's one or more processors (CPUs or cores). A <em>nice</em> + process, or one with a higher nice value, concedes priority to other processes. + Adjusting the nice value will increase or decrease the scheduling priority.</p> + + <p>The lower the nice value, the higher the priority of the process. The nice + value ranges from -20 (low nice, higher priority) to 20 (lower priority). The + default value of nice is usually 0.</p> + +</page> diff --git a/help/C/process-status.page b/help/C/process-status.page new file mode 100644 index 0000000..b437995 --- /dev/null +++ b/help/C/process-status.page @@ -0,0 +1,64 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-status"> + + <info> + <revision pkgversion="3.11" date="2014-01-28" status="complete"/> + <link type="guide" xref="index#processes-info" group="processes-info" /> + <link type="seealso" xref="process-kill" /> + <link type="seealso" xref="cpu-check" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2014</years> + </credit> + + <desc>The status of a process can be running, sleeping, stopped, or zombie.</desc> + </info> + + <title>What do the process statuses mean?</title> + + <p>The status of a process tells you whether it is currently doing something or not. There are four statuses that a process can have:</p> + + <terms> + <item> + <title>Running</title> + <p>Processes that are currently doing something (for example, a web + browser loading a web page). Running processes are those that are + actively using the processor (CPU).</p> + </item> + <item> + <title>Sleeping</title> + <p>Processes that are not currently doing anything (for example, because + they are waiting for something to happen). They don't use any of the + processor's time, but still take up memory. If they need to do something, + they will "wake up" and change their status to <em>running</em>.</p> + </item> + <item> + <title>Stopped</title> + <p>A <em>stopped</em> process is one that has been put to sleep manually. + You might want to stop a process temporarily if it is using too much + processing time, for example.</p> + <p>To do this, click the process in the <gui>Processes</gui> tab, then + right-click it and select <gui>Stop</gui> from the menu that appears. You + can wake it up again by clicking <gui>Continue</gui> on the same + menu.</p> + </item> + <item> + <title>Zombie</title> + <p>A zombie process is one that has finished running and will never start + again, but is being kept in the list of processes for some reason. This + usually happens because it was started by another program that needs to + know if it finished successfully or not, but which has not checked on the + process yet.</p> + <p>Zombie processes do not use any memory or processing time, and will + eventually go away. You do not need to do anything to get rid of them.</p> + </item> + </terms> + + <p>The majority of processes will either be running or sleeping.</p> + +</page> diff --git a/help/C/process-update-speed.page b/help/C/process-update-speed.page new file mode 100644 index 0000000..6531542 --- /dev/null +++ b/help/C/process-update-speed.page @@ -0,0 +1,53 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="process-update-speed"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#processes-tasks" group="processes-tasks" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Refresh the information shown in the System Monitor with a longer or + shorter interval.</desc> + </info> + + <title>Make the information update faster or slower</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Explain how to make the info update faster (see Preferences dialog). + Explain that faster updates mean that the System Monitor will use more + CPU.</p> + </comment> + + <p>To change the information refresh speed:</p> + + <steps> + <item><p>Click + <guiseq><gui>System Monitor</gui><gui>Preferences</gui></guiseq>.</p> + </item> + <item><p>Click the desired tab (<gui>Processes</gui>, <gui>Resources</gui> + or <gui>File Systems</gui>).</p> + </item> + <item><p>Enter a value for <gui>Update interval in seconds</gui>.</p> + </item> + </steps> + + <note style = "warning"><p>Setting the <gui>Update interval</gui> to a + lower value will cause <gui>System Monitor</gui> itself to use more of the + CPU.</p> + </note> + +</page> diff --git a/help/C/solaris-mode.page b/help/C/solaris-mode.page new file mode 100644 index 0000000..17ff7cd --- /dev/null +++ b/help/C/solaris-mode.page @@ -0,0 +1,51 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="solaris-mode"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#other" group="other" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Use Solaris mode to reflect the number of CPUs.</desc> + </info> + + <title>What is Solaris mode?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Very brief topic. Explain what "Solaris mode" in the preferences dialog + means. The current manual has some information.</p> + </comment> + + <p>In a system that has multiple CPUs or <link xref="cpu-multicore">cores</link>, + processes can use more than one at the same time. It is possible for the + <gui>% CPU</gui> column to display values that total greater than 100% (i.e. + 400% in a 4-CPU system). <gui>Solaris mode</gui> divides the <gui>% CPU</gui> + for each process by the number of CPUs in the system so that the total will be + 100%.</p> + + <p>To display the <gui>% CPU</gui> in <gui>Solaris mode</gui>:</p> + + <steps> + <item><p>Click <gui>Preferences</gui> in the app menu.</p></item> + <item><p>Click the <gui>Processes</gui> tab.</p></item> + <item><p>Select <gui>Divide CPU Usage by CPU Count</gui>.</p></item> + </steps> + + <note><p>The term <gui>Solaris mode</gui> derives from Sun's UNIX, compared + to the Linux default of IRIX mode, named for SGI's UNIX.</p></note> + +</page> diff --git a/help/C/units.page b/help/C/units.page new file mode 100644 index 0000000..c78b088 --- /dev/null +++ b/help/C/units.page @@ -0,0 +1,48 @@ +<page xmlns="http://projectmallard.org/1.0/" + type="topic" style="task" + id="units"> + <info> + <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/> + <link type="guide" xref="index#other" group="other" /> + + <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> + + <credit type="author copyright"> + <name>Phil Bull</name> + <email>philbull@gmail.com</email> + <years>2011</years> + </credit> + + <credit type="author copyright"> + <name>Michael Hill</name> + <email>mdhillca@gmail.com</email> + <years>2011, 2014</years> + </credit> + + <desc>Units of measure for memory and disk space</desc> + </info> + + <title>Is GiB the same as GB (gigabyte)?</title> + + <comment> + <cite date="2011-06-18" href="mailto:philbull@gmail.com">Phil Bull</cite> + <p>Answer this question, quite briefly.</p> + </comment> + + <p>The memory and disk space statistics are displayed using <em>IEC binary + prefixes</em>, KiB, MiB, GiB, TiB (for kibi, mebi, gibi and tebi). These are + intended to distinguish binary reporting of sizes used in System Monitor + (multiples of 1024) from decimal sizes (multiples of 1000) commonly used, for + instance, in packaging of hard disks.</p> + + <p>Typical binary units:</p> + <list> + <item><p>1 KiB = 1024 bytes</p></item> + <item><p>1 MiB = 1048576 bytes</p></item> + <item><p>1 GiB = 1073741842 bytes</p></item> + </list> + + <p>An external hard drive, advertised as 1.0 TB (terabytes), would display + as 0.909 TiB (tebibytes).</p> + +</page> |
