From: Jeremy C. Reed Date: Mon, 25 Jun 2012 19:27:07 +0000 (-0500) Subject: [master] remove mention of network use of msgq X-Git-Tag: trac2351_base~117^2~36^2~11 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cd2f58725f050e19cca4acc69d3388a1e4fda2f3;p=thirdparty%2Fkea.git [master] remove mention of network use of msgq msgq change from network to unix domain sockets over two years ago. --- diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index 3a55226d43..5689b9ae6f 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -1012,23 +1012,11 @@ address, but the usual ones don't." mean? --> Administrators do not communicate directly with the b10-msgq daemon. - By default, BIND 10 uses port 9912 for the - b10-msgq service. - It listens on 127.0.0.1. + By default, BIND 10 uses a UNIX domain socket file named + /usr/local/var/bind10-devel/msg_socket + for this interprocess communication. - - - - diff --git a/src/bin/msgq/msgq.xml b/src/bin/msgq/msgq.xml index fd9518d757..fed4c27c06 100644 --- a/src/bin/msgq/msgq.xml +++ b/src/bin/msgq/msgq.xml @@ -20,7 +20,7 @@ - August 4, 2010 + June 25, 2012 @@ -91,10 +91,6 @@ - - It listens on 127.0.0.1. - - The b10-msgq daemon may be cleanly stopped by sending the SIGTERM signal to the process. @@ -168,5 +164,3 @@ - End: --> - -