<?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>Chapter 14. Programmer Notes</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 Programmer's Reference Guide" />
<link rel="up" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
<link rel="prev" href="apprec_config.html" title="Application configuration" />
<link rel="next" href="program_errorret.html" title="Error returns to applications" />
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Chapter 14.
Programmer Notes
</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="apprec_config.html">Prev</a> </td>
<th width="60%" align="center"> </th>
<td width="20%" align="right"> <a accesskey="n" href="program_errorret.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a id="program"></a>Chapter 14.
Programmer Notes
</h2>
</div>
</div>
</div>
<div class="toc">
<p>
<b>Table of Contents</b>
</p>
<dl>
<dt>
<span class="sect1">
<a href="program.html#program_appsignals">Signal handling</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_errorret.html">Error returns to applications</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_environ.html">Environment variables</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_mt.html">Multithreaded applications</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_scope.html">Berkeley DB handles</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_namespace.html">Name spaces</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="program_namespace.html#id1619264">C Language Name Space</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="program_namespace.html#id1619124">Filesystem Name Space</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="program_ram.html">Memory-only or Flash configurations</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_cache.html">Disk drive caches</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_copy.html">Copying or moving databases</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_compatible.html">Compatibility with historic UNIX interfaces</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_runtime.html">Run-time configuration</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="program_faq.html">Programmer notes FAQ</a>
</span>
</dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="program_appsignals"></a>Signal handling</h2>
</div>
</div>
</div>
<p>When applications using Berkeley DB receive signals, it is important that they
exit gracefully, discarding any Berkeley DB locks that they may hold. This is
normally done by setting a flag when a signal arrives and then checking
for that flag periodically within the application. Because Berkeley DB is not
re-entrant, the signal handler should not attempt to release locks and/or
close the database handles itself. Re-entering Berkeley DB is not guaranteed to
work correctly, and the results are undefined.</p>
<p>If an application exits holding a lock, the situation is no different
than if the application crashed, and all applications participating in
the database environment must be shut down, and then recovery must be
performed. If this is not done, databases may be left in an
inconsistent state, or locks the application held may cause unresolvable
deadlocks inside the environment, causing applications to hang.</p>
<p>Berkeley DB restarts all system calls interrupted by signals, that is, any
underlying system calls that return failure with errno set to EINTR will
be restarted rather than failing.</p>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="apprec_config.html">Prev</a> </td>
<td width="20%" align="center"> </td>
<td width="40%" align="right"> <a accesskey="n" href="program_errorret.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Application configuration </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Error returns to applications</td>
</tr>
</table>
</div>
</body>
</html>
