]> git.ipfire.org Git - thirdparty/kea.git/commitdiff
[3513] improved the config.report texts trac3513_beforeW
authorFrancis Dupont <fdupont@isc.org>
Tue, 9 Jun 2015 08:13:37 +0000 (10:13 +0200)
committerFrancis Dupont <fdupont@isc.org>
Tue, 9 Jun 2015 08:13:37 +0000 (10:13 +0200)
doc/guide/ddns.xml
doc/guide/dhcp4-srv.xml
doc/guide/dhcp6-srv.xml

index a2a5fb948e9f947020726994b80833e65219b31b..319c9c2370c22a39df60b0d6d426a65ca7b3d7e1 100644 (file)
       </itemizedlist>
 
       <para>
-      As for any Kea executable binary, the <filename>config.report</filename>
-      file produced by <userinput>./configure</userinput> is embbeded.
-      The command extracting it is:
+            All of the executable binaries in Kea contain an embedded
+            copy of the <filename>config.report</filename>
+            file produced by <userinput>./configure</userinput>.
+            The following command may be used to extract this information.
+            The binary <userinput>path</userinput>, may be found in the
+            install directory or in the <filename>.libs</filename>
+            subdirectory in the source treee. For example
+            <filename>kea/src/bin/d2/.libs/kea-dhcp-ddns</filename>.
 <screen>
 strings <userinput>path</userinput>/kea-dhcp-ddns | sed -n 's/;;;; //p'
 </screen>
-      Beware the <userinput>path</userinput> to use for a binary
-      in the build tree finishes by <filename>.libs</filename>.
       </para>
 
       <para>
index b0bcc42d985ebe337d893e4950ed757559baa1fd..9613138b6990639b86bd580e7d7945a2bba4cb24 100644 (file)
       </itemizedlist>
 
       <para>
-            As for any Kea executable binary, the <filename>config.report</filename>
-            file produced by <userinput>./configure</userinput> is embbeded.
-            The command extracting it is:
+            All of the executable binaries in Kea contain an embedded
+            copy of the <filename>config.report</filename>
+            file produced by <userinput>./configure</userinput>.
+            The following command may be used to extract this information.
+            The binary <userinput>path</userinput>, may be found in the
+            install directory or in the <filename>.libs</filename>
+            subdirectory in the source treee. For example
+            <filename>kea/src/bin/dhcp4/.libs/kea-dhcp4</filename>.
+
 <screen>
 strings <userinput>path</userinput>/kea-dhcp4 | sed -n 's/;;;; //p'
 </screen>
-            Beware the <userinput>path</userinput> to use for a binary
-            in the build tree finishes by <filename>.libs</filename>.
       </para>
 
       <para>
index d10e99c39db230b3839f4d51389235597c338b55..5c7f211407f0b0393aa6e103d01628b7e49647e3 100644 (file)
       </itemizedlist>
 
       <para>
-            As for any Kea executable binary, the <filename>config.report</filename>
-            file produced by <userinput>./configure</userinput> is embbeded.
-            The command extracting it is:
+            All of the executable binaries in Kea contain an embedded
+            copy of the <filename>config.report</filename>
+            file produced by <userinput>./configure</userinput>.
+            The following command may be used to extract this information.
+            The binary <userinput>path</userinput>, may be found in the
+            install directory or in the <filename>.libs</filename>
+            subdirectory in the source treee. For example
+            <filename>kea/src/bin/dhcp6/.libs/kea-dhcp6</filename>.
+
 <screen>
 strings <userinput>path</userinput>/kea-dhcp6 | sed -n 's/;;;; //p'
 </screen>
-            Beware the <userinput>path</userinput> to use for a binary
-            in the build tree finishes by <filename>.libs</filename>.
       </para>
 
       <para>