The SysV scripts should now call the /usr/sbin executable instead

of executing the scripts them self.

Author: Dan Kelleher

base_deb/etc/init.d/vmcontext

@@ -52,25 +52,7 @@ function execute_scripts {
 
 case "$1" in
 "start")
-    CONTEXT_DEV=`blkid -l -t LABEL="CONTEXT" -o device`
-    if [ -e "$CONTEXT_DEV" ]; then
-        mount -t iso9660 -L CONTEXT -o ro /mnt
-        if [ -f /mnt/context.sh ]; then
-            export_rc_vars /mnt/context.sh
-        fi
-
-        execute_scripts
-
-        umount /mnt
-    else
-        if type vmtoolsd ; then
-            vmtoolsd --cmd 'info-get guestinfo.opennebula.context' | openssl base64 -d > /tmp/context.sh
-            export_rc_vars /tmp/context.sh
-        fi
-
-        execute_scripts
-    fi
-    ;;
+    /usr/sbin/one-contextd start
 
 esac
 

base_rpm/etc/init.d/vmcontext

@@ -52,25 +52,7 @@ function execute_scripts {
 
 case "$1" in
 "start")
-    CONTEXT_DEV=`blkid -l -t LABEL="CONTEXT" -o device`
-    if [ -e "$CONTEXT_DEV" ]; then
-        mount -t iso9660 -L CONTEXT -o ro /mnt
-        if [ -f /mnt/context.sh ]; then
-            export_rc_vars /mnt/context.sh
-        fi
-
-        execute_scripts
-
-        umount /mnt
-    else
-        if type vmtoolsd ; then
-            vmtoolsd --cmd 'info-get guestinfo.opennebula.context' | openssl base64 -d > /tmp/context.sh
-            export_rc_vars /tmp/context.sh
-        fi
-
-        execute_scripts
-    fi
-    ;;
+    /usr/sbin/one-contextd start
 
 esac