On Friday 20 October 2017 at 16:33:09, Adam Borowski wrote:

> On Fri, Oct 20, 2017 at 04:27:44PM +0200, John Hughes wrote:
> > Jaromil wrote:
> > > I would like to know here if anyone knows in detail the "reasons"
> > > Debian is removing the support for sysvinit scripts in the redis
> > > package.
> > 
> > Wouldn't it be more to the point to find out *if* Debian is removing the
> > support for sysvinit scripts in the redis package before trying to find
> > out why?
> > 
> > Because they aren't.
> 
> [...]
> 
> > The Debian supplied init scripts (debian/redis-server.init and
> > debian/redis-sentinel.init) still exist, they just no longer include the
> > (Debian specific) calls to "Run_parts".
> > 
> > These init scripts do not exist in the upstream redis distribution.  They
> > were added by Debian.
> > 
> > My apologies for posting to a list from which I have been banned, but I
> > thought it might be wise to have a little more light and a little less
> > heat.
> 
> Thanks for the correction -- that's always appreciated.

However, Bardot Jérôme's original posting in this thread, quoting Chris Lamb 
<la...@debian.org> Wed, 11 Oct 2017 22:55:00 -0400 said:

"This version drops the Debian-specific support for the 
/etc/redis/redis-{server}.sentinel.{pre,post}-{up,down}.d directories in 
favour of using systemd's ExecStartPre, ExecStartPost, ExecStopPre, 
ExecStopPost commands."

So, yes, what's been dropped is Debian-specific, but shouldn't we still be 
concerned about the "in favour of systemd's ... commands"?


Antony.

-- 
This email was created using 100% recycled electrons.

                                                   Please reply to the list;
                                                         please *don't* CC me.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to