On Ubuntu 16.04, I was hit by the unexpected (by me) behaviour of wesnoth-server, and noticed it just now (after probably 6 month running the server on each boot. My first idea was to go to /etc/default/wesntoh, looking for a ENABLE=1, but there is none.
So I think that: - the fact that the server will run on each boot should be much more obvious on installation - there should be simple way to disable it (something like /etc/default/wesnoth) I support the view that installing a game server is most of the time for playing a network game occasionally, and running a permanent game server is probably a less frequent use case (which might require explicitly enabling the server on boot) (notice this bug was opened... 8 years ago) -- You received this bug notification because you are a member of Debian/Ubuntu Games Team, which is subscribed to wesnoth in Ubuntu. https://bugs.launchpad.net/bugs/109434 Title: Installing a server for a game automatically auto-inits and runs every boot. Status in tremulous package in Ubuntu: Incomplete Status in wesnoth package in Ubuntu: Won't Fix Status in wesnoth-1.8 package in Ubuntu: Fix Released Bug description: Binary package hint: tremulous-server Summary: Installing the means to start a server for an entertainment game automatically puts it into the /etc/rc* startup sequence, thereby potentially opening a large security hole. This happens with little information to the end user, and should be _optional_ or offer a quick and easy way to see what is happening with the rc* startup sequences. Affects: tremulous-server, wesnoth-server to mention two. I suspect there are more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tremulous/+bug/109434/+subscriptions _______________________________________________ Pkg-games-ubuntu mailing list Pkg-games-ubuntu@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-games-ubuntu
