[Erp5-report] r11909 - /erp5/trunk/utils/oood/oood.rc

nobody at svn.erp5.org nobody at svn.erp5.org
Fri Jan 5 16:17:42 CET 2007


Author: alex
Date: Fri Jan  5 16:17:40 2007
New Revision: 11909

URL: http://svn.erp5.org?rev=11909&view=rev
Log:
put path to python interpreter in a variable, to allow changing it easily

Modified:
    erp5/trunk/utils/oood/oood.rc

Modified: erp5/trunk/utils/oood/oood.rc
URL: http://svn.erp5.org/erp5/trunk/utils/oood/oood.rc?rev=11909&r1=11908&r2=11909&view=diff
==============================================================================
--- erp5/trunk/utils/oood/oood.rc (original)
+++ erp5/trunk/utils/oood/oood.rc Fri Jan  5 16:17:40 2007
@@ -13,6 +13,7 @@
 RUNDIR=/var/run/oood
 LOCKFILE=$RUNDIR/server_pid.lock
 PIDFILE=$LOCKFILE
+PYTHON=python
 
 start() {
   if [ -f $LOCKFILE ] ; then
@@ -24,9 +25,9 @@
 
   gprintf "Starting %s: " "$NAME"
   # Initialize the Pool
-  su --login $USER --command="python $HOME/start.py --init > /dev/null 2>&1 /dev/null"
+  su --login $USER --command="$PYTHON $HOME/start.py --init > /dev/null 2>&1 /dev/null"
   # Start the server in the background
-  su --login $USER --command="python $HOME/runserw.py --start > /dev/null &"
+  su --login $USER --command="$PYTHON $HOME/runserw.py --start > /dev/null &"
   sleep 10 # Safe sleep to let the server create its lockfile
            # Warning: this trick should be replaced by a stronger mechanism,
            #   because under heavy load, the server can take several tenth of
@@ -35,7 +36,7 @@
     echo_success
   else
     gprintf "%s is not running (no pid file found)." "$NAME"
-    su --login $USER --command="python $HOME/start.py --flush > /dev/null 2>&1 /dev/null"
+    su --login $USER --command="$PYTHON $HOME/start.py --flush > /dev/null 2>&1 /dev/null"
     echo_failure
   fi
   echo
@@ -48,19 +49,19 @@
     echo_failure
   else
     gprintf "Stopping %s daemon: " "$NAME"
-    su --login $USER --command="python $HOME/runserw.py --stop" && echo_success || echo_failure
+    su --login $USER --command="$PYTHON $HOME/runserw.py --stop" && echo_success || echo_failure
   fi
   # Clean up in any case
-  su --login $USER --command="python $HOME/start.py --flush > /dev/null 2>&1 /dev/null"
+  su --login $USER --command="$PYTHON $HOME/start.py --flush > /dev/null 2>&1 /dev/null"
   echo
 }
 
 
 status() {
   echo
-  su --login $USER --command="python $HOME/runserw.py --status"
+  su --login $USER --command="$PYTHON $HOME/runserw.py --status"
   echo
-  su --login $USER --command="python $HOME/start.py   --status"
+  su --login $USER --command="$PYTHON $HOME/start.py   --status"
   echo
 }
 




More information about the Erp5-report mailing list