Comment 33 for bug 109434

     Hi,

* Franck <email address hidden> [2016-08-23 14:27:46 CEST]:
> 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.

 Of course there is none because that's an approach to the issue that
was rather a strange approach in the first place.

 systemctl disable wesnoth-1.12-server # would be the proper way

 But: It doesn't get enabled by default in the package, since the 1.8
times, 6 years ago. See above.

> So I think that:
> - the fact that the server will run on each boot should be much more obvious on installation

 This shouldn't be the case. I'll have to test that in an 16.04
environment, but as far as I can tell this shouldn't happen.

> - there should be simple way to disable it (something like /etc/default/wesnoth)

 "systemctl disable wesnoth-1.12-server" is the simple way and works
with every single service. No strange file that might or might not be
supported or used.

> 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)

 That's why it was changed six years ago. :)

> (notice this bug was opened... 8 years ago)

 (notice this "bug" was resolved in wesnoth... 6 years ago)

 Enjoy,
Rhonda
--
Fühlst du dich mutlos, fass endlich Mut, los |
Fühlst du dich hilflos, geh raus und hilf, los | Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los |