The memcached project use environment variables to tune the behaviour of the system (both for test programs and in production).
This document tries to list all the environment variables in use, and what they're used for.
This is a floating point and may be used to configure how often
malloc() / realloc() should return NULL.
This setting is only used if the BadMalloc allocator hook is enabled.
This is an unsigned integer used to allow the first N calls to
malloc() / realloc() to succeed.
This setting is only used if the BadMalloc allocator hook is enabled.
This is an unsigned integer used to specify a fixed seed for the random number generator which controls when to fail.
This setting is only used if the BadMalloc allocator hook is enabled.
CBSASL_PWFILE is used to tell cbsasl the location of the password
database in JSON format.
This variable is used by a unit test to have the config library simulate a memory allocation failure.
This variable is used by a unit test to have the config library simulate a failure reading stuff from disk.
Some of the command line tools will generate a packet dump if this variable is set.
Specify the list of ciphers allowed.
Variable set to identify that we're running the crash test (and allows) loading of the crash engine.
The number of CPU's to use for frontend threads.
The NUMA memory to use.
Set to indicate that we're running unit tests
Set to request memcached to stop (via SIGSTOP) at startup.
Set to indicate that we're running under valgrind
Used to fake a memory allocation in "default_bucket" (should not be used)
Used to tell "default_bucket" to preallocate memory (should not be used)
May be used to tell engine_testapp to retry failed tests.
May be set to let engine_testapp use colors in its output.
If set the logger will use 1GB file sizes
By setting this variable testapp dumps data sent/received in the old-style tests in the following format:
PLAIN> 0x80, 0xfd, 0x00, 0x00, 0x0c, 0x00, 0x00, 0x00, 0x00, ...
PLAIN< 0x81, 0xfd, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, ...