Home
last modified time | relevance | path

Searched refs:again (Results 1 – 8 of 8) sorted by relevance

/redis-3.2.3/deps/jemalloc/src/
H A Dtsd.c42 bool pending[MALLOC_TSD_CLEANUPS_MAX], again; in _malloc_thread_cleanup() local
49 again = false; in _malloc_thread_cleanup()
54 again = true; in _malloc_thread_cleanup()
57 } while (again); in _malloc_thread_cleanup()
/redis-3.2.3/tests/integration/
H A Dreplication-2.tcl27 test {If min-slaves-to-write is honored, write is accepted (again)} {
/redis-3.2.3/deps/linenoise/
H A DREADME.markdown15 …or command line utilities. Instead of retyping almost the same stuff again and again it's just muc…
106 again and again the same things, but can use the down and up arrows in order
/redis-3.2.3/tests/unit/
H A Dkeyspace.tcl155 test {DEL all keys again (DB 0)} {
162 test {DEL all keys again (DB 1)} {
/redis-3.2.3/
H A D00-RELEASENOTES250 when it is reachable again, as the slave of the new master. This was due
301 reconfigure back old masters to slaves after they are reachable again
1210 | Linenoise updated again (hints support).
1266 a timer event (that is the time after it want to run again) is added
1268 than the time it says it want to be scheduled again for running, an
1411 Finally the command was proposed again in a clear form by
H A DREADME.md170 to run Redis properly as a background daemon that will start again on
/redis-3.2.3/deps/hiredis/
H A DREADME.md378 large payloads. The context should be set back to `REDIS_READER_MAX_BUF` again
/redis-3.2.3/deps/jemalloc/include/jemalloc/internal/
H A Djemalloc_internal.h.in1063 /* Try again, without extra this time. */