A2OA Linux Server beta 1.59.84216

[peppe 10]

Hello,

this is my launch script:

ARMA_DIR=.

CONFIG=server159.cfg

CFG=arma2oa159.cfg

PORT=2326

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

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

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

SERVER=${ARMA_DIR}/server159b

PROFILE=${ARMA_DIR}/playerser/playerser.arma2oaprofile

NAME=playerser

OTHERPARAMS='-cpucount=2 -mod=expansion/beta;expansion/beta/expansion'

... what wrong?

thank you for your kind reply

Peppe

ps.

... maybe the executable place? I put the new one in the game root.

Edited September 6, 2011 by peppe

[byteslam 10]

Hello,

this is my launch script:

ARMA_DIR=.

CONFIG=server159.cfg

CFG=arma2oa159.cfg

PORT=2326

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

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

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

SERVER=${ARMA_DIR}/server159b

PROFILE=${ARMA_DIR}/playerser/playerser.arma2oaprofile

NAME=playerser

OTHERPARAMS='-cpucount=2 -mod=expansion/beta;expansion/beta/expansion'

... what wrong?

thank you for your kind reply

Peppe

ps.

... maybe the executable place? I put the new one in the game root.

do you really have placed the ArmAII Files into the system root?

on my server is looks like:

ARMA_DIR=/home/arma/arma2oaserver

The path must be absolute from the root....

[visceralsyn 10]

Game root, and system root are not the same thing. He clearly states he moved it to the 'game root'.

He should have left the Beta exe in its directory and edited the 'SERVER=' line with the path to the Beta exe.

...Syn...

[byteslam 10]

Game root, and system root are not the same thing. He clearly states he moved it to the 'game root'.

He should have left the Beta exe in its directory and edited the 'SERVER=' line with the path to the Beta exe.

...Syn...

We are on Linux, there is no EXE :-) anyway, the directory is absolute from the system root path...

[visceralsyn 10]

Linux binary, is the same as a Windows *.exe, they do the same thing, different names.

If he configures:

ARMA_DIR=.

Then he can configure the following, with a relative path:

SERVER=${ARMA_DIR}

...Syn...

Edited September 6, 2011 by VisceralSyn
typos and other grammatical errors, as usual...

[Vixente 10]

By the way, anyone knows where the .rpt file is located in linux? or if it even exists? .log file is fine, but i recall that .rpt in windows had much more info about errors about missions/addons and even server crash errors.

[Reezo 45]

By the way, anyone knows where the .rpt file is located in linux? or if it even exists? .log file is fine, but i recall that .rpt in windows had much more info about errors about missions/addons and even server crash errors.

I usually check (example for a server running on port 2302):

log.2302.txt

it looks pretty much as the equivalent of the RPT file.

[eddieck 10]

I usually check (example for a server running on port 2302):

log.2302.txt

it looks pretty much as the equivalent of the RPT file.

That's only the server log file.

The RPT data is outputted to STDERR, and is not part of the log file. If you want it, you could use Bash IO redirection:

arma2oaserver 2>server.rpt

(If you're using start-stop-daemon in your init scripts, you could write a launcher script which would then do this.)

I also use IO redirection for the main server log - it updates in real-time rather than the every 5 minutes or so using the built-in logging capability.

[Reezo 45]

I see what you mean, yes there is a difference. +1 what Eddieck said.

[Vixente 10]

I love you eddieck :286: :D