Fix spelling errors reported by lintian

colttt · May 15, 2018 · a89bc9f · a89bc9f
1 parent 6548e73
commit a89bc9f
Show file tree

Hide file tree

Showing 19 changed files with 25 additions and 25 deletions.
diff --git a/heartbeat/IPv6addr.c b/heartbeat/IPv6addr.c
@@ -790,7 +790,7 @@ write_pid_file(const char *pid_file)
 		}
 
 		if (kill(pid, SIGKILL) < 0 && errno != ESRCH) {
-			cl_log(LOG_INFO, "Error killing old proccess [%lu] "
+			cl_log(LOG_INFO, "Error killing old process [%lu] "
 	 				"from pid-file [%s]: %s", pid,
 					pid_file, strerror(errno));
 			return -1;

diff --git a/heartbeat/Raid1 b/heartbeat/Raid1
@@ -86,7 +86,7 @@ set to "auto" to manage all devices specified in raidconf.
 The value for the homehost directive; this is an mdadm feature to
 protect RAIDs against being activated by accident. It is recommended to
 create RAIDs managed by the cluster with "homehost" set to a special
-value, so they are not accidentially auto-assembled by nodes not
+value, so they are not accidentally auto-assembled by nodes not
 supposed to own them.
 </longdesc>
 <shortdesc lang="en">Homehost for mdadm</shortdesc>

diff --git a/heartbeat/Route b/heartbeat/Route
@@ -251,7 +251,7 @@ route_validate() {
     fi
     # Did we get either a device or a gateway address?
     if [ -z "${OCF_RESKEY_device}" -a -z "${OCF_RESKEY_gateway}" ]; then
-	ocf_exit_reason "Must specifiy either \"device\", or \"gateway\", or both."
+	ocf_exit_reason "Must specify either \"device\", or \"gateway\", or both."
 	return $OCF_ERR_ARGS
     fi
     # If a device has been configured, is it available on this system?

diff --git a/heartbeat/SAPInstance b/heartbeat/SAPInstance
@@ -127,7 +127,7 @@ That is only useful for double stack systems.
   <content type="string" default="3600" />
  </parameter>
  <parameter name="AUTOMATIC_RECOVER" unique="0" required="0">
-  <longdesc lang="en">The SAPInstance resource agent tries to recover a failed start attempt automaticaly one time. This is done by killing runing instance processes, removing the kill.sap file and executing cleanipc. Sometimes a crashed SAP instance leaves some processes and/or shared memory segments behind. Setting this option to true will try to remove those leftovers during a start operation. That is to reduce manual work for the administrator.</longdesc>
+  <longdesc lang="en">The SAPInstance resource agent tries to recover a failed start attempt automatically one time. This is done by killing running instance processes, removing the kill.sap file and executing cleanipc. Sometimes a crashed SAP instance leaves some processes and/or shared memory segments behind. Setting this option to true will try to remove those leftovers during a start operation. That is to reduce manual work for the administrator.</longdesc>
   <shortdesc lang="en">Enable or disable automatic startup recovery</shortdesc>
   <content type="boolean" default="false"/>
  </parameter>
@@ -204,7 +204,7 @@ The name of the SAP START profile. Specify this parameter, if you have changed t
  </parameter>
  <parameter name="IS_ERS" unique="0" required="0">
   <longdesc lang="en">Only used for ASCS/ERS SAP Netweaver installations without implementing a master/slave resource to
-    allow the ASCS to 'find' the ERS running on an other cluster node after a resource failure. This parameter should be set
+    allow the ASCS to 'find' the ERS running on another cluster node after a resource failure. This parameter should be set
     to true 'only' for the ERS instance for implementations following the SAP NetWeaver 7.40 HA certification (NW-HA-CLU-740). This includes also
     systems for NetWeaver less than 7.40, if you like to impelemnt the NW-HA-CLU-740 scenario.
   </longdesc>

diff --git a/heartbeat/Squid.in b/heartbeat/Squid.in
@@ -109,7 +109,7 @@ for a squid instance managed by this RA.
 <longdesc lang="en">
 This is a required parameter. This parameter specifies a port number
 for a squid instance managed by this RA. If plural ports are used,
-you must specifiy the only one of them.
+you must specify the only one of them.
 </longdesc>
 <shortdesc lang="en">Port number</shortdesc>
 <content type="integer" default=""/>

diff --git a/heartbeat/Stateful b/heartbeat/Stateful
@@ -42,7 +42,7 @@ meta_data() {
 <version>1.0</version>
 
 <longdesc lang="en">
-This is an example resource agent that impliments two states
+This is an example resource agent that implements two states
 </longdesc>
 <shortdesc lang="en">Example stateful resource agent</shortdesc>
 

diff --git a/heartbeat/db2 b/heartbeat/db2
@@ -101,7 +101,7 @@ DEPRECATED: The admin user of the instance.
 </parameter>
 <parameter name="dbpartitionnum" unique="0" required="0">
 <longdesc lang="en">
-The number of the partion (DBPARTITIONNUM) to be managed.
+The number of the partition (DBPARTITIONNUM) to be managed.
 </longdesc>
 <shortdesc lang="en">database partition number (DBPARTITIONNUM)</shortdesc>
 <content type="string" default="0" />
@@ -584,7 +584,7 @@ db2_stop() {
 
     if [ $must_kill -eq 1 ]
     then
-        # db2nkill kills *all* partions on the node
+        # db2nkill kills *all* partitions on the node
         if [ -x $db2bin/db2nkill ]
         then
             logasdb2 $db2bin/db2nkill $db2node

diff --git a/heartbeat/docker b/heartbeat/docker
@@ -99,7 +99,7 @@ provided in the 'name' argument of this agent.
 
 <parameter name="run_cmd" required="0" unique="0">
 <longdesc lang="en">
-Specifiy a command to launch within the container once
+Specify a command to launch within the container once
 it has initialized.
 </longdesc>
 <shortdesc lang="en">run command</shortdesc>
@@ -117,7 +117,7 @@ The agent will ensure they exist by running 'mkdir -p'
 
 <parameter name="monitor_cmd" required="0" unique="0">
 <longdesc lang="en">
-Specifiy the full path of a command to launch within the container to check
+Specify the full path of a command to launch within the container to check
 the health of the container. This command must return 0 to indicate that
 the container is healthy. A non-zero return code will indicate that the
 container has failed and should be recovered.

diff --git a/heartbeat/ethmonitor b/heartbeat/ethmonitor
@@ -64,7 +64,7 @@ Monitor the vitality of a local network interface.
 You may set up this RA as a clone resource to monitor the network interfaces on different nodes, with the same interface name.
 This is not related to the IP address or the network on which a interface is configured.
 You may use this RA to move resources away from a node, which has a faulty interface or prevent moving resources to such a node.
-This gives you independend control of the resources, without involving cluster intercommunication. But it requires your nodes to have more than one network interface.
+This gives you independent control of the resources, without involving cluster intercommunication. But it requires your nodes to have more than one network interface.
 
 The resource configuration requires a monitor operation, because the monitor does the main part of the work.
 In addition to the resource configuration, you need to configure some location constraints, based on a CIB attribute value.

diff --git a/heartbeat/iface-vlan b/heartbeat/iface-vlan
@@ -156,7 +156,7 @@ vlan_meta_data() {
     <parameter name="vlan_loose_binding" unique="0">
       <longdesc lang="en">
         Enable or disable VLAN loose bind. By default the VLAN interface
-        admin status (UP/DOWN) follows the underneath inteface status.
+        admin status (UP/DOWN) follows the underneath interface status.
         Enabling loose bind allows the VLAN to disconnect from the
         interface status. Be very careful that enabling loose binding
         could invalidate this agent monitor operations.

diff --git a/heartbeat/kamailio.in b/heartbeat/kamailio.in
@@ -242,11 +242,11 @@ Parameters for a third Kamailio instance:
     This parameter only needs to be provided in case of using multiple Kamailio server
     instances on a single cluster node:
 
-    In case that the parameter "kamctlrc" is not empty, this ressource agent monitors 
+    In case that the parameter "kamctlrc" is not empty, this resource agent monitors
     the health state of the Kamailio server via the command "kamctl monitor 1". This 
     setting is recommended in case of using a single Kamailio server instance.
 
-    In case that the parameter "kamctlrc" is empty, the ressource agent does not 
+    In case that the parameter "kamctlrc" is empty, the resource agent does not
     monitor the health state of the Kamailio server instance via the "kamctl" command.
 
     Please note that the "kamctl" control command of Kamailio 4.x does not support 
@@ -256,7 +256,7 @@ Parameters for a third Kamailio instance:
     check via "kamctl monitor 1" can be configured for a single Kamailio instance
     only.
 
-    Please refer to the long description of this resoure agent for an example
+    Please refer to the long description of this resource agent for an example
     of parameter combinations in case that multiple instances are to be 
     configured per cluster node.
 

diff --git a/heartbeat/ovsmonitor b/heartbeat/ovsmonitor
@@ -61,7 +61,7 @@ Monitor the vitality of a local ovs bond.
 You may set up this RA as a clone resource to monitor the network bonds on different nodes, with the same bond name.
 This is not related to the IP address or the network on which a bond is configured.
 You may use this RA to move resources away from a node, which has a faulty bond or prevent moving resources to such a node.
-This gives you independend control of the resources, without involving cluster intercommunication. But it requires your nodes to have more than one network bond.
+This gives you independent control of the resources, without involving cluster intercommunication. But it requires your nodes to have more than one network bond.
 
 The resource configuration requires a monitor operation, because the monitor does the main part of the work.
 In addition to the resource configuration, you need to configure some location constraints, based on a CIB attribute value.

diff --git a/heartbeat/portblock b/heartbeat/portblock
@@ -165,7 +165,7 @@ The action (block/unblock) to be done on the protocol::portno.
 If for some reason the long lived server side TCP sessions won't be cleaned up
 by a reconfiguration/flush/stop of whatever services this portblock protects,
 they would linger in the connection table, even after the IP is gone
-and services have been switched over to an other node.
+and services have been switched over to another node.
 
 An example would be the default NFS kernel server.
 

diff --git a/heartbeat/slapd.in b/heartbeat/slapd.in
@@ -146,7 +146,7 @@ For example, "ldap://127.0.0.1:389 ldaps:/// ldapi:///"
 <parameter name="watch_suffix" required="0" unique="0">
 <longdesc lang="en">
 Suffix (database backend) that will be monitored for availability. Multiple
-suffixes can be specified by providing a space seperated list. By providing one
+suffixes can be specified by providing a space separated list. By providing one
 or more suffixes here, the ignore_suffix parameter is discarded. All suffixes
 will be monitored if left blank.
 </longdesc>
@@ -157,7 +157,7 @@ will be monitored if left blank.
 <parameter name="ignore_suffix" required="0" unique="0">
 <longdesc lang="en">
 Suffix (database backend) that will not be monitored for availability. Multiple
-suffixes can be specified by providing a space seperated list. No suffix will
+suffixes can be specified by providing a space separated list. No suffix will
 be excluded if left blank.
 </longdesc>
 <shortdesc lang="en">Suffix that will not be monitored for availability.</shortdesc>

diff --git a/rgmanager/src/resources/SAPDatabase b/rgmanager/src/resources/SAPDatabase
@@ -124,7 +124,7 @@ Resource script for SAP databases. It manages a SAP database of any type as an H
   <content type="boolean" default="false"/>
  </parameter>
  <parameter name="AUTOMATIC_RECOVER" unique="0" required="0">
-  <longdesc lang="en">The SAPDatabase resource agent tries to recover a failed start attempt automaticaly one time. This is done by running a forced abort of the RDBMS and/or executing recovery commands.</longdesc>
+  <longdesc lang="en">The SAPDatabase resource agent tries to recover a failed start attempt automatically one time. This is done by running a forced abort of the RDBMS and/or executing recovery commands.</longdesc>
   <shortdesc lang="en">Enable or disable automatic startup recovery</shortdesc>
   <content type="boolean" default="false"/>
  </parameter>

diff --git a/rgmanager/src/resources/SAPInstance b/rgmanager/src/resources/SAPInstance
@@ -106,7 +106,7 @@ Resource script for SAP. It manages a SAP Instance as an HA resource.
   <content type="string" default="3600" />
  </parameter>
  <parameter name="AUTOMATIC_RECOVER" unique="0" required="0">
-  <longdesc lang="en">The SAPInstance resource agent tries to recover a failed start attempt automaticaly one time. This is done by killing runing instance processes and executing cleanipc.</longdesc>
+  <longdesc lang="en">The SAPInstance resource agent tries to recover a failed start attempt automatically one time. This is done by killing running instance processes and executing cleanipc.</longdesc>
   <shortdesc lang="en">Enable or disable automatic startup recovery</shortdesc>
   <content type="boolean" default="false"/>
  </parameter>

diff --git a/rgmanager/src/resources/db2.sh.in b/rgmanager/src/resources/db2.sh.in
@@ -63,7 +63,7 @@ Defaults to all databases in the instance.
 </parameter>
 <parameter name="dbpartitionnum" unique="0" required="0">
 <longdesc lang="en">
-The number of the partion (DBPARTITIONNUM) to be managed.
+The number of the partition (DBPARTITIONNUM) to be managed.
 </longdesc>
 <shortdesc lang="en">database partition number (DBPARTITIONNUM)</shortdesc>
 <content type="string" default="0" />

diff --git a/tools/ocft/db2 b/tools/ocft/db2
@@ -1,6 +1,6 @@
 # db2
 #
-# This test assumes a db2 ESE instance with two partions and a database.
+# This test assumes a db2 ESE instance with two partitions and a database.
 # Default is instance=db2inst1, database=ocft
 # adapt this in set_testenv below
 #

diff --git a/tools/send_arp.libnet.c b/tools/send_arp.libnet.c
@@ -720,7 +720,7 @@ write_pid_file(const char *pidfilename)
 		}
 
 		if (kill(pid, SIGKILL) < 0 && errno != ESRCH) {
-			cl_log(LOG_INFO, "Error killing old proccess [%lu] "
+			cl_log(LOG_INFO, "Error killing old process [%lu] "
 	 				"from pid-file [%s]: %s", pid,
 					pidfilename, strerror(errno));
 			return -1;