BIND 10 master, updated. dc2f6aabc9b1f28136e4513f46eb43c235bf505e [master]Merge branch 'master' of ssh://git.bind10.isc.org/var/bind10/git/bind10
BIND 10 source code commits
bind10-changes at lists.isc.org
Mon Jun 25 19:28:23 UTC 2012
The branch, master has been updated
via dc2f6aabc9b1f28136e4513f46eb43c235bf505e (commit)
via cd2f58725f050e19cca4acc69d3388a1e4fda2f3 (commit)
via 3dea78e6159c63d47ec887fa70c056753f84c41d (commit)
from 5c8c3e67e2c564ce3c2c1392fc665edb8a982df1 (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 dc2f6aabc9b1f28136e4513f46eb43c235bf505e
Merge: cd2f587 5c8c3e6
Author: Jeremy C. Reed <jreed at ISC.org>
Date: Mon Jun 25 14:28:22 2012 -0500
[master]Merge branch 'master' of ssh://git.bind10.isc.org/var/bind10/git/bind10
commit cd2f58725f050e19cca4acc69d3388a1e4fda2f3
Author: Jeremy C. Reed <jreed at ISC.org>
Date: Mon Jun 25 14:27:07 2012 -0500
[master] remove mention of network use of msgq
msgq change from network to unix domain sockets over two years ago.
commit 3dea78e6159c63d47ec887fa70c056753f84c41d
Author: Jeremy C. Reed <jreed at ISC.org>
Date: Mon Jun 25 13:33:26 2012 -0500
[master] various edits in the boss startup chapter
clarify about sockcreator
merge some paragraphs and slight rewording
various grammar fixes (added missing words)
add or change some docbook formatting tags
clarify about process and special components
remove redundant note about same component started multiple times;
and clarify about it.
fix typo
some of this was discussed in jabber, but most was trivial and not
reviewed.
-----------------------------------------------------------------------
Summary of changes:
doc/guide/bind10-guide.xml | 135 ++++++++++++++++++++------------------------
src/bin/msgq/msgq.xml | 8 +--
2 files changed, 63 insertions(+), 80 deletions(-)
-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 1463284..5689b9a 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -808,8 +808,9 @@ as a dependency earlier -->
The <command>b10-cfgmgr</command> daemon is always needed by every
module, if only to send information about themselves somewhere,
but more importantly to ask about their own settings, and
- about other modules. The <command>b10-sockcreator</command> will
- allocate sockets for the rest of the system.
+ about other modules. The <command>b10-sockcreator</command> daemon
+ helps allocate Internet addresses and ports as needed for BIND 10
+ network services.
</para>
<para>
@@ -840,23 +841,22 @@ as a dependency earlier -->
</section>
<section id="bind10.config">
- <title>Configuration of started processes</title>
- <para>
- The processes to be started can be configured, with the exception
- of the <command>b10-sockcreator</command>, <command>b10-msgq</command>
- and <command>b10-cfgmgr</command>.
- </para>
+ <title>Configuration to start processes</title>
<para>
- The configuration is in the Boss/components section. Each element
- represents one component, which is an abstraction of a process
- (currently there's also one component which doesn't represent
- a process).
+ The processes to be used can be configured for
+ <command>bind10</command> to start, with the exception
+ of the required <command>b10-sockcreator</command>,
+ <command>b10-msgq</command> and <command>b10-cfgmgr</command>
+ components.
+ The configuration is in the <varname>Boss/components</varname>
+ section. Each element represents one component, which is
+ an abstraction of a process.
</para>
<para>
- To add a process to the set, let's say the resolver (which not started
- by default), you would do this:
+ To add a process to the set, let's say the resolver (which
+ is not started by default), you would do this:
<screen>> <userinput>config add Boss/components b10-resolver</userinput>
> <userinput>config set Boss/components/b10-resolver/special resolver</userinput>
> <userinput>config set Boss/components/b10-resolver/kind needed</userinput>
@@ -864,17 +864,21 @@ as a dependency earlier -->
> <userinput>config commit</userinput></screen></para>
<para>
- Now, what it means. We add an entry called b10-resolver. It is both a
- name used to reference this component in the configuration and the
- name of the process to start. Then we set some parameters on how to
- start it.
+ Now, what it means. We add an entry called
+ <quote>b10-resolver</quote>. It is both a name used to
+ reference this component in the configuration and the name
+ of the process to start. Then we set some parameters on
+ how to start it.
</para>
<para>
- The special one is for components that need some kind of special care
- during startup or shutdown. Unless specified, the component is started
- in usual way. This is the list of components that need to be started
- in a special way, with the value of special used for them:
+ The <varname>special</varname> setting is for components
+ that need some kind of special care during startup or
+ shutdown. Unless specified, the component is started in a
+ usual way. This is the list of components that need to be
+ started in a special way, with the value of special used
+ for them:
+<!-- TODO: this still doesn't explain why they are special -->
<table>
<title>Special startup components</title>
<tgroup cols='3' align='left'>
@@ -883,9 +887,9 @@ as a dependency earlier -->
<colspec colname='description'/>
<thead><row><entry>Component</entry><entry>Special</entry><entry>Description</entry></row></thead>
<tbody>
- <row><entry>b10-auth</entry><entry>auth</entry><entry>Authoritative server</entry></row>
- <row><entry>b10-resolver</entry><entry>resolver</entry><entry>The resolver</entry></row>
- <row><entry>b10-cmdctl</entry><entry>cmdctl</entry><entry>The command control (remote control interface)</entry></row>
+ <row><entry>b10-auth</entry><entry>auth</entry><entry>Authoritative DNS server</entry></row>
+ <row><entry>b10-resolver</entry><entry>resolver</entry><entry>DNS resolver</entry></row>
+ <row><entry>b10-cmdctl</entry><entry>cmdctl</entry><entry>Command control (remote control interface)</entry></row>
<!-- TODO Either add xfrin and xfrout as well or clean up the workarounds in boss before the release -->
</tbody>
</tgroup>
@@ -893,32 +897,34 @@ as a dependency earlier -->
</para>
<para>
- The kind specifies how a failure of the component should
- be handled. If it is set to <quote>dispensable</quote>
- (the default unless you set something else), it will get
- started again if it fails. If it is set to <quote>needed</quote>
- and it fails at startup, the whole <command>bind10</command>
- shuts down and exits with error exit code. But if it fails
- some time later, it is just started again. If you set it
- to <quote>core</quote>, you indicate that the system is
- not usable without the component and if such component
- fails, the system shuts down no matter when the failure
- happened. This is the behaviour of the core components
- (the ones you can't turn off), but you can declare any
- other components as core as well if you wish (but you can
- turn these off, they just can't fail).
+ The <varname>kind</varname> specifies how a failure of the
+ component should be handled. If it is set to
+ <quote>dispensable</quote> (the default unless you set
+ something else), it will get started again if it fails. If
+ it is set to <quote>needed</quote> and it fails at startup,
+ the whole <command>bind10</command> shuts down and exits
+ with an error exit code. But if it fails some time later, it
+ is just started again. If you set it to <quote>core</quote>,
+ you indicate that the system is not usable without the
+ component and if such component fails, the system shuts
+ down no matter when the failure happened. This is the
+ behaviour of the core components (the ones you can't turn
+ off), but you can declare any other components as core as
+ well if you wish (but you can turn these off, they just
+ can't fail).
</para>
<para>
- The priority defines order in which the components should start.
- The ones with higher number are started sooner than the ones with
- lower ones. If you don't set it, 0 (zero) is used as the priority.
- Usually, leaving it at the default is enough.
+ The <varname>priority</varname> defines order in which the
+ components should start. The ones with higher numbers are
+ started sooner than the ones with lower ones. If you don't
+ set it, 0 (zero) is used as the priority. Usually, leaving
+ it at the default is enough.
</para>
<para>
There are other parameters we didn't use in our example.
- One of them is <quote>address</quote>. It is the address
+ One of them is <varname>address</varname>. It is the address
used by the component on the <command>b10-msgq</command>
message bus. The special components already know their
address, but the usual ones don't. The address is by
@@ -934,25 +940,17 @@ address, but the usual ones don't." mean? -->
<!-- TODO: document params when is enabled -->
<para>
- The last one is process. It is the name of the process to be started.
- It defaults to the name of the component if not set, but you can use
- this to override it.
+ The last one is <varname>process</varname>. It is the name
+ of the process to be started. It defaults to the name of
+ the component if not set, but you can use this to override
+ it. (The special components also already know their
+ executable name.)
</para>
<!-- TODO Add parameters when they work, not implemented yet-->
<note>
<para>
- This system allows you to start the same component multiple times
- (by including it in the configuration with different names, but the
- same process setting). However, the rest of the system doesn't expect
- such a situation, so it would probably not do what you want. Such
- support is yet to be implemented.
- </para>
- </note>
-
- <note>
- <para>
The configuration is quite powerful, but that includes
a lot of space for mistakes. You could turn off the
<command>b10-cmdctl</command>, but then you couldn't
@@ -972,7 +970,7 @@ address, but the usual ones don't." mean? -->
</note>
<para>
It is possible to start some components multiple times (currently
- <command>b10-auth</command> and <command>b10-resolzer</command>).
+ <command>b10-auth</command> and <command>b10-resolver</command>).
You might want to do that to gain more performance (each one uses only
single core). Just put multiple entries under different names, like
this, with the same config:
@@ -987,6 +985,9 @@ address, but the usual ones don't." mean? -->
server will keep its own copy of in-memory data and there could be
problems with locking the sqlite database, if used. The configuration
might be changed to something more convenient in future.
+ Other components don't expect such a situation, so it would
+ probably not do what you want. Such support is yet to be
+ implemented.
</para>
</section>
@@ -1011,23 +1012,11 @@ address, but the usual ones don't." mean? -->
<para>
Administrators do not communicate directly with the
<command>b10-msgq</command> daemon.
- By default, BIND 10 uses port 9912 for the
- <command>b10-msgq</command> service.
- It listens on 127.0.0.1.
+ By default, BIND 10 uses a UNIX domain socket file named
+ <filename>/usr/local/var/bind10-devel/msg_socket</filename>
+ for this interprocess communication.
</para>
-<!-- TODO: this is broken, see Trac #111
- <para>
- To select an alternate port for the <command>b10-msgq</command> to
- use, run <command>bind10</command> specifying the option:
- <screen> $ <userinput>bind10 -TODO-msgq-port 9912</userinput></screen>
- </para>
--->
-
-<!-- TODO: upcoming plans:
-Unix domain sockets
--->
-
</chapter>
<chapter id="cfgmgr">
diff --git a/src/bin/msgq/msgq.xml b/src/bin/msgq/msgq.xml
index fd9518d..fed4c27 100644
--- a/src/bin/msgq/msgq.xml
+++ b/src/bin/msgq/msgq.xml
@@ -20,7 +20,7 @@
<refentry>
<refentryinfo>
- <date>August 4, 2010</date>
+ <date>June 25, 2012</date>
</refentryinfo>
<refmeta>
@@ -92,10 +92,6 @@
</para>
<para>
- It listens on 127.0.0.1.
- </para>
-
- <para>
The <command>b10-msgq</command> daemon may be cleanly stopped by
sending the SIGTERM signal to the process.
This shutdown does not notify the subscribers.
@@ -168,5 +164,3 @@
- End:
-->
-
-
More information about the bind10-changes
mailing list