/dports/databases/db18/db-18.1.40/test/tcl/ |
H A D | env030.tcl | 34 -msgfile $testdir/msgfile -failchk -isalive my_isalive] 55 set ret [$dbenv failchk] 65 set ret [$dbenv failchk] 74 -home $testdir -failchk -isalive my_isalive] 89 set ret [catch { $dbenv failchk } res]
|
H A D | envscript.tcl | 37 set failchk [lindex $argv 6 ] 47 if {$failchk == "FAILCHK0" } { 50 if {$failchk == "FAILCHK1"} {
|
H A D | env030script.tcl | 82 error_check_good failchk [$dbenv failchk] 0
|
H A D | TESTS | 221 6. Verify process cannot connect when specifying -failchk and an 225 and -failchk and having specified an isalive function 228 with "-register -failchk -recover" 237 instead it would mean failchk could not recover. 405 Test failchk. 410 1. Open environment with is_alive function and failchk. 412 3. Test that failchk works when another process: exits cleanly, 415 4. Test that failchk returns RUNRECOVER when another process: 417 a mutex, and crashes while performing failchk. 2502 4. RepMgr can be started with -failchk and -isalive. [all …]
|
/dports/databases/db5/db-5.3.28/test/tcl/ |
H A D | envscript.tcl | 37 set failchk [lindex $argv 6 ] 46 if {$failchk == "FAILCHK0" } { 49 if {$failchk == "FAILCHK1"} {
|
H A D | repmgr102.tcl | 129 $masterenv failchk
|
H A D | TESTS | 204 6. Verify process cannot connect when specifying -failchk and an 208 and -failchk and having specified an isalive function 211 with "-register -failchk -recover" 213 9. 2nd process enters with "-register -failchk". Kill the 1st process. 215 3rd process can enter with "-register -recover -failchk". 3rd process 216 should run failchk, clear out open txn/log from process 1. It will 219 an indication that failchk ran. If DB_RUNRECOVERY were returned 220 instead it would mean failchk could not recover. 1917 Kill the listener process abruptly. Running failchk should show that
|
/dports/databases/db18/db-18.1.40/src/env/ |
H A D | env_failchk.c | 524 __env_in_failchk(env, failchk) in __env_in_failchk() argument 526 int *failchk; 533 *failchk = 0; 549 *failchk = 1;
|
/dports/databases/db18/db-18.1.40/test/c/ |
H A D | test_failchk.c | 63 void *failchk __P((void *)); 271 (ret = pthread_create(&tids[Nthreads], NULL, failchk, &i)) != 0) 828 failchk(arg) in failchk() function 848 if ((err = failenv->failchk(failenv, 0)) != 0) { 860 if ((err = failenv->failchk(failenv, 0)) != 0)
|
/dports/databases/db18/db-18.1.40/dist/aclocal/ |
H A D | options.m4 | 332 # Application which use failchk can choose to inform all threads waiting on 337 [Add support for immediately broadcasting failchk events to all waiting threads])], 343 [Define to 1 for failchk to inform all waiting threads about crashes.])
|
/dports/databases/db18/db-18.1.40/dist/ |
H A D | api_flags | 48 DB_FAILCHK # Run failchk on open 49 DB_FAILCHK_ISALIVE # UNDOC: failchk with isalive, for SQL 251 DB_SET_MUTEX_FAILCHK_TIMEOUT # Mutex support for failchk broadcasting
|
/dports/databases/mongodb36/mongodb-src-r3.6.23/src/third_party/wiredtiger/src/docs/ |
H A D | spell.ok | 224 failchk
|
/dports/lang/swi-pl/swipl-8.2.3/packages/bdb/ |
H A D | bdb.pl | 130 % - failchk(+Bool) 259 env_property(failchk(_)).
|
/dports/databases/db5/db-5.3.28/dist/ |
H A D | ChangeLog | 46 Fixed a race condition in the failchk code when cleaning up mutexes. [#21796] 349 Fix a race condition between DB_ENV->failchk() and the allocation of a mutex. [#21796]
|
H A D | api_flags | 46 DB_FAILCHK # Run failchk on open 47 DB_FAILCHK_ISALIVE # UNDOC: failchk with isalive, for SQL
|
/dports/archivers/rpm4/rpm-4.16.1.3/lib/backend/ |
H A D | db3.c | 512 rc = dbenv->failchk(dbenv, 0); in db_init() 589 rc = dbenv->failchk(dbenv, 0); in db3_dbiCursorInit()
|
/dports/databases/db5/db-5.3.28/lang/perl/BerkeleyDB/ |
H A D | BerkeleyDB.pod.P | 270 when the $env->failchk method will be used. It does not actually set the 478 used in combination with $env->failchk. 482 =item $env->failchk($flags) 484 The $env->failchk method checks for threads of control (either a true 490 If $env->failchk determines a thread of control exited while holding 491 database read locks, it will release those locks. If $env->failchk 495 Applications calling the $env->failchk method must have already called the
|
H A D | BerkeleyDB.pod | 270 when the $env->failchk method will be used. It does not actually set the 478 used in combination with $env->failchk. 482 =item $env->failchk($flags) 484 The $env->failchk method checks for threads of control (either a true 490 If $env->failchk determines a thread of control exited while holding 491 database read locks, it will release those locks. If $env->failchk 495 Applications calling the $env->failchk method must have already called the
|
H A D | Changes | 129 * Added failchk, set_isalive, lock_stat_print & mutex_stat_print.
|
/dports/databases/p5-BerkeleyDB/BerkeleyDB-0.64/ |
H A D | BerkeleyDB.pod.P | 281 when the $env->failchk method will be used. It does not actually set the 505 used in combination with $env->failchk. 509 =item $env->failchk($flags) 511 The $env->failchk method checks for threads of control (either a true 517 If $env->failchk determines a thread of control exited while holding 518 database read locks, it will release those locks. If $env->failchk 522 Applications calling the $env->failchk method must have already called the
|
H A D | BerkeleyDB.pod | 281 when the $env->failchk method will be used. It does not actually set the 505 used in combination with $env->failchk. 509 =item $env->failchk($flags) 511 The $env->failchk method checks for threads of control (either a true 517 If $env->failchk determines a thread of control exited while holding 518 database read locks, it will release those locks. If $env->failchk 522 Applications calling the $env->failchk method must have already called the
|
/dports/databases/db18/db-18.1.40/lang/perl/BerkeleyDB/ |
H A D | BerkeleyDB.pod.P | 281 when the $env->failchk method will be used. It does not actually set the 505 used in combination with $env->failchk. 509 =item $env->failchk($flags) 511 The $env->failchk method checks for threads of control (either a true 517 If $env->failchk determines a thread of control exited while holding 518 database read locks, it will release those locks. If $env->failchk 522 Applications calling the $env->failchk method must have already called the
|
H A D | BerkeleyDB.pod | 281 when the $env->failchk method will be used. It does not actually set the 505 used in combination with $env->failchk. 509 =item $env->failchk($flags) 511 The $env->failchk method checks for threads of control (either a true 517 If $env->failchk determines a thread of control exited while holding 518 database read locks, it will release those locks. If $env->failchk 522 Applications calling the $env->failchk method must have already called the
|
/dports/databases/db5/db-5.3.28/lang/java/libdb_java/ |
H A D | db.i | 705 db_ret_t failchk(u_int32_t flags) { in JAVA_EXCEPT() 706 return self->failchk(self, flags); in JAVA_EXCEPT()
|
/dports/databases/db18/db-18.1.40/lang/java/libdb_java/ |
H A D | db.i | 823 db_ret_t failchk(u_int32_t flags) { in JAVA_EXCEPT() 824 return self->failchk(self, flags); in JAVA_EXCEPT()
|