nutcracker 0.4.0.16 → 0.4.1.18

data/ext/nutcracker/notes/recommendation.md

@@ -2,7 +2,7 @@ If you are deploying nutcracker in your production environment, here are a few r
 
 ## Log Level
 
-By default debug logging is disabled in nutcracker. However, it is worthwhile running nutcracker with debug logging enabled and verbosity level set to LOG_INFO (-v 6 or --verbosity=6). This in reality does not add much overhead as you only pay the cost of checking an if condition for every log line encountered during the run time.
+By default debug logging is disabled in nutcracker. However, it is worthwhile running nutcracker with debug logging enabled and verbosity level set to LOG_INFO (-v 6 or --verbose=6). This in reality does not add much overhead as you only pay the cost of checking an if condition for every log line encountered during the run time.
 
 At LOG_INFO level, nutcracker logs the life cycle of every client and server connection and important events like the server being ejected from the hash ring and so on. Eg.
 
@@ -50,7 +50,7 @@ It is always a good idea to configure nutcracker `timeout:` for every server poo
 
 Relying only on client-side timeouts has the adverse effect of the original request having timedout on the client to proxy connection, but still pending and outstanding on the proxy to server connection. This further gets exacerbated when client retries the original request.
 
-By default, nutcracker waits indefinitely for any request sent to the server. However, when `timeout:` key is configured, a requests for which no response is received from the server in `timeout:` msec is timedout and an error response `SERVER_ERROR Connection timed out\r\n` is sent back to the client.
+By default, nutcracker waits indefinitely for any request sent to the server. However, when `timeout:` key is configured, a requests for which no response is received from the server in `timeout:` msec is timedout and an error response `SERVER_ERROR Connection timed out\r\n` (memcached) or `-ERR Connection timed out\r\n` (redis) is sent back to the client.
 
 ## Error Response
 
