[patch] mule-bin-1.3.2-script.patch

mule-bin-1.3.2-script.patch (text/plain), 2.89 KB, created by Matthew Schultz on 2007-01-02 14:39:16 UTC

--- mule_dist	2006-12-07 11:20:39.659419617 -0600
+++ mule	2007-01-01 13:22:33.772713963 -0600
@@ -24,11 +24,11 @@
 APP_LONG_NAME=${MULE_APP_LONG}
 
 # Wrapper
-WRAPPER_CMD="../sbin/wrapper"
-WRAPPER_CONF="../conf/wrapper.conf"
+WRAPPER_CMD="/usr/sbin/wrapper"
+WRAPPER_CONF="/etc/mule/wrapper.conf"
 
 # Set the startup directory so that any relative paths can be resolved later.
-STARTUP_DIR=`pwd`
+STARTUP_DIR=/var/mule
 
 MULE_OPTS="wrapper.working.dir=$STARTUP_DIR \
            wrapper.app.parameter.1=$2 \
@@ -48,7 +48,7 @@
 PRIORITY=
 
 # Location of the pid file.
-PIDDIR="."
+PIDDIR="/var/run/mule"
 
 # If uncommented, causes the Wrapper to be shutdown using an anchor file.
 #  When launched with the 'start' command, it will also ignore all INT and
@@ -63,12 +63,7 @@
 # NOTE - This will set the user which is used to run the Wrapper as well as
 #  the JVM and is not useful in situations where a privileged resource or
 #  port needs to be allocated prior to the user being changed.
-#RUN_AS_USER=
-
-# The following two lines are used by the chkconfig command. Change as is
-#  appropriate for your application.  They should remain commented.
-# chkconfig: 2345 20 80
-# description: Mule
+RUN_AS_USER=mule
 
 #-----------------------------------------------------------------------------
 
@@ -146,7 +141,7 @@
 ######################################################################
 PIDFILE="$PIDDIR/.$APP_NAME.pid"
 ######################################################################
-LOCKDIR="/var/lock/subsys"
+LOCKDIR="/var/lock/mule"
 LOCKFILE="$LOCKDIR/$APP_NAME"
 pid=""
 
@@ -164,7 +159,7 @@
 fi
 
 # Resolve the os
-DIST_OS=`uname -s | tr [:upper:] [:lower:] | tr -d [:blank:]`
+DIST_OS=`uname -s | tr '[:upper:]' '[:lower:]' | tr -d '[:blank:]'`
 case "$DIST_OS" in
     'sunos')
         DIST_OS="solaris"
@@ -185,7 +180,7 @@
 ######################################################################
 
 # Resolve the architecture
-PROC_ARCH=`uname -p | tr [:upper:] [:lower:] | tr -d [:blank:]`
+PROC_ARCH=`uname -m | tr '[:upper:]' '[:lower:]' | tr -d '[:blank:]'`
 while :
 do
 	case "$PROC_ARCH" in
@@ -212,7 +207,6 @@
 			then
 			    echo "Processor type $PROC_ARCH not recognized.  Falling back on machine hardware name (uname -m)"
 			    DIST_ARCH="unknown"
-			    PROC_ARCH=`uname -m | tr [:upper:] [:lower:] | tr -d [:blank:]`
 			else
 			    echo "Neither the processor type (uname -p) nor the machine hardware type (uname -m) were recognized."
 			    echo "Please report this message along with your machine's processor/architecture."
@@ -353,7 +347,7 @@
                 RUN_AS_GROUP=`groups $RUN_AS_USER | awk '{print $3}' | tail -1`
                 if [ "X$RUN_AS_GROUP" = "X" ]
                 then
-                    RUN_AS_GROUP=RUN_AS_USER
+                    RUN_AS_GROUP="${RUN_AS_USER}"
                 fi
                 touch $LOCKFILE
                 chown $RUN_AS_USER:$RUN_AS_GROUP $LOCKFILE