valgrind --track-origins=yes --suppressions=./src/valgrind.sup --show-reachable=no --show-possibly-lost=no --leak-check=full --log-file=err.txt ./src/redis-server test all
if grep -q 0x err.txt; then cat err.txt; exit 1; fi
@@ -15,10 +15,10 @@ Another good example is to think of Redis as a more complex version of memcached
...
@@ -15,10 +15,10 @@ Another good example is to think of Redis as a more complex version of memcached
If you want to know more, this is a list of selected starting points:
If you want to know more, this is a list of selected starting points:
* Introduction to Redis data types. http://redis.io/topics/data-types-intro
* Introduction to Redis data types. https://redis.io/topics/data-types-intro
* Try Redis directly inside your browser. http://try.redis.io
* Try Redis directly inside your browser. http://try.redis.io
* The full list of Redis commands. http://redis.io/commands
* The full list of Redis commands. https://redis.io/commands
* There is much more inside the official Redis documentation. http://redis.io/documentation
* There is much more inside the official Redis documentation. https://redis.io/documentation
Building Redis
Building Redis
--------------
--------------
...
@@ -49,7 +49,7 @@ To append a suffix to Redis program names, use:
...
@@ -49,7 +49,7 @@ To append a suffix to Redis program names, use:
% make PROG_SUFFIX="-alt"
% make PROG_SUFFIX="-alt"
You can run a 32 bit Redis binary using:
You can build a 32 bit Redis binary using:
% make 32bit
% make 32bit
...
@@ -184,7 +184,7 @@ then in another terminal try the following:
...
@@ -184,7 +184,7 @@ then in another terminal try the following:
(integer) 2
(integer) 2
redis>
redis>
You can find the list of all the available commands at http://redis.io/commands.
You can find the list of all the available commands at https://redis.io/commands.
Installing Redis
Installing Redis
-----------------
-----------------
...
@@ -294,19 +294,19 @@ the structure definition.
...
@@ -294,19 +294,19 @@ the structure definition.
Another important Redis data structure is the one defining a client.
Another important Redis data structure is the one defining a client.
In the past it was called `redisClient`, now just `client`. The structure
In the past it was called `redisClient`, now just `client`. The structure
has many fields, here we'll just show the main ones:
has many fields, here we'll just show the main ones:
```c
struct client {
structclient{
int fd;
intfd;
sds querybuf;
sdsquerybuf;
int argc;
intargc;
robj **argv;
robj**argv;
redisDb *db;
redisDb*db;
int flags;
intflags;
list *reply;
list*reply;
char buf[PROTO_REPLY_CHUNK_BYTES];
charbuf[PROTO_REPLY_CHUNK_BYTES];
... many other fields ...
// ... many other fields ...
}
}
```
The client structure defines a *connected client*:
The client structure defines a *connected client*:
* The `fd` field is the client socket file descriptor.
* The `fd` field is the client socket file descriptor.
...
@@ -453,7 +453,7 @@ Other C files
...
@@ -453,7 +453,7 @@ Other C files
*`scripting.c` implements Lua scripting. It is completely self-contained and isolated from the rest of the Redis implementation and is simple enough to understand if you are familiar with the Lua API.
*`scripting.c` implements Lua scripting. It is completely self-contained and isolated from the rest of the Redis implementation and is simple enough to understand if you are familiar with the Lua API.
*`cluster.c` implements the Redis Cluster. Probably a good read only after being very familiar with the rest of the Redis code base. If you want to read `cluster.c` make sure to read the [Redis Cluster specification][3].
*`cluster.c` implements the Redis Cluster. Probably a good read only after being very familiar with the rest of the Redis code base. If you want to read `cluster.c` make sure to read the [Redis Cluster specification][3].
createIntConfig("cluster-announce-bus-port",NULL,MODIFIABLE_CONFIG,0,65535,server.cluster_announce_bus_port,0,INTEGER_CONFIG,NULL,NULL),/* Default: Use +10000 offset. */
createIntConfig("cluster-announce-bus-port",NULL,MODIFIABLE_CONFIG,0,65535,server.cluster_announce_bus_port,0,INTEGER_CONFIG,NULL,NULL),/* Default: Use +10000 offset. */
createIntConfig("cluster-announce-port",NULL,MODIFIABLE_CONFIG,0,65535,server.cluster_announce_port,0,INTEGER_CONFIG,NULL,NULL),/* Use server.port */
createIntConfig("cluster-announce-port",NULL,MODIFIABLE_CONFIG,0,65535,server.cluster_announce_port,0,INTEGER_CONFIG,NULL,NULL),/* Use server.port */
createIntConfig("cluster-announce-tls-port",NULL,MODIFIABLE_CONFIG,0,65535,server.cluster_announce_tls_port,0,INTEGER_CONFIG,NULL,NULL),/* Use server.tls_port */