Problems setting up Chrooted Enemy Territory v2.55 server
 

I have followed the directions outlined here:
http://www.tjw.org/etded/

I had to copy the lib64 libs since I am working on a Cent OS 5.5 Xen VM. And used username enemy-territory instead of et adjusting the relevant init script lines accordingly.

I am able to run "chroot /usr/local/enemy-territory" and get to shell, I am root when I run that, of course.

starting /enemy-territory/etded I get:
[I have no name!@cobra /]#/enemy-territory/etded
bash: /enemy-territory/etded: /bin/sh: bad interpreter: Permission denied

starting /enemy-territory/etded.x86 I get:
[I have no name!@cobra /]#/enemy-territory/etded.x86
ET 2.55 linux-i386 May 27 2003
----- FS_Startup -----
Sys_Error: Unable to create directory "/root/.etwolf", error is No such file or directory(2)

I have set all files to be owned by root but are part of group enemy-territory. I can see the files in chroot.

Running the start script yields:
[root@cobra local]#/etc/rc.d/init.d/rc.etded start
[root@cobra local]#Could not find a PID for /usr/local/enemy-territory/enemy-territory/etded.x86!
If etded.x86 is actually running, update /usr/local/bin/etded.sh
so that it can properly detect the PID of /usr/local/enemy-territory/enemy-territory/etded.x86.
[root@cobra local]#

As any normal user I can run the program fine without problems. I am wanting the chroot setup, so I can limit collateral damage if we get hacked, and to allow me to have a non chroot location to store backup copies of the working directory.

The CentOS image I was using was toast. I switched to FC12 and evertyhing without a hitch. Lots of use of ldd on the various bin and library files used by ET allowed me to get everything needed to get ET running put in the lib and lib64 folders did the trick.