[53081] trunk/dports/databases/redis

jmr at macports.org jmr at macports.org
Sun Jun 28 21:24:22 PDT 2009


Revision: 53081
          http://trac.macports.org/changeset/53081
Author:   jmr at macports.org
Date:     2009-06-28 21:24:21 -0700 (Sun, 28 Jun 2009)
Log Message:
-----------
redis: update to 0.900 (#19970)

Modified Paths:
--------------
    trunk/dports/databases/redis/Portfile
    trunk/dports/databases/redis/files/redis-daemon.conf.sample.in
    trunk/dports/databases/redis/files/redis.conf.sample.in

Modified: trunk/dports/databases/redis/Portfile
===================================================================
--- trunk/dports/databases/redis/Portfile	2009-06-29 04:18:00 UTC (rev 53080)
+++ trunk/dports/databases/redis/Portfile	2009-06-29 04:24:21 UTC (rev 53081)
@@ -4,12 +4,14 @@
 PortSystem              1.0
 
 name                    redis
-version                 0.096
+version                 0.900
 categories              databases
 maintainers             gmail.com:brianjlandau openmaintainer
 homepage                http://code.google.com/p/redis/
 platforms               darwin
 master_sites            googlecode
+distname                ${name}-${version}_2
+worksrcdir              ${name}-${version}
 
 description             A persistent key-value database with built-in net \
                         interface written in ANSI-C for POSIX systems
@@ -28,9 +30,9 @@
                         includes initial support for master-slave replication \
                         in order to solve this problem by redundancy).
 
-checksums               md5     2f38efd3d2f6b4f7d61c3b761ae4a42c \
-                        sha1    51beeea696fff1a220aaed69216192e485e9ade9 \
-                        rmd160  5b3e52ddf3bbeb153f6e2ddd2616e562a12d9133
+checksums               md5     15ecbb37ba74b455ddfd5995730506bc \
+                        sha1    2d84ce062deba50bfdee5f2b4dbaccbb358f7a04 \
+                        rmd160  6bc2ad3a11dd39c5b04e9718e8a4c8794682da19
 
 use_configure           no
 

Modified: trunk/dports/databases/redis/files/redis-daemon.conf.sample.in
===================================================================
--- trunk/dports/databases/redis/files/redis-daemon.conf.sample.in	2009-06-29 04:18:00 UTC (rev 53080)
+++ trunk/dports/databases/redis/files/redis-daemon.conf.sample.in	2009-06-29 04:24:21 UTC (rev 53081)
@@ -16,7 +16,7 @@
 #
 # bind 127.0.0.1
 
-# Close the connection after a client is idle for N seconds
+# Close the connection after a client is idle for N seconds (0 to disable)
 timeout 300
 
 # Save the DB on disk:
@@ -34,6 +34,9 @@
 save 300 10
 save 60 10000
 
+# The filename where to dump the DB
+dbfilename dump.rdb
+
 # For default save/load DB in/from the working directory
 # Note that you must specify a directory not a file name.
 dir @PREFIX@/var/db/redis
@@ -50,7 +53,9 @@
 # output for logging but daemonize, logs will be sent to /dev/null
 logfile @PREFIX@/var/log/redis.log
 
-# Set the number of databases.
+# Set the number of databases. The default database is DB 0, you can select
+# a different one on a per-connection basis using SELECT <dbid> where
+# dbid is a number between 0 and 'databases'-1
 databases 16
 
 ################################# REPLICATION #################################
@@ -73,6 +78,35 @@
 
 # requirepass foobared
 
+################################### LIMITS ####################################
+
+# Set the max number of connected clients at the same time. By default there
+# is no limit, and it's up to the number of file descriptors the Redis process
+# is able to open. The special value '0' means no limts.
+# Once the limit is reached Redis will close all the new connections sending
+# an error 'max number of clients reached'.
+
+# maxclients 128
+
+# Don't use more memory than the specified amount of bytes.
+# When the memory limit is reached Redis will try to remove keys with an
+# EXPIRE set. It will try to start freeing keys that are going to expire
+# in little time and preserve keys with a longer time to live.
+# Redis will also try to remove objects from free lists if possible.
+#
+# 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
+# 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>
+
 ############################### ADVANCED CONFIG ###############################
 
 # Glue small output buffers together in order to send small replies in a
