head 1.2;
access;
symbols
RPM_4_2_1:1.1.1.5
RPM_4_2:1.1.1.5
RPM_4_1_1:1.1.1.5
RPM_4_1:1.1.1.4
RPM_4_0_5:1.1.1.3
RPM_4_0_4:1.1.1.2
RPM_4_0_3:1.1.1.1
RPM:1.1.1;
locks; strict;
comment @# @;
1.2
date 2008.01.02.09.56.10; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.38; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.13; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.04; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.07.23.20.09.19; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.05.00; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: Release 3.1: DB_SYSTEM_MEM
- Berkeley DB Reference Guide:
- Upgrading Berkeley DB Applications
|
  
|
Release 3.1: DB_SYSTEM_MEM
Using the DB_SYSTEM_MEM option on UNIX systems now requires the
specification of a base system memory segment ID, using the
DB_ENV->set_shm_key function. Any valid segment ID may be specified, for
example, one returned by the UNIX ftok(3) interface.
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d2 1
a2 1
a3 1
d19 1
a19 1
DB_ENV->set_shm_key method. Any valid segment ID may be specified, for
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d2 1
a2 1
d4 1
d20 1
a20 1
DB_ENV->set_shm_key function. Any valid segment ID may be specified, for
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d2 1
a2 1
a3 1
d19 1
a19 1
DB_ENV->set_shm_key method. Any valid segment ID may be specified, for
@