> For the time being I'll go ahead and create the required init script
> and will watch this bug to see how things go.
Fixed in Git, pending upload.
(Making another package was much nicer, as it means sentinel can have
separate logs, systemd entry, logrotate entries, etc.)
Regards,
--
,
On Thu, 15 Jan 2015, Chris Lamb wrote:
Is it not possible to have two init scripts in one package?
Possibly, but because daemons start by default in Debian, someone
installing "redis" (in an informal sense) will suddenly be running
redis-sentinel..which would be unexpected at the very least. S
> Is it not possible to have two init scripts in one package?
Possibly, but because daemons start by default in Debian, someone
installing "redis" (in an informal sense) will suddenly be running
redis-sentinel..which would be unexpected at the very least. Some might
call it antisocial!
The redis-
On Thu, 15 Jan 2015, Chris Lamb wrote:
It seems like the easiest thing to do would be to duplicate and slightly
modify the existing init script for redis-server, but pointing to the
redis-sentinel binary and to a redis-sentinel.conf.
Sure, although "duplicate" would actually imply making a
sep
Hi Chris,
> It seems like the easiest thing to do would be to duplicate and slightly
> modify the existing init script for redis-server, but pointing to the
> redis-sentinel binary and to a redis-sentinel.conf.
Sure, although "duplicate" would actually imply making a
separate/additional redis-sen
Package: redis-server
Version: 2:2.8.4-2
Severity: normal
Dear Maintainer,
While experimenting with adding sentinel support to puppet-redis it
became clear that there was no separate startup script for redis-sentinel[1].
Having such a thing is handy when running sentinel as a separate process
(a
6 matches
Mail list logo
