| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
At least FreeBSD has perl in /usr/local/bin/perl and no symlink by
default.
|
| |
|
|
|
|
| |
1. configure.ac - Add --disable-unix-socket to disable and define DISABLE_UNIX_SOCKET.
2. memcached.* - Guard all unix socket-related codes with DISABLE_UNIX_SOCKET. Take note of negative checking (#ifndef DISABLE_UNIX_SOCKET instead of #ifdef UNIX_SOCKET). This is just to make sure that current code even without a config file is the default or supports unix socket.
3. t/ - Check first if unix socket is supported before executing some unix socket-related tests.
|
| |
|
|
|
|
| |
this is helpful when it's required to identify which clients are
connected to which server address when memcached listens on
multiple addresses
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tests have randomly failed to start since the beginning of time, due largely
to port assignment. A random local port is tested, then passed onto the daemon
to try. If that port (on 0.0.0.0) becomes used in the meantime, it fails.
Now, tests default to using unix sockets unique to the pid of the test parent.
Some tests still run via the network and have been changed to 127.0.0.1, which
should collide less with normal internet connections. Some tests require that
due to some timing issues that unix sockets seem to create, and others expect
a network in a few cases.
Ran the tests with `PARALLEL=9 make test` on my machine for two hours and they
didn't fail once.
|
| | |
|
| | |
|
| | |
|
|
|
This is mostly for debugging purposes, e.g., to detect hung clients,
but the implementation also simplifies management of connection
descriptors by eliminating use of the freelist and allocating a
static pointer array indexed by descriptor. (The actual conn
structures are still allocated on demand, so the impact on memory
consumption is negligible.)
To be able to show multiple concurrent UDP requests, the UDP socket
is dup()ed so that each worker thread has its own UDP file descriptor
to process rather than all sharing a single one. This means the
server can handle slightly fewer TCP clients before running up
against its file descriptor limit, but any installation that's
running that close to the limit really ought to either raise the
limit or use a proxy of some kind anyway, so this should have no
real-world downside.
|
