08:06:33 GMT hello. Had a problems building Redis with cross-gcc. 08:07:11 GMT found that line 27 of deps/hiredis/Makefile is unnecessary: 08:07:20 GMT CC:=$(shell sh -c 'type $(CC) >/dev/null 2>/dev/null && echo $(CC) || echo gcc') 08:07:49 GMT it's behaviour is different for different systems and it's not well-portable 08:08:32 GMT the other bad thing that you're using this kind of GCC detection only at this makefile, not in others. 08:09:26 GMT `type $GCC` gives an error if $GCC is complex string in mebedded SDK environment 08:09:43 GMT so to build Redis I just cut this line off 08:09:47 GMT the patch: 08:09:56 GMT diff -ur ./redis-stable.orig/deps/hiredis/Makefile ./redis-stable/deps/hiredis/Makefile --- ./redis-stable.orig/deps/hiredis/Makefile 2016-09-26 10:10:17.000000000 +0300 +++ ./redis-stable/deps/hiredis/Makefile 2016-10-06 11:04:38.960069985 +0300 @@ -24,7 +24,6 @@ export REDIS_TEST_CONFIG # Fallback to gcc when $CC is not in $PATH. -CC:=$(shell sh -c 'type $(CC) >/dev/null 2>/dev/null && echo $(CC) || echo gcc') OPTIMIZ 08:11:12 GMT http://pastebin.com/L9TSz3cA 13:17:28 GMT Hi guys. There is a redis instance running on a server at my job - how do i figure out which port it is running on? 13:18:48 GMT sry I was too quick to ask. a simple redis-cli told me :P 13:42:17 GMT anyone here familiar with redis master / slave replication? More specifically, I'm trying to test how replicating from a slave to another slave works. 13:42:54 GMT i set up slave 2 to replicate from slave1, who in turn is replicating from master. 13:43:09 GMT slave 1 and slave 2 are both currently running only in memory 13:43:15 GMT master persists to disk 13:43:36 GMT then as a test, I rebooted slave 2 to see what would happen / what I need to do to re-establish connection to slave 2 13:43:47 GMT sorry, what I need to do to re-establish connection to slave 1 13:44:41 GMT upon reboot, the database on slave 2 is empty... which i think is because slave 1 doesn't have a .rdb file 13:45:43 GMT but... what I'm wondering is if there's a way to "refresh" or force the connection. slave 1 never had a .rdb and yet i was able to - at least initially - set up slave 2 to replicate from slave 1 13:56:06 GMT hi all. false alarm. it was a firewall setting to open up port 6379 that didn't get properly re-applied to server after it rebooted. 13:57:06 GMT sorry for the noise. In case anyone is interested, I think I've proven to myself, that you can have in memory slave-to-slave replication survive reboots 14:09:20 GMT cpama: you configure slave stuff in the config anyway, so of course it survives reboots. redis doesn't rewrite the config file (unless using sentinel or explicitly calling config rewrite) 14:17:20 GMT hey minus! 14:20:47 GMT minus, before I realized it was a firewall misconfig... i started to wonder about what mechanism would be used for the slave to replicate from the other slave. i forgot about this:http://redis.io/topics/replication - the "diskless replication" section. 14:21:07 GMT in any case, it's all working and mostly just human error because I'm a noob 19:58:11 GMT hey, I can’t seem to find the answer in the manual 19:58:33 GMT but is there a way to run redis-cli monitor and only output the keys, not the values 23:00:03 GMT i have a channel which i subscribe to get some data in realtime but I would like to create a queue with these data to be processed after. do you guys know any solution for this? i believe i'm not the first guy with this problem