Jump to content
Sign in to follow this  
Dwarden

ARMA 2: Operation Arrowhead - Linux Server beta 1.60.94743

Recommended Posts

Download:

ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.60.94743.tar.bz2

ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.60.94743.tar.bz2

mirror: http://www.gamefront.com/files/21974236/a2oa-server-1.60.94743.tar.bz2

-

CRC32: CBFC9A9B

MD5: 1C72F3B7019A9A15F438CD3CFB9DC17D

SHA-1: 5DD9B7FFA66D223732C7444B9B159A7BA8676EDA

Last fix:

* code sync with win platform

* recent crashfixes (as for windows, were crossplaform)

* channel disabling support as for windows

*changes and tweaks from windows branch including for netcode

*some crashes and issues across all platforms

previous fix:

*resolved crash on custom face textures (please verify if custom faces work in MP)

*[89964] Fixed: Linux servers were never green in server list.

older fix:

*resolved long loading times (this time it should work :) )

*resolved issue with "Failed to load TextureHeaderManager" , no need use -noTexHeaders commandline parameter!

Warning: This is 1.60 branch release

Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.60 first in order to run properly.

ideal to combine with latest OA beta client:

Please provide us with feedback to this topic.

* this version brings linux in sync with actual windows server improvements and ai/mp fixes ...

Arma 2: Operation Arrowhead - Linux Standalone Server 1.60

===============================================================

Copyrigt © 2010 Bohemia Interactive Studio. All rights reserved.

For more information please visit

http//community.bistudio.com/wiki/ArmA:_Dedicated_Server%22]"]http://[/size[/url]]

Installation instructions:

==========================

1. Following programs must have been installed on your Linux-box:

tar, gcc. Optional: md5sum (for setup integrity check)

1a. On some verions of Linux (this was reported for RedHat 9

and Gentoo linux 2.4.20) the NSCD deamon must be installed to

run ArmA 2 server successfully. Caching of DNS would be sufficient.

2. Copy the whole "ArmA 2 Operation Arrowhead" directory from Windows

to some Linux-directory (arma2arrowhead). DON'T DO ANY DATA CONVERSIONS

(even "dos2unix" translation of text files is not necessary).

Example: you can use PKZIP (WinZip, PowerArchiver, etc.) on

Windows and "unzip" on Linux.

Don't use upper case letters in the ArmA2 directory name

(/home/bob/arma2arrowhead will be good, /home/bob/ArmA2ArrowHead

may cause some troubles).

ArmA2 directory should contain subdirectories "Addons", "Bin",

"Campaigns", etc.

3. Copy the "server-x.xx.tar.gz" (x.xx is version number) file into

the arma2arrowhead directory. Unpack and install it with commands:

arma2arrowhead$ tar -xjf server-x.xx.tar.bz2

arma2arrowhead$ ./install

Watch the messages - they will inform you whether your installation

is successful.

4. Dedicated server can be started in foreground:

arma2arrowhead$ ./server

Or in background:

o$ nohup ./server > out.txt 2> err.txt &

[1] <pid>

5. Running server can be stopped by executing:

$ kill -s SIGINT <pid>

Where <pid> is process-id of mother server thread (printed out in

"nohup" command).

6. ArmA2 ArrowHead server has a feature: command-line parameter

"-pid=<pid_file>". It causes creation of <pid_file> with

PID of root ArmA2 process. If IP port specified in "-port=<nn>"

parameter is busy (in usage), ArmA2 will terminate immediately

and <pid_file> won't be written..

7. The "arma2server" script is provided for automatic server

start/restart/status query/etc. Please be sure to edit

CONFIGURATION PARAMETERS in lines 12 to 18 !

After this is done, install (hard-link?) the script into

"/etc/rc.d/init.d/arma2server" file. After that it can be managed

by "chkconfig" (see info/man).

previous thread about 1.60.94342 beta linux :

Edited by Dwarden

Share this post


Link to post
Share on other sites

not this week

Share this post


Link to post
Share on other sites

maybe after RC3, the nix code transift to 1.61 isn't still finished ...

Share this post


Link to post
Share on other sites

