View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000108||Volume 2||Feature||public||2019-05-18 19:17||2020-01-11 11:00|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0000108: Update DBServer/MapServer Initialization|
|Description||The loadbalancer is unfortunately designed to require separate launchers (and therefore separate physical machines due to a lack of port range) to load LogServer, StatServer, ArenaServer, and RaidServer as independent roles.|
For most server deployments this is unnecessary, as typically they will be running on the same machine as DBserver. This PR essentially removes them from the required list of auto-start launcher roles (if they are not manually specified in servers.cfg) and allows for them to be started as part of a standard loadbalance config.
Additionally, a -silent switch should be added for MapServer, which can be specified in Launcher to hide the (potentially hundreds) of console windows generated as new MapServer processes spin up. Based on management of a live server, this is a logistical NIGHTMARE when actually trying to do anything over RDP.
Feature provided by CoC team.
|Tags||No tags attached.|