<!--$Id: env_remove.so,v 11.17 2002/08/18 21:17:29 bostic Exp $--> <!--$Id: m4.tcl,v 11.28 2004/12/16 19:13:05 bostic Exp $--> <!--Copyright (c) 1997,2007 Oracle. All rights reserved.--> <!--See the file LICENSE for redistribution information.--> <html> <head> <title>Berkeley DB: berkdb envremove</title> <meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> <meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> </head> <body bgcolor=white> <table width="100%"><tr valign=top> <td> <h3><b>berkdb envremove</b></h3> </td> <td align=right> <a href="../api_tcl/api_tcl.html"><img src="../images/api.gif" alt="API"></a> <a href="../ref/toc.html"><img src="../images/ref.gif" alt="Ref"></a></td> </tr></table> <hr size=1 noshade> <tt> <h3><pre>berkdb envremove [-data_dir directory] [-force] [-home directory] [-log_dir directory] [-tmp_dir directory] [-use_environ] [-use_environ_root] </pre></h3> <h3>Description(berkdb envremove)</h3> <p>Remove a Berkeley DB environment.</p> <p>The options are as follows:</p> <dl compact> <dt>-data_dir dirname<dd>Specify the environment's data directory, as described in <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. <dt>-force<dd>If there are processes that have called <b>berkdb env</b> without calling <i>env</i> <b>close</b> (that is, there are processes currently using the environment), <b>berkdb envremove</b> will fail without further action, unless the <b>-force</b> flag is set, in which case <b>berkdb envremove</b> will attempt to remove the environment regardless of any processes still using it. <dt>-home directory<dd>The <b>-home</b> argument is described in <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. <dt>-log_dir dirname<dd>Specify the environment's log directory, as described in <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. <dt>-tmp_dir dirname<dd>Specify the environment's tmp directory, as described in <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. <dt>-use_environ<dd>The Berkeley DB process' environment may be permitted to specify information to be used when naming files; see <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. Because permitting users to specify which files are used can create security problems, environment information will be used in file naming for all users only if the <b>-use_environ</b> flag is set. <dt>-use_environ_root<dd>The Berkeley DB process' environment may be permitted to specify information to be used when naming files; see <a href="../ref/env/naming.html">Berkeley DB File Naming</a>. As permitting users to specify which files are used can create security problems, if the <b>-use_environ_root</b> flag is set, environment information will be used for file naming only for users with appropriate permissions (for example, users with a user-ID of 0 on IEEE/ANSI Std 1003.1 (POSIX) systems). </dl> <p>The <b>berkdb envremove</b> command returns 0 on success, and in the case of error, a Tcl error is thrown.</p> </tt> <table width="100%"><tr><td><br></td><td align=right> <a href="../api_tcl/api_tcl.html"><img src="../images/api.gif" alt="API"></a><a href="../ref/toc.html"><img src="../images/ref.gif" alt="Ref"></a> </td></tr></table> <p><font size=1>Copyright (c) 1996,2007 Oracle. All rights reserved.</font> </body> </html>