- 20 Oct, 2011 1 commit
-
-
Salvatore Sanfilippo authored
Cleaned up redis root directory a tiny bit and changed links to github issues
-
- 19 Oct, 2011 3 commits
- 18 Oct, 2011 6 commits
-
-
Jan Oberst authored
-
Jan Oberst authored
-
Jan Oberst authored
-
Salvatore Sanfilippo authored
Memory leak in redis-check-dump
-
smly authored
-
antirez authored
Return from syncWithMaster() ASAP if the event fired but the instance is no longer a slave. This should fix Issue #145.
-
- 17 Oct, 2011 6 commits
- 14 Oct, 2011 3 commits
- 13 Oct, 2011 2 commits
- 10 Oct, 2011 6 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Unlink Unix socket file on shutdown
-
Nathan Florea authored
Added a configuration directive to allow a user to specify the permissions to be granted to the Unix socket file. I followed the format Pieter and Salvatore discusses in issue #85 ( https://github.com/antirez/redis/issues/85).
-
antirez authored
-
antirez authored
-
antirez authored
-
- 09 Oct, 2011 1 commit
-
-
Nathan Florea authored
-
- 08 Oct, 2011 1 commit
-
-
antirez authored
Thanks to @ardsrk.
-
- 07 Oct, 2011 2 commits
- 05 Oct, 2011 6 commits
-
-
antirez authored
-
antirez authored
A node can populate a slot if a message from a trusted slot is received claiming ownership of this slot, that is currently empty or served by a node in FAIL state. However this feature was broken since calling clusterAddSlot() was not enough as the slot bit is already set in the node that pong us. We need to directly alter the table. This commit fixes the issue.
-
antirez authored
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
fixes to install scripts
-
- 04 Oct, 2011 3 commits
-
-
antirez authored
-
antirez authored
redisAssertWithClientInfo() is now redisAssertWithInfo() that is also able to report an optional object. The client is also optional. Specifying NULL will prevent dumping the not available information (either client or object).
-
antirez authored
Introduced a redisAssert() variant that is able to show information about the client in the context where the failed assertion was detected.
-