debian/0000755000000000000000000000000011706537207007176 5ustar debian/libdb5.3++-dev.dirs0000644000000000000000000000002411706537004012254 0ustar usr/include usr/lib debian/gbp.conf0000644000000000000000000000026011706537004010606 0ustar [DEFAULT] debian-branch = debian-sid debian-tag = debian/%(version)s upstream-branch = upstream-sid upstream-tag = upstream/%(version)s pristine-tar = True [git-dch] meta = 1 debian/saved_signature_amd64.txt0000644000000000000000000000001111706537004014100 0ustar 6b2fefb9 debian/libdb5.3.docs0000644000000000000000000000003411706537004011342 0ustar debian/build_signature*.txt debian/libdb5.3.dirs0000644000000000000000000000001011706537004011345 0ustar usr/lib debian/libdb5.3-sql.install0000644000000000000000000000003111706537004012652 0ustar usr/lib/*/libdb_sql-*.so debian/libdb5.3-java.install0000644000000000000000000000003511706537004013000 0ustar usr/lib/*/libdb_java-5.3*.so debian/rules0000755000000000000000000001277211706537004010262 0ustar #!/usr/bin/make -f # -*- makefile -*- # debian/rules for Berkeley DB defaults # Copyright (C) 2011 Ondřej Surý # Published under the GNU GPL license # Partially based on previous work by Clint Adams # # Uncomment this to turn on verbose mode. export DH_VERBOSE=1 export DH_ALWAYS_EXCLUDE=.arch-ids DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) DEB_BUILD_GNU_CPU ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_CPU) DEB_BUILD_GNU_SYSTEM ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_SYSTEM) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) DEB_HOST_GNU_CPU ?= $(shell dpkg-architecture -qDEB_HOST_GNU_CPU) DEB_HOST_GNU_SYSTEM ?= $(shell dpkg-architecture -qDEB_HOST_GNU_SYSTEM) DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) # Don't try to build this file if missing /usr/share/gcj/debian_defaults /usr/share/javahelper/java-vars.mk: : -include /usr/share/gcj/debian_defaults -include /usr/share/javahelper/java-vars.mk JAVA_BROKEN_ARCHS = GCJ_BROKEN_ARCHS = ia64 sparc mips sh4 GCJ_NATIVE_ARCHS = $(filter-out $(GCJ_BROKEN_ARCHS), $(gcj_native_archs)) ENABLE_JAVA=no ENABLE_GJ=no ifeq (,$(filter $(DEB_HOST_ARCH), $(JAVA_BROKEN_ARCHS))) ENABLE_JAVA=yes ifneq (,$(filter $(DEB_HOST_ARCH), $(GCJ_NATIVE_ARCHS))) ENABLE_GCJ=yes endif endif CONFIGURE_SWITCHES = --prefix=/usr \ --mandir=\$${prefix}/share/man \ --localstatedir=/var \ --sysconfdir=/etc \ --libexecdir=/usr/lib \ --enable-cxx \ --enable-compat185 \ --enable-sql \ --enable-stl \ --enable-tcl \ --with-tcl=/usr/lib ifeq (zx86_64-linux-gnuz,z$(DEB_HOST_GNU_TYPE)z) CONFIGURE_SWITCHES += --with-mutex=POSIX/pthreads/library endif ifeq (zavr32-linux-gnuz,z$(DEB_HOST_GNU_TYPE)z) CONFIGURE_SWITCHES += --enable-posixmutexes endif ifeq (yes,$(ENABLE_JAVA)) JAVA_HOME ?= /usr/lib/jvm/default-java CFLAGS += -I$(JAVA_HOME)/include -I$(JAVA_HOME)/include/linux CONFIGURE_SWITCHES += --enable-java DH_PLUGINS += --with=javahelper else CONFIGURE_SWITCHES += --disable-java DH_OPTIONS += -Nlibdb5.3-java -Nlibdb5.3-java-dev -Nlibdb5.3-java-gcj endif ifeq (no,$(ENABLE_GCJ)) DH_OPTIONS += -Nlibdb5.3-java-gcj endif BROKEN_CPUS = zs390z VERY_BROKEN_CPUS = zm68kz zhppaz BROKEN_SYSTEMS = zgnuz VERY_BROKEN_SYSTEMS = TCLSH=/usr/bin/tclsh export DH_OPTIONS package=db5.3 bdbversion=5.3 version=$(shell expr `pwd` : '.*-\([0-9.]*\)') version_major=$(shell expr `pwd` : '.*-\([0-9]*\).[0-9.]*') %: dh $@ $(DH_PLUGINS) override_dh_auto_configure: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) dh_auto_configure -Ddist -Bbuild-test -- $(CONFIGURE_SWITCHES) --enable-test endif dh_auto_configure -Ddist -Bbuild-production -- $(CONFIGURE_SWITCHES) --disable-test override_dh_auto_clean: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) dh_auto_clean -Ddist -Bbuild-test endif dh_auto_clean -Ddist -Bbuild-production rm -f $(CURDIR)/debian/build_signature.txt override_dh_auto_test: ifeq (,$(findstring z$(DEB_BUILD_GNU_CPU)z,$(VERY_BROKEN_CPUS))$(findstring z$(DEB_BUILD_GNU_SYSTEM)z,$(VERY_BROKEN_SYSTEMS))) ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) cd build-test && make cutest && ./cutest echo 'source ../test/tcl/test.tcl; run_std;' | tclsh ifeq (,$(findstring z$(DEB_BUILD_GNU_CPU)z,$(BROKEN_CPUS))$(findstring z$(DEB_BUILD_GNU_SYSTEM)z,$(BROKEN_SYSTEMS))) ! grep ^FAIL build-test/ALL.OUT else # Testsuite failures are marked as non-fatal on $(DEB_BUILD_GNU_SYSTEM)-$(DEB_BUILD_GNU_CPU) grep ^FAIL build-test/ALL.OUT || true endif else # Testsuite has been disabled by DEB_BUILD_OPTIONS=$(DEB_BUILD_OPTIONS) endif else # Testsuite has been disabled on $(DEB_BUILD_GNU_SYSTEM)-$(DEB_BUILD_GNU_CPU) endif override_dh_auto_install: dh_auto_install -Ddist -Bbuild-production # Remove .la files rm -f $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.la # Remove libdb*-5.so from all packages, we don't provide generic libdb5 packages rm -f $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libdb*5.so rm -f debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libdb.a ln -s libdb-$(bdbversion).a $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libdb.a # Compare built-in signature and fail build if it is different cc -o$(CURDIR)/debian/db_signature \ -I$(CURDIR)/debian/tmp/usr/include \ $(CURDIR)/debian/db_signature.c \ $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/libdb.a $(CURDIR)/debian/db_signature > $(CURDIR)/debian/build_signature_$(DEB_HOST_ARCH).txt echo -n "Berkeley DB signature is:"; $(CURDIR)/debian/db_signature if [ -f $(CURDIR)/debian/saved_signature_$(DEB_HOST_ARCH).txt ]; then \ cmp $(CURDIR)/debian/saved_signature_$(DEB_HOST_ARCH).txt \ $(CURDIR)/debian/build_signature_$(DEB_HOST_ARCH).txt \ || ( echo "Region environment signatures differ."; exit 1; ); \ fi mv $(CURDIR)/debian/tmp/usr/bin/dbsql $(CURDIR)/debian/tmp/usr/bin/db_sql rm -f $(CURDIR)/debian/tmp/usr/bin/sqlite3 for i in $(CURDIR)/debian/tmp/usr/bin/db_*; do \ mv $$i $$(echo $$i | sed -e 's{usr/bin/db_{usr/bin/$(package)_{'); \ done override_dh_install: dh_install -a -Xusr/doc --list-missing tcltk-depends override_dh_installdocs: dh_installdocs -pdb5.3-doc dh_installdocs --remaining-packages --link-doc=libdb5.3 override_dh_strip: dh_strip -s --dbg-package=libdb5.3-dbg override_dh_clean: DH_OPTIONS="" dh_clean override_jh_installlibs: ifeq (yes,$(ENABLE_JAVA)) jh_installlibs endif ifeq (yes,$(ENABLE_GCJ)) dh_nativejava endif debian/compat0000644000000000000000000000000211706537004010367 0ustar 9 debian/libdb5.3-java.dirs0000644000000000000000000000002711706537004012274 0ustar usr/lib usr/share/java debian/libdb5.3-sql-dev.install0000644000000000000000000000010211706537004013425 0ustar usr/include/dbsql.h usr/lib/*/libdb_sql-*.a usr/lib/*/libdb_sql.* debian/db5.3-sql-util.dirs0000644000000000000000000000003311706537004012433 0ustar usr/bin usr/share/man/man1 debian/libdb5.3-sql.dirs0000644000000000000000000000001011706537004012142 0ustar usr/lib debian/copyright0000644000000000000000000001653511706537004011136 0ustar This package was debianized by Clint Adams on Wed, 25 Jul 2007 20:37:51 +0700 It was downloaded from http://www.oracle.com/technology/software/products/berkeley-db/db/index.html Copyright and license: The following is the license that applies to this copy of the Berkeley DB software. For a license to use the Berkeley DB software under conditions other than those described here, or to purchase support for this software, please contact Oracle at berkeleydb-info_us@oracle.com. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /* * Copyright (c) 1990, 2010 Oracle and/or its affiliates. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Redistributions in any form must be accompanied by information on * how to obtain complete source code for the DB software and any * accompanying software that uses the DB software. The source code * must either be included in the distribution or be available for no * more than the cost of distribution plus a nominal fee, and must be * freely redistributable under reasonable conditions. For an * executable file, complete source code means the source code for all * modules it contains. It does not include source code for modules or * files that typically accompany the major components of the operating * system on which the executable file runs. * * THIS SOFTWARE IS PROVIDED BY ORACLE ``AS IS'' AND ANY EXPRESS OR * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED * WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR * NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL ORACLE BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN * IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ /* * Copyright (c) 1990, 1993, 1994, 1995 * The Regents of the University of California. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ /* * Copyright (c) 1995, 1996 * The President and Fellows of Harvard University. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY HARVARD AND ITS CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL HARVARD OR ITS CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= /*** * ASM: a very small and fast Java bytecode manipulation framework * Copyright (c) 2000-2005 INRIA, France Telecom * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. Neither the name of the copyright holders nor the names of its * contributors may be used to endorse or promote products derived from * this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF * THE POSSIBILITY OF SUCH DAMAGE. */ debian/libdb5.3-dev.install0000644000000000000000000000011411706537004012633 0ustar usr/include/db.h usr/include/db_185.h usr/lib/*/libdb-*.a usr/lib/*/libdb.* debian/libdb5.3-sql-dev.dirs0000644000000000000000000000002411706537004012723 0ustar usr/include usr/lib debian/libdb5.3++.dirs0000644000000000000000000000001011706537004011473 0ustar usr/lib debian/source/0000755000000000000000000000000011706537004010471 5ustar debian/source/format0000644000000000000000000000001411706537004011677 0ustar 3.0 (quilt) debian/libdb5.3-tcl.dirs0000644000000000000000000000001011706537004012125 0ustar usr/lib debian/libdb5.3++.install0000644000000000000000000000003111706537004012203 0ustar usr/lib/*/libdb_cxx-*.so debian/libdb5.3.install0000644000000000000000000000002511706537004012060 0ustar usr/lib/*/libdb-*.so debian/libdb5.3-sql.lintian-overrides0000644000000000000000000000025111706537004014646 0ustar # historical reasons libdb5.3-sql: package-name-doesnt-match-sonames libdb-sql-5.3 # not true, libdb5.3-sql provides sqlite3 ABI libdb5.3-sql: embedded-library * sqlite debian/db_signature.c0000644000000000000000000000024011706537004011777 0ustar #include #include "db.h" extern u_int32_t __env_struct_sig(); int main(int argc, char **argv) { printf("%x\n", __env_struct_sig()); return 0; } debian/db5.3-util.manpages0000644000000000000000000000002211706537004012466 0ustar debian/manpages/* debian/db5.3-doc.docs0000644000000000000000000000002611706537004011417 0ustar debian/tmp/usr/docs/* debian/libdb5.3-stl-dev.dirs0000644000000000000000000000002411706537004012726 0ustar usr/include usr/lib debian/libdb5.3-java-dev.dirs0000644000000000000000000000001011706537004013040 0ustar usr/lib debian/db5.3-util.install0000644000000000000000000000044011706537004012345 0ustar usr/bin/db5.3_archive usr/bin/db5.3_checkpoint usr/bin/db5.3_deadlock usr/bin/db5.3_dump usr/bin/db5.3_hotbackup usr/bin/db5.3_load usr/bin/db5.3_log_verify usr/bin/db5.3_printlog usr/bin/db5.3_recover usr/bin/db5.3_replicate usr/bin/db5.3_stat usr/bin/db5.3_upgrade usr/bin/db5.3_verify debian/patches/0000755000000000000000000000000011706537004010620 5ustar debian/patches/series0000644000000000000000000000016511706537004012037 0ustar 002-versioned_symbols.patch 003-jni_javac.patch 004-tclsleep.patch 005-pg_crypt_size.patch 006-mutex_alignment.patch debian/patches/003-jni_javac.patch0000644000000000000000000000150011706537004014061 0ustar --- a/dist/configure +++ b/dist/configure @@ -18413,7 +18413,7 @@ $as_echo "$_cur" >&6; } done _ACJNI_FOLLOWED="$_cur" -_JTOPDIR=`echo "$_ACJNI_FOLLOWED" | sed -e 's://*:/:g' -e 's:/[^/]*$::'` +_JTOPDIR=`echo "$_ACJNI_JAVAC" | sed -e 's://*:/:g' -e 's:/[^/]*$::'` case "$host_os" in darwin*) _JTOPDIR=`echo "$_JTOPDIR" | sed -e 's:/[^/]*$::'` _JINC="$_JTOPDIR/Headers";; --- a/dist/aclocal_java/ac_jni_include_dirs.m4 +++ b/dist/aclocal_java/ac_jni_include_dirs.m4 @@ -44,7 +44,7 @@ case "$_ACJNI_JAVAC" in esac _ACJNI_FOLLOW_SYMLINKS("$_ACJNI_JAVAC") -_JTOPDIR=`echo "$_ACJNI_FOLLOWED" | sed -e 's://*:/:g' -e 's:/[[^/]]*$::'` +_JTOPDIR=`echo "$_ACJNI_JAVAC" | sed -e 's://*:/:g' -e 's:/[[^/]]*$::'` case "$host_os" in darwin*) _JTOPDIR=`echo "$_JTOPDIR" | sed -e 's:/[[^/]]*$::'` _JINC="$_JTOPDIR/Headers";; debian/patches/002-versioned_symbols.patch0000644000000000000000000000125711706537004015713 0ustar --- a/dist/Makefile.in +++ b/dist/Makefile.in @@ -854,9 +854,15 @@ $(libdb_version): $(C_OBJS) $(RM) $(libdb) $(LN) -s $(libdb_version) $(libdb) +Versions: $(C_OBJS) + rm -f $@ + printf "DB5_3 {\n global:\n" > $@ + nm $$(sed -n "/^pic_object='\(.*\)'$$/ { s//\1/;s,.libs/,,;p;}" $(C_OBJS)) | grep " [DTR] " | cut -d" " -f3 | sed -e 's/$$/;/' >> $@ + printf "local: *; };\n" >> $@ + # Shared C library. -$(libso_target): $(C_OBJS) - $(SOLINK) $(SOFLAGS) $(LDFLAGS) -o $@ $(C_OBJS) \ +$(libso_target): $(C_OBJS) Versions + $(SOLINK) $(SOFLAGS) -Wl,--version-script=Versions $(LDFLAGS) -o $@ $(C_OBJS) \ $(LIBCSO_LIBS) $(RM) $(libdb) $(LN) -s .libs/$(libdb_version) $(libdb) debian/patches/004-tclsleep.patch0000644000000000000000000000052111706537004013753 0ustar --- a/test/tcl/env012.tcl +++ b/test/tcl/env012.tcl @@ -75,7 +75,7 @@ proc env012 { } { $testdir $testfile PUT $key $data RECOVER 0 10 &] # Wait a while so process 1 has a chance to get going. - tclsleep 2 + tclsleep 4 puts "\t\tEnv$tnum.b2: Start process 2." set p2 [exec $tclsh_path $test_path/wrap.tcl envscript.tcl \ debian/patches/006-mutex_alignment.patch0000644000000000000000000000053711706537004015351 0ustar --- a/src/dbinc/mutex_int.h +++ b/src/dbinc/mutex_int.h @@ -850,7 +850,11 @@ typedef volatile unsigned char tsl_t; * alignment locally. */ #ifndef MUTEX_ALIGN -#define MUTEX_ALIGN sizeof(unsigned int) +# if defined(__linux__) && defined(__sparc__) +# define MUTEX_ALIGN 8 +# else +# define MUTEX_ALIGN sizeof(unsigned int) +# endif #endif /* debian/patches/005-pg_crypt_size.patch0000644000000000000000000000167111706537004015031 0ustar --- a/src/dbinc/db_page.h +++ b/src/dbinc/db_page.h @@ -256,6 +256,17 @@ typedef struct __pg_crypto { */ } PG_CRYPTO; +/* + * With most compilers sizeof(PG_CRYPTO) == 38. However some ABIs + * require it to be padded to 40 bytes. The padding must be excluded + * from our size calculations due to the 16-byte alignment requirement + * for crypto. + * + * A similar problem applies to PG_CHKSUM, but it's too late to change + * that. + */ +#define SIZEOF_PG_CRYPTO 38 + typedef struct _db_page { DB_LSN lsn; /* 00-07: Log sequence number. */ db_pgno_t pgno; /* 08-11: Current page number. */ @@ -291,7 +302,7 @@ typedef struct _db_page { */ #define P_INP(dbp, pg) \ ((db_indx_t *)((u_int8_t *)(pg) + SIZEOF_PAGE + \ - (F_ISSET((dbp), DB_AM_ENCRYPT) ? sizeof(PG_CRYPTO) : \ + (F_ISSET((dbp), DB_AM_ENCRYPT) ? SIZEOF_PG_CRYPTO : \ (F_ISSET((dbp), DB_AM_CHKSUM) ? sizeof(PG_CHKSUM) : 0)))) #define P_IV(dbp, pg) \ debian/source.lintian-overrides0000644000000000000000000000067011706537004014054 0ustar # jdbc and odbc is not compiled db5.3 source: ancient-autotools-helper-file lang/sql/jdbc/config.guess * db5.3 source: ancient-autotools-helper-file lang/sql/jdbc/config.sub * db5.3 source: ancient-autotools-helper-file lang/sql/odbc/config.guess * db5.3 source: ancient-autotools-helper-file lang/sql/odbc/config.sub * db5.3 source: ancient-libtool lang/sql/jdbc/ltmain.sh * db5.3 source: package-needs-versioned-debhelper-build-depends 9 debian/libdb5.3-tcl.lintian-overrides0000644000000000000000000000012311706537004014627 0ustar # historical reasons libdb5.3-tcl: package-name-doesnt-match-sonames libdb-tcl-5.3 debian/libdb5.3-java.jlibs0000644000000000000000000000003411706537004012434 0ustar debian/tmp/usr/lib/*/db.jar debian/libdb5.3-java.lintian-overrides0000644000000000000000000000012511706537004014770 0ustar # historical reasons libdb5.3-java: package-name-doesnt-match-sonames libdb-java-5.3 debian/control0000644000000000000000000001573011706537004010602 0ustar Source: db5.3 Section: libs Priority: standard Maintainer: Debian Berkeley DB Group Uploaders: Ondřej Surý Standards-Version: 3.9.2 Build-Depends: debhelper (>= 8.1.3~), tcl-dev, procps [!hurd-i386], javahelper, default-jdk, gcj-native-helper Homepage: http://www.oracle.com/technology/software/products/berkeley-db/index.html Vcs-Browser: http://git.debian.org/?p=pkg-db/db5.3.git Vcs-Git: git://git.debian.org/pkg-db/db5.3.git Package: db5.3-doc Architecture: all Section: doc Priority: optional Depends: ${misc:Depends} Description: Berkeley v5.3 Database Documentation [html] This package contains documentation in HTML format for all of the APIs (C, C++, C#, STL, Java, Tcl) and utilities provided by version 5.3 of Berkeley DB. Package: libdb5.3-dev Architecture: any Section: libdevel Priority: extra Depends: libdb5.3 (= ${binary:Version}), ${misc:Depends} Suggests: db5.3-doc Conflicts: libdb4.6-dev, libdb4.7-dev, libdb4.8-dev, libdb5.1-dev, libdb5.2-dev Description: Berkeley v5.3 Database Libraries [development] This is the development package which contains headers and static libraries for the Berkeley v5.3 database library. Package: libdb5.3 Architecture: any Multi-Arch: same Pre-Depends: ${misc:Pre-Depends} Depends: ${shlibs:Depends}, ${misc:Depends} Description: Berkeley v5.3 Database Libraries [runtime] This is the runtime package for programs that use the v5.3 Berkeley database library. Package: db5.3-util Architecture: any Section: database Priority: optional Multi-Arch: foreign Depends: ${shlibs:Depends}, ${misc:Depends} Description: Berkeley v5.3 Database Utilities This package provides different tools for manipulating databases in the Berkeley v5.3 database format, and includes: - db5.3_archive: write the pathnames of the log files no longer in use. - db5.3_checkpoint: daemon process to monitor the database log and checkpoint it periodically. - db5.3_deadlock: traverse the database environment lock region and abort lock requests when a deadlock is detected. - db5.3_load: loads (and creates) a database from standard input. - db5.3_dump: read a database file and write it in a format understood by db4.{2..8}_load. - db5.3_printlog: dump log files in human readable format. - db5.3_stat: display statistics for Berkeley DB environments. - db5.3_upgrade: upgrades the version of files and the databases they contain. - db5.3_verify: check the structure of files and their databases. Package: db5.3-sql-util Architecture: any Section: database Priority: extra Depends: ${shlibs:Depends}, ${misc:Depends} Description: Berkeley v5.3 SQL Database Utilities This package provides different tools for manipulating databases in the Berkeley v5.3 SQL database format, and includes: - db5.3_sql: sqlite3 compatible command-line utility Package: libdb5.3++ Architecture: any Multi-Arch: same Pre-Depends: ${misc:Pre-Depends} Depends: ${shlibs:Depends}, ${misc:Depends} Priority: optional Description: Berkeley v5.3 Database Libraries for C++ [runtime] This is the runtime package for programs that use the Berkeley v5.3 database library. This is only for programs which use the C++ interface. Package: libdb5.3++-dev Architecture: any Section: libdevel Priority: extra Depends: libdb5.3++ (= ${binary:Version}), libdb5.3-dev (= ${binary:Version}), ${misc:Depends} Conflicts: libdb4.6++-dev, libdb4.7++-dev, libdb4.8++-dev, libdb5.1++-dev, libdb5.2++-dev Description: Berkeley v5.3 Database Libraries for C++ [development] This is the development package which contains headers and static libraries for the Berkeley v5.3 database library. This is only for programs which will use the C++ interface. Package: libdb5.3-tcl Architecture: any Section: interpreters Priority: extra Multi-Arch: same Pre-Depends: ${misc:Pre-Depends} Conflicts: libdb4.6-tcl, libdb4.7-tcl, libdb4.8-tcl, libdb5.1-tcl, libdb5.2-tcl Depends: ${tcl:Depends}, ${shlibs:Depends}, ${misc:Depends} Description: Berkeley v5.3 Database Libraries for Tcl [module] This package provides a Tcl module suitable for accessing Berkeley v5.3 databases from within Tcl programs. Package: libdb5.3-dbg Architecture: any Section: debug Priority: extra Depends: libdb5.3 (= ${binary:Version}), ${misc:Depends} Multi-Arch: same Description: Berkeley v5.3 Database Libraries [debug] This package provides the debug symbols for the Berkeley v5.3 database libraries and binaries. Package: libdb5.3-java Architecture: any Section: java Priority: optional Depends: ${shlibs:Depends}, ${misc:Depends} Pre-Depends: ${misc:Pre-Depends} Conflicts: libdb5.1-java, libdb5.2-java Recommends: libdb5.3-java-gcj Multi-Arch: same Description: Berkeley v5.3 Database Libraries for Java This package provides the Java interface for the Berkeley v5.3 database library. Package: libdb5.3-java-gcj Architecture: any Section: java Priority: optional Depends: libdb5.3-java (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Description: Berkeley v5.3 Database Libraries for Java (native code) This package provides the Java interface for the Berkeley v5.3 database library. . This package contains the natively compiled code for use by gij. Package: libdb5.3-java-dev Architecture: any Section: libdevel Priority: optional Depends: libdb5.3-java (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends} Conflicts: libdb4.6-java-dev, libdb4.7-java-dev, libdb4.8-java-dev, libdb5.1-java-dev, libdb5.2-java-dev Description: Berkeley v5.3 Database Libraries for Java [development] This package provides the Java interface for the Berkeley v5.3 database library. Package: libdb5.3-sql-dev Architecture: any Section: libdevel Priority: extra Depends: libdb5.3-sql (= ${binary:Version}), ${misc:Depends} Conflicts: libdb5.1-sql-dev, libdb5.2-sql-dev Suggests: db5.3-doc Description: Berkeley v5.3 Database Libraries [SQL development] This is the development package which contains headers and static libraries for the Berkeley v5.3 database library. Package: libdb5.3-sql Architecture: any Priority: extra Depends: ${shlibs:Depends}, ${misc:Depends} Pre-Depends: ${misc:Pre-Depends} Multi-Arch: same Description: Berkeley v5.3 Database Libraries [SQL runtime] This is the runtime package for programs that use the v5.3 Berkeley database SQL library. Package: libdb5.3-stl-dev Architecture: any Section: libdevel Priority: extra Depends: libdb5.3-stl (= ${binary:Version}), ${misc:Depends} Conflicts: libdb5.1-stl-dev, libdb5.2-stl-dev Suggests: db5.3-doc Description: Berkeley v5.3 Database Libraries [STL development] This is the development package which contains headers and static libraries for the Berkeley v5.3 database library. Package: libdb5.3-stl Architecture: any Priority: extra Depends: ${shlibs:Depends}, ${misc:Depends} Pre-Depends: ${misc:Pre-Depends} Multi-Arch: same Description: Berkeley v5.3 Database Libraries [STL runtime] This is the runtime package for programs that use the v5.3 Berkeley database STL library. debian/libdb5.3-stl.dirs0000644000000000000000000000001011706537004012145 0ustar usr/lib debian/changelog0000644000000000000000000003345011706537004011050 0ustar db5.3 (5.3.15-2) unstable; urgency=low * Update description for version 5.3 * Fix missing conflicts with db5.1 and db5.2 (Closes: #656725, #656726, #656727) -- Ondřej Surý Sat, 21 Jan 2012 14:29:58 +0100 db5.3 (5.3.15-1) unstable; urgency=low * Imported Upstream version 5.3.15 * Prepare db5.3 release * Run all tests in the TCL suite * s/sqlite/sqlite3/ in description of db5.3_sql * Bump versioned symbols to DB5_3 * Update patches for new release * Update saved db_signature on amd64 * Update lintian-overrides to not include dates for config.{sub,guess} -- Ondřej Surý Fri, 20 Jan 2012 18:28:06 +0100 db5.2 (5.2.36-1) experimental; urgency=low * Imported Upstream version 5.2.36 * Adapt debian/ directory from db5.1 to db5.2 * Update Vcs-* links to db5.2 * Add git-buildpackage configuration * Drop 001-documentation_update.patch; fixed upstream * Refresh patches to the new release * Do a double build and --disable-test for production version of Berkeley DB libraries (as recommended by upstream) * Update saved region environment signature to match production version * Update source.lintian-overrides to match source name -- Ondřej Surý Fri, 23 Sep 2011 13:39:02 +0200 db (5.1.25-11) unstable; urgency=low * Disable libdb5.1-java-gcj on sh4 (Closes: #623980) * Add code to compare built-in signature to prevent future bugs like #625484 * Print built-in signature to the build log * Update Vcs-* links * Apply MultiArch patch (Courtesy of Steve Langasek) (Closes: #631318) * Update db_signature linking to MultiArch libraries * Add lintian-override for (not)embedded sqlite in MultiArch * Generated db_signature is different on each arch + Only generate the signature if we don't have it (first pass) * Install build_signature_$(ARCH).txt to libdb5.1 package + This will allow to add all correct signatures in next upload -- Ondřej Surý Tue, 28 Jun 2011 14:26:40 +0200 db (5.1.25-10) unstable; urgency=low * Drop dependency on ca-certificates-java, it didn't work for non openjdk platforms anyway -- Ondřej Surý Sun, 24 Apr 2011 22:24:00 +0200 db (5.1.25-9) unstable; urgency=low * Fix HOST vs BUILD variables (Closes: #623543) * Rewrite debian/rules to use ENABLE_JAVA and ENABLE_GCJ * Enable Java on mips again * Move db5.1-sql util to separate package to prevent db5.1-util dependency on lidb5.1-sql library * Build-depends on ca-certificates-java (>> 20100412) -- Ondřej Surý Fri, 22 Apr 2011 14:30:22 +0200 db (5.1.25-8) unstable; urgency=low * Disable Java build on mips to fix FTBS -- Ondřej Surý Thu, 21 Apr 2011 15:22:27 +0200 db (5.1.25-7) unstable; urgency=low * Revert to upstream JAR name -> db.jar -- Ondřej Surý Thu, 21 Apr 2011 08:51:57 +0200 db (5.1.25-6) unstable; urgency=low * Enable Java support on every Debian architecture * Debian packaging: + Add javahelper addon for debhelper + Change DEB_HOST_ARCH to DEB_BUILD_ARCH + Keep -Ddist -Bbuild to overridden dh_auto_ commands to fix javahelper breakage + Fix typo and set GCJ CFLAGS out of the condition + Only rename db.jar to libdb5.1.jar and rest let to jh_installlibs + Change --fail-missing to --list-missing + Move dh_nativejava after jh_installibs -- Ondřej Surý Thu, 21 Apr 2011 00:21:34 +0200 db (5.1.25-5) unstable; urgency=low * Fix FTBFS when buildd directory is named db_ -- Ondřej Surý Wed, 20 Apr 2011 18:18:01 +0200 db (5.1.25-4) unstable; urgency=low * Add debug info for all libraries * Fix FTBFS on freebsd-{amd64,i386} (Thanks Matthias Klose) (Closes: #621878) * Fix lintian warnings and errors: + Update default java build dependencies + Tighten Java libraries dependencies + Fix errors in db5.1_load.1 manpage * Debian packaging: + Convert package build system to debhelper with overrides + Move debian/rules to debhelper + Remove some obsolete Conflicts + Add ${misc:Depends} since we build depend on debhelper now + Use tcltk-defaults command for tcl dependencies (Closes: #606065) + Use dh_nativejava debhelper command + Move upstream source changes to quilt patches * Add lintian-overrides for: + ancient-autotools-helper-file,ancient-libtool: odbc/jdbc is not used + package-name-doesnt-match-sonames: historical reasons + sqlite3 embedded-library: db5.1-sql provides sqlite3 ABI -- Ondřej Surý Wed, 20 Apr 2011 14:07:51 +0200 db (5.1.25-3) unstable; urgency=low * Add conflicts with previous -dev packages (Closes: #622711) * Fix Berkeley DB Debian Group email address * Remove .la files from the packages (Closes: #621303) -- Ondřej Surý Tue, 19 Apr 2011 15:31:30 +0200 db (5.1.25-2) unstable; urgency=low * Adopt the package (Closes: #619907) * Build-depend on Debian default tcl-dev * Move libdb-java, libdb-java-dev and libdb++-dev to empty packages built from db-defaults -- Ondřej Surý Wed, 13 Apr 2011 21:59:34 +0200 db (5.1.25-1) unstable; urgency=low * New upstream version. * Orphan the package. -- Clint Adams Thu, 10 Feb 2011 19:24:27 -0500 db (5.1.19-3) unstable; urgency=low [ Thorsten Glaser ] * Fix manpage-has-errors-from-man lintian warning * Add db4.7_codegen(1) from db4.7 (4.7.25-12), renamed appropriately * Correct db5.1-util override disparity * Use mktemp -t not --tmpdir to be backportable. (Closes: #584934) * Mark testsuite failures non-fatal on Hurd [ Clint Adams ] * Forward-ported Steve Langasek's cross-compilation patch from db4.8. * Re-enable Java package on armel. -- Clint Adams Tue, 01 Feb 2011 18:21:19 -0500 db (5.1.19-2) unstable; urgency=low * Remove ancient Conflicts. * Add Conflicts for libdb5.0-dev and libdb5.0-tcl just in case. closes: #602363. -- Clint Adams Sun, 05 Dec 2010 15:14:08 -0500 db (5.1.19-1) unstable; urgency=low * New upstream version. -- Clint Adams Mon, 20 Sep 2010 21:03:09 -0400 db (5.0.26-3) unstable; urgency=low * Patch from Aurelien Jarno to avoid following javac symlinks to ultimately avoid failing to equate /usr/lib/jvm/default-java/bin/../../../.. to /usr when using GCJ. closes: #594816. -- Clint Adams Mon, 30 Aug 2010 19:18:11 -0400 db (5.0.26-2) unstable; urgency=low * Version initialized data symbols as well, since they are occurring on mips for some reason. * Bump to Standards-Version 3.9.1. -- Clint Adams Sun, 29 Aug 2010 20:04:12 -0400 db (5.0.26-1) unstable; urgency=low * New upstream version. * Bump to Standards Version 3.9.0. -- Clint Adams Sat, 10 Jul 2010 12:37:46 -0400 db (5.0.21-2) unstable; urgency=low * Force POSIX mutexes on avr32. -- Clint Adams Wed, 21 Apr 2010 13:54:50 -0400 db (5.0.21-1) unstable; urgency=low * New upstream version. * Bump to Standards-Version 3.8.4. * Tweak symbol versioning hack to hack around db5.0 weirdness. * Add libdb5.0-{sql,stl}{,-dev} packages. -- Clint Adams Sun, 04 Apr 2010 09:37:47 -0400 db (4.8.26-2) unstable; urgency=low * Tweaked patch from Rafael Almeida to fix misnamed DB_CURSOR_BULK flag in C/C++ API documentation. closes: #574467. * Add avr32 as unsupported for Java. closes: #575138. * Rewrite db4.8-doc long description. closes: #550106. * Add Java support for alpha. closes: #541612. -- Clint Adams Thu, 25 Mar 2010 08:23:14 -0400 db (4.8.26-1) unstable; urgency=low * New upstream version. -- Clint Adams Tue, 29 Dec 2009 15:26:27 -0500 db (4.8.24-2) unstable; urgency=low * Fix typo in description of libdb4.8-java-gcj. * db4.8_load.1: fix typo of "keyword", thanks to "sobtwmxt". closes: #551457. * Clarify db4.8_load(1) title. closes: #557568. * Fix -java-gcj package build for gcj-4.4. closes: #558334. * Switch to 3.0 (quilt) source format. -- Clint Adams Wed, 16 Dec 2009 22:43:58 -0500 db (4.8.24-1) unstable; urgency=low * New upstream version. - RPC support has been dropped. * Bump to Standards-Version 3.8.3. * Force POSIX/pthreads/library mutexes on amd64. closes: #520926. -- Clint Adams Tue, 15 Sep 2009 00:13:05 -0400 db (4.7.25-7) unstable; urgency=low * Apply upstream patch 4.7.25.4: [#16299] Fix a bug which could cause a SEGV in __repmgr_available_site if a site becomes master after winning an election but is still processing client messages. * Bump to Standards-Version 3.8.2. * Move libdb4.7-dbg to section 'debug', priority 'extra'. * Move libdb4.7-java and libdb4.7-java-gcj to section 'java'. * Move libdb4.7-java-dev to section 'libdevel'. * Remove libdb4.7++'s relations with itself. * Run ldconfig in library package postinsts. -- Clint Adams Sun, 21 Jun 2009 15:22:37 -0400 db (4.7.25-6) unstable; urgency=low * Apply upstream patch 4.7.25.2: [#16415] DB_ENV->lock_get may self deadlock if user defined locks are used and there is only one lock partition defined. * Apply upstream patch 4.7.25.3: [#16541] Fix for dd segfaults. -- Clint Adams Tue, 30 Dec 2008 19:47:43 -0500 db (4.7.25-5) unstable; urgency=low * Apply upstream patch 4.7.25.1: [#16406] Replication clients should be able to open a sequence. -- Clint Adams Sat, 04 Oct 2008 13:29:59 -0400 db (4.7.25-4) unstable; urgency=medium * Make testsuite failures critical on both arm and sparc again. * Patch from Ben Hutchings to double the inter-process delay in test Env012.b. * Patch from Ben Hutchings to fix encrypted databases being unusable on ARM due to unexpected structure padding. closes: #437742. * Force 8-byte mutex alignment on sparc. closes: #498455. -- Clint Adams Wed, 10 Sep 2008 07:48:07 -0400 db (4.7.25-3) unstable; urgency=low * Add more conflicts to libdb4.7-dev. closes: #486318. -- Clint Adams Sun, 15 Jun 2008 09:50:46 -0400 db (4.7.25-2) unstable; urgency=low * Rename libdb-dev to libdb4.7-dev. -- Clint Adams Thu, 12 Jun 2008 20:56:51 -0400 db (4.7.25-1) unstable; urgency=low * New upstream version 4.7.25. * Adjust packaging for 4.7. * Bump to Standards-Version 3.8.0. -- Clint Adams Thu, 29 May 2008 22:09:39 -0400 db (4.6.21-8) unstable; urgency=high * Change Tcl build dependency to tcl8.5-dev. * Change Java architectures to everything but alpha, arm, hppa, hurd- i386, kfreebsd-i386, kfreebsd-amd64, and m32r. closes: #477855. * Switch java build dependency from java-gcj-compat-dev to default- jdk-builddep. -- Clint Adams Thu, 01 May 2008 08:28:24 -0400 db (4.6.21-7) unstable; urgency=medium * 4.6.21.1: [#15692] Fixes a race condition between checkpoint and DB->close which can result in the checkpoint thread self-deadlocking. -- Clint Adams Wed, 26 Mar 2008 22:51:04 -0400 db (4.6.21-6) unstable; urgency=low * Apply patch from Kevin Lindsay to avoid mutex deadlock in memory pool set_maxsize. closes: #469602. * Add Homepage control field. * Add Vcs-Browser and Vcs-Git control fields. * Tweak db4.6-util description to describe db4.6_dump more completely. -- Clint Adams Thu, 06 Mar 2008 08:06:34 -0500 db (4.6.21-5) unstable; urgency=low * Bump Standards-Version to 3.7.3. * Make libdb4.6-dbg depend on libdb4.6. -- Clint Adams Wed, 02 Jan 2008 15:44:18 -0500 db (4.6.21-4) unstable; urgency=low * Re-enable Java on hppa. -- Clint Adams Mon, 22 Oct 2007 12:36:02 -0400 db (4.6.21-3) unstable; urgency=low * Ship md5sums in each .deb. closes: #446807. * Skip test suite on hppa and m68k, since they are very broken. -- Clint Adams Mon, 15 Oct 2007 21:14:30 -0400 db (4.6.21-2) unstable; urgency=medium * Disable Java packages on hppa, since Java is yet again broken on hppa. -- Clint Adams Mon, 15 Oct 2007 13:18:57 -0400 db (4.6.21-1) unstable; urgency=low * New upstream version. -- Clint Adams Mon, 08 Oct 2007 22:35:29 -0400 db (4.6.19-1) unstable; urgency=medium * New upstream version. -- Clint Adams Fri, 24 Aug 2007 17:43:26 -0400 db (4.6.18-6) unstable; urgency=low * Tolerate testsuite failures on arm, sparc, s390. -- Clint Adams Thu, 16 Aug 2007 20:46:17 -0400 db (4.6.18-5) unstable; urgency=high * Apply patch to fix alignment issues in 32-bit binaries on 64-bit machines. -- Clint Adams Tue, 14 Aug 2007 14:43:39 -0400 db (4.6.18-4) unstable; urgency=low * Add libdb4.6-dbg package. * Fail the build if there are any testsuite failures. -- Clint Adams Sun, 12 Aug 2007 21:34:16 -0400 db (4.6.18-3) unstable; urgency=low * Disable stripping of binaries when DEB_BUILD_OPTIONS contains "nostrip". closes: #436766. -- Clint Adams Sat, 11 Aug 2007 12:34:38 -0400 db (4.6.18-2) unstable; urgency=medium * Forward-port db4.5 changes to build libdb4.6-java-gcj package. * Don't build-depend on java-gcj-compat-dev on m32r. * Forward-port db4.5 manpage typo fixes to db4.6_load(1). -- Clint Adams Tue, 07 Aug 2007 20:54:27 -0400 db (4.6.18-1) unstable; urgency=low * Initial packaging of Berkeley DB 4.6, under the source package name "db". -- Clint Adams Wed, 25 Jul 2007 20:37:51 +0700 debian/libdb5.3-tcl.install0000644000000000000000000000002511706537004012640 0ustar usr/lib/*/libdb_tcl* debian/libdb5.3-stl.install0000644000000000000000000000003111706537004012655 0ustar usr/lib/*/libdb_stl-*.so debian/libdb5.3-dev.dirs0000644000000000000000000000002411706537004012126 0ustar usr/include usr/lib debian/libdb5.3-java-gcj.dirs0000644000000000000000000000003211706537004013031 0ustar usr/lib/gcj usr/share/gcj debian/db5.3-sql-util.install0000644000000000000000000000002311706537004013137 0ustar /usr/bin/db5.3_sql debian/db5.3-util.dirs0000644000000000000000000000003311706537004011636 0ustar usr/bin usr/share/man/man1 debian/libdb5.3-stl-dev.install0000644000000000000000000000010311706537004013431 0ustar usr/include/dbstl*.h usr/lib/*/libdb_stl-*.a usr/lib/*/libdb_stl.* debian/libdb5.3.lintian-overrides0000644000000000000000000000011311706537004014046 0ustar # historical reasons libdb5.3: package-name-doesnt-match-sonames libdb-5.3 debian/libdb5.3++.lintian-overrides0000644000000000000000000000012111706537004014173 0ustar # historical reasons libdb5.3++: package-name-doesnt-match-sonames libdb-cxx-5.3 debian/libdb5.3-stl.lintian-overrides0000644000000000000000000000012211706537004014646 0ustar # historical reasons libdb5.3-stl: package-name-doesnt-match-sonames libdb-stl-5.3debian/libdb5.3-java-dev.install0000644000000000000000000000006011706537004013552 0ustar usr/lib/*/libdb_java-*.a usr/lib/*/libdb_java.* debian/libdb5.3++-dev.install0000644000000000000000000000010311706537004012757 0ustar usr/include/db_cxx.h usr/lib/*/libdb_cxx-*.a usr/lib/*/libdb_cxx.* debian/manpages/0000755000000000000000000000000011706537004010764 5ustar debian/manpages/db5.2_printlog.10000644000000000000000000000536511706537004013607 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_PRINTLOG 1 "28 January 2005" .SH NAME db5.2_printlog \- Dumps Berkeley DB log files in a human-readable format .SH SYNOPSIS .B db5.2_printlog [-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password] .SH DESCRIPTION The db5.2_printlog utility is a debugging utility that dumps Berkeley DB log files in a human-readable format. .SH OPTIONS .IP \fB\-b\fR Display log records starting at log sequence number (LSN) \fBstart-LSN\fR; \fBstart-LSN\fR is specified as a file number, followed by a slash (/) character, followed by an offset number, with no intervening whitespace. .IP \fB\-e\fR Stop displaying log records at log sequence number (LSN) \fBstop-LSN\fR; \fBstop-LSN\fR is specified as a file number, followed by a slash (/) character, followed by an offset number, with no intervening whitespace. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-N\fR Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-r\fR Read the log files in reverse order. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .PP The db5.2_printlog utility uses a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_printlog should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_printlog to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_printlog utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_printlog from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_deadlock.10000644000000000000000000000711411706537004013511 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_DEADLOCK 1 "28 January 2005" .SH NAME db5.2_deadlock \- Detect and abort deadlocks .SH SYNOPSIS .B db5.2_deadlock [-Vv] [-a e | m | n | o | W | w | y] [-h home] [-L file] [-t sec.usec] .SH DESCRIPTION The db5.2_deadlock utility traverses the database environment lock region, and aborts a lock request each time it detects a deadlock or a lock request that has timed out. By default, in the case of a deadlock, a random lock request is chosen to be aborted. .PP This utility should be run as a background daemon, or the underlying Berkeley DB deadlock detection interfaces should be called in some other way, whenever there are multiple threads or processes accessing a database and at least one of them is modifying it. .SH OPTIONS .IP \fB\-a\fR When a deadlock is detected, abort the locker: .RS .IP m with the most locks .IP n with the fewest locks .IP o with the oldest lock .IP W with the most write locks .IP w with the fewest write locks .IP y with the youngest lock .RE .IP When lock or transaction timeouts have been specified: .RS .IP e abort any lock request that has timed out .RE .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-L\fR Log the execution of the db5.2_deadlock utility to the specified file in the following format, where \fI###\fR is the process ID, and the date is the time the utility was started. .sp .TP 8 db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995 .sp This file will be removed if the db5.2_deadlock utility exits gracefully. .IP \fB\-t\fR Check the database environment every \fBsec\fR seconds plus \fBusec\fR microseconds to see if a process has been forced to wait for a lock; if one has, review the database environment lock structures. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode, generating messages each time the detector runs. .PP If the \fB-t\fR option is not specified, db5.2_deadlock will run once and exit. .PP The db5.2_deadlock utility uses a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_deadlock should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_deadlock to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_deadlock utility does not attempt to create the Berkeley DB shared memory regions if they do not already exist. The application which creates the region should be started first, and then, once the region is created, the db5.2_deadlock utility should be started. .PP The DB_ENV->lock_detect method is the underlying method used by the db_deadlock utility. See the db_deadlock utility source code for an example of using DB_ENV->lock_detect in a IEEE/ANSI Std 1003.1 (POSIX) environment. .PP The db5.2_deadlock utility exits 0 on success, and >0 if an error occurs. .PP .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_deadlock from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_archive.10000644000000000000000000001113011706537004013355 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_ARCHIVE 1 "28 January 2005" .SH NAME db5.2_archive \- Find unused log files for archiving purposes .SH SYNOPSIS .B db5.2_archive [-adlsVv] [-h home] [-P password] .SH DESCRIPTION The db5.2_archive utility writes the pathnames of log files that are no longer in use (for example, no longer involved in active transactions), to the standard output, one pathname per line. These log files should be written to backup media to provide for recovery in the case of catastrophic failure (which also requires a snapshot of the database files), but they may then be deleted from the system to reclaim disk space. .SH OPTIONS .PP .IP \fB\-a\fR Write all pathnames as absolute pathnames, instead of relative to the database home directories. .IP \fB\-d\fR Remove log files that are no longer needed; no filenames are written. Automatic log file removal is likely to make catastrophic recovery impossible. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-l\fR Write out the pathnames of all the database log files, whether or not they are involved in active transactions. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-s\fR Write the pathnames of all the database files that need to be archived in order to recover the database from catastrophic failure. If any of the database files have not been accessed during the lifetime of the current log files, db5.2_archive will not include them in this output. .sp It is possible that some of the files to which the log refers have since been deleted from the system. In this case, db5.2_archive will ignore them. When db5.2_recover is run, any files to which the log refers that are not present during recovery are assumed to have been deleted and will not be recovered. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode, listing the checkpoints in the log files as they are reviewed. .PP Log cursor handles (returned by the DB_ENV->log_cursor method) may have open file descriptors for log files in the database environment. Also, the Berkeley DB interfaces to the database environment logging subsystem (for example, DB_ENV->log_put and DB_TXN->abort) may allocate log cursors and have open file descriptors for log files as well. On operating systems where filesystem related system calls (for example, rename and unlink on Windows/NT) can fail if a process has an open file descriptor for the affected file, attempting to move or remove the log files listed by db5.2_archive may fail. All Berkeley DB internal use of log cursors operates on active log files only and furthermore, is short-lived in nature. So, an application seeing such a failure should be restructured to close any open log cursors it may have, and otherwise to retry the operation until it succeeds. (Although the latter is not likely to be necessary; it is hard to imagine a reason to move or rename a log file in which transactions are being logged or aborted.) .PP The db5.2_archive utility uses a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_archive should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_archive to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The DB_ENV->log_archive method is the underlying method used by the db5.2_archive utility. See the db5.2_archive utility source code for an example of using DB_ENV->log_archive in a IEEE/ANSI Std 1003.1 (POSIX) environment. .PP The db5.2_archive utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_archive from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_verify.10000644000000000000000000000607711706537004013256 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_VERIFY 1 "28 January 2005" .SH NAME db5.2_verify \- Verifies the structure databases .SH SYNOPSIS .B db5.2_verify [-NoqV] [-h home] [-P password] file ... .SH DESCRIPTION The db5.2_verify utility verifies the structure of one or more files and the databases they contain. .SH OPTIONS .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-o\fR Skip the database checks for btree and duplicate sort order and for hashing. .sp If the file being verified contains databases with non-default comparison or hashing configurations, calling the db5.2_verify utility without the \fB-o\fR flag will usually return failure. The \fB-o\fR flag causes db5.2_verify to ignore database sort or hash ordering and allows db5.2_verify to be used on these files. To fully verify these files, verify them explicitly using the DB->verify method, after configuring the correct comparison or hashing functions. .IP \fB\-N\fR Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-q\fR Suppress the printing of any error descriptions, simply exit success or failure. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .PP \fBThe db5.2_verify utility does not perform any locking, even in Berkeley DB environments that are configured with a locking subsystem. As such, it should only be used on files that are not being modified by another thread of control.\fR .PP The db5.2_verify utility may be used with a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_verify should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_verify to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_verify utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_verify from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_stat.10000644000000000000000000001162411706537004012717 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_STAT 1 "28 January 2005" .SH NAME db5.2_stat \- Display statistics for Berkeley DB environments .SH SYNOPSIS .B db5.2_stat -d file [-fN] [-h home] [-P password] [-s database] .B db5.2_stat [-cEelmNrtVZ] [-C Aclop] [-h home] [-L A] [-M A] [-R A] [-P password] .SH DESCRIPTION The db5.2_stat utility displays statistics for Berkeley DB environments. .SH OPTIONS .IP \fB\-C\fR Display internal information about the locking subsystem. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.) .RS .IP A Display all information. .IP c Display lock conflict matrix. .IP l Display lockers within hash chains. .IP o Display lock objects within hash chains. .IP p Display locking subsystem parameters. .RE .IP \fB\-c\fR Display locking subsystem statistics, as described in DB_ENV->lock_stat. .IP \fB\-d\fR Display database statistics for the specified file, as described in DB->stat. .sp If the database contains multiple databases and the \fB-s\fR flag is not specified, the statistics are for the internal database that describes the other databases the file contains, and not for the file as a whole. .IP \fB\-E\fR Display internal information about the database environment, including all configured subsystems of the database environment. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.) .IP \fB\-e\fR Display information about the database environment, including all configured subsystems of the database environment. .IP \fB\-f\fR Display only those database statistics that can be acquired without traversing the database. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-l\fR Display logging subsystem statistics, as described in DB_ENV->log_stat. .IP \fB\-M\fR Display internal information about the cache. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.) .RS .IP A Display all information. .IP h Display buffers within hash chains. .RE .IP \fB\-m\fR Display cache statistics, as described in DB_ENV->memp_stat. .IP \fB\-N\fR Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-R\fR Display internal information about the replication subsystem. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.) .RS .IP A Display all information. .RE .IP \fB\-r\fR Display replication statistics, as described in DB_ENV->rep_stat. .IP \fB\-s\fR Display statistics for the specified database contained in the file specified with the \fB-d\fR flag. .IP \fB\-t\fR Display transaction subsystem statistics, as described in DB_ENV->txn_stat. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-Z\fR Reset the statistics after reporting them; valid only with the \fB-C\fR, \fB-c\fR, \fB-E\fR, \fB-e\fR, \fB-L\fR, \fB-l\fR, \fB-M\fR, \fB-m\fR, \fB-R\fR, \fB-r\fR, and \fB-t\fR options. .PP Values normally displayed in quantities of bytes are displayed as a combination of gigabytes (GB), megabytes (MB), kilobytes (KB), and bytes (B). Otherwise, values smaller than 10 million are displayed without any special notation, and values larger than 10 million are displayed as a number followed by "M". .PP The db5.2_stat utility may be used with a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_stat should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_stat to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_stat utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_stat from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_hotbackup.10000644000000000000000000001345611706537004013731 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_HOTBACKUP 1 "28 January 2005" .SH NAME db5.2_hotbackup \- Create "hot backup" or "hot failover" snapshots .SH SYNOPSIS .B db5.2_hotbackup [-cDuVv] [-d data_dir ...] [-h home] [-l log_dir] [-P password] -b backup_dir .SH DESCRIPTION The db5.2_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments. .PP The db5.2_hotbackup utility performs the following steps: .RS .IP 1. If the \-c option is specified, checkpoint the source home database environment, and remove any unnecessary log files. .IP 2. If the target directory for the backup does not exist, it is created with mode read-write-execute for the owner. .sp If the target directory for the backup does exist and the \-u option was specified, all log files in the target directory are removed; if the \-u option was not specified, all files in the target directory are removed. .IP 3. If the \-u option was not specified, copy application-specific files found in the database environment home directory, or any directory specified using the -d option, into the target directory for the backup. .IP 4. Copy all log files found in the directory specified by the \-l option (or in the database environment home directory, if no \-l option was specified), into the target directory for the backup. .IP 5. Perform catastrophic recovery on the hot backup. .IP 6. Remove any unnecessary log files from the hot backup. .RE .PP The db5.2_hotbackup utility does not resolve pending transactions that are in the prepared state. Applications that use DB_TXN->prepare should specify DB_RECOVER_FATAL when opening the environment, and run DB_ENV->txn_recover to resolve any pending transactions, when failing over to the hot backup. .SH OPTIONS .IP \fB\-b\fR Specify the target directory for the backup. .IP \fB\-c\fR Before performing the snapshot, checkpoint the source database environment and remove any log files that are no longer required in that environment. \fBTo avoid making catastrophic failure impossible, log file removal must be integrated with log file archival.\fR .IP \fB\-d\fR Specify one or more source directories that contain databases; if none is specified, the database environment home directory will be searched for database files. As database files are copied into a single backup directory, files named the same, stored in different source directories, could overwrite each other when copied into the backup directory. .IP \fB\-h\fR Specify the source directory for the backup, that is, the database environment home directory. .IP \fB\-l\fR Specify a source directory that contains log files; if none is specified, the database environment home directory will be searched for log files. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-u\fR Update a pre-existing hot backup snapshot by copying in new log files. If the \fB\-u\fR option is specified, no databases will be copied into the target directory. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode, listing operations as they are done. .IP \fB\-D\fR Use the data directories listed in the DB_CONFIG configuration file in the source directory. This option has three effects: First, if they do not already exist, the specified data directories will be created relative to the target directory (with mode read-write-execute owner). Second, all files in the source data directories will be copied to the target data directories. If the DB_CONFIG file specifies one or more absolute pathnames, files in those source directories will be copied to the top-level target directory. Third, the DB_CONFIG configuration file will be copied from the +source directory to the target directory, and subsequently used for configuration if recovery is run in the target directory. .PP Care should be taken with the \fB-D\fR option and data directories which are named relative to the source directory but are not subdirectories (that is, the name includes the element "..") Specifically, the constructed target directory names must be meaningful and distinct from the source directory names, otherwise running recovery in the target directory might corrupt the source data files. .PP \fBIt is an error to use absolute pathnames for data directories or the log directory in this mode, as the DB_CONFIG configuration file copied into the target directory would then point at the source directories and running recovery would corrupt the source data files.\fR .PP The db5.2_hotbackup utility uses a Berkeley DB environment (as described for the \fB\-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_hotbackup should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_hotbackup to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_hotbackup utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Oracle Corporation. This manual page was created based on the HTML documentation for db_hotbackup from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_upgrade.10000644000000000000000000000773311706537004013401 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_UPGRADE 1 "28 January 2005" .SH NAME db5.2_upgrade \- Upgrade the Berkeley DB version to the current release version. .SH SYNOPSIS .B db5.2_upgrade [-NsVv] [-h home] [-P password] file ... .SH DESCRIPTION The db5.2_upgrade utility upgrades the Berkeley DB version of one or more files and the databases they contain to the current release version. .SH OPTIONS .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-N\fR Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-s\fR This flag is only meaningful when upgrading databases from releases before the Berkeley DB 3.1 release. .sp As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release, the on-disk format of duplicate data items changed. To correctly upgrade the format requires that applications specify whether duplicate data items in the database are sorted or not. Specifying the \fB-s\fR flag means that the duplicates are sorted; otherwise, they are assumed to be unsorted. Incorrectly specifying the value of this flag may lead to database corruption. .sp Because the db5.2_upgrade utility upgrades a physical file (including all the databases it contains), it is not possible to use db5.2_upgrade to upgrade files where some of the databases it includes have sorted duplicate data items, and some of the databases it includes have unsorted duplicate data items. If the file does not have more than a single database, if the databases do not support duplicate data items, or if all the databases that support duplicate data items support the same style of duplicates (either sorted or unsorted), db5.2_upgrade will work correctly as long as the \fB-s\fR flag is correctly specified. Otherwise, the file cannot be upgraded using db5.2_upgrade, and must be upgraded manually using the db5.2_dump and db5.0_load utilities. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode, displaying a message for each successful upgrade. .PP \fBIt is important to realize that Berkeley DB database upgrades are done in place, and so are potentially destructive.\fR This means that if the system crashes during the upgrade procedure, or if the upgrade procedure runs out of disk space, the databases may be left in an inconsistent and unrecoverable state. .PP The db5.2_upgrade utility may be used with a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_upgrade should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_upgrade to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_upgrade utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_upgrade from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_codegen.10000644000000000000000000002105011706537004013342 0ustar .\" Copyright \(co 2010 by Thorsten Glaser .\" .\" .\" .\" .Dd January 12, 2011 .Dt DB5.2_CODEGEN 1 .Os "Berkeley DB" .Sh NAME .Nm db5.2_codegen .Nd generate application code for Berkeley DB .Sh SYNOPSIS .Nm .Op Fl Vv .Op Fl a Ar api .Op Fl i Ar file .Op Fl o Ar prefix .Sh DESCRIPTION The .Nm utility generates application code to create and configure Berkeley DB database environments and databases based on a simple description language and writes it to one or more output files. The generated code may need modification, in the case of complicated applications, but will usually significantly reduce the time required to create Berkeley DB applications. .Pp The options are as follows: .Bl -tag -width XXX .It Fl a Ar api Generate code for the specified API .Pq currently, only Do c Dc is accepted . .It Fl i Ar file Specify an input .Ar file ; by default, standard input is used. .It Fl o Ar prefix Specify an output file .Ar prefix ; by default, .Dq application is used. .It Fl V Write the library version number to standard output and exit. .It Fl v Run in verbose mode. .El .Pp The .Nm utility exits 0 on success, and >0 if an error occurs. .Sh C Language Specific Information By default, when the .Nm utility generates C-language code, the output file is named .Dq Pa application.c . The output filename can be specified with the .Fl o option. .Pp At the beginning of the output file is a list of public database environment .Pq Vt DB_ENV handles and database .Pq Vt DB handles, as specified by the description language. The database environment handle variables are named .Dq Ar XXX Ns _dbenv , where .Dq Ar XXX is the name of the environment in the input specification. For databases associated with a database environment, the database handle variables are named .Dq Ar XXX Ns _ Ns Ar YYY , where .Dq Ar XXX is the name of the environment, and .Dq Ar YYY is the name of the database. For standalone databases, the database handle variables are named .Dq Ar XXX , where .Dq Ar XXX is the name of the database. .Pp There are two public functions in the output file: .Fn bdb_startup and .Fn bdb_shutdown . The .Fn bdb_startup function should be called to create and configure the database environments and databases, and the .Fn bdb_shutdown function should be called to gracefully shut down the environments and databases. .Sh Specification Language The .Nm uses a simple description language: .Pp .Bl -bullet -compact .It Lines in the input consist of white-space separated tokens. .It Tokens are case-insensitive. .It Empty lines and lines where the first non-space character is a hash mark .Pq Dq \&# are ignored. In addition, hash marks may appear in lines, in which case the content of the line from the hash mark to the end of the line is ignored. .El .Pp There are two top-level objects: .Dq environment and .Dq database , which correspond to database environments and databases, respectively. These top-level objects can be associated with keywords to describe their configuration and relationships. .Pp For example, the following input would create two standalone databases: .Bd -literal -offset indent database data_one { type btree } database data_two { type btree } .Ed .Pp In this case, there would be no .Vt DB_ENV handle, and the public .Vt DB handles would be: .Bd -literal -offset indent DB *data_one; DB *data_two; .Ed .Pp For example, the following input would create a database environment which contains three databases: .Bd -literal -offset indent environment myenv { database data_one { type btree } database data_two { type btree } database data_three { type btree } } .Ed .Pp In this case, the public .Vt DB_ENV and .Vt DB handles would be: .Bd -literal -offset indent DB_ENV *myenv_dbenv; DB *myenv_data_one; DB *myenv_data_two; DB *myenv_data_three; .Ed .Pp A variety of keywords can be specified for the databases and the environments. For example, the cache size can be specified for the database environment, and the page size can be specified for the database, as well as for secondary relationships: .Bd -literal -offset indent environment myenv { cachesize 2 0 10 database data_one { type btree pagesize 1024 } database data_two { primary data_one secondary_offset 10 15 type btree pagesize 32768 } database data_three { type btree pagesize 512 } } .Ed .Ss Environment Keywords .Bl -tag -width secondary_offset .It Ic environment Start a database environment block. .Pp There must be three tokens on the line: the keyword, the name of the environment and an opening brace .Pq Dq \&{ . .It Ic home Specify the database environment home directory. .Pp There must be two tokens on the line: the keyword and the home directory. .It Ic cachesize Specify the database environment cache size. .Pp There must be two tokens on the line: the keyword, the gigabytes of cache, the bytes of cache, and the number of caches (the number of underlying physical areas into which the cache is logically divided). .It Ic private Specify the database environment is private. .Pp There must be one token on the line: the keyword by itself. .It Ic \&} End the database environment block. .Pp There must be one token on the line: the keyword by itself. .El .Ss Database Keywords .Bl -tag -width secondary_offset .It Ic database Start a database block. .Pp There must be three tokens on the line: the keyword, the name of the database and an opening brace .Pq Dq \&{ . .It Ic custom Specify a custom key-comparison routine. This is used when the Btree database requires a specific sort that .Nm cannot generate. A stub key comparison routine will be created and configured for the database which should be modified as necessary. See the .Dq Ic key_type keyword for more information. .Pp There must be one token on the line: the keyword by itself. .It Ic dupsort Configure the database to support sorted duplicates. .Pp There must be one token on the line: the keyword by itself. .It Ic extentsize Configure the size of the Queue database extent files. .Pp There must be two tokens on the line: the keyword and the extent file size, as a number of pages. .It Ic key_type Configure a integral type key-comparison routine. This is used when the Btree database key is an integral type (such as .Dq Vt "unsigned int" or .Dq Vt u_int32_t ) . Any C-language integral type may be specified. See the .Dq Ic custom keyword for more information. A Btree comparison routine based on the type of the key will be created and configured. .Pp There must be two tokens on the line: the keyword and the type. .It Ic pagesize Configure the database page size. .Pp There must be two tokens on the line: the keyword and the page size in bytes. .It Ic primary Configure the database as a secondary index. A stub secondary callback routine will be created and configured for the database, which should be modified as necessary. See the .Dq Ic secondary_offset keyword for more information. .Pp There must be two tokens on the line: the keyword and the name of the primary database for which this database is a secondary. .It Ic recnum Configure the Btree database to support record number access. .Pp There must be one token on the line: the keyword by itself. .It Ic re_len Configure the record length for a Queue database or a fixed-length Recno database. .Pp There must be two tokens on the line: the keyword and the length of a record, in bytes. .Pp .It Ic secondary_offset Configure a secondary callback routine based on a byte string found in the primary database's data item. .Pp There must be three tokens on the line: the keyword, the byte offset from the beginning of the primary data item where the secondary key occurs, and the length of the secondary key in bytes. .It Ic transaction Configure the database (and, by extension, the database environment), to be transactional. .Pp There must be one token on the line: the keyword by itself. .It Ic type Configure the database type. .Pp There must be two tokens on the line: the keyword and the type, where the type is one of .Dq btree , .Dq hash , .Dq queue or .Dq recno . .It Ic \&} End the database environment block. .Pp There must be one token on the line: the keyword by itself. .El .Sh AUTHORS .An Thorsten Glaser Aq tg@debian.org wrote this manual page for the Debian project (but may be used by others) after the original HTML format documentation Copyright \(co 1996,2008 Oracle. All rights reserved. debian/manpages/db5.2_recover.10000644000000000000000000000762411706537004013416 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_RECOVER 1 "28 January 2005" .SH NAME db5.2_recover \- Restore the database to a consistent state .SH SYNOPSIS .B db5.2_recover [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]] .SH DESCRIPTION The db5.2_recover utility must be run after an unexpected application, Berkeley DB, or system failure to restore the database to a consistent state. All committed transactions are guaranteed to appear after db5.2_recover has run, and all uncommitted transactions will be completely undone. .SH OPTIONS .IP \fB\-c\fR Perform catastrophic recovery instead of normal recovery. .IP \fB\-e\fR Retain the environment after running recovery. This option will rarely be used unless a DB_CONFIG file is present in the home directory. If a DB_CONFIG file is not present, then the regions will be created with default parameter values. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-t\fR Recover to the time specified rather than to the most current possible date. The timestamp argument should be in the form [[CC]YY]MMDDhhmm[.SS] where each pair of letters represents the following: .RS .IP CC The first two digits of the year (the century). .IP YY The second two digits of the year. If "YY" is specified, but "CC" is not, a value for "YY" between 69 and 99 results in a "CC" value of 19. Otherwise, a "YY" value of 20 is used. .IP MM The month of the year, from 1 to 12. .IP DD The day of the month, from 1 to 31. .IP hh The hour of the day, from 0 to 23. .IP mm The minute of the hour, from 0 to 59. .IP SS The second of the minute, from 0 to 61. .RE .IP If the "CC" and "YY" letter pairs are not specified, the values default to the current year. If the "SS" letter pair is not specified, the value defaults to 0. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode. .PP In the case of catastrophic recovery, an archival copy - or \fIsnapshot\fR - of all database files must be restored along with all of the log files written since the database file snapshot was made. (If disk space is a problem, log files may be referenced by symbolic links). .PP If the failure was not catastrophic, the files present on the system at the time of failure are sufficient to perform recovery. .PP If log files are missing, db5.2_recover will identify the missing log file(s) and fail, in which case the missing log files need to be restored and recovery performed again. .PP The db5.2_recover utility uses a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_recover should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_recover to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_recover utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_recover from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_load.10000644000000000000000000002024111706537004012656 0ustar .\" Manual Page for Berkeley DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_LOAD 1 "22 November 2009" .SH NAME db5.2_load \- Load data from standard input .SH SYNOPSIS .B db5.2_load [-nTV] [-c name=value] [-f file] [-h home] [-P password] [-t btree | hash | queue | recno] file .B db5.2_load [-r lsn | fileid] [-h home] [-P password] file .SH DESCRIPTION The db5.2_load utility reads from the standard input and loads it into the database file. The database file is created if it does not already exist. .PP The input to db5.2_load must be in the output format specified by the db5.0_dump utility, utilities, or as specified for the -T below. .SH OPTIONS .IP \fB\-c\fR Specify configuration options ignoring any value they may have based on the input. The command-line format is \fBname=value\fR. See the Supported Keywords section below for a list of keywords supported by the \fB-c\fR option. .IP \fB\-f\fR Read from the specified \fBinput\fR file instead of from the standard input. .IP \fB\-h\fR Specify a home directory for the database environment. .sp If a home directory is specified, the database environment is opened using the DB_INIT_LOCK, DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, and DB_USE_ENVIRON flags to DB_ENV->open. (This means that db5.2_load can be used to load data into databases while they are in use by other processes.) If the DB_ENV->open call fails, or if no home directory is specified, the database is still updated, but the environment is ignored; for example, no locking is done. .IP \fB\-n\fR Do not overwrite existing keys in the database when loading into an already existing database. If a key/data pair cannot be loaded into the database for this reason, a warning message is displayed on the standard error output, and the key/data pair are skipped. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-r\fR Reset the database's file ID or log sequence numbers (LSNs). .sp All database pages in transactional environments contain references to the environment's log records. In order to copy a database into a different database environment, database page references to the old environment's log records must be reset, otherwise data corruption can occur when the database is modified in the new environment. The \fB-r\fR \fBlsn\fR option resets a database's log sequence numbers. .sp All databases contain an ID string used to identify the database in the database environment cache. If a database is copied, and used in the same environment as another file with the same ID string, corruption can occur. The \fB-r\fR \fBfileid\fR option resets a database's file ID to a new value. .sp \fBIn both cases, the physical file specified by the file argument is modified in-place.\fR .IP \fB\-T\fR The \fB-T\fR option allows non-Berkeley DB applications to easily load text files into databases. .sp If the database to be created is of type Btree or Hash, or the keyword \fBkeys\fR is specified as set, the input must be paired lines of text, where the first line of the pair is the key item, and the second line of the pair is its corresponding data item. If the database to be created is of type Queue or Recno and the keyword \fBkeys\fR is not set, the input must be lines of text, where each line is a new data item for the database. .sp A simple escape mechanism, where newline and backslash (\\) characters are special, is applied to the text input. Newline characters are interpreted as record separators. Backslash characters in the text will be interpreted in one of two ways: If the backslash character precedes another backslash character, the pair will be interpreted as a literal backslash. If the backslash character precedes any other character, the two characters following the backslash will be interpreted as a hexadecimal specification of a single character; for example, \\0a is a newline character in the ASCII character set. .sp For this reason, any backslash or newline characters that naturally occur in the text input must be escaped to avoid misinterpretation by db5.2_load. .sp If the \fB-T\fR option is specified, the underlying access method type must be specified using the \fB-t\fR option. .IP \fB\-t\fR Specify the underlying access method. If no \fB-t\fR option is specified, the database will be loaded into a database of the same type as was dumped; for example, a Hash database will be created if a Hash database was dumped. .sp Btree and Hash databases may be converted from one to the other. Queue and Recno databases may be converted from one to the other. If the \fB-k\fR option was specified on the call to db5.2_dump then Queue and Recno databases may be converted to Btree or Hash, with the key being the integer record number. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .PP The db5.2_load utility may be used with a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_load should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_load to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_load utility exits 0 on success, 1 if one or more key/data pairs were not loaded into the database because the key already existed, and >1 if an error occurs. .SH EXAMPLES The db5.2_load utility can be used to load text files into databases. For example, the following command loads the standard UNIX \fI/etc/passwd\fR file into a database, with the login name as the key item and the entire password entry as the data item: .PP .TP 8 awk \-F: '{print $1; print $0}' < /etc/passwd | sed 's/\\\\/\\\\\\\\/g' | db5.2_load \-T \-t hash passwd.db .PP Note that backslash characters naturally occurring in the text are escaped to avoid interpretation as escape characters by db5.2_load. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH SUPPORTED KEYWORDS The following keywords are supported for the \fB-c\fR command-line ption to the db5.2_load utility. See DB->open for further discussion of these keywords and what values should be specified. .PP The parenthetical listing specifies how the value part of the \fBname=value\fR pair is interpreted. Items listed as (boolean) expect value to be \fB1\fR (set) or \fB0\fR (unset). Items listed as (number) convert value to a number. Items listed as (string) use the string value without modification. .IP "bt_minkey (number)" The minimum number of keys per page. .IP "chksum (boolean)" Enable page checksums. .IP "database (string)" The database to load. .IP "db_lorder (number)" The byte order for integers in the stored database metadata. .IP "db_pagesize (number)" The size of database pages, in bytes. .IP "duplicates (boolean)" The value of the DB_DUP flag. .IP "dupsort (boolean)" The value of the DB_DUPSORT flag. .IP "extentsize (number)" The size of database extents, in pages, for Queue databases configured to use extents. .IP "h_ffactor (number)" The density within the Hash database. .IP "h_nelem (number)" The size of the Hash database. .IP "keys (boolean)" Specify whether keys are present for Queue or Recno databases. .IP "re_len (number)" Specify fixed-length records of the specified length. .IP "re_pad (string)" Specify the fixed-length record pad character. .IP "recnum (boolean)" The value of the DB_RECNUM flag. .IP "renumber (boolean)" The value of the DB_RENUMBER flag. .IP "subdatabase (string)" The subdatabase to load. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_load from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/berkeley_db5.2_svc.10000644000000000000000000000510511706537004014416 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH BERKELEY_DB5.2_SVC 1 "28 January 2005" .SH NAME berkeley_db5.2_svc \- Berkeley DB RPC server .SH SYNOPSIS .B berkeley_db5.2_svc [-Vv] [-h home] [-I seconds] [-L file] [-t seconds] [-T seconds] .SH DESCRIPTION The berkeley_db5.2_svc utility is the Berkeley DB RPC server. .SH OPTIONS .IP \fB\-h\fR Add the specified home directory to the list of allowed home directories that can be specified by the client. The home directory should be an absolute pathname. The last component of each home directory specified must be unique because that is how clients specify which database environment they want to join. .sp Recovery will be run on each specified environment before the server begins accepting requests from clients. For this reason, only one copy of the server program should ever be run at any time because recovery must always be single-threaded. .IP \fB\-I\fR Set the default idle timeout for client environments to the specified number of seconds. The default timeout is 24 hours. .IP \fB\-L\fR Log the execution of the berkeley_db5.2_svc utility to the specified file in the following format, where \fI###\fR is the process ID, and the date is the time the utility was started. .sp berkeley_db5.2_svc: ### Wed Jun 15 01:23:45 EDT 1995 .sp This file will be removed if the berkeley_db5.2_svc utility exits gracefully. .IP \fB\-t\fR Set the default timeout for client resources (idle transactions and cursors) to the specified number of seconds. When the timeout expires, if the resource is a transaction, it is aborted; if the resource is a cursor, it is closed. The default timeout is 5 minutes. .IP \fB\-T\fR Set the maximum timeout allowed for client resources. The default timeout is 20 minutes. If a client application requests a server timeout greater than the maximum timeout set for this server, the client's timeout will be capped at the maximum timeout value. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Run in verbose mode. .PP The berkeley_db5.2_svc utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for berkeley_db_svc from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_dump.10000644000000000000000000001256211706537004012713 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_DUMP 1 "28 January 2005" .SH NAME db5.2_dump \- Write database to flat-text format .SH SYNOPSIS .B db5.2_dump [-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file .SH DESCRIPTION The db5.2_dump utility reads the database file file and writes it to the standard output using a portable flat-text format understood by the db5.2_load utility. The file argument must be a file produced using the Berkeley DB library functions. .SH OPTIONS .IP \fB\-d\fR Dump the specified database in a format helpful for debugging the Berkeley DB library routines. .RS .IP a Display all information. .IP h Display only page headers. .IP r Do not display the free-list or pages on the free list. This mode is used by the recovery tests. .RE .IP \fBThe output format of the -d option is not standard and may change, without notice, between releases of the Berkeley DB library.\fR .IP \fB\-f\fR Write to the specified \fBfile\fR instead of to the standard output. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-k\fR Dump record numbers from Queue and Recno databases as keys. .IP \fB\-l\fR List the databases stored in the file. .IP \fB\-N\fR Do not acquire shared region mutexes while running. Other problems, such as potentially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-p\fR If characters in either the key or data items are printing characters (as defined by \fBisprint\fR(3)), use printing characters in \fBfile\fR to represent them. This option permits users to use standard text editors and tools to modify the contents of databases. .sp Note: different systems may have different notions about what characters are considered \fIprinting characters\fR, and databases dumped in this manner may be less portable to external systems. .IP \fB\-R\fR Aggressively salvage data from a possibly corrupt file. The \fB-R\fR flag differs from the \fB-r\fR option in that it will return all possible data from the file at the risk of also returning already deleted or otherwise nonsensical items. Data dumped in this fashion will almost certainly have to be edited by hand or other means before the data is ready for reload into another database .IP \fB\-r\fR Salvage data from a possibly corrupt file. When used on a uncorrupted database, this option should return equivalent data to a normal dump, but most likely in a different order. .IP \fB\-s\fR Specify a single database to dump. If no database is specified, all databases in the database file are dumped. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .PP Dumping and reloading Hash databases that use user-defined hash functions will result in new databases that use the default hash function. Although using the default hash function may not be optimal for the new database, it will continue to work correctly. .PP Dumping and reloading Btree databases that use user-defined prefix or comparison functions will result in new databases that use the default prefix and comparison functions. \fBIn this case, it is quite likely that the database will be damaged beyond repair permitting neither record storage or retrieval.\fR .PP The only available workaround for either case is to modify the sources for the db5.2_load utility to load the database using the correct hash, prefix, and comparison functions. .PP The db5.2_dump utility output format is documented in the Dump Output Formats section of the Berkeley DB Reference Guide. .PP The db5.2_dump utility may be used with a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_dump should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_dump to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP Even when using a Berkeley DB database environment, the db5.2_dump utility does not use any kind of database locking if it is invoked with the \fB-d\fR, \fB-R\fR, or \fB-r\fR arguments. If used with one of these arguments, the db5.2_dump utility may only be safely run on databases that are not being modified by any other process; otherwise, the output may be corrupt. .PP The db5.2_dump utility exits 0 on success, and >0 if an error occurs. .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_dump from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/manpages/db5.2_checkpoint.10000644000000000000000000000656111706537004014077 0ustar .\" Manual Page for Berkely DB utils, created from upstream .\" documentation by Thijs Kinkhorst . .TH DB5.2_CHECKPOINT 1 "28 January 2005" .SH NAME db5.2_checkpoint \- Periodically checkpoint transactions .SH SYNOPSIS .B db5.2_checkpoint [-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min] .SH DESCRIPTION The db5.2_checkpoint utility is a daemon process that monitors the database log, and periodically calls DB_ENV->txn_checkpoint to checkpoint it. .SH OPTIONS .IP \fB\-1\fR Checkpoint the log once, regardless of whether or not there has been activity since the last checkpoint and then exit. .IP \fB\-h\fR Specify a home directory for the database environment; by default, the current working directory is used. .IP \fB\-k\fR Checkpoint the database at least as often as every \fBkbytes\fR of log file are written. .IP \fB\-L\fR Log the execution of the db5.2_checkpoint utility to the specified file in the following format, where \fI###\fR is the process ID, and the date is the time the utility was started. .sp .TP 8 db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995 .sp This file will be removed if the db5.2_checkpoint utility exits gracefully. .IP \fB\-P\fR Specify an environment password. Although Berkeley DB utilities overwrite password strings as soon as possible, be aware there may be a window of vulnerability on systems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments. .IP \fB\-p\fR Checkpoint the database at least every \fBmin\fR minutes if there has been any activity since the last checkpoint. .IP \fB\-V\fR Write the library version number to the standard output, and exit. .IP \fB\-v\fR Write the time of each checkpoint attempt to the standard output. .PP At least one of the \fB-1\fR, \fB-k\fR, and \fB-p\fR options must be specified. .PP The db5.2_checkpoint utility uses a Berkeley DB environment (as described for the \fB-h\fR option, the environment variable \fBDB_HOME\fR, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db5.2_checkpoint should always be given the chance to detach from the environment and exit gracefully. To cause db5.2_checkpoint to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). .PP The db5.2_checkpoint utility does not attempt to create the Berkeley DB shared memory regions if they do not already exist. The application that creates the region should be started first, and once the region is created, the db5.2_checkpoint utility should be started. .PP The DB_ENV->txn_checkpoint method is the underlying method used by the db5.2_checkpoint utility. See the db_checkpoint utility source code for an example of using DB_ENV->txn_checkpoint in a IEEE/ANSI Std 1003.1 (POSIX) environment. .PP The db5.2_checkpoint utility exits 0 on success, and >0 if an error occurs. .PP .SH ENVIRONMENT .IP \fBDB_HOME\fR If the \fB-h\fR option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in DB_ENV->open. .SH AUTHORS Sleepycat Software, Inc. This manual page was created based on the HTML documentation for db_checkpoint from Sleepycat, by Thijs Kinkhorst , for the Debian system (but may be used by others). debian/runtests.tclsh0000644000000000000000000000236111706537004012121 0ustar #!/usr/bin/tclsh source ../test/test.tcl #run_std global one_test source ../test/include.tcl set one_test "ALL" set display 1 set run 1 fileremove -f ALL.OUT set o [open ALL.OUT a] puts -nonewline "Modified test suite run started at: " puts [clock format [clock seconds] -format "%H:%M %D"] puts [berkdb version -string] puts -nonewline $o "Modified test suite run started at: " puts $o [clock format [clock seconds] -format "%H:%M %D"] puts $o [berkdb version -string] close $o set test_list { {"environment" "env"} {"archive" "archive"} {"backup" "backup"} {"locking" "lock"} {"logging" "log"} {"memory pool" "memp"} {"transaction" "txn"} {"byte-order" "byte"} {"recno backing file" "rsrc"} {"DBM interface" "dbm"} {"NDBM interface" "ndbm"} {"Hsearch interface" "hsearch"} } #{"file operations" "fop"} #{"deadlock detection" "dead"} #{"subdatabase" "sdb"} #{"secondary index" "sindex"} foreach pair $test_list { set msg [lindex $pair 0] set cmd [lindex $pair 1] puts "Running $msg tests ([clock format [clock seconds] -format "%H:%M:%S"])" if [catch {exec /usr/bin/tclsh << \ "source ../test/test.tcl; r $cmd" \ >>& ALL.OUT } res] { set o [open ALL.OUT a] puts $o "FAIL: $cmd test: $res" close $o } }