Changeset 1ea160c0 for server/databases


Ignore:
Timestamp:
04/19/2012 04:33:45 PM (12 years ago)
Author:
Andrew Benton <andy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
40a4d44
Parents:
22ab8c0b
Message:

Berkeley DB-5.3.15

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@9948 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • server/databases/db.xml

    r22ab8c0b r1ea160c0  
    55  %general-entities;
    66
    7   <!ENTITY db-download-http " ">
     7  <!ENTITY db-download-http
     8    "http://download.oracle.com/berkeley-db/db-&db-version;.tar.gz">
    89  <!ENTITY db-download-ftp  "&gentoo-ftp-repo;/db-&db-version;.tar.gz">
    9   <!ENTITY db-md5sum        "88466dd6c13d5d8cddb406be8a1d4d92">
     10  <!ENTITY db-md5sum        "5493fb5f7cc3915887c836b096f18773">
    1011  <!ENTITY db-size          "33 MB">
    11   <!ENTITY db-buildsize     "181 MB (additional 100 MB to run parallel standard test suite)">
    12   <!ENTITY db-time          "1.4 SBU (builds all bindings, add an additional 145 SBU to run parallel standard test suite)">
     12  <!ENTITY db-buildsize     "264 MB (additional 100 MB to run parallel standard
     13    test suite)">
     14  <!ENTITY db-time          "0.8 SBU (add an additional 145 SBU to run parallel
     15    standard test suite)">
    1316]>
    1417
    … …  
    3033    <title>Introduction to Berkeley DB</title>
    3134
    32     <para>The <application>Berkeley DB</application> package contains programs
    33     and utilities used by many other applications for database related
    34     functions.</para>
     35    <para>
     36      The <application>Berkeley DB</application> package contains programs and
     37      utilities used by many other applications for database related functions.
     38    </para>
    3539
    3640    &lfs71_checked;
    … …  
    3943    <itemizedlist spacing="compact">
    4044      <listitem>
    41         <para>Download (HTTP): <ulink url="&db-download-http;"/></para>
    42       </listitem>
    43       <listitem>
    44         <para>Download (FTP): <ulink url="&db-download-ftp;"/></para>
    45       </listitem>
    46       <listitem>
    47         <para>Download MD5 sum: &db-md5sum;</para>
    48       </listitem>
    49       <listitem>
    50         <para>Download size: &db-size;</para>
    51       </listitem>
    52       <listitem>
    53         <para>Estimated disk space required: &db-buildsize;</para>
    54       </listitem>
    55       <listitem>
    56         <para>Estimated build time: &db-time;</para>
     45        <para>
     46          Download (HTTP): <ulink url="&db-download-http;"/>
     47        </para>
     48      </listitem>
     49      <listitem>
     50        <para>
     51          Download (FTP): <ulink url="&db-download-ftp;"/>
     52        </para>
     53      </listitem>
     54      <listitem>
     55        <para>
     56          Download MD5 sum: &db-md5sum;
     57        </para>
     58      </listitem>
     59      <listitem>
     60        <para>
     61          Download size: &db-size;
     62        </para>
     63      </listitem>
     64      <listitem>
     65        <para>
     66          Estimated disk space required: &db-buildsize;
     67        </para>
     68      </listitem>
     69      <listitem>
     70        <para>
     71          Estimated build time: &db-time;
     72        </para>
    5773      </listitem>
    5874    </itemizedlist>
    … …  
    6480      <xref linkend="tcl"/>,
    6581      <xref linkend="icedtea6"/> or <xref linkend="jdk"/>, and
    66       <xref linkend='sharutils'/> (for the <command>uudecode</command> command)
    67     </para>
    68 
    69     <para condition="html" role="usernotes">User Notes:
    70     <ulink url="&blfs-wiki;/db"/></para>
    71 
     82      <xref linkend="sharutils"/> (for the <command>uudecode</command> command)
     83    </para>
     84
     85    <para condition="html" role="usernotes">
     86      User Notes: <ulink url="&blfs-wiki;/db"/>
     87    </para>
    7288  </sect2>
    7389
    … …  
    7591    <title>Testing Berkeley DB</title>
    7692
    77     <para>You may want to skip ahead to <xref linkend="bdb-installation"/>. The
    78     test suite can take up to 150 SBUs and has a few bugs causing a report of
    79     <quote>Regression tests failed</quote>. However, running the test suite is
    80     a very exhaustive test of your hardware, perhaps pushing your machine
    81     harder (especially disk I/O) than it will ever see during production use.
    82     Note that you must have <application>Tcl</application> installed to run the
    83     test suite.</para>
    84 
    85     <para>Build for the <application>Berkeley DB</application> test by running
    86     the following commands:</para>
    87 
    88 <screen><userinput>cd build_unix &amp;&amp;
    89 ../dist/configure --prefix=/usr \
    90                   --enable-test \
    91                   --enable-tcl  \
    92                   --enable-dbm  \
     93    <para>
     94      If you can't wait 12 hours or so you may want to skip ahead to
     95      <xref linkend="bdb-installation"/>. The test suite can take a long time
     96      and has a few bugs causing a report of <quote>Regression tests
     97      failed</quote>. However, running the test suite is a very exhaustive test
     98      of your hardware, perhaps pushing your machine harder (especially disk
     99      I/O) than it will ever see during production use. Note that you must have
     100      <application>Tcl</application> installed to run the test suite.
     101    </para>
     102
     103    <para>
     104      Build for the <application>Berkeley DB</application> test by running the
     105      following commands:
     106    </para>
     107
     108<screen><userinput>cd build_unix                         &amp;&amp;
     109../dist/configure --prefix=/usr       \
     110                  --enable-test       \
     111                  --enable-tcl        \
     112                  --enable-dbm        \
    93113                  --with-tcl=/usr/lib &amp;&amp;
    94114make</userinput></screen>
    95115
    96     <para>To test the results, start <command>tclsh</command>:</para>
     116    <para>
     117      To test the results, start <command>tclsh</command>:
     118    </para>
    97119
    98120<screen><userinput>tclsh</userinput></screen>
    99121
    100     <para>From the <command>tclsh</command> prompt (<prompt>%&nbsp;</prompt>),
    101     run:</para>
     122    <para>
     123      From the <command>tclsh</command> prompt (<prompt>%&nbsp;</prompt>), run:
     124    </para>
    102125
    103126<screen><userinput>source ../test/tcl/test.tcl
    … …  
    105128exit</userinput></screen>
    106129
    107     <para>Clean up the source tree with the following command:</para>
     130    <para>
     131      Clean up the source tree with the following command:
     132    </para>
    108133
    109134<screen><userinput>make realclean &amp;&amp;
    110135cd ..</userinput></screen>
    111136
    112     <note><para>Test127.f and Repmgr026.c are known to fail.</para></note>
    113 
    114     <para>There are additional testing suites in the <filename
    115     class='directory'>test/c</filename> and <filename
    116     class='directory'>test/cxx</filename> directories.  See the
    117     <filename>README</filename> in each directory for instructions on how to
    118     run the tests.</para>
    119 
     137    <note><para>
     138      Test127.f and Repmgr026.c are known to fail.
     139    </para></note>
     140
     141    <para>
     142      There are additional testing suites in the
     143      <filename class="directory">test/c</filename> and
     144      <filename class="directory">test/cxx</filename> directories.  See the
     145      <filename>README</filename> in each directory for instructions on how to
     146      run the tests.
     147    </para>
    120148  </sect2>
    121149
    … …  
    124152
    125153    <note>
    126       <para>If you plan on installing <application>Berkeley DB</application>
    127       with Java support, you should check the system for certain versions
    128       of <xref linkend="jdk"/> and <xref linkend="gmime"/>. Specifically, if
    129       <application>JDK</application>-6 Update X and the
    130       <command>uudecode</command> program from the
    131       <application>GMime</application> program is on the system, the build will
    132       fail (unless you run the modified <command>./configure</command> command
    133       shown below). You can run two commands (<command>javac -version</command>
    134       and <command>uudecode --version</command>) to determine what versions are
    135       installed. You can also download and run a shell script from
    136       <ulink url="&files-anduin;/jdk-uudecode-check.sh"/> that will alert
    137       you to a non-working condition. If the identified programs exist on the
    138       system, you must modify the
    139       <command>./configure</command> command as shown below.</para>
     154      <para>
     155        If you plan on installing <application>Berkeley DB</application> with
     156        Java support, you should check the system for certain versions of
     157        <xref linkend="jdk"/> and <xref linkend="gmime"/>. Specifically, if
     158        <application>JDK</application>-6 Update X and the
     159        <command>uudecode</command> program from the
     160        <application>GMime</application> program is on the system, the build
     161        will fail (unless you run the modified <command>./configure</command>
     162        command shown below). You can run two commands
     163        (<command>javac -version</command> and
     164        <command>uudecode --version</command>) to determine what versions are
     165        installed. You can also download and run a shell script from
     166        <ulink url="&files-anduin;/jdk-uudecode-check.sh"/> that will alert you
     167        to a non-working condition. If the identified programs exist on the
     168        system, you must modify the <command>./configure</command> command as
     169        shown below.
     170      </para>
    140171
    141172<screen><userinput>uudecode="no" ../dist/configure --(use the parameters shown below)</userinput></screen>
    142173    </note>
    143174
    144     <para>Install <application>Berkeley DB</application> by running the
    145     following commands:</para>
    146 
    147 <screen><userinput>cd build_unix &amp;&amp;
    148 ../dist/configure --prefix=/usr \
     175    <para>
     176      Install <application>Berkeley DB</application> by running the following
     177      commands:
     178    </para>
     179
     180<screen><userinput>cd build_unix                        &amp;&amp;
     181../dist/configure --prefix=/usr      \
    149182                  --enable-compat185 \
    150                   --enable-dbm  \
    151                   --enable-cxx &amp;&amp;
     183                  --enable-dbm       \
     184                  --disable-static   \
     185                  --enable-cxx       &amp;&amp;
    152186make</userinput></screen>
    153187
    154     <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     188    <para>
     189      Now, as the <systemitem class="username">root</systemitem> user:
     190    </para>
    155191
    156192<screen role="root"><userinput>make docdir=/usr/share/doc/db-&db-version; install &amp;&amp;
    157 chown -v -R root:root \
    158       /usr/bin/db_* \
    159       /usr/include/db{,_185,_cxx}.h \
    160       /usr/lib/libdb*.{so,a,la} \
     193chown -v -R root:root                        \
     194      /usr/bin/db_*                          \
     195      /usr/include/db{,_185,_cxx}.h          \
     196      /usr/lib/libdb*.{so,la}                \
    161197      /usr/share/doc/db-&db-version;</userinput></screen>
    162 
    163198  </sect2>
    164199
    … …  
    166201    <title>Command Explanations</title>
    167202
    168     <para><command>cd build_unix &amp;&amp;
    169     ../dist/configure --prefix=/usr...</command>:
    170     This replaces the normal <command>./configure</command> command, as
    171     <application>Berkeley DB</application> comes with various
    172     build directories for different platforms.</para>
    173 
    174     <para><parameter>--enable-compat185</parameter>: This switch enables
    175     building the DB-1.85 compatibility API.</para>
    176 
    177     <para><parameter>--enable-cxx</parameter>: This switch enables building
    178     C++ API libraries.</para>
    179 
    180     <para><parameter>--enable-tcl --with-tcl=/usr/lib</parameter>:
    181     Enables <application>Tcl</application> support in DB and creates the
    182     <filename class="libraryfile">libdb_tcl</filename> libraries.</para>
    183 
    184     <para><parameter>--enable-dbm</parameter>: Enables legacy interface support
    185     support needed by some older packages.</para>
    186 
    187     <para><parameter>--enable-java</parameter>: Enables
    188     <application>Java</application> support in DB and creates the
    189     <filename class='libraryfile'>libdb_java</filename> libraries.</para>
    190 
    191     <para><command>make docdir=/usr/share/doc/db-&db-version;
    192     install</command>: This installs the documentation in
    193     the standard location instead of
    194     <filename class='directory'>/usr/docs</filename>.</para>
    195 
    196     <para><command>chown -v -R root:root ...</command>:This command changes
    197     the ownership of various installed files from the uid:gid of the
    198     builder to root:root.</para>
    199 
     203    <para>
     204      <command>cd build_unix &amp;&amp; ../dist/configure
     205      --prefix=/usr...</command>: This replaces the normal
     206      <command>./configure</command> command, as
     207      <application>Berkeley DB</application> comes with various build
     208      directories for different platforms.
     209    </para>
     210
     211    <para>
     212      <parameter>--enable-compat185</parameter>: This switch enables building
     213      the DB-1.85 compatibility API.
     214    </para>
     215
     216    <para>
     217      <parameter>--enable-cxx</parameter>: This switch enables building C++ API
     218      libraries.
     219    </para>
     220
     221    <para>
     222      <parameter>--enable-tcl --with-tcl=/usr/lib</parameter>: Enables
     223      <application>Tcl</application> support in DB and creates the
     224      <filename class="libraryfile">libdb_tcl</filename> libraries.
     225    </para>
     226
     227    <para>
     228      <parameter>--enable-dbm</parameter>: Enables legacy interface support
     229      needed by some older packages.
     230    </para>
     231
     232    <para>
     233      <parameter>--enable-java</parameter>: Enables
     234      <application>Java</application> support in DB and creates the
     235      <filename class="libraryfile">libdb_java</filename> libraries.
     236    </para>
     237
     238    <para>
     239      <command>make docdir=/usr/share/doc/db-&db-version; install</command>:
     240      This installs the documentation in the standard location instead of
     241      <filename class="directory">/usr/docs</filename>.
     242    </para>
     243
     244    <para>
     245      <command>chown -v -R root:root ...</command>:This command changes the
     246      ownership of various installed files from the uid:gid of the builder to
     247      root:root.
     248    </para>
    200249  </sect2>
    201250
    … …  
    209258
    210259      <seglistitem>
    211         <seg>db_archive, db_checkpoint, db_deadlock, db_dump,
    212         db_load, db_printlog, db_recover, db_stat, db_upgrade, db_verify</seg>
    213         <seg>libdb.{so,a}, libdb_cxx.{so,a}, libdb_java.{so,a},
    214         libdb_tcl.{so,a} and db.jar</seg>
     260        <seg>
     261          db_archive, db_checkpoint, db_deadlock, db_dump, db_hotbackup,
     262          db_load, db_log_verify, db_printlog, db_recover, db_replicate,
     263          db_stat, db_tuner, db_upgrade and db_verify.
     264        </seg>
     265        <seg>
     266          libdb.so, libdb_cxx.so, libdb_java.so, libdb_tcl.so and db.jar.
     267        </seg>
    215268        <seg>/usr/share/doc/db-&db-version;</seg>
    216269      </seglistitem>
    … …  
    225278        <term><command>db_archive</command></term>
    226279        <listitem>
    227           <para>prints the pathnames of log files that are no longer in
    228           use.</para>
     280          <para>
     281            prints the pathnames of log files that are no longer in use.
     282          </para>
    229283          <indexterm zone="db db_archive">
    230284            <primary sortas="b-db_archive">db_archive</primary>
    … …  
    236290        <term><command>db_checkpoint</command></term>
    237291        <listitem>
    238           <para>is a daemon process used to monitor and checkpoint database
    239           logs.</para>
     292          <para>
     293            is a daemon process used to monitor and checkpoint database logs.
     294          </para>
    240295          <indexterm zone="db db_checkpoint">
    241296            <primary sortas="b-db_checkpoint">db_checkpoint</primary>
    … …  
    247302        <term><command>db_deadlock</command></term>
    248303        <listitem>
    249           <para>is used to abort lock requests when deadlocks are
    250           detected.</para>
     304          <para>
     305            is used to abort lock requests when deadlocks are detected.
     306          </para>
    251307          <indexterm zone="db db_deadlock">
    252308            <primary sortas="b-db_deadlock">db_deadlock</primary>
    … …  
    258314        <term><command>db_dump</command></term>
    259315        <listitem>
    260           <para>converts database files to a flat file format readable by
    261           <command>db_load</command>.</para>
     316          <para>
     317            converts database files to a flat file format readable by
     318            <command>db_load</command>.
     319          </para>
    262320          <indexterm zone="db db_dump">
    263321            <primary sortas="b-db_dump">db_dump</primary>
    … …  
    266324      </varlistentry>
    267325
     326      <varlistentry id="db_hotbackup">
     327        <term><command>db_hotbackup</command></term>
     328        <listitem>
     329          <para>
     330            creates "hot backup" or "hot failover" snapshots of Berkeley DB
     331            databases.
     332          </para>
     333          <indexterm zone="db db_hotbackup">
     334            <primary sortas="b-db_hotbackup">db_hotbackup</primary>
     335          </indexterm>
     336        </listitem>
     337      </varlistentry>
     338
    268339      <varlistentry id="db_load">
    269340        <term><command>db_load</command></term>
    270341        <listitem>
    271           <para>is used to create database files from flat files created with
    272           <command>db_dump</command>.</para>
     342          <para>
     343            is used to create database files from flat files created with
     344            <command>db_dump</command>.
     345          </para>
    273346          <indexterm zone="db db_load">
    274347            <primary sortas="b-db_load">db_load</primary>
     348          </indexterm>
     349        </listitem>
     350      </varlistentry>
     351
     352      <varlistentry id="db_log_verify">
     353        <term><command>db_log_verify</command></term>
     354        <listitem>
     355          <para>verifies the log files of a database.</para>
     356          <indexterm zone="db db_log_verify">
     357            <primary sortas="b-db_log_verify">db_log_verify</primary>
    275358          </indexterm>
    276359        </listitem>
    … …  
    290373        <term><command>db_recover</command></term>
    291374        <listitem>
    292           <para>is used to restore a database to a consistent state after a
    293           failure.</para>
     375          <para>
     376            is used to restore a database to a consistent state after a failure.
     377          </para>
    294378          <indexterm zone="db db_recover">
    295379            <primary sortas="b-db_recover">db_recover</primary>
     380          </indexterm>
     381        </listitem>
     382      </varlistentry>
     383
     384      <varlistentry id="db_replicate">
     385        <term><command>db_replicate</command></term>
     386        <listitem>
     387          <para>
     388            is a daemon process that provides replication/HA services on a
     389            transactional environment.
     390          </para>
     391          <indexterm zone="db db_replicate">
     392            <primary sortas="b-db_replicate">db_replicate</primary>
    296393          </indexterm>
    297394        </listitem>
    … …  
    308405      </varlistentry>
    309406
     407      <varlistentry id="db_tuner">
     408        <term><command>db_tuner</command></term>
     409        <listitem>
     410          <para>
     411            analyzes the data in a btree database, and suggests a page size that
     412            is likely to deliver optimal operation.
     413          </para>
     414          <indexterm zone="db db_tuner">
     415            <primary sortas="b-db_tuner">db_tuner</primary>
     416          </indexterm>
     417        </listitem>
     418      </varlistentry>
     419
    310420      <varlistentry id="db_upgrade">
    311421        <term><command>db_upgrade</command></term>
    312422        <listitem>
    313           <para>is used to upgrade database files to a newer version of
    314           <application>Berkeley DB</application>.</para>
     423          <para>
     424            is used to upgrade database files to a newer version of
     425            <application>Berkeley DB</application>.
     426          </para>
    315427          <indexterm zone="db db_upgrade">
    316428            <primary sortas="b-db_upgrade">db_upgrade</primary>
    … …  
    328440        </listitem>
    329441      </varlistentry>
    330 
    331442    </variablelist>
    332 
    333443  </sect2>
    334 
    335444</sect1>
Note: See TracChangeset for help on using the changeset viewer.