Because tired of anonymous process names

gistfile1.hs

[Everything here is ps output captured by "ps auxww|grep [r]edis-"]

Master / Replica (no config specified on the master):
./redis-server /Users/matt/repos/redis/redis.conf *:9999 replica (connected to 127.0.0.1:6379)   
./redis-server *:6379 master (1 replica)

Master with config file:
./redis-server /Users/matt/repos/redis/redis.conf *:6379 master (1 replica)

Same master as above, but with a name defined too (if name is set, name shows instead of config file path):
./redis-server [userdb01-offsite] *:6379 master (1 replica)

Single instance, no replicas (without config):
./redis-server *:6379 

Single instance, no replicas (with config): 
./redis-server /Users/matt/repos/redis/redis.conf *:6379

/* old 
Configured with customizable title format string: "{{executable}} {{name}} {{config}} {{ip0}}:{{port}} {{mode}} {{role}} {{state}}"
*/
Now configured with that same string, but in static non-user-configurable element positions.
name is one of: [name] | <empty>
config is one of: configfile path | <empty>
[Note: the name and config policy is (name xor config) — If a name is set, the config path doesn't show.]
mode is one of: cluster | sentinel | <empty>
role is one of: master | replica | <empty> (empty if standalone master with no replicas)
state is one of: active cluster instance description | live replica description | live sentinel description | <empty> (if no replica _or_ if a forked background process)

Redis Cluster, 9 instances, brought up with "redis-trib.rb create --replicas 2 127.0.0.1:7000 127.0.0.1:7001 127.0.0.1:7002 127.0.0.1:7003 127.0.0.1:7004 127.0.0.1:7005 127.0.0.1:7006 127.0.0.1:7007 127.0.0.1:7008":
redis-server 127.0.0.1:7003 cluster replica (epoch: 4; replicating from 127.0.0.1:7000)            
redis-server 127.0.0.1:7002 cluster master (epoch: 3; replicas: 2; slots: 10923-16383)            
redis-server 127.0.0.1:7001 cluster master (epoch: 2; replicas: 2; slots: 5461-10922)            
redis-server 127.0.0.1:7000 cluster master (epoch: 1; replicas: 2; slots: 0-5460)            
redis-server 127.0.0.1:7008 cluster replica (epoch: 9; replicating from 127.0.0.1:7002)            
redis-server 127.0.0.1:7007 cluster replica (epoch: 8; replicating from 127.0.0.1:7002)            
redis-server 127.0.0.1:7006 cluster replica (epoch: 7; replicating from 127.0.0.1:7001)            
redis-server 127.0.0.1:7005 cluster replica (epoch: 6; replicating from 127.0.0.1:7001)            
redis-server 127.0.0.1:7004 cluster replica (epoch: 5; replicating from 127.0.0.1:7000)

Sentinel with two monitored masters:
./redis-sentinel /Users/matt/repos/redis/src/sent.conf *:26379 sentinel (bob-master2=127.0.0.1:3333; bob-master=127.0.0.1:6379) 

Sentinel on startup before contacting masters:
./redis-sentinel /Users/matt/repos/redis/src/sent.conf *:26379 sentinel (bob-master [not connected]; bob-master2 [not connected])

Sentinel with two masters down and unable to failover (no replicas):
./redis-sentinel /Users/matt/repos/redis/src/sent.conf *:26379 sentinel (bob-master [down, no failover]; bob-master2 [down, no failover])

Sentinel after one of the two down masters comes back up:
./redis-sentinel /Users/matt/repos/redis/src/sent.conf *:26379 sentinel (bob-master=127.0.0.1:6379; bob-master2 [down, no failover])

Sentinel with an IPv6 address:
./redis-sentinel /Users/matt/repos/redis/src/sent.conf [::1]:26379 sentinel (bob-master2 [not connected]; bob-master [not connected])