Greetings: Finaly got 7.3 installed on two boxes on the weekend and all I can say is that it more than I expected. The level of hardware diagnostics durring the install is excellent, the selection of apps on the ftp server is well excellent and the level of integration is well, excellent...:) Well done and many thanks to all the good people as SuSE.!!! One small issue. The SuSE default zope intallation now installs into opt with the boot scripts sym linked to /usr/sbin/rczope. Setting Yast1 to start Zope at boot time (and also manually) produces the following error. #"Starting zope: The specified locale is not supported by your system. #See your operating system documentation for more #information on locale support. #startproc: exit status of parent of /usr/bin/python: 1" Typically the zope start process is a call to python to execute the Zope supplies start script that is very basic as it calls anther python script (Z2.py) again very basic. Never seen this error before?? Lookng at the SuSE manual (online version) their is no discussion on local support and looking at the rczope file which I dont completely understand as I'm not a programmer it appears to be OK. The script is attached below for reference. Anyone have any suggestions or ideas as to what is the issue here? Any assistance would be greatly appreciated. Thought I would seek help hear first befor moving too the zope discussion list. TIA Chris H> ______________ rczope script: #! /bin/sh # Copyright (c) 1995-2000 SuSE GmbH Nuernberg, Germany. # # Authors: Kurt Garloff, Vladimír Linek # <feedback@suse.de> # # init.d/zope # # and symbolic its link # # /usr/sbin/rczope # # System startup script for the Zope server # ### BEGIN INIT INFO # Provides: zope # Required-Start: $remote_fs # Required-Stop: $remote_fs # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Zope server. ### END INIT INFO # Source SuSE config . /etc/rc.config # Source Zope relevant things . /etc/rc.config.d/zope.rc.config # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} # Force execution if not called by a runlevel directory. test $link = $base && START_ZOPE=yes test "$START_ZOPE" = yes || exit 0 PYTHON_BIN="/usr/bin/python" test -x $PYTHON_BIN || exit 5 ZOPE_HOME="/opt/zope" test -d $ZOPE_HOME || exit 5 ZOPE_SCRIPT="$ZOPE_HOME/z2.py" test -f $ZOPE_SCRIPT || exit 5 # Shell functions sourced from /etc/rc.status: # rc_check check and set local and overall rc status # rc_status check and set local and overall rc status # rc_status -v ditto but be verbose in local rc status # rc_status -v -r ditto and clear the local rc status # rc_failed set local and overall rc status to failed # rc_failed <num> set local and overall rc status to <num><num> # rc_reset clear local rc status (overall remains) # rc_exit exit appropriate to overall rc status . /etc/rc.status # First reset status of this service rc_reset # Return values acc. to LSB for all commands but status: # 0 - success # 1 - generic or unspecified error # 2 - invalid or excess argument(s) # 3 - unimplemented feature (e.g. "reload") # 4 - insufficient privilege # 5 - program is not installed # 6 - program is not configured # 7 - program is not running # # Note that starting an already running service, stopping # or restarting a not-running service as well as the restart # with force-reload (in case signalling is not supported) are # considered a success. COMMON_PARAMS="-u zope -z $ZOPE_HOME -Z /var/run/zope.pid -L $RC_LANG -l /var/log/zope.log" PCGI_PARAMS="-p $ZOPE_HOME/Zope.cgi" [ -z "$ZOPE_HTTP_PORT" ] && ZOPE_HTTP_PORT="8080" ALONE_PARAMS="-w $ZOPE_HTTP_PORT" # For debugging... #SPECIAL_PARAMS="-D" [ -z "$ZOPE_FTP_PORT" ] && ZOPE_FTP_PORT="8021" if [ "$ZOPE_FTP" == "yes" ]; then SPECIAL_PARAMS="-f $ZOPE_FTP_PORT $SPECIAL_PARAMS" fi if [ "$ZOPE_PCGI" == "yes" ]; then PARAMS="$SPECIAL_PARAMS $PCGI_PARAMS $COMMON_PARAMS" else PARAMS="$SPECIAL_PARAMS $ALONE_PARAMS $COMMON_PARAMS" fi case "$1" in start) echo -n "Starting zope" ## Start daemon with startproc(8). If this fails ## the echo return value is set appropriate. # NOTE: startproc return 0, even if service is # already running to match LSB spec. startproc $PYTHON_BIN $ZOPE_SCRIPT -X $PARAMS # Remember status and be verbose rc_status -v ;; stop) echo -n "Shutting down zope" ## Stop daemon with killproc(8) and if this fails ## set echo the echo return value. killproc -g -p /var/run/zope.pid -TERM $PYTHON_BIN # Remember status and be verbose rc_status -v ;; try-restart) ## Stop the service and if this succeeds (i.e. the ## service was running before), start it again. ## Note: try-restart is not (yet) part of LSB (as of 0.7.5) $0 status >/dev/null && $0 restart # Remember status and be quiet rc_status ;; restart) ## Stop the service and regardless of whether it was ## running or not, start it again. $0 stop $0 start # Remember status and be quiet rc_status ;; force-reload) ## Signal the daemon to reload its config. Most daemons ## do this on signal 1 (SIGHUP). ## If it does not support it, restart. echo -n "Reload service zope" $0 stop && $0 start rc_status ;; reload) ## Like force-reload, but if daemon does not support ## signalling, do nothing (!) rc_failed 3 rc_status -v ;; status) echo -n "Checking for zope: " ## Check status with checkproc(8), if process is running ## checkproc will return with exit status 0. # Status has a slightly different for the status command: # 0 - service running # 1 - service dead, but /var/run/ pid file exists # 2 - service dead, but /var/lock/ lock file exists # 3 - service not running # NOTE: checkproc returns LSB compliant status values. checkproc -p /var/run/zope.pid $PYTHON_BIN rc_status -v ;; probe) ## Optional: Probe for the necessity of a reload, ## give out the argument which is required for a reload. test $ZOPE_HOME/superuser -nt /var/run/zope.pid && echo reload ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}" exit 1 ;; esac rc_exit _________________________end of file__________________