We seriously need support for DayZ to run on Linux dedicated Server. Please add functionality for this so DayZ developers can add the code for linux servers.

Thanks alot!

Share this post


Link to post
Share on other sites

this week, we just finalizing the windows code branch then we can do nix ...

Share this post


Link to post
Share on other sites

I am also waiting on 1.62 server update for linux. Our server is usually full 24/7 but now almost nobody can play because they updated their clients. Oh and I would also love some commands to be able to interact with a mysql database on linux, either directly or through scripting. We run a life mod and it would be awesome to be able to save stats through server restarts.

Share this post


Link to post
Share on other sites

in meantime You may try run window server in headless WINE mode (it's supposed to work according to some)

Share this post


Link to post
Share on other sites

There's absolutely no way to get the 1.62 beta running on a dedi Linux 1.60 server is there?

Share this post


Link to post
Share on other sites

The only way to get the beta running on a Linux dedicated server at the moment is via WINE. It's that or wait for the 1.62 Linux server to be released. :)

Share this post


Link to post
Share on other sites
Also need Linux 1.62 patch Server all empty as eveyone has updated ETA ?

When its done and tested.

Share this post


Link to post
Share on other sites

For an emulated windows enviroment to run Arma 2 server you can use VirtualBox too. We normally use this system in the server when an update of the linux gamefiles is needed. Update virtual windows arma, then grab the files outside to the linux copy.

While waiting for the new binary we are running our server in the vbox windows.

:)

Share this post


Link to post
Share on other sites

Ah, but VirtualBox is emulation - WINE is a library. There's a big performance difference between these two architectures as WINE is more of a translator than an emulator (VirtualBox emulates a whole system, including hardware, WINE simply converts Windows API calls to Linux ones).

Share this post


Link to post
Share on other sites
Ah, but VirtualBox is emulation - WINE is a library. There's a big performance difference between these two architectures as WINE is more of a translator than an emulator (VirtualBox emulates a whole system, including hardware, WINE simply converts Windows API calls to Linux ones).

Ok, but that's another alternative and it works as a temporary solution. In a i7 cpu and 2 cores for the VM, performance hasn't been an issue in the vbox-windows-arma-server yet. 50 FPS most of the time. (like the 'real' one)

Share this post


Link to post
Share on other sites

Sounds good! Though I have to say, if you're wanting the best performance from a VM I'd choose Xen or KVM (or OpenVZ for absolutely highest performance, though it's not true virtualization since it uses the host's kernel and requires a Linux host) over VirtualBox. They've got much better kernel modules for disks as well as the ability to assign different processor architectures and dynamically allocate memory. Xen and KVM (to a lesser extent) can even pass devices through directly to the VM, eg. a NIC or GFX card.

Share this post


Link to post
Share on other sites
Sounds good! Though I have to say, if you're wanting the best performance from a VM I'd choose Xen or KVM (or OpenVZ for absolutely highest performance, though it's not true virtualization since it uses the host's kernel and requires a Linux host) over VirtualBox. They've got much better kernel modules for disks as well as the ability to assign different processor architectures and dynamically allocate memory. Xen and KVM (to a lesser extent) can even pass devices through directly to the VM, eg. a NIC or GFX card.

Thanks for all the info man. I've been wanting to try KVM myself, will try it some day out of curiosity. ;)

Share this post


Link to post
Share on other sites
Thanks for all the info man. I've been wanting to try KVM myself, will try it some day out of curiosity. ;)

KVM works well, I use Proxmox to manage the system, it is quite nice. our DayZ server is running on a Windows7 hostet by Linux KVM.

my problem is the maintanance, Windows is as a Server pain in the ass, reboots,updates...and you need vnc or RDP to connect to your server.

So i prefer a Linux one but BI nerver supported the Linux one like the Windows version..they lost already a lot of expirienced admins with a high effort to offer free servers, while the Windows Admins normaly are less expirienced and they run only for short time the server...

But try Debian with Proxmox, it works well so far, even faster then running Windows7 directly on the hardware.

---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------

same for us, we closed both Servers and just kept the DayZ in a proxmox KVM enviroment running...sad but the reality

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×