Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Fixed installation script for the chkconfig check, fixed init.d template... #453

wants to merge 1 commit into from

2 participants

Anthony Scalisi Josh Sherman
Anthony Scalisi

The current state doesnt allow a clean installation of redis on an ubuntu box.

As fixed, it's a smooth process.

Tested on Ubuntu 10.04.

Anthony Scalisi

Any feedback?

Josh Sherman

Confirmed working on 10.04 LTS and 12.04 LTS.

Jackie JackieXie168 referenced this pull request from a commit
Slava Akhmechet Fixing broken #453 regression test 4df303b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
Showing with 4 additions and 4 deletions.
  1. +4 −4 utils/
8 utils/
@@ -146,12 +146,12 @@ REDIS_CHKCONFIG_INFO=\
# Description: Redis daemon\n
### END INIT INFO\n\n"
-if [[ ! `which chkconfig` ]] ; then
+if [ ! `which chkconfig` ] ; then
#combine the header and the template (which is actually a static footer)
- echo -e $REDIS_INIT_HEADER > $TMP_FILE && cat $INIT_TPL_FILE >> $TMP_FILE || die "Could not write init script to $TMP_FILE"
+ echo -n $REDIS_INIT_HEADER > $TMP_FILE && cat $INIT_TPL_FILE >> $TMP_FILE || die "Could not write init script to $TMP_FILE"
#if we're a box with chkconfig on it we want to include info for chkconfig
- echo -e $REDIS_INIT_HEADER $REDIS_CHKCONFIG_INFO > $TMP_FILE && cat $INIT_TPL_FILE >> $TMP_FILE || die "Could not write init script to $TMP_FILE"
+ echo -n $REDIS_INIT_HEADER $REDIS_CHKCONFIG_INFO > $TMP_FILE && cat $INIT_TPL_FILE >> $TMP_FILE || die "Could not write init script to $TMP_FILE"
#copy to /etc/init.d
@@ -160,7 +160,7 @@ echo "Copied $TMP_FILE => $INIT_SCRIPT_DEST"
#Install the service
echo "Installing service..."
-if [[ ! `which chkconfig` ]] ; then
+if [ ! `which chkconfig` ] ; then
#if we're not a chkconfig box assume we're able to use update-rc.d
update-rc.d redis_$REDIS_PORT defaults && echo "Success!"
Something went wrong with that request. Please try again.