Em 26-07-2015 09:31, Douglas R. Reno escreveu:
> On Jul 26, 2015 5:59 AM, "Tommy Lincoln" <[email protected]> wrote:
>>
>> In the development version of BLFS, I found that the configure line for
> the full OpenLDAP installation (not the client version) has spaces after
> some of the backslashes. If copy/pasting this in to a script to help
> automate installation, this will cause the configure to fail.
>>
>> If copying these lines, be sure to remove any spaces following
> backslashes that are meant to escape the newline - the last three
> backslashes of the configure command are followed by a single space before
> the newline, ending the command prematurely. If you are with BLFS, could
> you please consider correcting these?
>
> I will fix this at my next commit
>
>> This is my first correspondence here so if I've contacted the wrong list
> please let me know.
>>
>> Thank you!
>
> Your welcome! Thanks for reporting this problem!
Doug, I had done this in my local repository, when I saw your post.
There are other lines ended in spaces. I don't know how you do this, but
I configured JuffEd to remove them automatically for any file I edit.
Just made a modification, so could save the file, and produced the
attached diff.
This post is also one more test to check if I am sending well formatted
mails.
Thanks to Tommy and to you.
--
[]s,
Fernando
Index: BLFS/trunk/BOOK/server/other/openldap.xml
===================================================================
--- BLFS/trunk/BOOK/server/other/openldap.xml (revisão 16283)
+++ BLFS/trunk/BOOK/server/other/openldap.xml (cópia de trabalho)
@@ -93,9 +93,9 @@
<xref linkend="icu"/>,
<xref linkend="pth"/>,
<xref linkend="unixodbc"/>,
- <xref linkend="mariadb"/> or
- <xref linkend="postgresql"/> or
- <ulink url="http://www.mysql.com/";>MySQL</ulink>,
+ <xref linkend="mariadb"/> or
+ <xref linkend="postgresql"/> or
+ <ulink url="http://www.mysql.com/";>MySQL</ulink>,
<ulink url="http://www.openslp.org/";>OpenSLP</ulink>, and
<xref linkend="db"/> (not recommended by the developers)
</para>
@@ -135,7 +135,7 @@
<screen role="root"><userinput>make install</userinput></screen>
</note>
-
+
<warning>
<para>If upgrading from a previos installation that used Berkeley DB as
the backend, you will need to dump the database(s) using the
@@ -184,9 +184,9 @@
--enable-backends=mod \
--disable-ndb \
--disable-sql \
- --disable-shell \
- --disable-bdb \
- --disable-hdb \
+ --disable-shell \
+ --disable-bdb \
+ --disable-hdb \
--enable-overlays=mod &&
make depend &&
@@ -194,9 +194,9 @@
<para>
The tests appear to be fragile. Errors may cause the tests to abort
- prior to finishing, apparently due to timing issues. The tests
+ prior to finishing, apparently due to timing issues. The tests
take about 65 minutes and are processor independent.
- To test the results, issue: <command>make test</command>.
+ To test the results, issue: <command>make test</command>.
</para>
<para>
@@ -288,7 +288,7 @@
SLPv2 support. Use it if you have installed
<ulink url="http://www.openslp.org/";>OpenSLP</ulink>.
</para>
-
+
<note>
<para>
You can run <command>./configure --help</command> to see if there
@@ -305,7 +305,7 @@
admin password in PLAIN TEXT. That's why mode 640 and root:ldap ownership
were used. The owner is root, so only root can modify the file, and group is
ldap, so that the group which owns slapd daemon could read but not modify
- the file in case of a security breach.
+ the file in case of a security breach.
</para>
</sect2>
@@ -369,7 +369,7 @@
<listitem>
<para>
The <ulink url="http://www.openldap.org/doc/admin24/";> OpenLDAP 2.4
- Administrator's Guide</ulink> (also installed locally in
+ Administrator's Guide</ulink> (also installed locally in
<filename class='directory'>
/usr/share/doc/openldap-&openldap-version;/guide/admin</filename>).
</para>
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
