diff options
| author | Sergey Poznyakoff <gray@gnu.org> | 2021-06-26 11:41:29 +0300 |
|---|---|---|
| committer | Sergey Poznyakoff <gray@gnu.org> | 2021-07-17 22:56:25 +0300 |
| commit | e95088c11c015623bdb7bd9d293e91162a86edcc (patch) | |
| tree | cc814bb0768cf6473f5e591e06344c17428df6d3 /NEWS | |
| parent | bdeab7e9b711126ac04b53a058e850a84bff9463 (diff) | |
| download | gdbm-e95088c11c015623bdb7bd9d293e91162a86edcc.tar.gz gdbm-e95088c11c015623bdb7bd9d293e91162a86edcc.tar.bz2 | |
Document crash tolerance API
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -12,8 +12,8 @@ By default it is possible for an abrupt crash (e.g., power failure, OS kernel panic, or application process crash) to corrupt the gdbm database file. A new Linux-only mechanism enables applications to recover the database state corresponding to the most recent -successful gdbm_sync() call before the crash. See file -"README_crash_tolerance.txt". +successful gdbm_sync() call before the crash. See the chapter 15 +"Crash Tolerance" in the GDBM manual. Version 1.20, 2021-06-17 |