@@ -115,7 +115,7 @@ Note that when using node names for consistent hashing, twemproxy ignores the we
 
 [Hash Tags](http://antirez.com/post/redis-presharding.html) enables you to use part of the key for calculating the hash. When the hash tag is present, we use part of the key within the tag as the key to be used for consistent hashing. Otherwise, we use the full key as is. Hash tags enable you to map different keys to the same server as long as the part of the key within the tag is the same.
 
-For example, the configuration of server pool _beta_, aslo shown below, specifies a two character hash_tag string - "{}". This means that keys "user:{user1}:ids" and "user:{user1}:tweets" map to the same server because we compute the hash on "user1". For a key like "user:user1:ids", we use the entire string "user:user1:ids" to compute the hash and it may map to a different server.
+For example, the configuration of server pool _beta_, also shown below, specifies a two character hash_tag string - "{}". This means that keys "user:{user1}:ids" and "user:{user1}:tweets" map to the same server because we compute the hash on "user1". For a key like "user:user1:ids", we use the entire string "user:user1:ids" to compute the hash and it may map to a different server.
 
     beta:
       listen: 127.0.0.1:22122
@@ -130,8 +130,7 @@ For example, the configuration of server pool _beta_, aslo shown below, specifie
        - 127.0.0.1:6381:1 server2
        - 127.0.0.1:6382:1 server3
        - 127.0.0.1:6383:1 server4
-       
-       
+
 ## Graphing Cache-pool State
 
 When running nutcracker in production, you often would like to know the list of live and ejected servers at any given time. You can easily answer this question, by generating a time series graph of live and/or dead servers that are part of any cache pool. To do this your graphing client must collect the following stats exposed by nutcracker:
@@ -155,3 +154,9 @@ You can also graph the timestamp at which any given server was ejected by graphi
 By design, twemproxy multiplexes several client connections over few server connections. It is important to note that **"read my last write"** constraint doesn't necessarily hold true when twemproxy is configured with `server_connections: > 1`. 
 
 To illustrate this, consider a scenario where twemproxy is configured with `server_connections: 2`. If a client makes pipelined requests with the first request in pipeline being `set foo 0 0 3\r\nbar\r\n` (write) and the second request being `get foo\r\n` (read), the expectation is that the read of key `foo` would return the value `bar`. However, with configuration of two server connections it is possible that write and read request are sent on different server connections which would mean that their completion could race with one another. In summary, if the client expects "read my last write" constraint, you either configure twemproxy to use `server_connections:1` or use clients that only make synchronous requests to twemproxy.
+
+## twemproxy and python-memcached
+
+The implementation of delete command in [python-memcached](https://github.com/linsomniac/python-memcached) conflicts with the one in twemproxy. See [issue 283](https://github.com/twitter/twemproxy/pull/283) for details. The workaround for this issue is to call `delete_multi` in python-memcached as follows:
+
+        mc.delete_multi([key1, key2, ... keyN], time=None)

data/ext/nutcracker/notes/redis.md

@@ -39,7 +39,7 @@
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
     |      RESTORE      |    Yes     | RESTORE key ttl serialized-value                                                                                    |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
-    |      SORT         |    Yes*    | SORT key [BY pattern] [LIMIT offset count] [GET pattern [GET pattern ...]] [ASC|DESC] [ALPHA] [STORE destination]   |
+    |      SORT         |    Yes     | SORT key [BY pattern] [LIMIT offset count] [GET pattern [GET pattern ...]] [ASC|DESC] [ALPHA] [STORE destination]   |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
     |       TTL         |    Yes     | TTL key                                                                                                             |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
@@ -48,8 +48,6 @@
     |      SCAN         |    No      | SCAN cursor [MATCH pattern] [COUNT count]                                                                           |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
-* SORT support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for all keys in the command.
-
 ### Strings Command
 
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
@@ -176,7 +174,7 @@
     |      RPUSHX       |    Yes     | RPUSHX key value                                                                                                    |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
-* RPOPLPUSH support requires that source and destination keys hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for source and destination key. Twemproxy does no checking on its end to verify that source and destination key hash to the same server, and the RPOPLPUSH command is forwarded to the server that the source key hashes to
+* RPOPLPUSH support requires that source and destination keys hash to the same server. You can ensure this by using the same [hashtag](recommendation.md#hash-tags) for source and destination key. Twemproxy does no checking on its end to verify that source and destination key hash to the same server, and the RPOPLPUSH command is forwarded to the server that the source key hashes to
 
 ### Sets
 
@@ -214,7 +212,7 @@
     |      SSCAN        |    Yes     | SSCAN key cursor [MATCH pattern] [COUNT count]                                                                      |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
-* SIDFF, SDIFFSTORE, SINTER, SINTERSTORE, SMOVE, SUNION and SUNIONSTORE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
+* SIDFF, SDIFFSTORE, SINTER, SINTERSTORE, SMOVE, SUNION and SUNIONSTORE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
 
 
 ### Sorted Sets
@@ -263,7 +261,7 @@
     |      ZSCAN        |    Yes     | ZSCAN key cursor [MATCH pattern] [COUNT count]                                                                      |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
-* ZINTERSTORE and ZUNIONSTORE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
+* ZINTERSTORE and ZUNIONSTORE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
 
 ### HyperLogLog
 
@@ -277,7 +275,7 @@
     |      PFMERGE      |    Yes*    | PFMERGE destkey sourcekey [sourcekey ...]                                                                           |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
-* PFMERGE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
+* PFMERGE support requires that the supplied keys hash to the same server. You can ensure this by using the same [hashtag](recommendation.md#hash-tags) for all keys in the command. Twemproxy does no checking on its end to verify that all the keys hash to the same server, and the given command is forwarded to the server that the first key hashes to.
 
 
 ### Pub/Sub
@@ -330,7 +328,7 @@
     |    SCRIPT LOAD    |    No      | SCRIPT LOAD script                                                                                                  |
     +-------------------+------------+---------------------------------------------------------------------------------------------------------------------+
 
- * EVAL and EVALSHA support is limited to scripts that take at least 1 key. If multiple keys are used, all keys must hash to the same server. You can ensure this by using the same [hashtag](notes/recommendation.md#hash-tags) for all keys. If you use more than 1 key, the proxy does no checking to verify that all keys hash to the same server, and the entire command is forwarded to the server that the first key hashes to
+ * EVAL and EVALSHA support is limited to scripts that take at least 1 key. If multiple keys are used, all keys must hash to the same server. You can ensure this by using the same [hashtag](recommendation.md#hash-tags) for all keys. If you use more than 1 key, the proxy does no checking to verify that all keys hash to the same server, and the entire command is forwarded to the server that the first key hashes to
 
 ### Connection
 
@@ -399,7 +397,7 @@
 ## Note
 
 - redis commands are not case sensitive
-- only vectored commands 'MGET key [key ...]' and 'DEL key [key ...]' needs to be fragmented
+- only vectored commands 'MGET key [key ...]', 'MSET key value [key value ...]', 'DEL key [key ...]' needs to be fragmented
 
 ## Performance
 
@@ -445,3 +443,19 @@
     LRANGE_500 (first 450 elements): 8605.85 requests per second
     LRANGE_600 (first 600 elements): 6587.62 requests per second
 
+## redis-auth feature
+
++ you can enable redis-auth for a pool with 'redis_auth':
+
+        alpha:
+          listen: 127.0.0.1:22121
+          hash: fnv1a_64
+          distribution: ketama
+          redis: true
+          redis_auth: testpass
+
++ notice:
+    + *MUST* set all redis with a same passwd, and all twemproxy with the same passwd
+    + Length of password should less than 256 
+
+

data/ext/nutcracker/scripts/nutcracker.init

@@ -26,6 +26,16 @@ prog="nutcracker"
 
 start () {
     echo -n $"Starting $prog: "
+    #Test the config before start.
+    daemon --user ${USER} ${prog} $OPTIONS -t >/dev/null  2>&1
+    RETVAL=$?
+    if [ $RETVAL -ne 0 ] ; then
+        echo  "Config check fail! Please  use 'nutcracker -c /etc/nutcracker/nutcracker.yml' for detail."
+        echo_failure;
+        echo; 
+        exit 1 
+    fi
+
     daemon --user ${USER} ${prog} $OPTIONS
     RETVAL=$?
     echo

data/ext/nutcracker/scripts/nutcracker.init.debian

@@ -0,0 +1,83 @@
+#!/bin/sh
+### BEGIN INIT INFO
+# Provides:          nutcracker
+# Required-Start:    $network $remote_fs $local_fs
+# Required-Stop:     $network $remote_fs $local_fs
+# Default-Start:     2 3 4 5
+# Default-Stop:      0 1 6
+# Short-Description: Stop/start nutcracker
+### END INIT INFO
+
+PATH=/sbin:/usr/sbin:/bin:/usr/bin
+DESC=nutcracker
+NAME=nutcracker
+USER=nobody
+CONFFILE=/opt/nutcracker/etc/$NAME.yml
+LOGFILE=/opt/nutcracker/log/nutcracker.log
+DAEMON=/opt/nutcracker/sbin/nutcracker
+PIDFILE=/var/run/nutcracker/$NAME.pid
+STATSPORT=22222
+DAEMON_ARGS="-c $CONFFILE -o $LOGFILE -p $PIDFILE -s $STATSPORT -v 11 -m 2048 -d"
+#DAEMON_ARGS="-c $CONFFILE -p $PIDFILE -s $STATSPORT -d"
+SCRIPTNAME=/etc/init.d/$NAME
+
+ulimit -Hn 100000
+ulimit -Sn 100000
+
+[ -x $DAEMON ] || exit 0
+
+[ -r /etc/default/$NAME ] && . /etc/default/$NAME
+
+. /lib/init/vars.sh
+
+. /lib/lsb/init-functions
+
+do_start()
+{
+    mkdir -p /var/run/nutcracker
+    touch $PIDFILE
+    chown $USER:$USER -R /var/run/nutcracker
+    chmod 755 /var/run/nutcracker
+
+    echo -n "Starting ${NAME}: "
+    start-stop-daemon --start --quiet -m --pidfile $PIDFILE --chuid $USER:$USER --exec $DAEMON -- \
+        $DAEMON_ARGS
+        case "$?" in
+            0|1) echo "STARTED." ;;
+            2) echo "FAILED." ;;
+        esac
+}
+
+do_stop()
+{
+    echo -n "Stopping ${NAME}: "
+    start-stop-daemon --stop --quiet --pidfile $PIDFILE --exec $DAEMON || true
+
+    case "$?" in
+        0|1) echo "STOPPED.";;
+        2) echo "FAILED." ;;
+    esac
+}
+
+case "$1" in
+    start)
+        do_start
+    ;;
+    stop)
+        do_stop
+    ;;
+    status)
+      status_of_proc -p $PIDFILE "$DAEMON" nutcracker && exit 0 || exit $?
+    ;;
+    restart)
+      do_stop
+      do_start
+    ;;
+    *)
+        echo "Usage: $SCRIPTNAME {start|stop|status|restart}" >&2
+        exit 3
+        ;;
+esac
+
+exit
+$RETVAL

