Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ISC Open Source Projects
Kea
Commits
b9c80fb8
Commit
b9c80fb8
authored
Sep 27, 2017
by
Wlodzimierz Wencel
Browse files
[master] fixing typos in documentation
parent
28b4f8aa
Changes
3
Hide whitespace changes
Inline
Side-by-side
doc/guide/dhcp4-srv.xml
View file @
b9c80fb8
...
...
@@ -3468,7 +3468,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
subnet, it is easier to simply configure additional subnet on top of the
existing one. Sometimes, due to address space fragmentation (e.g. only many
disjoint /24s are available) this is the only choice. Also, configuring
additional subnet has the advantage of not dis
t
rupting the operation of
additional subnet has the advantage of not disrupting the operation of
existing devices.
</para>
<para>
Another very frequent use case comes from cable networks. There are two types
...
...
@@ -3528,8 +3528,8 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
consist of two or more subnets. However, for testing purposes it is allowed
to define a shared network with just one subnet or even an empty one. This
is not a recommended practice in production networks, as the shared network
logic requires additional processing and thus lowers server's performace.
To avoid unnecessary peformance degradation the shared subnets should only
logic requires additional processing and thus lowers server's performa
n
ce.
To avoid unnecessary pe
r
formance degradation the shared subnets should only
be defined when required by the deployment.
</para>
...
...
doc/guide/dhcp6-srv.xml
View file @
b9c80fb8
...
...
@@ -3087,8 +3087,8 @@ If not specified, the default value is:
consist of two or more subnets. However, for testing purposes it is allowed
to define a shared network with just one subnet or even an empty one. This
is not a recommended practice in production networks, as the shared network
logic requires additional processing and thus lowers server's performace.
To avoid unnecessary peformance degradation the shared subnets should only
logic requires additional processing and thus lowers server's performa
n
ce.
To avoid unnecessary pe
r
formance degradation the shared subnets should only
be defined when required by the deployment.
</para>
...
...
doc/guide/hooks.xml
View file @
b9c80fb8
...
...
@@ -1239,7 +1239,7 @@ An example deletion by (subnet-id, identifier-type, identifier) looks as follows
</para>
<para><command>
lease6-add
</command>
command requires four
param
a
ters: an IPv6 address, a subnet-id, and IAID value
param
e
ters: an IPv6 address, a subnet-id, and IAID value
(identity association identifier, a value sent by clients) and
a DUID:
<screen>
...
...
@@ -1294,7 +1294,7 @@ The commands can take a number of additional optional parameters:
not be conducted at the lease insertion time. If configured, a DNS
update to remove the A or AAAA records will be conducted when the
lease is removed due to expiration or being released by a
client. If not specifed, the default value is false. Hostname
client. If not specif
i
ed, the default value is false. Hostname
parameter must be specified in fqdn-fwd is set to true.
</para>
</listitem>
<listitem>
...
...
@@ -1304,7 +1304,7 @@ The commands can take a number of additional optional parameters:
not be conducted at the lease insertion time. If configured, a DNS
update to remove the PTR record will be conducted when the lease
is removed due to expiration or being released by a client. If not
specifed, the default value is false. Hostname parameter must be
specif
i
ed, the default value is false. Hostname parameter must be
specified in fqdn-fwd is set to true.
</para>
</listitem>
<listitem>
...
...
@@ -1535,7 +1535,7 @@ as follows:
<command>
leaseX-get
</command>
, if needed.
</para>
<para>
An example command updating IPv
6
lease looks as follows:
An example command updating IPv
4
lease looks as follows:
<screen>
{
"command": "lease4-update",
"arguments": {
...
...
@@ -1594,7 +1594,7 @@ as follows:
number of leases removed and 0 (success) status code if any
leases were removed and 2 (empty) if there were no
leases. Status code 1 (error) may be returned in case the
parame
e
ters are incorrect or some other exception is
parameters are incorrect or some other exception is
encountered.
</para>
<para>
Note: not all backends support this command.
</para>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment