Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Sebastian Schrader
Kea
Commits
134a55c7
Commit
134a55c7
authored
Aug 12, 2016
by
Stephen Morris
Browse files
[4489] Minor edits to documentation
parent
e6936baa
Changes
3
Hide whitespace changes
Inline
Side-by-side
doc/guide/admin.xml
View file @
134a55c7
...
...
@@ -714,7 +714,7 @@ $ <userinput>kea-admin lease-upgrade cql -n <replaceable>database-name</replacea
the read only mode.
Sections
<xref
linkend=
"read-only-database-configuration4"
/>
and
<xref
linkend=
"read-only-database-configuration6"
/>
describe when
such configuration may be
des
ired and how to configure Kea to
such configuration may be
req
ired and how to configure Kea to
operate using read only host database.
</para>
</section>
...
...
doc/guide/dhcp4-srv.xml
View file @
134a55c7
...
...
@@ -541,10 +541,10 @@ If a timeout is given though, it should be an integer greater than zero.
</section>
<section
id=
"read-only-database-configuration4"
>
<title>
Using Read
Only Databases for Host Reservations
</title>
<title>
Using Read
-
Only Databases for Host Reservations
</title>
<para>
In some deployments the database user
,
wh
ich
name is specified in the database backend
configuration
,
may not have write privileges to the database. This is often
In some deployments the database user wh
ose
name is specified in the database backend
configuration may not have write privileges to the database. This is often
required by the policy within a given network to secure the data from being
unintentionally modified. In many cases administrators have inventory databases
deployed, which contain substantially more information about the hosts than
...
...
@@ -552,13 +552,13 @@ static reservations assigned to them. The inventory database can be used to crea
a view of a Kea hosts database and such view is often read only.
</para>
<para>
Kea host database backends operate with implicit configuration to both
read
from and write to the database. If the
host
database
is read only for th
e
particular u
se
r
, the backend will fail to start and
consequently the server
will refuse to start
/
reconfigure.
If the administrator intends to use the
read
only host database for retrieving reservations for clients
, to assign
specific addresses and options, it is possible to explicitly
configure
Kea to start in "read-only" mode. This is controlled by the
Kea host database backends operate with
an
implicit configuration to both
read
from and write to the database. If the database
user does not hav
e
write access to the host databa
se, the backend will fail to start and
the
server
will refuse to start
(or
reconfigure
)
.
However, if access to a read
only host database
is required
for retrieving reservations for clients
and/or assign
specific addresses and options, it is possible to explicitly
configure
Kea to start in "read-only" mode. This is controlled by the
<command>
readonly
</command>
boolean parameter as follows:
<screen>
"Dhcp4": { "hosts-database": {
<userinput>
"readonly": true
</userinput>
, ... }, ... }
...
...
doc/guide/dhcp6-srv.xml
View file @
134a55c7
...
...
@@ -542,10 +542,10 @@ If a timeout is given though, it should be an integer greater than zero.
</section>
<section
id=
"read-only-database-configuration6"
>
<title>
Using Read
Only Databases for Host Reservations
</title>
<title>
Using Read
-
Only Databases for Host Reservations
</title>
<para>
In some deployments the database user
,
wh
ich
name is specified in the database backend
configuration
,
may not have write privileges to the database. This is often
In some deployments the database user wh
ose
name is specified in the database backend
configuration may not have write privileges to the database. This is often
required by the policy within a given network to secure the data from being
unintentionally modified. In many cases administrators have inventory databases
deployed, which contain substantially more information about the hosts than
...
...
@@ -553,16 +553,16 @@ static reservations assigned to them. The inventory database can be used to crea
a view of a Kea hosts database and such view is often read only.
</para>
<para>
Kea host database backends operate with implicit configuration to both
read from
and write to the database. If the
host
database
is read only for th
e
particular u
se
r
, the backend will fail to start and
consequently the server
will refuse to start
/
reconfigure.
If the administrator intends to use the
read
only host database for retrieving reservations for clients
, to assign
specific addresses and options, it is possible to explicitly
configure
Kea to start in "read-only" mode. This is controlled by the
Kea host database backends operate with
an
implicit configuration to both
read from
and write to the database. If the database
user does not hav
e
write access to the host databa
se, the backend will fail to start and
the
server
will refuse to start
(or
reconfigure
)
.
However, if access to a read
only host database
is required
for retrieving reservations for clients
and/or assign
specific addresses and options, it is possible to explicitly
configure
Kea to start in "read-only" mode. This is controlled by the
<command>
readonly
</command>
boolean parameter as follows:
<screen>
"Dhcp
4
": { "hosts-database": {
<userinput>
"readonly": true
</userinput>
, ... }, ... }
"Dhcp
6
": { "hosts-database": {
<userinput>
"readonly": true
</userinput>
, ... }, ... }
</screen>
Setting this parameter to
<userinput>
false
</userinput>
would configure the
database backend to operate in "read-write" mode, which is also a default
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a 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