data/ext/nutcracker/scripts/nutcracker.spec

@@ -1,6 +1,6 @@
 Summary: Twitter's nutcracker redis and memcached proxy
 Name: nutcracker
-Version: 0.3.0
+Version: 0.4.1
 Release: 1
 
 URL: https://github.com/twitter/twemproxy/
@@ -16,7 +16,8 @@ BuildRequires: libtool
 
 %description
 twemproxy (pronounced "two-em-proxy"), aka nutcracker is a fast and lightweight proxy for memcached and redis protocol.
-It was primarily built to reduce the connection count on the backend caching servers.
+It was primarily built to reduce the connection count on the backend caching servers. This, together with protocol
+pipelining and sharding enables you to horizontally scale your distributed caching architecture.
 
 %prep
 %setup -q
@@ -65,6 +66,39 @@ fi
 %config(noreplace)%{_sysconfdir}/%{name}/%{name}.yml
 
 %changelog
+* Mon Jun 22 2015  Manju Rajashekhar  <manj@cs.stanford.edu>
+- twemproxy: version 0.4.1 release
+- redis_auth is only valid for a redis pool
+- getaddrinfo returns non-zero +ve value on error
+- fix-hang-when-command-only (charsyam)
+- fix bug crash when get command without key and whitespace (charsyam)
+- mark server as failed on protocol level transiet failures like -OOM, -LOADING, etc
+- implemented support for parsing fine grained redis error response
+- remove redundant conditional judgement in rbtree deletion (leo ma)
+- fix bug mset has invalid pair (charsyam)
+- fix bug mset has invalid pair (charsyam)
+- temp fix a core on kqueue (idning)
+- support "touch" command for memcached (panmiaocai)
+- fix redis parse rsp bug (charsyam)
+- SORT command can take multiple arguments. So it should be part of redis_argn() and not redis_arg0()
+- remove incorrect assert because client could send data after sending a quit request which must be discarded
+- allow file permissions to be set for UNIX domain listening socket (ori liveneh)
+- return error if formatted is greater than mbuf size by using nc_vsnprintf() in msg_prepend_format()
+- fix req_make_reply on msg_get, mark it as response (idning)
+- redis database select upon connect (arne claus)
+- redis_auth (charsyam)
+- allow null key(empty key) (idning)
+- fix core on invalid mset like "mset a a a" (idning)
+
+* Tue Oct 18 2014 idning <idning@gmail.com>
+- twemproxy: version 0.4.0 release
+- mget improve (idning)
+- many new commands supported: LEX, PFADD, PFMERGE, SORT, PING, QUIT, SCAN... (mattrobenolt, areina, idning)
+- handle max open file limit(allenlz)
+- add notice-log and use ms time in log(idning)
+- fix bug in string_compare (andyqzb)
+- fix deadlock in sighandler (idning)
+
 * Fri Dec 20 2013  Manju Rajashekhar  <manj@cs.stanford.edu>
 - twemproxy: version 0.3.0 release
 - SRANDMEMBER support for the optional count argument (mkhq)

