Linux 1.07 Dedi question

[skadog 0]

I recently installed and setup A2 1.07 dedicated server. When I edit the arma2server and add "OTHERPARAMS=-mod=@mymod" to the Configuration Parameters the mod never loads. However if I have this same parameter in my OA 1.54 dedicated server, there is no problem. What gives?

ARMA_DIR=/home/armadedi/arma2

CONFIG=server.cfg

PORT=2302

PIDFILE=${ARMA_DIR}/${PORT}.pid

RUNFILE=${ARMA_DIR}/${PORT}.run

LOGFILE=${ARMA_DIR}/log.${PORT}.txt

SERVER=${ARMA_DIR}/server

OTHERPARAMS=-mod=@wict

Alternatively I can start the server:

./server -mod=mymod

and the mod loads with out a hitch. :confused:

[viper.cless 1]

When I edit the arma2server and add "OTHERPARAMS=-mod=@mymod" to the Configuration Parameters the mod never loads.

Adding the variable to the Configuration Params section isn't sufficient.

You just defined a script variable named OTHERPARAMS, but the variables value is never passed to the server executable.

You need to edit the line

${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -port=${PORT} -pid=${PIDFILE}

in the arma2server script too by appending ${OTHERPARAMS}

[skadog 0]

Adding the variable to the Configuration Params section isn't sufficient.

You just defined a script variable named OTHERPARAMS, but the variables value is never passed to the server executable.

You need to edit the line

${SERVER} >>${LOGFILE} 2>&1 -server -config=${CONFIG} -port=${PORT} -pid=${PIDFILE}

in the arma2server script too by appending ${OTHERPARAMS}

Thanks Viper for the quick answer, it working great now. I diff'd the two files as well and I saw the missing bit.