- 23 Jan, 2019 4 commits
- 22 Jan, 2019 4 commits
- 21 Jan, 2019 1 commit
-
-
antirez authored
-
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 17 Jan, 2019 2 commits
- 16 Jan, 2019 1 commit
-
-
antirez authored
-
- 15 Jan, 2019 3 commits
- 14 Jan, 2019 2 commits
- 11 Jan, 2019 2 commits
- 10 Jan, 2019 1 commit
-
-
antirez authored
-
- 09 Jan, 2019 15 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Because in RESP3 commands can be sent in the Pub/Sub connection without problems, so it's better if in such mode there is no exception about PING.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 12 Dec, 2018 1 commit
-
-
antirez authored
Related to issue #5686 and PR #5689.
-
- 07 Dec, 2018 1 commit
-
-
antirez authored
-
- 02 Dec, 2018 1 commit
-
-
Oran Agra authored
these metrics become negative when RSS is smaller than the used_memory. This can easily happen when the program allocated a lot of memory and haven't written to it yet, in which case the kernel doesn't allocate any pages to the process
-
- 23 Nov, 2018 1 commit
-
-
Chris Lamb authored
If we encounter an unsupported protocol in the "bind" list, don't ipso-facto consider it a fatal error. We continue to abort startup if there are no listening sockets at all. This ensures that the lack of IPv6 support does not prevent Redis from starting on Debian where we try to bind to the ::1 interface by default (via "bind 127.0.0.1 ::1"). A machine with IPv6 disabled (such as some container systems) would simply fail to start Redis after the initiall call to apt(8). This is similar to the case for where "bind" is not specified: https://github.com/antirez/redis/issues/3894 ... and was based on the corresponding PR: https://github.com/antirez/redis/pull/4108 ... but also adds EADDRNOTAVAIL to the list of errors to catch which I believe is missing from there. This issue was raised in Debian as both <https://bugs.debian.org/900284> & <https://bugs.debian.org/914354>.
-