On Tuesday, February 12, 2019 11:16:25 AM CET Adam Majer wrote:
On 2/12/19 10:32 AM, aplanas(a)suse.de wrote:
The reason is
about the configuration file. Sometime the defaults are
insecure, useless or simply wrong. Starting a service in those conditions
The important keyword here is "sometimes" but how do these apply
enabled services? Can I get logical answers?
Uhm I get your points and I think that you are right.
1. If something is enabled by default, why is it not
started by default?
2. Does reboot automatically makes things better when
Surely not. I understand that the same window that we give to the user to
update the configuration files, can be used to do a systemctl enable. Is
simply less work to the user.
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.
Sounds sane to me.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham
Norton, HRB 21284 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org