03-09-2009, 06:30 PM
If im testing a server via ssh with a console and it gets stuck on startup cuz i forgot to add +map cp_dustbowl or whatever and i hit crtl+z to stop it and restart it with +map the server port has changed +1 however the startup line reads 27015 still the new port will become 27016 and so on... anyone know how i can like LOCK the port?
Linux OS - CentOS5
Panel - Swiftpanel
Linux OS - CentOS5
Panel - Swiftpanel