source: server/databases/db.xml@ 9d39476e

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
Last change on this file since 9d39476e was 9d39476e, checked in by Bruce Dubbs <bdubbs@…>, 12 years ago

Move Berkely-DB to a place that doesn't require registration (or a web broswer)
to download.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@10222 af4574ff-66df-0310-9fd7-8a98e5e911e0
  • Property mode set to 100644
File size: 14.4 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY db-download-http "&sources-anduin-http;/d/db-&db-version;.tar.gz">
8 <!ENTITY db-download-ftp "&sources-anduin-ftp;/d/db-&db-version;.tar.gz">
9 <!ENTITY db-md5sum "5493fb5f7cc3915887c836b096f18773">
10 <!ENTITY db-size "33 MB">
11 <!ENTITY db-buildsize "264 MB (additional 100 MB to run parallel standard
12 test suite)">
13 <!ENTITY db-time "0.8 SBU (add an additional 145 SBU to run parallel
14 standard test suite)">
15]>
16
17<sect1 id="db" xreflabel="Berkeley DB-&db-version;">
18 <?dbhtml filename="db.html"?>
19
20 <sect1info>
21 <othername>$LastChangedBy$</othername>
22 <date>$Date$</date>
23 </sect1info>
24
25 <title>Berkeley DB-&db-version;</title>
26
27 <indexterm zone="db">
28 <primary sortas="a-Berkeley-DB">Berkeley DB</primary>
29 </indexterm>
30
31 <sect2 role="package">
32 <title>Introduction to Berkeley DB</title>
33
34 <para>
35 The <application>Berkeley DB</application> package contains programs and
36 utilities used by many other applications for database related functions.
37 </para>
38
39 &lfs71_checked;
40
41 <bridgehead renderas="sect3">Package Information</bridgehead>
42 <itemizedlist spacing="compact">
43 <listitem>
44 <para>
45 Download (HTTP): <ulink url="&db-download-http;"/>
46 </para>
47 </listitem>
48 <listitem>
49 <para>
50 Download (FTP): <ulink url="&db-download-ftp;"/>
51 </para>
52 </listitem>
53 <listitem>
54 <para>
55 Download MD5 sum: &db-md5sum;
56 </para>
57 </listitem>
58 <listitem>
59 <para>
60 Download size: &db-size;
61 </para>
62 </listitem>
63 <listitem>
64 <para>
65 Estimated disk space required: &db-buildsize;
66 </para>
67 </listitem>
68 <listitem>
69 <para>
70 Estimated build time: &db-time;
71 </para>
72 </listitem>
73 </itemizedlist>
74
75 <bridgehead renderas="sect3">Berkeley DB Dependencies</bridgehead>
76
77 <bridgehead renderas="sect4">Optional</bridgehead>
78 <para role="optional">
79 <xref linkend="tcl"/>,
80 <xref linkend="icedtea6"/><!-- or <xref linkend="jdk"/>-->, and
81 <xref linkend="sharutils"/> (for the <command>uudecode</command> command)
82 </para>
83
84 <para condition="html" role="usernotes">
85 User Notes: <ulink url="&blfs-wiki;/db"/>
86 </para>
87 </sect2>
88
89 <sect2 role="testing">
90 <title>Testing Berkeley DB</title>
91
92 <para>
93 If you can't wait 12 hours or so you may want to skip ahead to
94 <xref linkend="bdb-installation"/>. The test suite can take a long time
95 and has a few bugs causing a report of <quote>Regression tests
96 failed</quote>. However, running the test suite is a very exhaustive test
97 of your hardware, perhaps pushing your machine harder (especially disk
98 I/O) than it will ever see during production use. Note that you must have
99 <application>Tcl</application> installed to run the test suite.
100 </para>
101
102 <para>
103 Build for the <application>Berkeley DB</application> test by running the
104 following commands:
105 </para>
106
107<screen><userinput>cd build_unix &amp;&amp;
108../dist/configure --prefix=/usr \
109 --enable-test \
110 --enable-tcl \
111 --enable-dbm \
112 --with-tcl=/usr/lib &amp;&amp;
113make</userinput></screen>
114
115 <para>
116 To test the results, start <command>tclsh</command>:
117 </para>
118
119<screen><userinput>tclsh</userinput></screen>
120
121 <para>
122 From the <command>tclsh</command> prompt (<prompt>%&nbsp;</prompt>), run:
123 </para>
124
125<screen><userinput>source ../test/tcl/test.tcl
126run_parallel 5 run_std
127exit</userinput></screen>
128
129 <para>
130 Clean up the source tree with the following command:
131 </para>
132
133<screen><userinput>make realclean &amp;&amp;
134cd ..</userinput></screen>
135
136 <note><para>
137 Test127.f and Repmgr026.c are known to fail.
138 </para></note>
139
140 <para>
141 There are additional testing suites in the
142 <filename class="directory">test/c</filename> and
143 <filename class="directory">test/cxx</filename> directories. See the
144 <filename>README</filename> in each directory for instructions on how to
145 run the tests.
146 </para>
147 </sect2>
148
149 <sect2 role="installation" id="bdb-installation">
150 <title>Installation of Berkeley DB</title>
151
152 <note>
153 <para>
154 If you plan on installing <application>Berkeley DB</application> with
155 Java support, you should check the system for certain versions of
156 <!-- <xref linkend="jdk"/> and--> <xref linkend="gmime"/>. Specifically, if
157 <application>JDK</application>-6 Update X and the
158 <command>uudecode</command> program from the
159 <application>GMime</application> program is on the system, the build
160 will fail (unless you run the modified <command>./configure</command>
161 command shown below). You can run two commands
162 (<command>javac -version</command> and
163 <command>uudecode --version</command>) to determine what versions are
164 installed. You can also download and run a shell script from
165 <ulink url="&files-anduin;/jdk-uudecode-check.sh"/> that will alert you
166 to a non-working condition. If the identified programs exist on the
167 system, you must modify the <command>./configure</command> command as
168 shown below.
169 </para>
170
171<screen><userinput>uudecode="no" ../dist/configure --(use the parameters shown below)</userinput></screen>
172 </note>
173
174 <para>
175 Install <application>Berkeley DB</application> by running the following
176 commands:
177 </para>
178
179<screen><userinput>cd build_unix &amp;&amp;
180../dist/configure --prefix=/usr \
181 --enable-compat185 \
182 --enable-dbm \
183 --disable-static \
184 --enable-cxx &amp;&amp;
185make</userinput></screen>
186
187 <para>
188 Now, as the <systemitem class="username">root</systemitem> user:
189 </para>
190
191<screen role="root"><userinput>make docdir=/usr/share/doc/db-&db-version; install &amp;&amp;
192chown -v -R root:root \
193 /usr/bin/db_* \
194 /usr/include/db{,_185,_cxx}.h \
195 /usr/lib/libdb*.{so,la} \
196 /usr/share/doc/db-&db-version;</userinput></screen>
197 </sect2>
198
199 <sect2 role="commands">
200 <title>Command Explanations</title>
201
202 <para>
203 <command>cd build_unix &amp;&amp; ../dist/configure
204 --prefix=/usr...</command>: This replaces the normal
205 <command>./configure</command> command, as
206 <application>Berkeley DB</application> comes with various build
207 directories for different platforms.
208 </para>
209
210 <para>
211 <parameter>--enable-compat185</parameter>: This switch enables building
212 the DB-1.85 compatibility API.
213 </para>
214
215 <para>
216 <parameter>--enable-cxx</parameter>: This switch enables building C++ API
217 libraries.
218 </para>
219
220 <para>
221 <parameter>--enable-tcl --with-tcl=/usr/lib</parameter>: Enables
222 <application>Tcl</application> support in DB and creates the
223 <filename class="libraryfile">libdb_tcl</filename> libraries.
224 </para>
225
226 <para>
227 <parameter>--enable-dbm</parameter>: Enables legacy interface support
228 needed by some older packages.
229 </para>
230
231 <para>
232 <parameter>--enable-java</parameter>: Enables
233 <application>Java</application> support in DB and creates the
234 <filename class="libraryfile">libdb_java</filename> libraries.
235 </para>
236
237 <para>
238 <command>make docdir=/usr/share/doc/db-&db-version; install</command>:
239 This installs the documentation in the standard location instead of
240 <filename class="directory">/usr/docs</filename>.
241 </para>
242
243 <para>
244 <command>chown -v -R root:root ...</command>:This command changes the
245 ownership of various installed files from the uid:gid of the builder to
246 root:root.
247 </para>
248 </sect2>
249
250 <sect2 role="content">
251 <title>Contents</title>
252
253 <segmentedlist>
254 <segtitle>Installed Programs</segtitle>
255 <segtitle>Installed Libraries</segtitle>
256 <segtitle>Installed Directory</segtitle>
257
258 <seglistitem>
259 <seg>
260 db_archive, db_checkpoint, db_deadlock, db_dump, db_hotbackup,
261 db_load, db_log_verify, db_printlog, db_recover, db_replicate,
262 db_stat, db_tuner, db_upgrade and db_verify.
263 </seg>
264 <seg>
265 libdb.so, libdb_cxx.so, libdb_java.so, libdb_tcl.so and db.jar.
266 </seg>
267 <seg>/usr/share/doc/db-&db-version;</seg>
268 </seglistitem>
269 </segmentedlist>
270
271 <variablelist>
272 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
273 <?dbfo list-presentation="list"?>
274 <?dbhtml list-presentation="table"?>
275
276 <varlistentry id="db_archive">
277 <term><command>db_archive</command></term>
278 <listitem>
279 <para>
280 prints the pathnames of log files that are no longer in use.
281 </para>
282 <indexterm zone="db db_archive">
283 <primary sortas="b-db_archive">db_archive</primary>
284 </indexterm>
285 </listitem>
286 </varlistentry>
287
288 <varlistentry id="db_checkpoint">
289 <term><command>db_checkpoint</command></term>
290 <listitem>
291 <para>
292 is a daemon process used to monitor and checkpoint database logs.
293 </para>
294 <indexterm zone="db db_checkpoint">
295 <primary sortas="b-db_checkpoint">db_checkpoint</primary>
296 </indexterm>
297 </listitem>
298 </varlistentry>
299
300 <varlistentry id="db_deadlock">
301 <term><command>db_deadlock</command></term>
302 <listitem>
303 <para>
304 is used to abort lock requests when deadlocks are detected.
305 </para>
306 <indexterm zone="db db_deadlock">
307 <primary sortas="b-db_deadlock">db_deadlock</primary>
308 </indexterm>
309 </listitem>
310 </varlistentry>
311
312 <varlistentry id="db_dump">
313 <term><command>db_dump</command></term>
314 <listitem>
315 <para>
316 converts database files to a flat file format readable by
317 <command>db_load</command>.
318 </para>
319 <indexterm zone="db db_dump">
320 <primary sortas="b-db_dump">db_dump</primary>
321 </indexterm>
322 </listitem>
323 </varlistentry>
324
325 <varlistentry id="db_hotbackup">
326 <term><command>db_hotbackup</command></term>
327 <listitem>
328 <para>
329 creates "hot backup" or "hot failover" snapshots of Berkeley DB
330 databases.
331 </para>
332 <indexterm zone="db db_hotbackup">
333 <primary sortas="b-db_hotbackup">db_hotbackup</primary>
334 </indexterm>
335 </listitem>
336 </varlistentry>
337
338 <varlistentry id="db_load">
339 <term><command>db_load</command></term>
340 <listitem>
341 <para>
342 is used to create database files from flat files created with
343 <command>db_dump</command>.
344 </para>
345 <indexterm zone="db db_load">
346 <primary sortas="b-db_load">db_load</primary>
347 </indexterm>
348 </listitem>
349 </varlistentry>
350
351 <varlistentry id="db_log_verify">
352 <term><command>db_log_verify</command></term>
353 <listitem>
354 <para>verifies the log files of a database.</para>
355 <indexterm zone="db db_log_verify">
356 <primary sortas="b-db_log_verify">db_log_verify</primary>
357 </indexterm>
358 </listitem>
359 </varlistentry>
360
361 <varlistentry id="db_printlog">
362 <term><command>db_printlog</command></term>
363 <listitem>
364 <para>converts database log files to human readable text.</para>
365 <indexterm zone="db db_printlog">
366 <primary sortas="b-db_printlog">db_printlog</primary>
367 </indexterm>
368 </listitem>
369 </varlistentry>
370
371 <varlistentry id="db_recover">
372 <term><command>db_recover</command></term>
373 <listitem>
374 <para>
375 is used to restore a database to a consistent state after a failure.
376 </para>
377 <indexterm zone="db db_recover">
378 <primary sortas="b-db_recover">db_recover</primary>
379 </indexterm>
380 </listitem>
381 </varlistentry>
382
383 <varlistentry id="db_replicate">
384 <term><command>db_replicate</command></term>
385 <listitem>
386 <para>
387 is a daemon process that provides replication/HA services on a
388 transactional environment.
389 </para>
390 <indexterm zone="db db_replicate">
391 <primary sortas="b-db_replicate">db_replicate</primary>
392 </indexterm>
393 </listitem>
394 </varlistentry>
395
396 <varlistentry id="db_stat">
397 <term><command>db_stat</command></term>
398 <listitem>
399 <para>displays database environment statistics.</para>
400 <indexterm zone="db db_stat">
401 <primary sortas="b-db_stat">db_stat</primary>
402 </indexterm>
403 </listitem>
404 </varlistentry>
405
406 <varlistentry id="db_tuner">
407 <term><command>db_tuner</command></term>
408 <listitem>
409 <para>
410 analyzes the data in a btree database, and suggests a page size that
411 is likely to deliver optimal operation.
412 </para>
413 <indexterm zone="db db_tuner">
414 <primary sortas="b-db_tuner">db_tuner</primary>
415 </indexterm>
416 </listitem>
417 </varlistentry>
418
419 <varlistentry id="db_upgrade">
420 <term><command>db_upgrade</command></term>
421 <listitem>
422 <para>
423 is used to upgrade database files to a newer version of
424 <application>Berkeley DB</application>.
425 </para>
426 <indexterm zone="db db_upgrade">
427 <primary sortas="b-db_upgrade">db_upgrade</primary>
428 </indexterm>
429 </listitem>
430 </varlistentry>
431
432 <varlistentry id="db_verify">
433 <term><command>db_verify</command></term>
434 <listitem>
435 <para>is used to run consistency checks on database files.</para>
436 <indexterm zone="db db_verify">
437 <primary sortas="b-db_verify">db_verify</primary>
438 </indexterm>
439 </listitem>
440 </varlistentry>
441 </variablelist>
442 </sect2>
443</sect1>
Note: See TracBrowser for help on using the repository browser.