fluencelabs/redis
1
0
Fork 0
mirror of https://github.com/fluencelabs/redis synced 2025-03-19 09:00:51 +00:00
Code Issues Projects Releases Wiki Activity

minor fix for Solaris boxes

Browse Source
This commit is contained in:
antirez 2009-05-28 18:25:22 +02:00
parent 3fd78bcd45
commit 144d479b7c
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pqsort.c
View File

@ -37,6 +37,8 @@
* SUCH DAMAGE. * SUCH DAMAGE.
*/ */
#define __P(protos) protos
#include <sys/cdefs.h> #include <sys/cdefs.h>
#if defined(LIBC_SCCS) && !defined(lint) #if defined(LIBC_SCCS) && !defined(lint)
#if 0 #if 0

7
redis.conf
View File

@ -97,6 +97,13 @@ databases 16
# If all this fails, Redis will start to reply with errors to commands # If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue # that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET. # to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
# maxmemory <bytes> # maxmemory <bytes>