FORMULA_FONTSIZE = 10
-# Use the FORMULA_TRANPARENT tag to determine whether or not the images
+# Use the FORMULA_TRANSPARENT tag to determine whether or not the images
# generated for formulas are transparent PNGs. Transparent PNGs are
# not supported properly for IE 6.0, but are supported on all modern browsers.
# Note that when changing this option you need to delete any form_*.png files
-// Copyright (C) 2013-2016 Internet Systems Consortium, Inc. ("ISC")
+// Copyright (C) 2013-2017 Internet Systems Consortium, Inc. ("ISC")
//
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
it. You have surely checked that it compiles on your system, but Kea
is portable software. Besides Linux, it is compiled and used on
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
is expected to run on many other architectures. You may take a look at
system specific build notes (http://kea.isc.org/wiki/Install).
requests and will stay there. The third benefit is that the pull request mechanism is
very flexible. Kea engineers (and other users, too) can comment on it, attach
links, mention other users etc. You as a submitter can augment the patch by
-commiting extra changes to your repository. Those extra commits will appear instantly
+committing extra changes to your repository. Those extra commits will appear instantly
in the pull request. This is really useful during the review. Finally, ISC engineers can
better assess all open pull requests and add labels to them, such as "enhancement", "bug", or
"unit-tests missing". This makes our life easier. Oh, and your commits will later
or see what the exact scope of changes are. Nevertheless, if we given a choice
of getting a tarball or not getting a patch at all, we prefer tarballs. Just
keep in mind that processing a tarball is really cumbersome for ISC
-engineers, so it may take sigificantly longer than other ways.
+engineers, so it may take significantly longer than other ways.
@section contributorGuideReview Going through a review
For example, Kea currently only stores lease information
and host reservations. Future versions of Kea will store
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.
</para>
<orderedlist>
<listitem>
<para>
- Export CQLSH_HOST environemnt variable:
+ Export CQLSH_HOST environment variable:
<screen>
$ <userinput>export CQLSH_HOST=localhost</userinput>
</screen>
read-only mode.
Sections <xref linkend="read-only-database-configuration4"/> and
<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.
</para>
</section>
</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.
The specific loggers are "kea-dhcp4.eval" and "kea-dhcp6.eval".
</para>
</section> <!-- "d2-reverse-ddns-config" -->
- <section id="d2-exmaple-config">
+ <section id="d2-example-config">
<title>Example DHCP-DDNS Server Configuration</title>
<para>
This section provides an example DHCP-DDNS server configuration based
With DHCPv4-over-DHCPv6 the DHCPv4 server does not have access
to several of the identifiers it would normally use to select a
subnet. In order to address this issue three new configuration
- entires have been added. The presence of any of these allows the
+ entries have been added. The presence of any of these allows the
subnet to be used with DHCPv4-over-DHCPv6. These entries are:
<itemizedlist>
<listitem>
0a:0b:0c:0d:0e:0f. (Note that if you plan to do DNS updates, it
is strongly recommended for the hostnames to be unique.) The third
example reserves address 192.0.3.203 to a client whose request
- would be relayed by a relay agent that inserts a circuid-it option
+ would be relayed by a relay agent that inserts a circuit-it option
with the value 'charter950'. The fourth entry reserves address
192.0.2.204 for a client that uses a client identifier with value
01:11:22:33:44:55:66.</para>
- <para>The above example is used for ilustrational purposes only
+ <para>The above example is used for illustrational purposes only
and in actual deployments it is recommended to use as few types as possible
(preferably just one). See <xref linkend="reservations4-tuning"/> for a detailed
discussion of this point.</para>
S46 container options group rules and optional port parameters
for a specified domain. There are three container options specified
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.
They do not include any data fields.
</para>
statistic is expected to grow if there are devices
that are using DHCPv4-over-DHCPv6. DHCPv4-QUERY
messages are used by DHCPv4 clients on an IPv6 only
- line which encapsulatesi the requests over DHCPv6.
+ line which encapsulates the requests over DHCPv6.
</entry>
</row>
<title>Forensic Logging Hooks</title>
<para>
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
is only available to ISC customers with a support contract.
</para>
</para></listitem>
<listitem><para>
base-name - an arbitrary value which is used in conjunction with
- the current system date to form the current foresnic file name. It defaults
+ the current system date to form the current forensic file name. It defaults
to <filename>kea-legal</filename>.
</para></listitem>
</itemizedlist>
Kea is officially supported on Red Hat Enterprise Linux,
CentOS, Fedora and FreeBSD systems. It is also likely to work on many
other platforms: Kea 1.1.0 builds have been tested on (in no
- particular order) Red Hat Enteprise Linux 6.4, Debian GNU/Linux 7,
+ particular order) Red Hat Enterprise Linux 6.4, Debian GNU/Linux 7,
Ubuntu 12.04, Ubuntu 14.04, Ubuntu 16.04, Fedora Linux 19,
Fedora 20, Fedora 22, CentOS Linux 7, NetBSD 6, FreeBSD 10.3,
OpenBSD 5.7, OpenBSD 6.0, OS X 10.10, OS X 10.11.
runtime) are responsible for creating the loggers used by those
libraries. Such loggers should have unique names, different
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
the loggers to be configured independently of loggers used
by Kea. Whenever it makes sense, a hook library can use multiple
packet drops, you must create configuration entry for the
logger called <quote>kea-dhcp4.bad-packets</quote> and specify
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
configuration.
</para>
projects / thirdparty / kea.git / commitdiff
