source: server/databases/db.xml@ 58720a7b

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 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 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 58720a7b was 491df213, checked in by Fernando de Oliveira <fernando@…>, 10 years ago

Updates to mercurial-2.9.1, Berkeley DB 6.0.30, libisofs-1.3.6, libburn-1.3.6 and libisoburn-1.3.6.

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