libdb/docs/upgrading/upgrade_3_1_sysmem.html
2012-11-14 16:35:20 -05:00

64 lines
2.9 KiB
HTML
Raw Permalink Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>DB_SYSTEM_MEM</title>
<link rel="stylesheet" href="gettingStarted.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Berkeley DB Upgrade Guide" />
<link rel="up" href="upgrade_3_1_toc.html" title="Chapter 13. Upgrading Berkeley DB 3.0 applications to Berkeley DB 3.1" />
<link rel="prev" href="upgrade_3_1_btstat.html" title="DB-&gt;stat" />
<link rel="next" href="upgrade_3_1_log_register.html" title="log_register" />
</head>
<body>
<div xmlns="" class="navheader">
<div class="libver">
<p>Library Version 11.2.5.3</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">DB_SYSTEM_MEM</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="upgrade_3_1_btstat.html">Prev</a> </td>
<th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 3.0 applications to Berkeley DB 3.1</th>
<td width="20%" align="right"> <a accesskey="n" href="upgrade_3_1_log_register.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="upgrade_3_1_sysmem"></a>DB_SYSTEM_MEM</h2>
</div>
</div>
</div>
<p>Using the <a href="../api_reference/C/envopen.html#envopen_DB_SYSTEM_MEM" class="olink">DB_SYSTEM_MEM</a> option on UNIX systems now requires the
specification of a base system memory segment ID, using the
<a href="../api_reference/C/envset_shm_key.html" class="olink">DB_ENV-&gt;set_shm_key()</a> method. Any valid segment ID may be specified, for
example, one returned by the UNIX <code class="literal">ftok</code>(3) function.</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="upgrade_3_1_btstat.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="upgrade_3_1_toc.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="upgrade_3_1_log_register.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">DB-&gt;stat </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> log_register</td>
</tr>
</table>
</div>
</body>
</html>