Software: Apache/2.0.54 (Unix) mod_perl/1.99_09 Perl/v5.8.0 mod_ssl/2.0.54 OpenSSL/0.9.7l DAV/2 FrontPage/5.0.2.2635 PHP/4.4.0 mod_gzip/2.0.26.1a 

uname -a: Linux snow.he.net 4.4.276-v2-mono-1 #1 SMP Wed Jul 21 11:21:17 PDT 2021 i686 

uid=99(nobody) gid=98(nobody) groups=98(nobody) 

Safe-mode: OFF (not secure)

/usr/doc/db-3.3.11/ref/env/   drwxr-xr-x
Free 318.37 GB of 458.09 GB (69.5%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     faq.html (2.43 KB)      -rw-r--r--

Berkeley DB Reference Guide: Environment

Environment FAQ

1. I'm using multiple processes to access an Berkeley DB database environment; is there any way to ensure that two processes don't run recovery at the same time, or that all processes have exited the database environment so that recovery can be run?

   It's the responsibility of the processes (and/or threads of control) using a Berkeley DB environment to ensure recovery is never performed if there are other processes running recovery or using an existing database environment. It would be great if Berkeley DB could solve this, but it requires a way to single-thread execution on a system, and there's rarely anything Berkeley DB can use for that purpose -- let alone a portable method.

   Most application suites solve this problem by writing a tiny watch program that recovers the database environment and then runs the processes that actually use the database environment to perform work. The watcher program then monitors the working processes, and if any of them exit badly for any reason, the watcher kills any remaining processes and restarts the cycle.

Copyright Sleepycat Software