1) No server should automatically start for a game. They are _not_ necessary for standard game playing, and can be launched from within the entertainment software. Often the server software is installed for a more temporary basis than say, something akin to Apache, and therefore should be treated accordingly.
2) Absolutely, under no circumstance, should a game schedule an open port server policy with _zero_ level of feedback notification.
I find this technique to be fundamentally flawed and insecure. We _should_ develop a game policy for server startup / shutdown.
It is also worth mentioning that an average gamer might not be familiar with the rc.* level startup / shutdown sequence format. Perhaps providing the scripts but leaving them _off_ would be wise?
I can think of a few notes:
1) No server should automatically start for a game. They are _not_ necessary for standard game playing, and can be launched from within the entertainment software. Often the server software is installed for a more temporary basis than say, something akin to Apache, and therefore should be treated accordingly.
2) Absolutely, under no circumstance, should a game schedule an open port server policy with _zero_ level of feedback notification.
I find this technique to be fundamentally flawed and insecure. We _should_ develop a game policy for server startup / shutdown.
It is also worth mentioning that an average gamer might not be familiar with the rc.* level startup / shutdown sequence format. Perhaps providing the scripts but leaving them _off_ would be wise?