On 26/10/17 15:55, John Hughes wrote:
They are around 89 lines long. Hardly broken compared to most init
scripts, check out /etc/init.d/sendmail -- a 1321 line monster in some
versions.
Duh, hardly "bloated" I meant to say.
___
Dng mailing
On 25/10/17 19:51, Steve Litt wrote:
How bout this: Have a "runit-supervisor-only" pacakge that installs
runit but doesn't make it PID1. Have sysvinit run runit, and have runit
run redis, with all the correct config. The runit run script is
probably 1/10 the size of its bloatacious and
On Tue, 24 Oct 2017 07:44:51 -0500
Patrick Meade wrote:
> However, if they are on Devuan, there is no systemd. And without
> restoring the old functionality or providing new functionality, our
> answer will be an empty one: "Debian upstream broke it. Sorry." And
> our poor
This is what the debian maintainer wrote to me about redis.
(i ask if i miss understood the patch loq )
> Maybe i miss understood the message ?
You did. As the changelog entry mentions, it's only the Debian-
specific (eg.) /etc/redis/redis-server.pre-up.d support that have
been removed... and
On 24/10/17 14:44, Patrick Meade wrote:
Only the first option is acceptable to me, so what needs to be done is
also clear to me. I'm hoping that the Debian maintainer will be
willing to revert this change, as that would be the easiest way for
everybody to win. If not, well... there is some
On 10/23/2017 09:19 AM, John Hughes wrote:
On 23/10/17 15:59, Patrick Meade wrote:
As John Hughes said, this isn't quite as bad as we originally thought.
We can still run redis-server with the Debian provided sysvinit
script, and Debian isn't throwing away upstream files for no reason.
Also
On 23/10/17 15:59, Patrick Meade wrote:
As John Hughes said, this isn't quite as bad as we originally thought.
We can still run redis-server with the Debian provided sysvinit
script, and Debian isn't throwing away upstream files for no reason.
Also note that the upstream init script
On 10/23/2017 04:10 AM, John Hughes wrote:
On 21/10/17 01:53, Patrick Meade wrote:
That text is not from the Debian changelog, but rather from debian/NEWS.
Ah, didn't notice that. Always trust the code before the doc.
Still don't understand why it says "in favour of systemd's ... commands"
On 21/10/17 01:53, Patrick Meade wrote:
That text is not from the Debian changelog, but rather from debian/NEWS.
Ah, didn't notice that. Always trust the code before the doc.
Still don't understand why it says "in favour of systemd's ... commands"
when the patch does no such thing.
The
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
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
On Thu, 19 Oct 2017 23:46:28 +0200
Adam Borowski wrote:
> On Thu, Oct 19, 2017 at 10:22:33AM +0200, Jaromil wrote:
> > On Wed, 18 Oct 2017, Arnt Gulbrandsen wrote:
> >
> > > Steve Litt writes:
> > > > Does anyone here actually use redis? I looked it up, and to me
> > >
On 10/20/2017 10:22 AM, John Hughes wrote:
On 20/10/17 16:37, Antony Stone wrote:
However, Bardot Jérôme's original posting in this thread, quoting
Chris Lamb
Wed, 11 Oct 2017 22:55:00 -0400 said:
"This version drops the Debian-specific support for the
On 20/10/17 16:37, Antony Stone wrote:
However, Bardot Jérôme's original posting in this thread, quoting Chris Lamb
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
On 20/10/17 16:48, goli...@dyne.org wrote:
On 2017-10-20 09:27, John Hughes wrote:
My appologies for posting to a list from which I have been banned . . .
If you were 'banned' you would would not have been able to post. I
just checked and your account has no restrictions on it.
Yup, I
On 2017-10-20 09:27, John Hughes wrote:
My appologies for posting to a list from which I have been banned . . .
If you were 'banned' you would would not have been able to post. I just
checked and your account has no restrictions on it.
Wouldn't it be more to the point to find out *if* you
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
> > >
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
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
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. Is there a limitation of sorts, or a problem generated by
> having the init scripts left in the package, or is it just vandalism?
> is
On Thu, 19 Oct 2017, Steve Litt wrote:
> When you contact them, you might want to also give them the runit run
> script for redis from the Void distro:
cheers Steve, I will pass it on.
ah!! now you like redis do you??? :^
___
Dng mailing list
On Thu, 19 Oct 2017 10:22:33 +0200
Jaromil wrote:
> On Wed, 18 Oct 2017, Arnt Gulbrandsen wrote:
>
> > Steve Litt writes:
> > > Does anyone here actually use redis? I looked it up, and to me it
> > > looks like dbus on steroids. An in-memory data store accessible
> > > by
On 2017-10-19 06:24, Arnt Karlsen wrote:
On Thu, 19 Oct 2017 11:09:34 +0300, Aldemir wrote in message
:
>
> No need to panic. The situation is under control. Noone will pull
> sysv init support from redis.
>
> HND
>
> KatolaZ
On Thu, 19 Oct 2017 11:09:34 +0300, Aldemir wrote in message
:
> >
> >
> >
> >
> > No need to panic. The situation is under control. Noone will pull
> > sysv init support from redis.
> >
> > HND
> >
> > KatolaZ
> >
> >
>
On Wed, 18 Oct 2017, Alberto Zuin - Liste wrote:
> Redis project started by an Italian guy which is also in the VUA
> group.
indeed. yet another VUA being outed :^) let's hope systemd-hooligans
don't go and delete wikipedia pages about him and his work too now.
antirez just replied me on the
jaro...@dyne.org writes:
Same here, its a core part of many software projects, not only web
based but also on embedded systems and micro-service related.
Totally offtopic but some if you will be fascinated by the references to
redis in this talk by John Regehr: https://youtu.be/Ux0YnVEaI6A
On Wed, 18 Oct 2017, Arnt Gulbrandsen wrote:
> Steve Litt writes:
> > Does anyone here actually use redis? I looked it up, and to me it looks
> > like dbus on steroids. An in-memory data store accessible by lots of
> > different applications. What could POSSIBLY go wrong?
>
> I've used in
>
>
>
>
> No need to panic. The situation is under control. Noone will pull sysv
> init support from redis.
>
> HND
>
> KatolaZ
>
>
That's the spirit! Many many thanks!
--
aldemir
___
Dng mailing list
Dng@lists.dyne.org
On Wed, Oct 18, 2017 at 03:46:39PM +0200, Bardot Jérôme wrote:
> redis (4:4.0.2-3) unstable; urgency=medium
>
> 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,
On Thu, Oct 19, 2017 at 4:56 AM, Hendrik Boom wrote:
> On Wed, Oct 18, 2017 at 03:46:39PM +0200, Bardot Jérôme wrote:
>> redis (4:4.0.2-3) unstable; urgency=medium
>>
>> This version drops the Debian-specific support for the
>>
On Wed, Oct 18, 2017 at 03:46:39PM +0200, Bardot Jérôme wrote:
> redis (4:4.0.2-3) unstable; urgency=medium
>
> 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,
On 18/10/17 09:46 AM, Bardot Jérôme wrote:
redis (4:4.0.2-3) unstable; urgency=medium
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,
Redis, for sure, is one of the most used in memory datastore, a good
cache system like memcache but more flexible when you have to store real
data and a standard SQL database is not fast enough: one common example
of application, is to store the authentication tokens in a clustered web
server
Quoting Steve Litt (sl...@troubleshooters.com):
> Does anyone here actually use redis? I looked it up, and to me it looks
> like dbus on steroids. An in-memory data store accessible by lots of
> different applications. What could POSSIBLY go wrong?
Extremely useful for large Web sites. _Not_ a
On 10/18/2017 10:04 AM, Steve Litt wrote:
> Does anyone here actually use redis? I looked it up, and to me it looks
> like dbus on steroids. An in-memory data store accessible by lots of
> different applications. What could POSSIBLY go wrong?
>
> SteveT
The Nextcloud project[1] recommends
On Wed, 18 Oct 2017 15:46:39 +0200
Bardot Jérôme wrote:
> redis (4:4.0.2-3) unstable; urgency=medium
>
> 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
redis (4:4.0.2-3) unstable; urgency=medium
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.
-- Chris Lamb
37 matches
Mail list logo