[gnome-system-monitor/mallard-help] Relicense files; rewrite files that Kelly wrote, as she is not responding to relicensing requests
- From: Phil Bull <philbull src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-system-monitor/mallard-help] Relicense files; rewrite files that Kelly wrote, as she is not responding to relicensing requests
- Date: Sun, 26 Jan 2014 16:35:58 +0000 (UTC)
commit 2479a78b5cf431a53ca61618a418f97da98c7a8b
Author: Phil Bull <philbull gmail com>
Date: Sun Jan 26 16:34:29 2014 +0000
Relicense files; rewrite files that Kelly wrote, as she is not responding to relicensing requests
help/C/fs-device.page | 26 ++++++-----
help/C/fs-diskusage.page | 15 ++----
help/C/fs-info.page | 14 ++++++
help/C/legal.xml | 80 +++--------------------------------
help/C/process-end-kill.page | 23 ++++------
help/C/process-files.page | 31 +++++--------
help/C/process-kill.page | 42 +++++++------------
help/C/process-many.page | 24 ++++-------
help/C/process-priority-change.page | 48 ++++++++++++---------
help/C/process-priority-what.page | 17 ++------
help/C/process-status.page | 58 ++++++++++++-------------
11 files changed, 144 insertions(+), 234 deletions(-)
---
diff --git a/help/C/fs-device.page b/help/C/fs-device.page
index ca28700..e87159b 100644
--- a/help/C/fs-device.page
+++ b/help/C/fs-device.page
@@ -3,27 +3,29 @@
id="fs-device">
<info>
- <revision version="0.1" date="2011-08-19" status="review"/>
+ <revision version="0.1" date="2014-01-26" status="review"/>
<link type="guide" xref="index" 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>2011</years>
- </credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <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 System tab?</title>
-
- <p>The <gui>File Systems</gui> tab of <app>System Monitor</app> displays a list of the <em>disk
devices</em> on your computer. The path given in the column <gui>Device</gui> is an interface assigned by
your computer during start-up to a given <em>partition</em> of the disk it exists on. The term "partition"
describes one or more physical areas of storage on a single physical drive. The computer makes these
partitions accessible to the user via an assigned <em>file system</em> in a process referred to as
<em>mounting</em>. The <gui>Device</gui> column shows the automatically assigned interface (which may or may
not be mounted) while the <gui>Directory</gui> column shows the mounted location. You can double-click the
device to open up the mounted directory in <app>Nautilus</app>.</p>
- <p>The identifiers assigned by the computer (in the <gui>Device</gui> column) reflect the physical
location of each device. <cmd>/dev/sda</cmd> is the first disk. <cmd>/dev/sda1</cmd> is the first partition
on the first disk. <cmd>/dev/sdb2</cmd> is the second partition on the second disk, and so on. The final
letter describes the disk, and the number describes the partition on that disk.</p>
+ <title>What are the different devices in the File Systems tab?</title>
- <note><p>To learn more about disk setup, look for the <app>Disk Utility</app> application in the
<gui>Activities</gui> menu. This tool provides comprehensive information about your computer's drives and
their partitions.</p></note>
+ <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>Disk
Utility</app> application.</p>
+ </note>
</page>
diff --git a/help/C/fs-diskusage.page b/help/C/fs-diskusage.page
index 0d84eea..95a1b8b 100644
--- a/help/C/fs-diskusage.page
+++ b/help/C/fs-diskusage.page
@@ -2,7 +2,7 @@
type="topic" style="task"
id="fs-diskusage">
<info>
- <revision version="0.1" date="2011-08-19" status="review"/>
+ <revision version="0.1" date="2014-01-26" status="review"/>
<link type="guide" xref="index" group="filesystems" />
<credit type="author copyright">
@@ -10,22 +10,16 @@
<email>philbull gmail com</email>
<years>2011</years>
</credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</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>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Point the user to the File Systems tab. Point to resources on freeing-up disk space.</p>
- </comment>
+ <app>Disk Usage Analyzer</app>
+
+<!--
<p>Low disk space can result in many issues. from not having enough space for new files to processes
acting slower or crashing. To check your disk usage using <gui>System Monitor</gui>:</p>
<steps>
@@ -40,4 +34,5 @@ One way to check disk usage is to use the <app>Disk Usage Analyzer</app> program
<note><p>One more technique is to clear package files which are not being used. Look at the documentation
for your distribution for instructions on how to do this.
</p></note>
+-->
</page>
diff --git a/help/C/fs-info.page b/help/C/fs-info.page
index e7ba52d..7101136 100644
--- a/help/C/fs-info.page
+++ b/help/C/fs-info.page
@@ -20,6 +20,20 @@
</info>
<title>Learn what the File System information means</title>
+
+ <!-- ================================= -->
+
+ <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>
+
+ <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>
+
+ <p><gui>Type</gui> tells you the type of <em>filesystem</em> that is used on the disk or partition. The
filesystem specifies how the computer should store files on the disk; some operating systems can only
understand some types, and not others.</p>
+
+ <!-- ================================= -->
+
+
+
+
<p>For each device listed in the <gui>File System</gui> tab, <app>System Monitor</app> provides
information in a number of categories. </p>
diff --git a/help/C/legal.xml b/help/C/legal.xml
index 899282c..aa36246 100644
--- a/help/C/legal.xml
+++ b/help/C/legal.xml
@@ -1,76 +1,8 @@
- <legalnotice id="legalnotice">
- <para>
- Permission is granted to copy, distribute and/or modify this
- document under the terms of the GNU Free Documentation
- License (GFDL), Version 1.1 or any later version published
- by the Free Software Foundation with no Invariant Sections,
- no Front-Cover Texts, and no Back-Cover Texts. You can find
- a copy of the GFDL at this <ulink type="help"
- url="help:fdl">link</ulink> or in the file COPYING-DOCS
- distributed with this manual.
- </para>
- <para> This manual is part of a collection of GNOME manuals
- distributed under the GFDL. If you want to distribute this
- manual separately from the collection, you can do so by
- adding a copy of the license to the manual, as described in
- section 6 of the license.
- </para>
+<license xmlns="http://projectmallard.org/1.0/";
+ href="http://creativecommons.org/licenses/by-sa/3.0/";>
- <para>
- Many of the names used by companies to distinguish their
- products and services are claimed as trademarks. Where those
- names appear in any GNOME documentation, and the members of
- the GNOME Documentation Project are made aware of those
- trademarks, then the names are in capital letters or initial
- capital letters.
- </para>
-
- <para>
- DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED
- UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE
- WITH THE FURTHER UNDERSTANDING THAT:
-
- <orderedlist>
- <listitem>
- <para>DOCUMENT IS PROVIDED ON AN "AS IS" BASIS,
- WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
- IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES
- THAT THE DOCUMENT OR MODIFIED VERSION OF THE
- DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR
- A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE
- RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE
- OF THE DOCUMENT OR MODIFIED VERSION OF THE
- DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR
- MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT,
- YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY
- CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
- SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
- OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
- LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED
- VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER
- EXCEPT UNDER THIS DISCLAIMER; AND
- </para>
- </listitem>
- <listitem>
- <para>UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL
- THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE),
- CONTRACT, OR OTHERWISE, SHALL THE AUTHOR,
- INITIAL WRITER, ANY CONTRIBUTOR, OR ANY
- DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION
- OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH
- PARTIES, BE LIABLE TO ANY PERSON FOR ANY
- DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
- CONSEQUENTIAL DAMAGES OF ANY CHARACTER
- INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS
- OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR
- MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR
- LOSSES ARISING OUT OF OR RELATING TO USE OF THE
- DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT,
- EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF
- THE POSSIBILITY OF SUCH DAMAGES.
- </para>
- </listitem>
- </orderedlist>
- </para>
- </legalnotice>
+ <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/process-end-kill.page b/help/C/process-end-kill.page
index 5d7d2f0..e1b34a1 100644
--- a/help/C/process-end-kill.page
+++ b/help/C/process-end-kill.page
@@ -2,29 +2,26 @@
type="topic" style="task"
id="process-end-kill">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-25" status="review"/>
<link type="guide" xref="index" 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>2011</years>
- </credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <years>2014</years>
</credit>
+
<desc>End and Kill are different ways to make a process stop running.</desc>
+
</info>
<title>What is the difference between End and Kill?</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain the different ways of killing a process.</p>
- </comment>
+<p>When you right-click a process, there are two similar-sounding options to stop it running: <gui>End
Process</gui> and <gui>Kill Process</gui>. You should try <gui>End Process</gui> first, as it will try to
close the program properly (as if you'd clicked the close or exit button in the program itself).</p>
-<p>The menu that shows up when you click a process contains both <gui>End Process</gui> and <gui>Kill
Process.</gui> <gui>End Process</gui> tries to end the process as the programmer intended, using the built in
"quit" or "exit" function. <gui>Kill Process</gui> forces the process to close immediately, and should be
used only if <gui>End Process</gui> does not work.</p>
+<p>If the program still does not close, click <gui>Kill Process</gui> instead. This will force it to close,
even if it has completely frozen. For some programs, this might mean that you lose unsaved files. The next
time you open the program, you might also get a message saying that it did not close correctly.</p>
</page>
diff --git a/help/C/process-files.page b/help/C/process-files.page
index 15aee84..7630513 100644
--- a/help/C/process-files.page
+++ b/help/C/process-files.page
@@ -2,18 +2,15 @@
type="topic" style="task"
id="process-files">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-25" status="review"/>
<link type="guide" xref="index" 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>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <years>2014</years>
</credit>
<desc>View files being accessed by processes.</desc>
@@ -21,18 +18,14 @@
<title>List which files a process has open</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain how to show which files a process has open, and what it means for a process to have a file
open.</p>
- </comment>
-
- <p>In order to function, processes may need access to certain files. To view which
-files a process is using, you can do the following: </p>
-
+ <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>Click the <gui>Processes</gui> tab in <app>System Monitor</app>.</p></item>
- <item><p>Right-click on the process you would like to view.</p></item>
- <item><p>Select <gui>Open Files</gui> from the drop-down menu.</p></item>
+ <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-kill.page b/help/C/process-kill.page
index 5dcc361..5dbaabc 100644
--- a/help/C/process-kill.page
+++ b/help/C/process-kill.page
@@ -2,43 +2,31 @@
type="topic" style="task"
id="process-kill">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-25" status="review"/>
<link type="guide" xref="index" group="processes-tasks" />
-
+ <link type="seealso" xref="process-end-kill" />
+
+ <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>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <years>2014</years>
</credit>
- <desc>If an application won't close normally or stops responding, you might want to "kill" it.</desc>
+ <desc>If a program stops working or freezes, you can force it to close.</desc>
</info>
<title>Kill (close) a program immediately</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain how to kill a program, and why you might want to do that.</p>
- </comment>
-
- <p>If a program has frozen and it will not allow you to close it, you may want to end or kill that program
using <app>System Monitor</app>.</p>
-
+ <p>If a program stops working or freezes, you can force it to close ("kill" it) using <app>System
Monitor</app>:</p>
+
<steps>
- <item><p>Click the <gui>Processes</gui> tab.</p></item>
- <item><p>Find the process you would like to kill.</p></item>
- <item><p>Press the <gui>End Process</gui> button in the lower right of the window.</p></item>
+ <item><p>Go to the <gui>Processes</gui> tab and click to select the process you want to kill.</p></item>
+ <item><p>Click <gui>End Process</gui>.</p></item>
+ <item><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></item>
</steps>
-
-<p>If the <gui>End Process</gui> button fails the stop the program, you may wish to kill the process as
follows:</p>
- <steps>
- <item><p>Right click on the process you would like to kill.</p></item>
- <item><p>Select <gui>Kill Process</gui> from the menu.</p></item>
- </steps>
-
-<note><p><gui>Kill Process</gui> forces the process to close immediately, without bringing the program to a
natural end. It should be used only if <gui>End Process</gui> does not work.</p></note>
+
+ <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. You should always try <gui>End Process</gui>
first.</p>
+
</page>
diff --git a/help/C/process-many.page b/help/C/process-many.page
index a3792ac..5ed97f3 100644
--- a/help/C/process-many.page
+++ b/help/C/process-many.page
@@ -2,28 +2,22 @@
type="topic" style="task"
id="process-many">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-25" status="review"/>
<link type="guide" xref="index" 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>
+ <years>2014</years>
</credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
- </credit>
- <desc>Most of the items in the Processes tab are system processes which run in the background.</desc>
+
+ <desc>Lots of system processes run automatically in the background</desc>
</info>
<title>Why are there processes listed that I did not start?</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain that the OS starts a lot of system processes of its own, which work in the background. You
shouldn't usually try to kill them.</p>
- </comment>
-
- <p>When you view the process list in the <gui>Processes</gui> tab, you will see quite a few processes that
you did not start. These processes are started by the system and work in the background. Do not try to kill
them unless you know what you are doing.</p>
-
+ <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
index 6101331..2ccf52b 100644
--- a/help/C/process-priority-change.page
+++ b/help/C/process-priority-change.page
@@ -2,38 +2,44 @@
type="topic" style="task"
id="process-priority-change">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-26" status="review"/>
<link type="guide" xref="index" 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>2011</years>
- </credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <years>2014</years>
</credit>
- <desc>Let processes that are more important take a bigger share of the computer's resources.</desc>
+ <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>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain how to change the nice value of a process, why you might want to do that, and what the
implications might be.</p>
- </comment>
-
- <p>The <em>nice</em> value of a process determines how much it allows other processes to take priority
over itself. Processes with low nice values take up a bigger share of the available resources. If you would
like to change a process's nice value, do the following:</p>
-
+ <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>Click the <gui>Processes</gui> tab in the <app>System Monitor</app> window.</p></item>
- <item><p>Right-click on the process you would like to change the priority of.</p></item>
- <item><p>Select <gui>Change Priority...</gui> from the menu.</p></item>
- <item><p>Use the slider to select a nice value (higher means a lower priority).</p></item>
- <item><p>Click the <gui>Change Priority</gui> button.</p></item>
+ <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
index d8e2c13..e6da91c 100644
--- a/help/C/process-priority-what.page
+++ b/help/C/process-priority-what.page
@@ -2,13 +2,15 @@
type="topic" style="task"
id="process-priority-what">
<info>
- <revision version="0.1" date="2011-08-19" status="stub"/>
+ <revision version="0.1" date="2014-01-26" status="stub"/>
<link type="guide" xref="index" 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</years>
+ <years>2011, 2014</years>
</credit>
<credit type="author copyright">
@@ -22,17 +24,6 @@
<title>What is the "nice" value of a process?</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Explain, in brief and simple terms, what nice levels are, why they are
- used, and how process scheduling works (Wikipedia article on nice is good for
- this.)</p>
-</comment>
-<comment>
- <cite date="2011-06-23" href="mailto:mdhillca gmail com">Mike Hill</cite>
- <p>Link "CPUs or cores" to cpu-check.</p>
- </comment>
-
<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 'nice' process,
or one with a higher nice value, concedes priority to other processes.
diff --git a/help/C/process-status.page b/help/C/process-status.page
index 47195c7..dc78006 100644
--- a/help/C/process-status.page
+++ b/help/C/process-status.page
@@ -2,18 +2,17 @@
type="topic" style="task"
id="process-status">
<info>
- <revision version="0.1" date="2011-08-28" status="review"/>
+ <revision version="0.1" date="2014-01-26" status="review"/>
<link type="guide" xref="index" 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>2011</years>
- </credit>
- <credit type="author copyright">
- <name>Kelly Sinnott</name>
- <email>ksinnott5ht gmail com</email>
- <years>2011</years>
+ <years>2014</years>
</credit>
<desc>The status of a process can be running, sleeping, stopped, or zombie.</desc>
@@ -21,34 +20,33 @@
<title>What do the process statuses mean?</title>
- <comment>
- <cite date="2011-06-18" href="mailto:philbull gmail com">Phil Bull</cite>
- <p>Briefly explain the different statuses a process can have.</p>
- </comment>
+ <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>
- <p>The <gui>Status</gui> column for a process provides information on the state of the process. The
possible states for a process are:</p>
-
-<table shade="rows">
+ <table shade="rows">
<tr>
- <td><p>Running</p></td>
- <td><p>A process that is <gui>Running</gui> is actively executing its code. For example, when your
browser is open and accessing a webpage, the browser process is running. </p></td>
-
+ <td><p>Running</p></td>
+ <td><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></td>
</tr>
<tr>
- <td><p>Sleeping</p></td>
- <td><p>If a process is <gui>Sleeping</gui>, this means that it is not being executed and is currently
waiting for an event from the user or the system to wake it up. This allows the process to be ready to
execute without using up resources.</p></td>
- </tr>
+ <td><p>Sleeping</p></td>
+ <td><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></td>
+ </tr>
<tr>
- <td><p>Stopped</p></td>
- <td><p>A process can be stopped manually by right-clicking it and selecting <gui>Stop Process</gui>.
This puts it in a state similar to sleep. It can be resumed with <gui>Continue Process</gui>.</p>
- </td>
+ <td><p>Stopped</p></td>
+ <td>
+ <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>
+ </td>
</tr>
-
<tr>
- <td><p>Zombie</p></td>
- <td><p>A Zombie process has been killed or otherwise has stopped running. It can't be killed because
the process can no longer receive the "kill signal." All that is left is for the system to clean up the
remnants of the process in memory. </p>
- </td>
- </tr>
-</table>
+ <td><p>Zombie</p></td>
+ <td>
+ <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 that hasn't checked on it yet.</p>
+ <p>Zombies 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>
+ </td>
+ </tr>
+ </table>
+
+ <p>The majority of processes will either be running or sleeping.</p>
</page>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
