BIND 10 master, updated. 6160ff536fe0a97b0d1020e1857c678f0343d8f5 [master] fixed typos and misspellings in .mes message files
BIND 10 source code commits
bind10-changes at lists.isc.org
Tue Apr 8 18:18:25 UTC 2014
The branch, master has been updated
via 6160ff536fe0a97b0d1020e1857c678f0343d8f5 (commit)
via 580b893a413f387b46d0ac222c2c4b9e538a80d8 (commit)
via 5778d45a1d85e1e3aa3389cc93f2f5b9ce8f389a (commit)
via 271af445dde579b17130347dbd74268fd98c71e5 (commit)
via 398a4dec3587220d0bec3c58a743bc0810cebd27 (commit)
via 5f5dfa25b2453193d25456eb050fa7d5d52d6d31 (commit)
from c2bd605806c2e938cb30eeaa51b0e1566d906b50 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 6160ff536fe0a97b0d1020e1857c678f0343d8f5
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 13:17:51 2014 -0500
[master] fixed typos and misspellings in .mes message files
commit 580b893a413f387b46d0ac222c2c4b9e538a80d8
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 13:05:27 2014 -0500
[master] fix misspellings
fixed many typos
also consistently spell and capitalize PostgreSQL.
commit 5778d45a1d85e1e3aa3389cc93f2f5b9ce8f389a
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 12:52:33 2014 -0500
[master] fix typo
as reported on dhcp jabber
commit 271af445dde579b17130347dbd74268fd98c71e5
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 12:51:32 2014 -0500
[master] don't have duplicate ID
(discussed a little on jabber)
commit 398a4dec3587220d0bec3c58a743bc0810cebd27
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 12:39:44 2014 -0500
[master] bump year for copyright in guide
commit 5f5dfa25b2453193d25456eb050fa7d5d52d6d31
Author: Jeremy C. Reed <jreed at isc.org>
Date: Tue Apr 8 12:38:18 2014 -0500
[master] increase copyright year for the generated messages documentation
(maybe this should be automatically set to current year)
-----------------------------------------------------------------------
Summary of changes:
doc/guide/bind10-guide.xml | 64 ++++++++++-----------
src/bin/auth/auth_messages.mes | 2 +-
src/bin/bind10/init_messages.mes | 2 +-
src/bin/dhcp6/dhcp6_messages.mes | 4 +-
src/bin/memmgr/memmgr_messages.mes | 2 +-
src/hooks/dhcp/user_chk/user_chk_messages.mes | 4 +-
src/lib/asiodns/asiodns_messages.mes | 2 +-
src/lib/datasrc/datasrc_messages.mes | 2 +-
src/lib/datasrc/memory/memory_messages.mes | 2 +-
src/lib/dhcpsrv/dhcpsrv_messages.mes | 2 +-
src/lib/hooks/hooks_messages.mes | 2 +-
src/lib/python/isc/memmgr/libmemmgr_messages.mes | 2 +-
src/lib/python/isc/notify/notify_out_messages.mes | 2 +-
tools/system_messages.py | 2 +-
14 files changed, 47 insertions(+), 47 deletions(-)
-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index a92bf71..7bb7be2 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -30,7 +30,7 @@
<subtitle>Administrator Reference for BIND 10</subtitle>
<copyright>
- <year>2010-2013</year><holder>Internet Systems Consortium, Inc.</holder>
+ <year>2010-2014</year><holder>Internet Systems Consortium, Inc.</holder>
</copyright>
<abstract>
@@ -3640,7 +3640,7 @@ $</screen>
PostgreSQL configuration program "pg_config" with the "--with-dhcp-pgsql" switch,
i.e.
<screen><userinput>./configure [other-options] --with-dhcp-pgsql</userinput></screen>
- ...if Postgresql was installed in the default location, or:
+ ...if PostgreSQL was installed in the default location, or:
<screen><userinput>./configure [other-options] --with-dhcp-pgsql=<replaceable>path-to-pg_config</replaceable></userinput></screen>
...if not.
</para>
@@ -3687,7 +3687,7 @@ $</screen>
5. Create the database tables using the new user's credentials.
After entering the following command, you will be prompted for the new
user's password. When the command completes you will be returned to
- the shell prompt. You should see output similiar to following:
+ the shell prompt. You should see output similar to following:
<screen>$ <userinput>psql -d <replaceable>database-name</replaceable> -U <replaceable>user-name</replaceable> -f <replaceable>path-to-bind10</replaceable>/share/bind10/dhcpdb_create.pgsql</userinput>
Password for user <replaceable>user-name</replaceable>:
CREATE TABLE
@@ -3715,14 +3715,14 @@ $
psql: FATAL: no pg_hba.conf entry for host "[local]", user "<replaceable>user-name</replaceable>", database "<replaceable>database-name</replaceable>", SSL off
</screen>
<para>
- This indicates that the Postgresql configuration needs to be modified.
+ This indicates that the PostgreSQL configuration needs to be modified.
Kea uses password authentication when connecting to the database and must
- have the appropriate entries added to Posgresql's pg_hba.conf file. This
- file is normally located in the primary data directory for your Postgresql
- server. The precise path may vary but the default location for Postgres 9.3
+ have the appropriate entries added to PostgreSQL's pg_hba.conf file. This
+ file is normally located in the primary data directory for your PostgreSQL
+ server. The precise path may vary but the default location for PostgreSQL 9.3
on Centos 6.5 is:
<filename>/var/lib/pgsql/9.3/data/pg_hba.conf</filename>.
- Assuming Kea is running on the same host as Postgresql, adding lines similiar
+ Assuming Kea is running on the same host as PostgreSQL, adding lines similar
to following should be sufficient to provide password-authenticated access to
Kea's database:
</para>
@@ -4451,7 +4451,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
It is recommended that boolean values are specified using "true" and "false"
strings. This helps to prevent errors when typing multiple comma separated
values, as it make it easier to identify the type of the value being typed,
- and compare it with the order of data fields. Nevetheless, it is possible
+ and compare it with the order of data fields. Nevertheless, it is possible
to use integer values: "1" and "0", instead of "true" and "false"
accordingly. If other integer value is specified, the configuration is
rejected.
@@ -4722,7 +4722,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
The FQDN, lease address, and DHCID
</para></listitem>
</orderedlist>
- The paramaters for controlling the generation of NCRs for submission to D2
+ The parameters for controlling the generation of NCRs for submission to D2
are contained in the "dhcp-ddns" section of the DHCPv4 server
configuration. The default values for this section appears as follows:
<screen>
@@ -4749,7 +4749,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
> <userinput>config commit</userinput>
</screen>
<section id="dhcpv4-d2-io-config">
- <title>DHCP-DDNS Server Connectivty</title>
+ <title>DHCP-DDNS Server Connectivity</title>
<para>
In order for NCRs to reach the D2 server, DHCPv4 must be able
to communicate with it and so the relevant parameters must be set
@@ -4784,14 +4784,14 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
It is important to keep in mind that DHCPv4 provides the initial decision
making of when and what to update and forwards that information to D2 in
the form of NCRs. Carrying out the actual DNS updates and dealing with
- such things as conflict resolution are the purvue of D2 (<xref linkend="dhcp-ddns-server"/>).
+ such things as conflict resolution are the purview of D2 (<xref linkend="dhcp-ddns-server"/>).
<para>
This section describes when DHCPv4 will generate NCRs and the
configuration parameters that can be used to influence this decision.
- It assumes that the "enable-updates" paramater is true.
+ It assumes that the "enable-updates" parameter is true.
</para>
<para>
- In general, DHCPv4 will generate DDNS udpate requests when:
+ In general, DHCPv4 will generate DDNS update requests when:
<orderedlist>
<listitem><para>
A new lease is granted in response to a DHCP REQUEST
@@ -4861,7 +4861,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
<para>
The first row in the table above represents "client delegation". Here
the DHCP client states that it intends to do the forward DNS updates and
- the server should do the reverese updates. By default, DHCPv4 will honor
+ the server should do the reverse updates. By default, DHCPv4 will honor
the client's wishes and generate a DDNS request to D2 to update only
reverse DNS data. The parameter, "override-client-update", can be used
to instruct the server to override client delegation requests. When
@@ -4886,7 +4886,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
The third row in the table above describes the case in which the client
requests that no DNS updates be done. The parameter, "override-no-update",
can be used to instruct the server to disregard the client's wishes. When
- this parameter is true, DHCPv4 will generate DDNS udpate request to D2
+ this parameter is true, DHCPv4 will generate DDNS update request to D2
even if the client requests no updates be done. The N-S-O flags in the
server's response to the client will be 0-1-1.
</para>
@@ -5083,7 +5083,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
<para>The subnet selection mechanism described in this section is based
on the assumption that client classification is not used. The classification
mechanism alters the way in which subnet is selected for the client,
- depending on the clasess that the client belongs to.</para>
+ depending on the classes that the client belongs to.</para>
</note>
</section>
@@ -5563,7 +5563,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
> <userinput>config set Dhcp6/interfaces[0] eth1/2001:db8::1</userinput>
> <userinput>config commit</userinput></screen>
When configuration gets committed, the server will start to listen on
- eth1 on link-local address, mutlicast group (ff02::1:2) and 2001:db8::1.
+ eth1 on link-local address, multicast group (ff02::1:2) and 2001:db8::1.
</para>
<para>
It is possible to mix interface names, wildcards and interface name/addresses
@@ -5935,7 +5935,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
It is recommended that boolean values are specified using "true" and "false"
strings. This helps to prevent errors when typing multiple comma separated
values, as it make it easier to identify the type of the value being typed,
- and compare it with the order of data fields. Nevetheless, it is possible
+ and compare it with the order of data fields. Nevertheless, it is possible
to use integer values: "1" and "0", instead of "true" and "false"
accordingly. If other integer value is specified, the configuration is
rejected.
@@ -6303,7 +6303,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
> <userinput>config commit</userinput>
</screen>
<section id="dhcpv6-d2-io-config">
- <title>DHCP-DDNS Server Connectivty</title>
+ <title>DHCP-DDNS Server Connectivity</title>
In order for NCRs to reach D2, DHCPv6 must be able to communicate with it.
The following parameters are used to establish connectivty between DHCPv6
and D2.
@@ -6334,16 +6334,16 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
</para>
</section>
<section id="dhcpv6-d2-rules-config">
- <title>When does DHCPv6 generates DDNS request</title>
+ <title>When does DHCPv6 generate DDNS request</title>
DHCPv6 follows the behavior prescribed for DHCP servers in RFC 4704.
It is important to keep in mind that DHCPv6 provides the initial decision
making of when and what to update and forwards that information to D2 in
the form of NCRs. Carrying out the actual DNS updates and dealing with
- such things as conflict resolution are the purvue of D2 (<xref linkend="dhcp-ddns-server"/>).
+ such things as conflict resolution are the purview of D2 (<xref linkend="dhcp-ddns-server"/>).
<para>
This section describes when DHCPv6 will generate NCRs and the
configuration parameters that can be used to influence this decision.
- It assumes that the "enable-updates" paramater is true.
+ It assumes that the "enable-updates" parameter is true.
</para>
<note>
<para>
@@ -6355,7 +6355,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
</para>
</note>
<para>
- In general, DHCPv6 will generate DDNS udpate requests when:
+ In general, DHCPv6 will generate DDNS update requests when:
<orderedlist>
<listitem><para>
A new lease is granted in response to a DHCP REQUEST
@@ -6381,7 +6381,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
respect the FQDN N and S flags specified by the client as shown in the
following table:
</para>
- <table id="fqdn-flag-table">
+ <table id="dhcp6-fqdn-flag-table">
<title>Default FQDN Flag Behavior</title>
<tgroup cols='4' align='left'>
<colspec colname='cflags'/>
@@ -6423,7 +6423,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
<para>
The first row in the table above represents "client delegation". Here
the DHCP client states that it intends to do the forward DNS updates and
- the server should do the reverese updates. By default, DHCPv6 will honor
+ the server should do the reverse updates. By default, DHCPv6 will honor
the client's wishes and generate a DDNS request to D2 to update only
reverse DNS data. The parameter, "override-client-update", can be used
to instruct the server to override client delegation requests. When
@@ -6448,7 +6448,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
The third row in the table above describes the case in which the client
requests that no DNS updates be done. The parameter, "override-no-update",
can be used to instruct the server to disregard the client's wishes. When
- this parameter is true, DHCPv6 will generate DDNS udpate request to D2
+ this parameter is true, DHCPv6 will generate DDNS update request to D2
even if the client requests no updates be done. The N-S-O flags in the
server's response to the client will be 0-1-1.
</para>
@@ -6956,7 +6956,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<listitem>
<simpara>
<command>name</command> —
- is a unique text label used to idenfity the this key within the
+ is a unique text label used to identify the this key within the
list. It is this value that is used to specify which key (if any)
should be used with a specific DNS server. So long as it is
unique, its content is arbitrary. It cannot be blank.
@@ -7051,7 +7051,7 @@ DhcpDdns/forward_ddns/ddns_domains [] list (default)
If TSIG is used with this domain's servers, this
value should be the name of the key from within the TSIG Key List
to use. If the value is blank (the default), TSIG will not be
- used in DDNS converations with this domain's servers. Currently
+ used in DDNS conversations with this domain's servers. Currently
TSIG has not been implemented, so this value is ignored.
</simpara>
</listitem>
@@ -7085,7 +7085,7 @@ DhcpDdns/forward_ddns/ddns_domains[0]/dns_servers [] list (default)
<userinput>> config set DhcpDdns/forward_ddns/ddns_domains[1]/name "other.example.com"</userinput>
<userinput>> config commit</userinput>
</screen>
- It is permissable to add a domain without any servers. If that domain
+ It is permissible to add a domain without any servers. If that domain
should be matched to a request, however, the request will fail. In
order to make the domain useful though, we must add at least one DNS
server to it.
@@ -7202,7 +7202,7 @@ DhcpDdns/reverse_ddns/ddns_domains [] list (default)
If TSIG should be used with this domain's servers, then this
value should be the name of the key from within the TSIG Key List
to use. If the value is blank (the default), TSIG will not be
- used in DDNS converations with this domain's servers. Currently
+ used in DDNS conversations with this domain's servers. Currently
this value is not used as TSIG has not been implemented.
</simpara>
</listitem>
@@ -7237,7 +7237,7 @@ DhcpDdns/reverse_ddns/ddns_domains[0]/dns_servers [] list (default)
<userinput>> config set DhcpDdns/reverse_ddns/ddns_domains[1]/name "1.0.0.0.8.B.D.0.1.0.0.2.ip6.arpa."</userinput>
<userinput>> config commit</userinput>
</screen>
- It is permissable to add a domain without any servers. If that domain
+ It is permissible to add a domain without any servers. If that domain
should be matched to a request, however, the request will fail. In
order to make the domain useful though, we must add at least one DNS
server to it.
diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes
index 5009de8..bf87321 100644
--- a/src/bin/auth/auth_messages.mes
+++ b/src/bin/auth/auth_messages.mes
@@ -177,7 +177,7 @@ The separate thread for maintaining data source clients has been stopped.
% AUTH_DATASRC_CLIENTS_BUILDER_WAKE_ERR failed to wake up main thread: %1
A low-level error happened when trying to send data to the main thread to wake
-it up. Terminating to prevent inconsistent state and possiblu hang ups.
+it up. Terminating to prevent inconsistent state and possible hang ups.
% AUTH_DATASRC_CLIENTS_SHUTDOWN_ERROR error on waiting for data source builder thread: %1
This indicates that the separate thread for maintaining data source
diff --git a/src/bin/bind10/init_messages.mes b/src/bin/bind10/init_messages.mes
index 7135b2d..a3e3413 100644
--- a/src/bin/bind10/init_messages.mes
+++ b/src/bin/bind10/init_messages.mes
@@ -29,7 +29,7 @@ The named component failed previously and we will try to restart it to provide
as flawless service as possible, but it should be investigated what happened,
as it could happen again.
-% BIND10_COMPONENT_SHUTDOWN_ERROR An error occured stopping component %1
+% BIND10_COMPONENT_SHUTDOWN_ERROR An error occurred stopping component %1
An attempt to gracefully shutdown a component failed.
% BIND10_COMPONENT_START component %1 is starting
diff --git a/src/bin/dhcp6/dhcp6_messages.mes b/src/bin/dhcp6/dhcp6_messages.mes
index 804db33..e3903a4 100644
--- a/src/bin/dhcp6/dhcp6_messages.mes
+++ b/src/bin/dhcp6/dhcp6_messages.mes
@@ -146,7 +146,7 @@ a brief service interruption.
A warning message indicating that a client is attempting to extend lease lifetime
for the address, but the server does not have any information about the subnet this
client belongs to. This may mean that faulty the mobile client changed its location
-and is trying to renew its old address (client is supposed to send confirm, not rewew
+and is trying to renew its old address (client is supposed to send confirm, not renew
in such cases, according to RFC3315) or the server configuration has changed and
information about existing subnet was removed. Note that in a sense this is worse
case of DHCP6_EXTEND_NA_UNKNOWN, as not only the lease is unknown, but also the subnet
@@ -490,7 +490,7 @@ reconfiguration procedure.
% DHCP6_SERVERID_WRITE_FAIL server was not able to write its ID to file %1
This warning message indicates that server was not able to write its
server identifier (DUID) to a file. This likely indicates lack of write
-permission to a given file or directory. This is not cricital and the
+permission to a given file or directory. This is not critical and the
server will continue to operate, but server will generate different DUID
during every start and clients will need to go through a rebind phase
to recover.
diff --git a/src/bin/memmgr/memmgr_messages.mes b/src/bin/memmgr/memmgr_messages.mes
index 6ca5c0f..44d92f7 100644
--- a/src/bin/memmgr/memmgr_messages.mes
+++ b/src/bin/memmgr/memmgr_messages.mes
@@ -22,7 +22,7 @@ The cause of the error is included in the message. None of the received
updates applied, and the daemon keeps running with the previous configuration.
% MEMMGR_CONFIG_UPDATE received new configuration
-A debug message. The memmgr daemon receives configuratiopn updates
+A debug message. The memmgr daemon receives configuration updates
and is now applying them to its running configurations.
% MEMMGR_DATASRC_CONFIG_ERROR failed to update data source configuration: %1
diff --git a/src/hooks/dhcp/user_chk/user_chk_messages.mes b/src/hooks/dhcp/user_chk/user_chk_messages.mes
index 23e3023..0b11a1c 100644
--- a/src/hooks/dhcp/user_chk/user_chk_messages.mes
+++ b/src/hooks/dhcp/user_chk/user_chk_messages.mes
@@ -22,7 +22,7 @@ This is an error message issued when an error occurs while unloading the
UserCheckHook library. This is unlikely to occur and normal operations of the
library will likely resume when it is next loaded.
-% USER_CHK_SUBNET4_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet4_select callout: %1
+% USER_CHK_SUBNET4_SELECT_ERROR DHCP UserCheckHook an unexpected error occurred in subnet4_select callout: %1
This is an error message issued when the DHCP UserCheckHook subnet4_select hook
encounters an unexpected error. The message should contain a more detailed
explanation.
@@ -32,7 +32,7 @@ This is an error message issued when the DHCP UserCheckHook subnet4_select hook
has been invoked but the UserRegistry has not been created. This is a
programmatic error and should not occur.
-% USER_CHK_SUBNET6_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet6_select callout: %1
+% USER_CHK_SUBNET6_SELECT_ERROR DHCP UserCheckHook an unexpected error occurred in subnet6_select callout: %1
This is an error message issued when the DHCP UserCheckHook subnet6_select hook
encounters an unexpected error. The message should contain a more detailed
explanation.
diff --git a/src/lib/asiodns/asiodns_messages.mes b/src/lib/asiodns/asiodns_messages.mes
index 71aded7..9739542 100644
--- a/src/lib/asiodns/asiodns_messages.mes
+++ b/src/lib/asiodns/asiodns_messages.mes
@@ -65,7 +65,7 @@ included in the log message. The server still keeps accepting new
connections, so unless it happens often it's probably okay to ignore
this error. If the shown error indicates something like "too many
open files", it's probably because the run time environment is too
-restrictive on this limitation, so consider adjusing the limit using
+restrictive on this limitation, so consider adjusting the limit using
a tool such as ulimit. If you see other types of errors too often,
there may be something overlooked; please file a bug report in that case.
diff --git a/src/lib/datasrc/datasrc_messages.mes b/src/lib/datasrc/datasrc_messages.mes
index c5e55ca..9fe907e 100644
--- a/src/lib/datasrc/datasrc_messages.mes
+++ b/src/lib/datasrc/datasrc_messages.mes
@@ -19,7 +19,7 @@ $NAMESPACE isc::datasrc
% DATASRC_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'
The software refuses to load NSEC3 records into a wildcard domain or
the owner name has two or more labels below the zone origin.
-It isn't explicitly forbidden, but no sane zone wouldn have such names
+It isn't explicitly forbidden, but no sane zone would have such names
for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is
compatible with BIND 9.
diff --git a/src/lib/datasrc/memory/memory_messages.mes b/src/lib/datasrc/memory/memory_messages.mes
index 37539e7..973a9b8 100644
--- a/src/lib/datasrc/memory/memory_messages.mes
+++ b/src/lib/datasrc/memory/memory_messages.mes
@@ -23,7 +23,7 @@ by providing everything found inside the domain.
% DATASRC_MEMORY_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'
The software refuses to load NSEC3 records into a wildcard domain or
the owner name has two or more labels below the zone origin.
-It isn't explicitly forbidden, but no sane zone wouldn have such names
+It isn't explicitly forbidden, but no sane zone would have such names
for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is
compatible with BIND 9.
diff --git a/src/lib/dhcpsrv/dhcpsrv_messages.mes b/src/lib/dhcpsrv/dhcpsrv_messages.mes
index 4767c3e..76478cb 100644
--- a/src/lib/dhcpsrv/dhcpsrv_messages.mes
+++ b/src/lib/dhcpsrv/dhcpsrv_messages.mes
@@ -418,7 +418,7 @@ V6) is about to open a PostgreSQL lease database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
-% DHCPSRV_PGSQL_DEALLOC_ERROR An error occured deallocating SQL statements while closing the PostgreSQL lease database: %1
+% DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
This is an error message issued when a DHCP server (either V4 or V6) experienced
and error freeing database SQL resources as part of closing its connection to
the Postgresql database. The connection is closed as part of normal server
diff --git a/src/lib/hooks/hooks_messages.mes b/src/lib/hooks/hooks_messages.mes
index 53090ab..bae21cd 100644
--- a/src/lib/hooks/hooks_messages.mes
+++ b/src/lib/hooks/hooks_messages.mes
@@ -63,7 +63,7 @@ restart BIND 10.
% HOOKS_HOOK_LIST_RESET the list of hooks has been reset
This is a message indicating that the list of hooks has been reset.
While this is usual when running the BIND 10 test suite, it should not be
-seen when running BIND 10 in a producion environment. If this appears,
+seen when running BIND 10 in a production environment. If this appears,
please report a bug through the usual channels.
% HOOKS_INCORRECT_VERSION hook library %1 is at version %2, require version %3
diff --git a/src/lib/python/isc/memmgr/libmemmgr_messages.mes b/src/lib/python/isc/memmgr/libmemmgr_messages.mes
index c8fcf05..891b4c9 100644
--- a/src/lib/python/isc/memmgr/libmemmgr_messages.mes
+++ b/src/lib/python/isc/memmgr/libmemmgr_messages.mes
@@ -30,6 +30,6 @@ The MemorySegmentBuilder failed to load the specified zone when handling
the load command. This zone will be skipped.
% LIBMEMMGR_BUILDER_ZONE_WRITER_LOAD_2_ERROR Error loading zone '%1', data source '%2': '%3'
-An exception occured when the MemorySegmentBuilder tried to load the
+An exception occurred when the MemorySegmentBuilder tried to load the
specified zone when handling the load command. This zone will be
skipped.
diff --git a/src/lib/python/isc/notify/notify_out_messages.mes b/src/lib/python/isc/notify/notify_out_messages.mes
index fd08f43..7401ee9 100644
--- a/src/lib/python/isc/notify/notify_out_messages.mes
+++ b/src/lib/python/isc/notify/notify_out_messages.mes
@@ -55,7 +55,7 @@ the one we sent. Since there was a response, no more notifies will
be sent to this server for this notification event.
% NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1
-The notify_out library sent a notify message to the namesever at the
+The notify_out library sent a notify message to the nameserver at the
given address, but the reply did not have the QR bit set to one.
Since there was a response, no more notifies will be sent to this
server for this notification event.
diff --git a/tools/system_messages.py b/tools/system_messages.py
index 869a164..0fc209d 100644
--- a/tools/system_messages.py
+++ b/tools/system_messages.py
@@ -71,7 +71,7 @@ SEC_HEADER="""<?xml version="1.0" encoding="UTF-8"?>
<title>BIND 10 Messages Manual</title>
<copyright>
- <year>2011-2013</year><holder>Internet Systems Consortium, Inc.</holder>
+ <year>2011-2014</year><holder>Internet Systems Consortium, Inc.</holder>
</copyright>
<abstract>
More information about the bind10-changes
mailing list