[27062] in CVS-changelog-for-Kerberos-V5
krb5 commit: Correct docs re: kpropd usage w/ iprop
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Oct 5 14:37:20 2012
Date: Fri, 5 Oct 2012 14:37:15 -0400
From: Greg Hudson <ghudson@mit.edu>
Message-Id: <201210051837.q95IbFEi018081@drugstore.mit.edu>
To: cvs-krb5@mit.edu
Reply-To: krbdev@mit.edu
Content-Type: multipart/mixed; boundary="===============1527665353=="
Errors-To: cvs-krb5-bounces@mit.edu
--===============1527665353==
https://github.com/krb5/krb5/commit/4a50490ed48050e7a6d061553a6b610dc979aa2b
commit 4a50490ed48050e7a6d061553a6b610dc979aa2b
Author: Nicolas Williams <nico@cryptonector.com>
Date: Mon Sep 24 10:24:54 2012 -0500
Correct docs re: kpropd usage w/ iprop
ticket: 7379
.../krb_admins/admin_commands/kpropd.rst | 11 ++++++-----
doc/rst_source/krb_admins/install_kdc.rst | 4 ++--
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/doc/rst_source/krb_admins/admin_commands/kpropd.rst b/doc/rst_source/krb_admins/admin_commands/kpropd.rst
index 555ec3c..8f048b5 100644
--- a/doc/rst_source/krb_admins/admin_commands/kpropd.rst
+++ b/doc/rst_source/krb_admins/admin_commands/kpropd.rst
@@ -32,16 +32,17 @@ Kerberos server to use :ref:`kprop(8)` to propagate its database to
the slave servers. Upon a successful download of the KDC database
file, the slave Kerberos server will have an up-to-date KDC database.
-Normally, kpropd is invoked out of inetd(8). This is done by adding
-a line to the ``/etc/inetd.conf`` file which looks like this:
+Where incremental propagation is not used, kpropd is commonly invoked
+out of inetd(8) as a nowait service. This is done by adding a line to
+the ``/etc/inetd.conf`` file which looks like this:
::
kprop stream tcp nowait root /usr/local/sbin/kpropd kpropd
-kpropd can also run as a standalone daemon by specifying the **-S**
-option. This is done for debugging purposes, or if for some reason
-the system administrator just doesn't want to run it out of inetd(8).
+kpropd can also run as a standalone daemon. This is required for
+incremental propagation. But this is also useful for debugging
+purposes.
Incremental propagation may be enabled with the **iprop_enable**
variable in :ref:`kdc.conf(5)`. If incremental propagation is
diff --git a/doc/rst_source/krb_admins/install_kdc.rst b/doc/rst_source/krb_admins/install_kdc.rst
index c43e416..3d0d0f1 100644
--- a/doc/rst_source/krb_admins/install_kdc.rst
+++ b/doc/rst_source/krb_admins/install_kdc.rst
@@ -378,8 +378,8 @@ used)::
Restart inetd daemon.
-Alternatively, start :ref:`kpropd(8)` as a stand-alone daemon with
-``kpropd -S``.
+Alternatively, start :ref:`kpropd(8)` as a stand-alone daemon. This is
+required when incremental propagation is enabled.
Now that the slave KDC is able to accept database propagation, you’ll
need to propagate the database from the master server.
--===============1527665353==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
cvs-krb5 mailing list
cvs-krb5@mit.edu
https://mailman.mit.edu/mailman/listinfo/cvs-krb5
--===============1527665353==--