data/ext/nutcracker/scripts/redis-check.sh

@@ -616,3 +616,7 @@ printf '*4\r\n$4\r\neval\r\n$10\r\nreturn 123\r\n$1\r\n1\r\n$1\r\n1\r\n' | socat
 printf '*7\r\n$4\r\neval\r\n$40\r\nreturn {KEYS[1],KEYS[2],ARGV[1],ARGV[2]}\r\n$1\r\n2\r\n$9\r\nkey1{tag}\r\n$4\r\narg1\r\n$9\r\nkey2{tag}\r\n$4\r\narg2\r\n' | socat ${debug} ${timeout} - TCP:localhost:${port},shut-close
 printf '*9\r\n$4\r\neval\r\n$56\r\nreturn {KEYS[1],KEYS[2],KEYS[3],ARGV[1],ARGV[2],ARGV[3]}\r\n$1\r\n3\r\n$9\r\nkey1{tag}\r\n$4\r\narg1\r\n$9\r\nkey2{tag}\r\n$4\r\narg2\r\n$9\r\nkey3{tag}\r\n$4\r\narg3\r\n' | socat ${debug} ${timeout} - TCP:localhost:${port},shut-close
 printf '*4\r\n$4\r\neval\r\n$11\r\nreturn {10}\r\n$1\r\n1\r\n$4\r\nTEMP\r\n' | socat ${debug} ${timeout} - TCP:localhost:${port},shut-close
+
+# quit
+printf '\nquit\n'
+printf '*1\r\n$4\r\nquit\r\n' | socat ${debug} ${timeout} - TCP:localhost:${port},shut-close

data/ext/nutcracker/src/Makefile.am

