1. 27 Jul, 2015 2 commits
  2. 26 Jul, 2015 6 commits
  3. 16 Jul, 2015 1 commit
  4. 12 Mar, 2015 2 commits
  5. 11 Mar, 2015 3 commits
  6. 10 Mar, 2015 2 commits
  7. 08 Mar, 2015 1 commit
  8. 12 Feb, 2015 1 commit
  9. 04 Feb, 2015 1 commit
  10. 09 Jan, 2015 1 commit
    • Matt Stancliff's avatar
      Supervise redis processes only if configured · 36a3b753
      Matt Stancliff authored
      Adds configuration option 'supervised [no | upstart | systemd | auto]'
      
      Also removed 'bzero' from the previous implementation because it's 2015.
      (We could actually statically initialize those structs, but clang
      throws an invalid warning when we try, so it looks bad even though it
      isn't bad.)
      
      Fixes #2264
      36a3b753
  11. 02 Jan, 2015 1 commit
    • Matt Stancliff's avatar
      Config: Add quicklist, remove old list options · 02bb515a
      Matt Stancliff authored
      This removes:
        - list-max-ziplist-entries
        - list-max-ziplist-value
      
      This adds:
        - list-max-ziplist-size
        - list-compress-depth
      
      Also updates config file with new sections and updates
      tests to use quicklist settings instead of old list settings.
      02bb515a
  12. 11 Dec, 2014 1 commit
  13. 27 Oct, 2014 1 commit
  14. 16 Oct, 2014 1 commit
  15. 29 Sep, 2014 1 commit
  16. 17 Sep, 2014 1 commit
  17. 08 Sep, 2014 1 commit
  18. 04 Sep, 2014 1 commit
    • antirez's avatar
      Sentinel: announce ip/port changes + rewrite. · cd576a1a
      antirez authored
      The original implementation was modified in order to allow to
      selectively announce a different IP or port, and to rewrite the two
      options in the config file after a rewrite.
      cd576a1a
  19. 13 Aug, 2014 1 commit
  20. 08 Aug, 2014 1 commit
  21. 02 Jul, 2014 1 commit
  22. 26 Jun, 2014 1 commit
  23. 16 Jun, 2014 1 commit
    • antirez's avatar
      Client types generalized. · 56d26c23
      antirez authored
      Because of output buffer limits Redis internals had this idea of type of
      clients: normal, pubsub, slave. It is possible to set different output
      buffer limits for the three kinds of clients.
      
      However all the macros and API were named after output buffer limit
      classes, while the idea of a client type is a generic one that can be
      reused.
      
      This commit does two things:
      
      1) Rename the API and defines with more general names.
      2) Change the class of clients executing the MONITOR command from "slave"
         to "normal".
      
      "2" is a good idea because you want to have very special settings for
      slaves, that are not a good idea for MONITOR clients that are instead
      normal clients even if they are conceptually slave-alike (since it is a
      push protocol).
      
      The backward-compatibility breakage resulting from "2" is considered to
      be minimal to care, since MONITOR is a debugging command, and because
      anyway this change is not going to break the format or the behavior, but
      just when a connection is closed on big output buffer issues.
      56d26c23
  24. 22 May, 2014 1 commit
  25. 15 Apr, 2014 1 commit
  26. 24 Mar, 2014 1 commit
    • Matt Stancliff's avatar
      Fix maxclients error handling · c138631c
      Matt Stancliff authored
      Everywhere in the Redis code base, maxclients is treated
      as an int with (int)maxclients or `maxclients = atoi(source)`,
      so let's make maxclients an int.
      
      This fixes a bug where someone could specify a negative maxclients
      on startup and it would work (as well as set maxclients very high)
      because:
      
          unsigned int maxclients;
          char *update = "-300";
          maxclients = atoi(update);
          if (maxclients < 1) goto fail;
      
      But, (maxclients < 1) can only catch the case when maxclients
      is exactly 0.  maxclients happily sets itself to -300, which isn't
      -300, but rather 4294966996, which isn't < 1, so... everything
      "worked."
      
      maxclients config parsing checks for the case of < 1, but maxclients
      CONFIG SET parsing was checking for case of < 0 (allowing
      maxclients to be set to 0).  CONFIG SET parsing is now updated to
      match config parsing of < 1.
      
      It's tempting to add a MINIMUM_CLIENTS define, but... I didn't.
      
      These changes were inspired by antirez#356, but this doesn't
      fix that issue.
      c138631c
  27. 19 Mar, 2014 1 commit
  28. 06 Mar, 2014 1 commit
  29. 05 Mar, 2014 1 commit
  30. 04 Mar, 2014 1 commit