redis/redis-sentinel@.service

[Unit]
Description=Redis Sentinel instance: %i
After=network.target
PartOf=redis-sentinel.target

[Service]
Type=notify
User=redis
Group=redis
PrivateTmp=true
PIDFile=/var/run/redis/sentinel-%i.pid
ExecStart=/usr/sbin/redis-sentinel /etc/redis/sentinel-%i.conf
LimitNOFILE=10240
Restart=on-failure

[Install]
WantedBy=multi-user.target redis.target
Accepting request 633784 from home:darix:apps - make check && true -> make check \|\| true This was probably meant to catch an error in the test suite, but with && it would only return true if it would return true already. - added systemd unit file file redis-sentinel - the unit file uses the same multiple instance mechanism as the normal redis unit file systemctl start redis-sentinel@default will look for /etc/redis/sentinel-default.conf and expects a pid file /var/run/redis/sentinel-default.pid Please make sure your sentinel config sets the pid file. - adapted the default sentinel.conf.example to set the pid file and the log file similar to the normal redis.conf: /var/log/redis/sentinel-<instancename>.log /var/run/redis/sentinel-<instancename>.pid The unit file checks for the pid file so please adapt your local sentinel configs. Changed: redis-conf.patch - adapt and restructure README.SUSE - move the LimitNoFile to the service file itself so the user do not have to manually do that step for every instance - move the apache integration into its own section - add section for redis-sentinel - install sentinel example config with group write permissions to indicate that the actually config needs to be writable. OBS-URL: https://build.opensuse.org/request/show/633784 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=120 2018-09-06 21:15:00 +02:00			`[Unit]`
Accepting request 772349 from home:darix:apps - print instance name in the from the service files OBS-URL: https://build.opensuse.org/request/show/772349 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=133 2020-02-08 22:38:07 +01:00			`Description=Redis Sentinel instance: %i`
Accepting request 633784 from home:darix:apps - make check && true -> make check \|\| true This was probably meant to catch an error in the test suite, but with && it would only return true if it would return true already. - added systemd unit file file redis-sentinel - the unit file uses the same multiple instance mechanism as the normal redis unit file systemctl start redis-sentinel@default will look for /etc/redis/sentinel-default.conf and expects a pid file /var/run/redis/sentinel-default.pid Please make sure your sentinel config sets the pid file. - adapted the default sentinel.conf.example to set the pid file and the log file similar to the normal redis.conf: /var/log/redis/sentinel-<instancename>.log /var/run/redis/sentinel-<instancename>.pid The unit file checks for the pid file so please adapt your local sentinel configs. Changed: redis-conf.patch - adapt and restructure README.SUSE - move the LimitNoFile to the service file itself so the user do not have to manually do that step for every instance - move the apache integration into its own section - add section for redis-sentinel - install sentinel example config with group write permissions to indicate that the actually config needs to be writable. OBS-URL: https://build.opensuse.org/request/show/633784 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=120 2018-09-06 21:15:00 +02:00			`After=network.target`
			`PartOf=redis-sentinel.target`

			`[Service]`
Accepting request 652038 from home:EGDFree:branches:server:database - update systemd unit file to fix redis shutdown immedaiate after start OBS-URL: https://build.opensuse.org/request/show/652038 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=123 2018-11-26 17:50:24 +01:00			`Type=notify`
Accepting request 633784 from home:darix:apps - make check && true -> make check \|\| true This was probably meant to catch an error in the test suite, but with && it would only return true if it would return true already. - added systemd unit file file redis-sentinel - the unit file uses the same multiple instance mechanism as the normal redis unit file systemctl start redis-sentinel@default will look for /etc/redis/sentinel-default.conf and expects a pid file /var/run/redis/sentinel-default.pid Please make sure your sentinel config sets the pid file. - adapted the default sentinel.conf.example to set the pid file and the log file similar to the normal redis.conf: /var/log/redis/sentinel-<instancename>.log /var/run/redis/sentinel-<instancename>.pid The unit file checks for the pid file so please adapt your local sentinel configs. Changed: redis-conf.patch - adapt and restructure README.SUSE - move the LimitNoFile to the service file itself so the user do not have to manually do that step for every instance - move the apache integration into its own section - add section for redis-sentinel - install sentinel example config with group write permissions to indicate that the actually config needs to be writable. OBS-URL: https://build.opensuse.org/request/show/633784 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=120 2018-09-06 21:15:00 +02:00			`User=redis`
			`Group=redis`
			`PrivateTmp=true`
			`PIDFile=/var/run/redis/sentinel-%i.pid`
			`ExecStart=/usr/sbin/redis-sentinel /etc/redis/sentinel-%i.conf`
			`LimitNOFILE=10240`
			`Restart=on-failure`

			`[Install]`
			`WantedBy=multi-user.target redis.target`