@@ -9,7 +9,9 @@ AM_CPPFLAGS += -I $(top_srcdir)/src/proto
 AM_CPPFLAGS += -I $(top_srcdir)/src/event
 AM_CPPFLAGS += -I $(top_srcdir)/contrib/yaml-0.1.4/include
 
-AM_CFLAGS =
+AM_CFLAGS = 
+# about -fno-strict-aliasing: https://github.com/twitter/twemproxy/issues/276
+AM_CFLAGS += -fno-strict-aliasing
 AM_CFLAGS += -Wall -Wshadow
 AM_CFLAGS += -Wpointer-arith
 AM_CFLAGS += -Winline
@@ -23,6 +25,9 @@ AM_LDFLAGS += -lm -lpthread -rdynamic
 if OS_SOLARIS
 AM_LDFLAGS += -lnsl -lsocket
 endif
+if OS_FREEBSD
+AM_LDFLAGS += -lexecinfo
+endif
 
 SUBDIRS = hashkit proto event
 

data/ext/nutcracker/src/Makefile.in

@@ -1,7 +1,7 @@
-# Makefile.in generated by automake 1.14.1 from Makefile.am.
+# Makefile.in generated by automake 1.15 from Makefile.am.
 # @configure_input@
 
-# Copyright (C) 1994-2013 Free Software Foundation, Inc.
+# Copyright (C) 1994-2014 Free Software Foundation, Inc.
 
 # This Makefile.in is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -15,7 +15,17 @@
 @SET_MAKE@
 
 VPATH = @srcdir@
-am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)'
+am__is_gnu_make = { \
+  if test -z '$(MAKELEVEL)'; then \
+    false; \
+  elif test -n '$(MAKE_HOST)'; then \
+    true; \
+  elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
+    true; \
+  else \
+    false; \
+  fi; \
+}
 am__make_running_with_option = \
   case $${target_option-} in \
       ?) ;; \
@@ -80,10 +90,9 @@ build_triplet = @build@
 host_triplet = @host@
 @OS_SOLARIS_FALSE@am__append_1 = -D_GNU_SOURCE
 @OS_SOLARIS_TRUE@am__append_2 = -lnsl -lsocket
+@OS_FREEBSD_TRUE@am__append_3 = -lexecinfo
 sbin_PROGRAMS = nutcracker$(EXEEXT)
 subdir = src
-DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \
-	$(top_srcdir)/config/depcomp
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
 	$(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
@@ -91,6 +100,7 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
 	$(top_srcdir)/configure.ac
 am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
 	$(ACLOCAL_M4)
+DIST_COMMON = $(srcdir)/Makefile.am $(am__DIST_COMMON)
 mkinstalldirs = $(install_sh) -d
 CONFIG_HEADER = $(top_builddir)/config.h
 CONFIG_CLEAN_FILES =
@@ -190,6 +200,7 @@ am__define_uniq_tagged_files = \
 ETAGS = etags
 CTAGS = ctags
 DIST_SUBDIRS = $(SUBDIRS)
+am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/config/depcomp
 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
 am__relativize = \
   dir0=`pwd`; \
@@ -259,6 +270,7 @@ LIBTOOL = @LIBTOOL@
 LIPO = @LIPO@
 LN_S = @LN_S@
 LTLIBOBJS = @LTLIBOBJS@
+LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@
 MAKEINFO = @MAKEINFO@
 MANIFEST_TOOL = @MANIFEST_TOOL@
 MKDIR_P = @MKDIR_P@
@@ -340,12 +352,13 @@ MAINTAINERCLEANFILES = Makefile.in
 AM_CPPFLAGS = $(am__append_1) -I $(top_srcdir)/src/hashkit -I \
 	$(top_srcdir)/src/proto -I $(top_srcdir)/src/event -I \
 	$(top_srcdir)/contrib/yaml-0.1.4/include
-AM_CFLAGS = -Wall -Wshadow -Wpointer-arith -Winline -Wunused-function \
-	-Wunused-variable -Wunused-value -Wno-unused-parameter \
-	-Wno-unused-value -Wconversion -Wsign-compare \
-	-Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls \
-	-Wmissing-declarations
-AM_LDFLAGS = -lm -lpthread -rdynamic $(am__append_2)
+# about -fno-strict-aliasing: https://github.com/twitter/twemproxy/issues/276
+AM_CFLAGS = -fno-strict-aliasing -Wall -Wshadow -Wpointer-arith \
+	-Winline -Wunused-function -Wunused-variable -Wunused-value \
+	-Wno-unused-parameter -Wno-unused-value -Wconversion \
+	-Wsign-compare -Wstrict-prototypes -Wmissing-prototypes \
+	-Wredundant-decls -Wmissing-declarations
+AM_LDFLAGS = -lm -lpthread -rdynamic $(am__append_2) $(am__append_3)
 SUBDIRS = hashkit proto event
 nutcracker_SOURCES = \
 	nc_core.c nc_core.h		\
@@ -388,7 +401,6 @@ $(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign src/Makefile'; \
 	$(am__cd) $(top_srcdir) && \
 	  $(AUTOMAKE) --foreign src/Makefile
-.PRECIOUS: Makefile
 Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
 	@case '$?' in \
 	  *config.status*) \
@@ -793,6 +805,8 @@ uninstall-am: uninstall-sbinPROGRAMS
 	mostlyclean-libtool pdf pdf-am ps ps-am tags tags-am uninstall \
 	uninstall-am uninstall-sbinPROGRAMS
 
+.PRECIOUS: Makefile
+
 
 # Tell versions [3.59,3.63) of GNU make to not export all variables.
 # Otherwise a system limit (for SysV at least) may be exceeded.

data/ext/nutcracker/src/event/Makefile.in

@@ -1,7 +1,7 @@
-# Makefile.in generated by automake 1.14.1 from Makefile.am.
+# Makefile.in generated by automake 1.15 from Makefile.am.
 # @configure_input@
 
-# Copyright (C) 1994-2013 Free Software Foundation, Inc.
+# Copyright (C) 1994-2014 Free Software Foundation, Inc.
 
 # This Makefile.in is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -16,7 +16,17 @@
 
 
 VPATH = @srcdir@
-am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)'
+am__is_gnu_make = { \
+  if test -z '$(MAKELEVEL)'; then \
+    false; \
+  elif test -n '$(MAKE_HOST)'; then \
+    true; \
+  elif test -n '$(MAKE_VERSION)' && test -n '$(CURDIR)'; then \
+    true; \
+  else \
+    false; \
+  fi; \
+}
 am__make_running_with_option = \
   case $${target_option-} in \
       ?) ;; \
