On 22/10/17 11:37, Jaromil wrote:
Thanks everyone for adding details,
On Fri, 20 Oct 2017, Patrick Meade wrote:
https://github.com/lamby/pkg-redis/commit/6a9e4d0142b45195a0d55945bbc558df4c48707b#diff-9e388da7cd119765989cc22d2bc07e5c
This diff clearly shows that redis-sentinel example scripts provided
by upstream redis developers for compatibility with sysvinit are being
*deleted* from the package, de facto removing even the documentation
on how to start/stop from init.d despite it being just an example.
The scripts that are removed:
+rm_conffile /etc/redis/redis-sentinel.pre-up.d/00_example 4:4.0.2-3~
+rm_conffile /etc/redis/redis-sentinel.pre-down.d/00_example 4:4.0.2-3~
+rm_conffile /etc/redis/redis-sentinel.post-up.d/00_example 4:4.0.2-3~
+rm_conffile /etc/redis/redis-sentinel.post-down.d/00_example 4:4.0.2-3~
Do not exist in the upstream distribution of redis, *which does not
include sysvinit scripts*.
They were added by the Debian redis developers as part of a poorly
documented feature (only mentioned in the changelog!) which only exists
on Debian.
Debian still include sysvinit scripts for redis, which provide as much
functionality as sysvinit can give. (The systemd service files allow
running multiple copies of redis. The Debian provided sysvinit scripts
never allowed this, the only way of doing it would be for the user to
write his own init scripts, which will be much easier to do without the
{pre,post}-{up,down} complexity),
it is even worse than I initially thought.
No, it isn't.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
