From: Greg Hudson Date: Tue, 26 Jun 2012 16:28:26 +0000 (-0400) Subject: Clarify module names in host_config X-Git-Tag: krb5-1.11-alpha1~483 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b192edd9e9157741521bb08088d26f6a5276a4f9;p=thirdparty%2Fkrb5.git Clarify module names in host_config Explicitly state that a module name will usually be the same as the shared object name, but doesn't have to be. --- diff --git a/doc/rst_source/krb_admins/host_config.rst b/doc/rst_source/krb_admins/host_config.rst index 2adc702596..e5ef06bf1f 100644 --- a/doc/rst_source/krb_admins/host_config.rst +++ b/doc/rst_source/krb_admins/host_config.rst @@ -23,8 +23,11 @@ A plugin module takes the form of a Unix shared object installed a third-party plugin module and want to register it, you do so using the **module** relation in the appropriate subsection of the [plugins] section. The value for **module** must give the module name -and the path to the module, separated by a colon. For example, to -register a client preauthentication module named ``otp`` installed at +and the path to the module, separated by a colon. The module name +will often be the same as the shared object's name, but in unusual +cases (such as a shared object which implements multiple modules for +the same interface) it might not be. For example, to register a +client preauthentication module named ``otp`` installed at ``/path/to/otp.so``, you could write:: [plugins]