Commit 90825001 authored by Andrei Pavel's avatar Andrei Pavel

Corrected typos

parent 039622a4
...@@ -37,7 +37,7 @@ that your code compiles. This may seem obvious, but there's more to ...@@ -37,7 +37,7 @@ that your code compiles. This may seem obvious, but there's more to
it. You have surely checked that it compiles on your system, but Kea it. You have surely checked that it compiles on your system, but Kea
is portable software. Besides Linux, it is compiled and used on is portable software. Besides Linux, it is compiled and used on
relatively uncommon systems like OpenBSD. Will your code relatively uncommon systems like OpenBSD. Will your code
compile and work there? What about endianess? It is likely that you used compile and work there? What about endianness? It is likely that you used
a regular x86 architecture machine to write your patch, but the software a regular x86 architecture machine to write your patch, but the software
is expected to run on many other architectures. You may take a look at is expected to run on many other architectures. You may take a look at
system specific build notes (http://kea.isc.org/wiki/Install). system specific build notes (http://kea.isc.org/wiki/Install).
......
...@@ -26,7 +26,7 @@ ...@@ -26,7 +26,7 @@
# 2. MySQL backend. Leases will be stored in MySQL database. Make sure it # 2. MySQL backend. Leases will be stored in MySQL database. Make sure it
# is up, running and properly initialized. See kea-admin documentation # is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type and name. If other parameters are not specified, # parameters are type and name. If other parameters are not specified,
# Kea will assume the database is avaiable on localhost, that user and # Kea will assume the database is avaiable on localhost, that user and
# password is not necessary to connect and that timeout is 5 seconds. # password is not necessary to connect and that timeout is 5 seconds.
...@@ -42,7 +42,7 @@ ...@@ -42,7 +42,7 @@
# 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make # 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make
# sure it is up, running and properly initialized. See kea-admin documentation # sure it is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type and name. If other parameters are not specified, # parameters are type and name. If other parameters are not specified,
# Kea will assume the database is avaiable on localhost, that user and # Kea will assume the database is avaiable on localhost, that user and
# password is not necessary to connect and that timeout is 5 seconds. # password is not necessary to connect and that timeout is 5 seconds.
...@@ -57,7 +57,7 @@ ...@@ -57,7 +57,7 @@
# 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make # 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make
# sure it is up, running and properly initialized. See kea-admin documentation # sure it is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type, keyspace and contact_points. At least one contact point # parameters are type, keyspace and contact_points. At least one contact point
# must be specified, but more than one is required for redundancy. Make sure # must be specified, but more than one is required for redundancy. Make sure
# you specify the contact points without spaces. Kea must be compiled with # you specify the contact points without spaces. Kea must be compiled with
......
...@@ -26,7 +26,7 @@ ...@@ -26,7 +26,7 @@
# 2. MySQL backend. Leases will be stored in MySQL database. Make sure it # 2. MySQL backend. Leases will be stored in MySQL database. Make sure it
# is up, running and properly initialized. See kea-admin documentation # is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type and name. If other parameters are not specified, # parameters are type and name. If other parameters are not specified,
# Kea will assume the database is avaiable on localhost, that user and # Kea will assume the database is avaiable on localhost, that user and
# password is not necessary to connect and that timeout is 5 seconds. # password is not necessary to connect and that timeout is 5 seconds.
...@@ -42,7 +42,7 @@ ...@@ -42,7 +42,7 @@
# 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make # 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make
# sure it is up, running and properly initialized. See kea-admin documentation # sure it is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type and name. If other parameters are not specified, # parameters are type and name. If other parameters are not specified,
# Kea will assume the database is avaiable on localhost, that user and # Kea will assume the database is avaiable on localhost, that user and
# password is not necessary to connect and that timeout is 5 seconds. # password is not necessary to connect and that timeout is 5 seconds.
...@@ -57,7 +57,7 @@ ...@@ -57,7 +57,7 @@
# 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make # 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make
# sure it is up, running and properly initialized. See kea-admin documentation # sure it is up, running and properly initialized. See kea-admin documentation
# for details on how to intialize the database. The only strictly required # for details on how to initialize the database. The only strictly required
# parameters are type, keyspace and contact_points. At least one contact point # parameters are type, keyspace and contact_points. At least one contact point
# must be specified, but more than one is required for redundancy. Make sure # must be specified, but more than one is required for redundancy. Make sure
# you specify the contact points without spaces. Kea must be compiled with # you specify the contact points without spaces. Kea must be compiled with
......
...@@ -18,7 +18,7 @@ ...@@ -18,7 +18,7 @@
For example, Kea currently only stores lease information For example, Kea currently only stores lease information
and host reservations. Future versions of Kea will store and host reservations. Future versions of Kea will store
additional data such as subnet definitions: the database additional data such as subnet definitions: the database
structure will need to be updated to accomdate the extra structure will need to be updated to accommodate the extra
information. information.
</para> </para>
...@@ -616,7 +616,7 @@ $ <userinput>kea-admin lease-upgrade pgsql -u <replaceable>database-user</replac ...@@ -616,7 +616,7 @@ $ <userinput>kea-admin lease-upgrade pgsql -u <replaceable>database-user</replac
<orderedlist> <orderedlist>
<listitem> <listitem>
<para> <para>
Export CQLSH_HOST environemnt variable: Export CQLSH_HOST environment variable:
<screen> <screen>
$ <userinput>export CQLSH_HOST=localhost</userinput> $ <userinput>export CQLSH_HOST=localhost</userinput>
</screen> </screen>
...@@ -715,7 +715,7 @@ $ <userinput>kea-admin lease-upgrade cql -n <replaceable>database-name</replacea ...@@ -715,7 +715,7 @@ $ <userinput>kea-admin lease-upgrade cql -n <replaceable>database-name</replacea
read-only mode. read-only mode.
Sections <xref linkend="read-only-database-configuration4"/> and Sections <xref linkend="read-only-database-configuration4"/> and
<xref linkend="read-only-database-configuration6"/> describe when <xref linkend="read-only-database-configuration6"/> describe when
such configuration may be reqired and how to configure Kea to such configuration may be required and how to configure Kea to
operate using a read-only host database. operate using a read-only host database.
</para> </para>
</section> </section>
......
...@@ -820,7 +820,7 @@ concatenation of the strings</entry></row> ...@@ -820,7 +820,7 @@ concatenation of the strings</entry></row>
</para> </para>
<para> <para>
To enable the debug statements in the classifciaton system you will To enable the debug statements in the classification system you will
need to set the severity to "DEBUG" and the debug level to at least 55. need to set the severity to "DEBUG" and the debug level to at least 55.
The specific loggers are "kea-dhcp4.eval" and "kea-dhcp6.eval". The specific loggers are "kea-dhcp4.eval" and "kea-dhcp6.eval".
</para> </para>
......
...@@ -104,7 +104,7 @@ where <command>/path/to/the/kea/socket</command> is the path specified in the ...@@ -104,7 +104,7 @@ where <command>/path/to/the/kea/socket</command> is the path specified in the
configuration file. Text passed to <command>socat</command> configuration file. Text passed to <command>socat</command>
will be sent to Kea and the responses received from Kea printed to standard output.</para> will be sent to Kea and the responses received from Kea printed to standard output.</para>
<para>It is also easy to open UNIX socket programmatically. An example of <para>It is also easy to open UNIX socket programatically. An example of
such a simplistic client written in C is available in the Kea Developer's such a simplistic client written in C is available in the Kea Developer's
Guide, chapter Control Channel Overview, section Using Control Channel.</para> Guide, chapter Control Channel Overview, section Using Control Channel.</para>
......
...@@ -716,7 +716,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -716,7 +716,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</section> <!-- "d2-reverse-ddns-config" --> </section> <!-- "d2-reverse-ddns-config" -->
<section id="d2-exmaple-config"> <section id="d2-example-config">
<title>Example DHCP-DDNS Server Configuration</title> <title>Example DHCP-DDNS Server Configuration</title>
<para> <para>
This section provides an example DHCP-DDNS server configuration based This section provides an example DHCP-DDNS server configuration based
......
...@@ -2969,7 +2969,7 @@ It is merely echoed by the server ...@@ -2969,7 +2969,7 @@ It is merely echoed by the server
</screen> </screen>
<para>Static class assignments, as shown above, can be used in conjuction <para>Static class assignments, as shown above, can be used in conjunction
with classification using expressions.</para> with classification using expressions.</para>
</section> </section>
......
...@@ -1203,7 +1203,7 @@ temporarily override a list of interface names and listen on all interfaces. ...@@ -1203,7 +1203,7 @@ temporarily override a list of interface names and listen on all interfaces.
S46 container options group rules and optional port parameters S46 container options group rules and optional port parameters
for a specified domain. There are three container options specified for a specified domain. There are three container options specified
in the "dhcp6" (top level) option space: MAP-E Container option, in the "dhcp6" (top level) option space: MAP-E Container option,
MAP-T Container option and S46 Lieghtweight 4over6 Container option. MAP-T Container option and S46 Lightweight 4over6 Container option.
These options only contain encapsulated options specified below. These options only contain encapsulated options specified below.
They do not include any data fields. They do not include any data fields.
</para> </para>
...@@ -2904,7 +2904,7 @@ should include options from the isc option space: ...@@ -2904,7 +2904,7 @@ should include options from the isc option space:
} }
</screen> </screen>
<para>Static class assignments, as shown above, can be used in conjuction <para>Static class assignments, as shown above, can be used in conjunction
with classification using expressions.</para> with classification using expressions.</para>
</section> </section>
......
...@@ -271,7 +271,7 @@ ...@@ -271,7 +271,7 @@
</itemizedlist> </itemizedlist>
</para> </para>
<para> <para>
Once loaded, the library allows segregating incomings requests into Once loaded, the library allows segregating incoming requests into
known and unknown clients. For known clients, the packets are known and unknown clients. For known clients, the packets are
processed mostly as usual, except it is possible to override certain processed mostly as usual, except it is possible to override certain
options being sent. That can be done on a per host basis. Clients options being sent. That can be done on a per host basis. Clients
...@@ -306,7 +306,7 @@ ...@@ -306,7 +306,7 @@
is "HW_ADDR" for IPv4 users or "DUID" for IPv6 is "HW_ADDR" for IPv4 users or "DUID" for IPv6
users</para></listitem> users</para></listitem>
<listitem><para><command>id</command>, whose value is <listitem><para><command>id</command>, whose value is
either the hardware address or the DUID from the equest either the hardware address or the DUID from the request
formatted as a string of hex digits, with or without formatted as a string of hex digits, with or without
":" delimiters.</para></listitem> ":" delimiters.</para></listitem>
</itemizedlist> </itemizedlist>
...@@ -344,7 +344,7 @@ and may have the zero or more of the following entries: ...@@ -344,7 +344,7 @@ and may have the zero or more of the following entries:
<title>Forensic Logging Hooks</title> <title>Forensic Logging Hooks</title>
<para> <para>
This section describes the forensic log hooks library. This library This section describes the forensic log hooks library. This library
povides hooks that record a detailed log of lease assignments provides hooks that record a detailed log of lease assignments
and renewals into a set of log files. Currently this library and renewals into a set of log files. Currently this library
is only available to ISC customers with a support contract. is only available to ISC customers with a support contract.
</para> </para>
......
...@@ -61,7 +61,7 @@ ...@@ -61,7 +61,7 @@
runtime) are responsible for creating the loggers used by those runtime) are responsible for creating the loggers used by those
libraries. Such loggers should have unique names, different libraries. Such loggers should have unique names, different
from the logger names used by Kea. In this way the from the logger names used by Kea. In this way the
messages output by the hooks library can be distingued from messages output by the hooks library can be distinguished from
messages issued by the core Kea code. Unique names also allow messages issued by the core Kea code. Unique names also allow
the loggers to be configured independently of loggers used the loggers to be configured independently of loggers used
by Kea. Whenever it makes sense, a hook library can use multiple by Kea. Whenever it makes sense, a hook library can use multiple
...@@ -150,7 +150,7 @@ ...@@ -150,7 +150,7 @@
packet drops, you must create configuration entry for the packet drops, you must create configuration entry for the
logger called <quote>kea-dhcp4.bad-packets</quote> and specify logger called <quote>kea-dhcp4.bad-packets</quote> and specify
severity DEBUG for this logger. All other configuration severity DEBUG for this logger. All other configuration
parameters may be omited for this logger if the logger should parameters may be omitted for this logger if the logger should
use the default values specified in the root logger's use the default values specified in the root logger's
configuration. configuration.
</para> </para>
......
...@@ -15,14 +15,14 @@ ...@@ -15,14 +15,14 @@
// \brief Coroutine object // \brief Coroutine object
// //
// A coroutine object maintains the state of a re-enterable routine. It // A coroutine object maintains the state of a re-enterable routine. It
// is assignable and copy-constructable, and can be used as a base class // is assignable and copy-constructible, and can be used as a base class
// for a class that uses it, or as a data member. The copy overhead is // for a class that uses it, or as a data member. The copy overhead is
// a single int. // a single int.
// //
// A reenterable function contains a CORO_REENTER (coroutine) { ... } // A reentrant function contains a CORO_REENTER (coroutine) { ... }
// block. Whenever an asychrnonous operation is initiated within the // block. Whenever an asychrnonous operation is initiated within the
// routine, the function is provided as the handler object. (The simplest // routine, the function is provided as the handler object. (The simplest
// way to do this is to have the reenterable function be the operator() // way to do this is to have the reentrant function be the operator()
// member for the coroutine object itself.) For example: // member for the coroutine object itself.) For example:
// //
// CORO_YIELD socket->async_read_some(buffer, *this); // CORO_YIELD socket->async_read_some(buffer, *this);
...@@ -30,7 +30,7 @@ ...@@ -30,7 +30,7 @@
// The CORO_YIELD keyword updates the current status of the coroutine to // The CORO_YIELD keyword updates the current status of the coroutine to
// indicate the line number currently being executed. The // indicate the line number currently being executed. The
// async_read_some() call is initiated, with a copy of the updated // async_read_some() call is initiated, with a copy of the updated
// corotutine as its handler object, and the current coroutine exits. When // coroutine as its handler object, and the current coroutine exits. When
// the async_read_some() call finishes, the copied coroutine will be // the async_read_some() call finishes, the copied coroutine will be
// called, and will resume processing exactly where the original one left // called, and will resume processing exactly where the original one left
// off--right after asynchronous call. This allows asynchronous I/O // off--right after asynchronous call. This allows asynchronous I/O
......
...@@ -81,7 +81,7 @@ cql_lease_version_test() { ...@@ -81,7 +81,7 @@ cql_lease_version_test() {
$keaadmin lease-init cql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir $keaadmin lease-init cql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
assert_eq 0 $? "kea-admin lease-init cql failed, expected exit code: %d, actual: %d" assert_eq 0 $? "kea-admin lease-init cql failed, expected exit code: %d, actual: %d"
# Verfiy that kea-admin lease-version returns the correct version. # Verify that kea-admin lease-version returns the correct version.
version=$($keaadmin lease-version cql -u $db_user -p $db_password -n $db_name) version=$($keaadmin lease-version cql -u $db_user -p $db_password -n $db_name)
assert_str_eq "1.0" $version "Expected kea-admin to return %s, returned value was %s" assert_str_eq "1.0" $version "Expected kea-admin to return %s, returned value was %s"
......
...@@ -38,7 +38,7 @@ mysql_lease_init_test() { ...@@ -38,7 +38,7 @@ mysql_lease_init_test() {
# Let's wipe the whole database # Let's wipe the whole database
mysql_wipe mysql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
...@@ -117,7 +117,7 @@ mysql_host_reservation_init_test() { ...@@ -117,7 +117,7 @@ mysql_host_reservation_init_test() {
# Let's wipe the whole database # Let's wipe the whole database
mysql_wipe mysql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
...@@ -387,7 +387,7 @@ mysql_lease4_dump_test() { ...@@ -387,7 +387,7 @@ mysql_lease4_dump_test() {
# Let's wipe the whole database # Let's wipe the whole database
mysql_wipe mysql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d" assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d"
...@@ -447,7 +447,7 @@ mysql_lease6_dump_test() { ...@@ -447,7 +447,7 @@ mysql_lease6_dump_test() {
# Let's wipe the whole database # Let's wipe the whole database
mysql_wipe mysql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init mysql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d" assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d"
......
...@@ -86,7 +86,7 @@ pgsql_lease_version_test() { ...@@ -86,7 +86,7 @@ pgsql_lease_version_test() {
${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
assert_eq 0 $? "cannot initialize the database, expected exit code: %d, actual: %d" assert_eq 0 $? "cannot initialize the database, expected exit code: %d, actual: %d"
# Verfiy that kea-admin lease-version returns the correct version # Verify that kea-admin lease-version returns the correct version
version=$(${keaadmin} lease-version pgsql -u $db_user -p $db_password -n $db_name) version=$(${keaadmin} lease-version pgsql -u $db_user -p $db_password -n $db_name)
assert_str_eq "3.0" ${version} "Expected kea-admin to return %s, returned value was %s" assert_str_eq "3.0" ${version} "Expected kea-admin to return %s, returned value was %s"
...@@ -280,7 +280,7 @@ pgsql_lease4_dump_test() { ...@@ -280,7 +280,7 @@ pgsql_lease4_dump_test() {
# Let's wipe the whole database # Let's wipe the whole database
pgsql_wipe pgsql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d" assert_eq 0 $ERRCODE "could not create database, expected exit code %d, actual %d"
...@@ -375,7 +375,7 @@ pgsql_lease6_dump_test() { ...@@ -375,7 +375,7 @@ pgsql_lease6_dump_test() {
# Let's wipe the whole database # Let's wipe the whole database
pgsql_wipe pgsql_wipe
# Ok, now let's initalize the database # Ok, now let's initialize the database
${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir ${keaadmin} lease-init pgsql -u $db_user -p $db_password -n $db_name -d $db_scripts_dir
ERRCODE=$? ERRCODE=$?
assert_eq 0 $ERRCODE "could not create database, status code %d" assert_eq 0 $ERRCODE "could not create database, status code %d"
......
...@@ -80,7 +80,7 @@ D2CfgMgr::forwardUpdatesEnabled() { ...@@ -80,7 +80,7 @@ D2CfgMgr::forwardUpdatesEnabled() {
bool bool
D2CfgMgr::reverseUpdatesEnabled() { D2CfgMgr::reverseUpdatesEnabled() {
// Reverse updates are not enabled if no revese servers are defined. // Reverse updates are not enabled if no reverse servers are defined.
return (getD2CfgContext()->getReverseMgr()->size() > 0); return (getD2CfgContext()->getReverseMgr()->size() > 0);
} }
......
...@@ -130,7 +130,7 @@ operator<<(std::ostream& os, const D2Params& config) { ...@@ -130,7 +130,7 @@ operator<<(std::ostream& os, const D2Params& config) {
} }
// *********************** TSIGKeyInfo ************************* // *********************** TSIGKeyInfo *************************
// Note these values match correpsonding values for Bind9's // Note these values match corresponding values for Bind9's
// dnssec-keygen // dnssec-keygen
const char* TSIGKeyInfo::HMAC_MD5_STR = "HMAC-MD5"; const char* TSIGKeyInfo::HMAC_MD5_STR = "HMAC-MD5";
const char* TSIGKeyInfo::HMAC_SHA1_STR = "HMAC-SHA1"; const char* TSIGKeyInfo::HMAC_SHA1_STR = "HMAC-SHA1";
......
...@@ -258,7 +258,7 @@ private: ...@@ -258,7 +258,7 @@ private:
/// @brief Dumps the contents of a D2Params as text to an output stream /// @brief Dumps the contents of a D2Params as text to an output stream
/// ///
/// @param os output stream to which text should be sent