Attachment 5118 Details for Bug 6935 – Correction of spelling errors in manpages

[patch] Correction of spelling errors in manpages

0001-Correction-of-spelling-errors-in-manpages.patch (text/plain), 4.45 KB, created by Mathieu Parent on 2010-01-05 04:02:14 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Mathieu Parent

Created: 2010-01-05 04:02:14 UTC

Size: 4.45 KB

patch

obsolete

>From 7bfc046c719e32517807d0f8fbb5699d17f3f69a Mon Sep 17 00:00:00 2001
>From: Mathieu Parent <math.parent@gmail.com>
>Date: Tue, 5 Jan 2010 10:59:44 +0100
>Subject: [PATCH] Correction of spelling errors in manpages
>
>thanks to lintian
>
>See https://bugzilla.samba.org/show_bug.cgi?id=6935
>---
> doc/ctdb.1.xml  |    6 +++---
> doc/ctdbd.1.xml |    8 ++++----
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
>diff --git a/doc/ctdb.1.xml b/doc/ctdb.1.xml
>index a88e8ad..cd42cbd 100644
>--- a/doc/ctdb.1.xml
>+++ b/doc/ctdb.1.xml
>@@ -47,7 +47,7 @@
>         <listitem>
>           <para>
>             This specifies the physical node number on which to execute the 
>-	    command. Default is to run the command on the deamon running on 
>+	    command. Default is to run the command on the daemon running on 
> 	    the local host.
> 	  </para>
> 	  <para>
>@@ -591,7 +591,7 @@ CTDB version 1
>         Administratively ban a node for bantime seconds. A bantime of 0 means that the node should be permanently banned. 
>       </para>
>       <para>
>-        A banned node does not participate in the cluster and does not host any records for the clustered TDB. Its ip address has been taken over by an other node and no services are hosted.
>+        A banned node does not participate in the cluster and does not host any records for the clustered TDB. Its ip address has been taken over by another node and no services are hosted.
>       </para>
>       <para>
>         Nodes are automatically banned if they are the cause of too many
>@@ -856,7 +856,7 @@ dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTEN
> 
>     <refsect2><title>setmonmode &lt;0|1&gt;</title>
>       <para>
>-        This command can be used to explicitely disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
>+        This command can be used to explicitly disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
>       </para>
>     </refsect2>
> 
>diff --git a/doc/ctdbd.1.xml b/doc/ctdbd.1.xml
>index f90b671..aea7c8f 100644
>--- a/doc/ctdbd.1.xml
>+++ b/doc/ctdbd.1.xml
>@@ -212,7 +212,7 @@
> 	    This option is used to tell ctdbd to NOT run as a real-time process
> 	    and instead run ctdbd as a normal userspace process.
> 	    This is useful for debugging and when you want to run ctdbd under
>-	    valgrind or gdb. (You dont want to attach valgrind or gdb to a
>+	    valgrind or gdb. (You don't want to attach valgrind or gdb to a
> 	    real-time process.)
>           </para>
>         </listitem>
>@@ -237,7 +237,7 @@
> 	    </para>
> 	    <para>
> 	    This is only required when using public ip addresses and only when
>-	    you dont specify the interface explicitly in /etc/ctdb/public_addresses or when you are using --single-public-ip.
>+	    you don't specify the interface explicitly in /etc/ctdb/public_addresses or when you are using --single-public-ip.
>           </para>
>           <para>
> 	  If you omit this argument when using public addresses or single public ip, ctdb will not be able to send out Gratious ARPs correctly or be able to kill tcp connections correctly which will lead to application failures. 
>@@ -589,7 +589,7 @@
>     eventually become banned from the cluster.
>     This controls how long the culprit node will be banned from the cluster
>     before it is allowed to try to join the cluster again.
>-    Dont set to small. A node gets banned for a reason and it is usually due
>+    Don't set to small. A node gets banned for a reason and it is usually due
>     to real problems with the node.
>     </para>
>     </refsect2>
>@@ -608,7 +608,7 @@
>     <refsect2><title>EnableBans</title>
>     <para>Default: 1</para>
>     <para>
>-    When set to 0, this disables BANNING completely in the cluster and thus nodes can not get banned, even it they break. Dont set to 0.
>+    When set to 0, this disables BANNING completely in the cluster and thus nodes can not get banned, even it they break. Don't set to 0.
>     </para>
>     </refsect2>
>     <refsect2><title>DeterministicIPs</title>
>-- 
>1.6.5
>

Actions: View

Attachments on bug 6935: 5019 | 5101 | 5118 | 5119 | 6341