source: server/databases/db.xml@ aed3e6ec

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since aed3e6ec was aed3e6ec, checked in by Bruce Dubbs <bdubbs@…>, 9 years ago

Partial update of KDE to 14.12.2
Lots of tagging

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@15561 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 "bfea581b42dc0fc247041e7d48cfd7fb">
11 <!ENTITY db-size "36 MB">
12 <!ENTITY db-buildsize "300 MB with Java and Tcl supports">
13 <!ENTITY db-time "0.8 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 &lfs77_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;
191
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 <option>--enable-compat185</option>: This switch enables building
212 the DB-1.85 compatibility API.
213 </para>
214
215 <para>
216 <option>--enable-cxx</option>: This switch enables building C++ API
217 libraries.
218 </para>
219
220 <para>
221 <option>--enable-dbm</option>: Enables legacy interface support
222 needed by some older packages.
223 </para>
224
225 <para>
226 <command>make docdir=/usr/share/doc/db-&db-version; install</command>:
227 This installs the documentation in the standard location instead of
228 <filename class="directory">/usr/docs</filename>.
229 </para>
230
231 <para>
232 <command>chown -v -R root:root ...</command>:This command changes the
233 ownership of various installed files from the uid:gid of the builder to
234 root:root.
235 </para>
236
237 <para>
238 <option>--enable-tcl --with-tcl=/usr/lib</option>: Enables
239 <application>Tcl</application> support in DB and creates the
240 <filename class="libraryfile">libdb_tcl</filename> libraries.
241 </para>
242
243 <para>
244 <option>--enable-java</option>: Enables
245 <application>Java</application> support in DB and creates the
246 <filename class="libraryfile">libdb_java</filename> libraries.
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,
261 db_checkpoint,
262 db_deadlock,
263 db_dump,
264 db_hotbackup,
265 db_load,
266 db_log_verify,
267 db_printlog,
268 db_recover,
269 db_replicate,
270 db_stat,
271 db_tuner,
272 db_upgrade, and
273 db_verify.
274 </seg>
275 <seg>
276 libdb.so,
277 libdb_cxx.so,
278 libdb_java.so, and
279 libdb_tcl.so
280 </seg>
281 <seg>/usr/share/doc/db-&db-version;</seg>
282 </seglistitem>
283 </segmentedlist>
284
285 <variablelist>
286 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
287 <?dbfo list-presentation="list"?>
288 <?dbhtml list-presentation="table"?>
289
290 <varlistentry id="db_archive">
291 <term><command>db_archive</command></term>
292 <listitem>
293 <para>
294 prints the pathnames of log files that are no longer in use.
295 </para>
296 <indexterm zone="db db_archive">
297 <primary sortas="b-db_archive">db_archive</primary>
298 </indexterm>
299 </listitem>
300 </varlistentry>
301
302 <varlistentry id="db_checkpoint">
303 <term><command>db_checkpoint</command></term>
304 <listitem>
305 <para>
306 is a daemon process used to monitor and checkpoint database logs.
307 </para>
308 <indexterm zone="db db_checkpoint">
309 <primary sortas="b-db_checkpoint">db_checkpoint</primary>
310 </indexterm>
311 </listitem>
312 </varlistentry>
313
314 <varlistentry id="db_deadlock">
315 <term><command>db_deadlock</command></term>
316 <listitem>
317 <para>
318 is used to abort lock requests when deadlocks are detected.
319 </para>
320 <indexterm zone="db db_deadlock">
321 <primary sortas="b-db_deadlock">db_deadlock</primary>
322 </indexterm>
323 </listitem>
324 </varlistentry>
325
326 <varlistentry id="db_dump">
327 <term><command>db_dump</command></term>
328 <listitem>
329 <para>
330 converts database files to a flat file format readable by
331 <command>db_load</command>.
332 </para>
333 <indexterm zone="db db_dump">
334 <primary sortas="b-db_dump">db_dump</primary>
335 </indexterm>
336 </listitem>
337 </varlistentry>
338
339 <varlistentry id="db_hotbackup">
340 <term><command>db_hotbackup</command></term>
341 <listitem>
342 <para>
343 creates "hot backup" or "hot failover" snapshots of Berkeley DB
344 databases.
345 </para>
346 <indexterm zone="db db_hotbackup">
347 <primary sortas="b-db_hotbackup">db_hotbackup</primary>
348 </indexterm>
349 </listitem>
350 </varlistentry>
351
352 <varlistentry id="db_load">
353 <term><command>db_load</command></term>
354 <listitem>
355 <para>
356 is used to create database files from flat files created with
357 <command>db_dump</command>.
358 </para>
359 <indexterm zone="db db_load">
360 <primary sortas="b-db_load">db_load</primary>
361 </indexterm>
362 </listitem>
363 </varlistentry>
364
365 <varlistentry id="db_log_verify">
366 <term><command>db_log_verify</command></term>
367 <listitem>
368 <para>verifies the log files of a database.</para>
369 <indexterm zone="db db_log_verify">
370 <primary sortas="b-db_log_verify">db_log_verify</primary>
371 </indexterm>
372 </listitem>
373 </varlistentry>
374
375 <varlistentry id="db_printlog">
376 <term><command>db_printlog</command></term>
377 <listitem>
378 <para>converts database log files to human readable text.</para>
379 <indexterm zone="db db_printlog">
380 <primary sortas="b-db_printlog">db_printlog</primary>
381 </indexterm>
382 </listitem>
383 </varlistentry>
384
385 <varlistentry id="db_recover">
386 <term><command>db_recover</command></term>
387 <listitem>
388 <para>
389 is used to restore a database to a consistent state after a failure.
390 </para>
391 <indexterm zone="db db_recover">
392 <primary sortas="b-db_recover">db_recover</primary>
393 </indexterm>
394 </listitem>
395 </varlistentry>
396
397 <varlistentry id="db_replicate">
398 <term><command>db_replicate</command></term>
399 <listitem>
400 <para>
401 is a daemon process that provides replication/HA services on a
402 transactional environment.
403 </para>
404 <indexterm zone="db db_replicate">
405 <primary sortas="b-db_replicate">db_replicate</primary>
406 </indexterm>
407 </listitem>
408 </varlistentry>
409
410 <varlistentry id="db_stat">
411 <term><command>db_stat</command></term>
412 <listitem>
413 <para>displays database environment statistics.</para>
414 <indexterm zone="db db_stat">
415 <primary sortas="b-db_stat">db_stat</primary>
416 </indexterm>
417 </listitem>
418 </varlistentry>
419
420 <varlistentry id="db_tuner">
421 <term><command>db_tuner</command></term>
422 <listitem>
423 <para>
424 analyzes the data in a btree database, and suggests a page size that
425 is likely to deliver optimal operation.
426 </para>
427 <indexterm zone="db db_tuner">
428 <primary sortas="b-db_tuner">db_tuner</primary>
429 </indexterm>
430 </listitem>
431 </varlistentry>
432
433 <varlistentry id="db_upgrade">
434 <term><command>db_upgrade</command></term>
435 <listitem>
436 <para>
437 is used to upgrade database files to a newer version of
438 <application>Berkeley DB</application>.
439 </para>
440 <indexterm zone="db db_upgrade">
441 <primary sortas="b-db_upgrade">db_upgrade</primary>
442 </indexterm>
443 </listitem>
444 </varlistentry>
445
446 <varlistentry id="db_verify">
447 <term><command>db_verify</command></term>
448 <listitem>
449 <para>is used to run consistency checks on database files.</para>
450 <indexterm zone="db db_verify">
451 <primary sortas="b-db_verify">db_verify</primary>
452 </indexterm>
453 </listitem>
454 </varlistentry>
455 </variablelist>
456 </sect2>
457</sect1>
Note: See TracBrowser for help on using the repository browser.