@@ -84,4 +118,15 @@
 # string in your dataset, but performs lookups against the shared objects
 # pool so it uses more CPU and can be a bit slower. Usually it's a good
 # idea.
+#
+# When object sharing is enabled (shareobjects yes) you can use
+# shareobjectspoolsize to control the size of the pool used in order to try
+# object sharing. A bigger pool size will lead to better sharing capabilities.
+# In general you want this value to be at least the double of the number of
+# very common strings you have in your dataset.
+#
+# WARNING: object sharing is experimental, don't enable this feature
+# in production before of Redis 1.0-stable. Still please try this feature in
+# your development environment so that we can test it better.
 shareobjects no
+# shareobjectspoolsize 1024

Modified: trunk/dports/databases/redis/files/redis.conf.sample.in
===================================================================
--- trunk/dports/databases/redis/files/redis.conf.sample.in	2009-06-29 04:18:00 UTC (rev 53080)
+++ trunk/dports/databases/redis/files/redis.conf.sample.in	2009-06-29 04:24:21 UTC (rev 53081)
@@ -1,4 +1,4 @@
-# Redis Daemon configuration file example
+# Redis configuration file example
 
 # By default Redis does not run as a daemon. Use 'yes' if you need it.
 # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
@@ -16,7 +16,7 @@
 #
 # bind 127.0.0.1
 
-# Close the connection after a client is idle for N seconds
+# Close the connection after a client is idle for N seconds (0 to disable)
 timeout 300
 
 # Save the DB on disk:
@@ -34,6 +34,9 @@
 save 300 10
 save 60 10000
 
+# The filename where to dump the DB
+dbfilename dump.rdb
+
 # For default save/load DB in/from the working directory
 # Note that you must specify a directory not a file name.
 dir @PREFIX@/var/db/redis
@@ -50,7 +53,9 @@
 # output for logging but daemonize, logs will be sent to /dev/null
 logfile stdout
 
-# Set the number of databases.
+# Set the number of databases. The default database is DB 0, you can select
+# a different one on a per-connection basis using SELECT <dbid> where
+# dbid is a number between 0 and 'databases'-1
 databases 16
 
 ################################# REPLICATION #################################
@@ -73,6 +78,35 @@
 
 # requirepass foobared
 
+################################### LIMITS ####################################
+
+# Set the max number of connected clients at the same time. By default there
+# is no limit, and it's up to the number of file descriptors the Redis process
+# is able to open. The special value '0' means no limts.
+# Once the limit is reached Redis will close all the new connections sending
+# an error 'max number of clients reached'.
+
+# maxclients 128
+
+# Don't use more memory than the specified amount of bytes.
+# When the memory limit is reached Redis will try to remove keys with an
+# EXPIRE set. It will try to start freeing keys that are going to expire
+# in little time and preserve keys with a longer time to live.
+# Redis will also try to remove objects from free lists if possible.
+#
+# 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
+# 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>
+
 ############################### ADVANCED CONFIG ###############################
 
 # Glue small output buffers together in order to send small replies in a
@@ -84,4 +118,15 @@
 # string in your dataset, but performs lookups against the shared objects
 # pool so it uses more CPU and can be a bit slower. Usually it's a good
 # idea.
+#
+# When object sharing is enabled (shareobjects yes) you can use
+# shareobjectspoolsize to control the size of the pool used in order to try
+# object sharing. A bigger pool size will lead to better sharing capabilities.
+# In general you want this value to be at least the double of the number of
+# very common strings you have in your dataset.
+#
+# WARNING: object sharing is experimental, don't enable this feature
+# in production before of Redis 1.0-stable. Still please try this feature in
+# your development environment so that we can test it better.
 shareobjects no
+# shareobjectspoolsize 1024
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20090628/e1db4138/attachment-0001.html>


More information about the macports-changes mailing list