@@ -80,8 +90,6 @@ POST_UNINSTALL = :
 build_triplet = @build@
 host_triplet = @host@
 subdir = src/event
-DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \
-	$(top_srcdir)/config/depcomp $(noinst_HEADERS)
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
 	$(top_srcdir)/m4/ltoptions.m4 $(top_srcdir)/m4/ltsugar.m4 \
@@ -89,6 +97,8 @@ am__aclocal_m4_deps = $(top_srcdir)/m4/libtool.m4 \
 	$(top_srcdir)/configure.ac
 am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
 	$(ACLOCAL_M4)
+DIST_COMMON = $(srcdir)/Makefile.am $(noinst_HEADERS) \
+	$(am__DIST_COMMON)
 mkinstalldirs = $(install_sh) -d
 CONFIG_HEADER = $(top_builddir)/config.h
 CONFIG_CLEAN_FILES =
@@ -169,6 +179,7 @@ am__define_uniq_tagged_files = \
   done | $(am__uniquify_input)`
 ETAGS = etags
 CTAGS = ctags
+am__DIST_COMMON = $(srcdir)/Makefile.in $(top_srcdir)/config/depcomp
 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
 ACLOCAL = @ACLOCAL@
 AMTAR = @AMTAR@
@@ -213,6 +224,7 @@ LIBTOOL = @LIBTOOL@
 LIPO = @LIPO@
 LN_S = @LN_S@
 LTLIBOBJS = @LTLIBOBJS@
+LT_SYS_LIBRARY_PATH = @LT_SYS_LIBRARY_PATH@
 MAKEINFO = @MAKEINFO@
 MANIFEST_TOOL = @MANIFEST_TOOL@
 MKDIR_P = @MKDIR_P@
@@ -316,7 +328,6 @@ $(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
 	echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign src/event/Makefile'; \
 	$(am__cd) $(top_srcdir) && \
 	  $(AUTOMAKE) --foreign src/event/Makefile
-.PRECIOUS: Makefile
 Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
 	@case '$?' in \
 	  *config.status*) \
@@ -584,6 +595,8 @@ uninstall-am:
 	mostlyclean-generic mostlyclean-libtool pdf pdf-am ps ps-am \
 	tags tags-am uninstall uninstall-am
 
+.PRECIOUS: Makefile
+
 
 # Tell versions [3.59,3.63) of GNU make to not export all variables.
 # Otherwise a system limit (for SysV at least) may be exceeded.