On 2/12/19 10:32 AM, aplanas@suse.de wrote:
On Tuesday, February 12, 2019 10:21:04 AM CET Matwey V. Kornilov wrote:
12.02.2019 12:07, Adam Majer пишет:
The "never" is also actually "mostly". There are services that are auto-enabled as otherwise we would have bad user experience despite it being more secure.
https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Enabling_sys temd_unit_files
epmd.socket is auto-enabled and always been so. Auto-enabling does not assumes auto-starting. So epmd.socket is active after the next reboot, but it is not active until then.
The reason is about the configuration file. Sometime the defaults are insecure, useless or simply wrong. Starting a service in those conditions will
The important keyword here is "sometimes" but how do these apply to enabled services? Can I get logical answers? 1. If something is enabled by default, why is it not started by default? 2. Does reboot automatically makes things better when things are automatically started? 3. If default configuration is wrong or needs customization, why was the service enabled by default? Either the service is enabled and then started or we have it disabled in the first place until the user configures it. Configuration clearly includes enabling the service. - Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org