forked from pool/redis
Marcus Rueckert
3d8f17d5b2
https://raw.githubusercontent.com/antirez/redis/4.0.10/00-RELEASENOTES - Important security issues related to the Lua scripting engine. Please check https://github.com/antirez/redis/issues/5017 for more information. - A bug with SCAN, SSCAN, HSCAN and ZSCAN, that may not return all the elements. We also add a regression test that can trigger the issue often when present, and may in theory be able to find unrelated regressions. - A PSYNC2 bug is fixed: Redis should not expire keys when saving RDB files because otherwise it is no longer possible to use such RDB file as a base for partial resynchronization. It no longer represents the right state. - Compatibility of AOF with RDB preamble when the RDB checksum is disabled. - Sentinel bug that in some cases prevented Sentinel to detect that the master was down immediately. A delay was added to the detection. - Update redis-enable-bactrace-on-x86-and-ia64-only.patch to handle - Add redis-disable_integration_logging.patch to disable logging test OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=112 |
||
|---|---|---|
| .gitattributes | ||
| .gitignore | ||
| README.SUSE | ||
| redis-4.0.10.tar.gz | ||
| redis-conf.patch | ||
| redis-disable_integration_logging.patch | ||
| redis-enable-bactrace-on-x86-ia64-and_arm32_only.patch | ||
| redis-initscript.patch | ||
| redis.changes | ||
| redis.logrotate | ||
| redis.spec | ||
| redis.sysctl | ||
| redis.target | ||
| redis.tmpfiles.d | ||
| redis@.service | ||
README.SUSE ------------- 1. copy /etc/redis/default.conf.example to /etc/redis/default.conf (or /etc/redis/otherapp.conf and so on) For the example we will use otherapp.conf 2. change at least pidfile, logfile and dir setting # the pid file *has* to match your config filename without the ".conf" pidfile /var/run/redis/otherapp.pid logfile /var/log/redis/otherapp.log dir /var/lib/redis/otherapp/ If you want to run more than one instance you also have to change the socket path and/or the ip:port combination. e.g. /var/run/redis/otherapp.sock If you plan to use redis in combination with apache, then you should add 'redis' to apache group and set 'unixsocketperm 770': $ usermod -a -G redis wwwrun $ systemctl restart apache2 then apache is able to connect to redis socket Also make sure if you copy configurations from somewhere, that "daemonize" should be set to "no". 3a. create the database dir: $ install -d -o redis -g redis -m 0750 /var/lib/redis/otherapp/ 3b. add limits (ulimit) to each service $ install -d -m 0755 /etc/systemd/system/redis@otherapp.service.d $ echo "[Service] LimitNOFILE=10240" > /etc/systemd/system/redis@otherapp.service.d/limits.conf 4. systemctl start redis@otherapp 5. systemctl enable redis@otherapp 6. to interact with all instances at the same time use: systemctl restart redis.target systemctl stop redis.target