Starting a server that way isn't the best of ideas. Instead of starting it as a service, why not just start it as a normal screen from a non-privileged user? That way it doesn't require root to start/stop the process.
Also, if you read the comments on that site, it mentions that it starts 2 instances, and how to fix it. *I had the issue as well, I am no expert but my solution was to comment ‘#’ out line 19* * * *replace ” screen -d -m -S $NAME $DAEMON $PARAMS ” with “# screen -d -m -S $NAME $DAEMON $PARAMS ” and I no longer have 2 instances.* The guide also has a few inaccuracies, such as saying that srcds won't run on 64 bit architecture. These days, I'd say the "right" way would be to have a dedicated non-privileged user for the tf2 server, and have nemrun to keep the server running and up to date. http://nephyrin.net/tools/nemrun/latest/ On Fri, Feb 10, 2012 at 3:11 PM, Brian <br...@doublejump.eu> wrote: > Hi, > > I recently installed SRCDS on my server. I followed this guide: > http://stevenbenner.com/2010/11/how-to-set-up-a-team-fortress-2-dedicated-server-on-ubuntu/ > > However, when I use his method of running srcds as a service in > /etc/init.d/, my server starts two instances... one on 20175 and > subsequently another on 27016, in separate screen sessions. > > I thought it might be this section, which seems to repeat itself: > > su $SRCDS_USER -l -c "screen -d -m -S $NAME $DAEMON $PARAMS" > screen -d -m -S $NAME $DAEMON $PARAMS > > > But removing the second line ends up making the server not start at all.. > > Advice appreciated. > > Brian > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
