I am now running a 24/7 bleeding edge server. I have finished writting a script that updates the server from the subversion repository nightly, so (unless the trunk won't build under 64 bit linux) it should always been the latest revision. Get out there, grab the lattest RE version from the repository, and use it. Damn it. (server.orbitaldecay.com 28777).
Bob
Edit:
For the record, here is the shitty bash script that does it. On my server, I have a cron job that executes this script every night at 4:00 EST (GMT -4). Also for the record, pushing out development builds in a production environment without even testing that they compile is a bad idea. So if this script causes your server to explode and melt simultaneously... I'm sorry.
- {l Code}: {l Select All Code}
#!/bin/bash
# Check out the most recent revision of Red Eclipse from the official subversion repository,
# then stick servexec.cfg, servinit.cfg, and this script in the Red Eclipse directory. Set up
# a cron job to execute it as frequently as you'd like.
HERE=`dirname $0`
cd $HERE
# If the server is running, kill it
read pid < ./server.pid
kill $pid
# Update from subversion
svn up
# Do a clean build of the server
cd src
make clean
make server
cp reserver ../bin/reserver_linux_64
cd ..
# Update server name to reflect new revision in servexec.cfg
REV="$(svn info | sed -ne 's/^Revision: //p')"
DATE="$(date +%D\ %H:%M\ EST)"
eval "sed 's/^.*sv_serverdesc.*/ sv_serverdesc \"Orbitals SVN r$REV\"/' servexec.cfg > servexec.tmp"
mv servexec.tmp servexec.cfg
# Restart the server
./server.sh >> $HERE/reserver.log &
pid=$!
echo $pid > ./server.pid
Good to see someone working on sound though 
