GNOME.org
 

[gnome-system-monitor/wip/mallard-help: 35/68] Rewrote commandline, started adding license link

commit 693df6c3da32afdabd095eadf9e3a4110c7225b7
Author: Michael Hill <mdhill gnome org>
Date:   Sun Jan 26 13:22:18 2014 +0000

    Rewrote commandline, started adding license link

 help/C/commandline.page     |   61 ++++++++++++++++---------
 help/C/memory-map-use.page  |  105 +++++++++++++++++++++++------------------
 help/C/memory-map-what.page |  107 +-----------------------------------------
 3 files changed, 101 insertions(+), 172 deletions(-)
---
diff --git a/help/C/commandline.page b/help/C/commandline.page
index c173e43..e2ae48b 100644
--- a/help/C/commandline.page
+++ b/help/C/commandline.page
@@ -2,49 +2,66 @@
       type="topic" style="task"
       id="commandline">
   <info>
-    <revision version="0.1" date="2011-08-19" status="review"/>
+    <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/>
     <link type="guide" xref="index" group="other" />
 
+    <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/>
+
     <credit type="author copyright">
-      <name>Kelly Sinnott</name>
-      <email>ksinnott5ht gmail com</email>
+      <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>All of the information in the System Monitor can also be found using command line tools.</desc>
+    <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>
+  <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>
+    <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>If you would like to access the information provided by the System Monitor from the terminal, there are 
several handy command-line tools available.</p>
+  <p>Most of the information displayed by System Monitor can also be obtained
+  using these command line tools.</p>
 
 <table shade="rows">
+
+  <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>System information</p></td>
-       <td><p>The command <cmd>uname -a</cmd> will give you information about your system including your 
machine's hostname, operating system, and processor.</p></td>
+       <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>
   <tr>
-       <td><p>Running processes and other live system data</p></td>
-       <td><p>The tool <cmd>top</cmd> displays a continually updating view of current processes, their CPU 
and memory usage, and other details.</p></td>
-       </tr>
+       <td><p><cmd>free -m</cmd></p></td>
+       <td><p>shows you how much memory is available.</p></td>
+   </tr>
+
   <tr>
-       <td><p>Disk space</p></td>
-       <td><p>To review available disk space, mount location, and file type of mounted file systems, issue 
the command <cmd>df -h</cmd>.</p>
-       </td>
-  </tr>
+       <td><p><cmd>vmstat</cmd></p></td>
+       <td><p>provides information about current virtual memory use.</p></td>
+   </tr>
 
   <tr>
-       <td><p>Network information</p></td>
-       <td><p>The command <cmd>iftop</cmd> works like <cmd>top</cmd>, displaying continually updating 
network statistics. This command must be run as an administrator.
-       Note: iftop may not be included in your distribution. It should be available via your package 
manager.</p>
-       </td>
+       <td><p><cmd>df -h</cmd></p></td>
+       <td><p>displays available disk space on mounted filesystems.</p></td>
    </tr>
+
 </table>
+
 </page>
diff --git a/help/C/memory-map-use.page b/help/C/memory-map-use.page
index a933ee7..73cd370 100644
--- a/help/C/memory-map-use.page
+++ b/help/C/memory-map-use.page
@@ -2,9 +2,11 @@
       type="topic" style="task"
       id="memory-map-use">
   <info>
-    <revision version="0.1" date="2011-08-19" status="review"/>
+    <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="incomplete"/>
     <link type="guide" xref="index" 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>
@@ -14,7 +16,7 @@
     <credit type="author copyright">
       <name>Michael Hill</name>
       <email>mdhillca gmail com</email>
-      <years>2011</years>
+      <years>2014</years>
     </credit>
 
     <desc>Display the memory map of a process.</desc>
@@ -31,8 +33,8 @@
 
   <steps>
     <item><p>Click the <gui>Processes</gui> tab.</p></item>
-    <item><p>Select the desired process in the <gui>process list</gui>.</p></item>
-    <item><p>Click <gui>Memory Maps</gui> in the <gui>View</gui> menu.</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>
 
   <p>When a program is launched, the system assigns it a unique process ID (PID)
@@ -80,44 +82,53 @@
  called the <em>stack</em>.</p>
     </item>
     <item>
-      <p>The program itself and each of the shared libraries have three entries
+      <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>
 
- <terms>
- <title>Properties</title>
-  <item>
-    <title><gui>Filename</gui></title>
-    <p>The location of a shared library that is currently used by the process.
+<table shade="rows">
+
+  <tr>
+       <td><p>Properties</p></td>
+   </tr>
+
+  <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>
-  </item>
-  <item>
-    <title><gui>VM Start</gui></title>
-    <p>The address at which the memory segment begins. VM Start, VM End and VM
+ 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>
-  </item>
-  <item>
-    <title><gui>VM End</gui></title>
-    <p>The address at which the memory segment ends.</p>
-  </item>
-    <item>
-      <title><gui>VM Offset</gui></title>
-    <p>The location of the address within the memory segment, measured from VM
- Start.</p>
-    </item>
-  <item>
-    <title><gui>VM Size</gui></title>
-    <p>The size of the memory segment.</p>
-  </item>
-  <item>
-    <title><gui>Flags</gui></title>
-    <p>The following flags describe the different types of memory-segment access
+ 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 Offset</p></td>
+       <td><p>The location of the address within the memory segment, measured from VM
+ Start.</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>
@@ -142,19 +153,21 @@
     <p>The process has permission to execute instructions that are contained
  within the memory segment.</p>
     </item>
-    <item>
-      <title><gui>Device</gui></title>
-    <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>
-    </item>
-    <item>
-      <title><gui>Inode</gui></title>
-    <p>The inode on the device from which the shared library location is loaded
+    </terms>
+   </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>
-    </item>
-  </terms>
-  </item>
-</terms>
+ the number assigned to it is unique.</p></td>
+   </tr>
+
+</table>
 
 </page>
diff --git a/help/C/memory-map-what.page b/help/C/memory-map-what.page
index 452fe42..c2b134c 100644
--- a/help/C/memory-map-what.page
+++ b/help/C/memory-map-what.page
@@ -2,9 +2,11 @@
       type="topic" style="task"
       id="memory-map-what">
   <info>
-    <revision version="0.1" date="2011-08-19" status="stub"/>
+    <revision version="0.2" pkgversion="3.11" date="2014-01-26" status="review"/>
     <link type="guide" xref="index" 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>
@@ -63,107 +65,4 @@
  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>
 
-  <p>Reading the memory map:</p>
-  <list>
-
-    <item>
-      <p>Addresses are diplayed 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">
-
-  <tr>
-       <td><p>Properties</p></td>
-   </tr>
-
-  <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 Offset</p></td>
-       <td><p>The location of the address within the memory segment, measured from VM
- Start.</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>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>
-
 </page>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]