search

gdaws / hopmod

Automatically exported from code.google.com/p/hopmod
0 stars 0 forks source link

Multiple server problem #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. compile a hopmod server
2. execute /bin/newserver.sh
3. configure different ports for multiple servers
4. try to start them with each server's /bin/server

It always uses port 28785, no matter what you define in the configs, so you 
have to start each server with "screen /bin/sauer_server" and restart the 
terminal(pretty annoying with 7 servers)

What version of the product are you using? On what operating system?
r1923
Linux Debian 5.0
on a virtual server with 768MB RAM

Please provide any additional information below.
I'm just wondering... why aren't you supposed to start /bin/server as root 
anyway? I know it doesn't have anything to do with the problem but I can't see 
how this make sense(especially since most people run sauerbraten servers on 
root servers, you have to comment it out)

Original issue reported on code.google.com by andreas....@gmail.com on 13 Aug 2010 at 7:10

GoogleCodeExporter commented 8 years ago 
What is the server output when bin/server is run? Check the error log file at 
log/error.log to see if there is a script error occurring at startup time, if 
there is then it could be causing server.conf to be missed. Recently, some 
users have reported an issue about scripts not loading because of a problem 
with the lua filesystem module, this is probably the problem you're having, 
which I think is resolved after r1923. So svn update your working copy and try 
running again.

The hopmod start script prevents you from starting a game server process under 
root user. There's no reason to give your game server root access, it's just a 
security risk. The game server only needs read and write access to files in the 
hopmod directory.

Original comment by graham.d...@gmail.com on 15 Aug 2010 at 10:09

GoogleCodeExporter commented 8 years ago 
well I don't have any problems with starting multiple servers on debian 5.0
I also did use the bin/utils/newserver.sh ( -> utils ) I used a newer revision.
So I think this issue might be set to fixed :?

Original comment by c.zy...@gmail.com on 6 Dec 2010 at 2:59

GoogleCodeExporter commented 8 years ago

Original comment by graham.d...@gmail.com on 15 Dec 2010 at 12:35