monitor output cannot distinguish between TCP socket and UNIX socket #563

Closed
quiver opened this Issue Jun 22, 2012 · 1 comment

2 participants

@quiver

Starting from 2.6, monitor command now shows client's info.
But, regardless of how you connect to the server(tcp or unix socket), it always returns ip style info

1340358274.406840 [0 127.0.0.1:36892] "set" "foo" "bar" <- tcp socket : no pro lem
1340358282.686123 [0 56.177.201.182:1288] "set" "foo" "bar" <- unix socket ???

It would be great it returns unix socket path if the command is sent via unix domain socket.

1340358282.686123 [0 /tmp/redis.sock] "set" "foo" "bar" <- unix socket
@mattsta

Fixed in 2ea4124

@mattsta mattsta closed this Aug 1, 2014
@JackieXie168 JackieXie168 pushed a commit that referenced this issue Sep 16, 2014
@jdoliner jdoliner No more crashing or failing when machines are down.
Also gets rid of /propose

Closes #563.
8643760
@JackieXie168 JackieXie168 pushed a commit that referenced this issue Sep 16, 2014
@al3xandru al3xandru API docs fix for #563 02a8769
@JackieXie168 JackieXie168 pushed a commit that referenced this issue Sep 16, 2014
@wmrowan wmrowan fixes issue #563 
Michael OTS review
88bc52b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment