4 ms·
This is why upstream developers should use /etc/default/ to place daemon configuration files into. Then the configuration file could have "START=no", and even t
by atoponce 12y ago
This is why upstream developers should use /etc/default/ to place daemon configuration files into. Then the configuration file could have "START=no", and even though the policy would start the daemon by default, the upstream developer could prevent this from happening.
- fsniper 12y agoBut if it's not covered yet rc-d policy would help.
- regularfry 12y ago> This is why upstream developers should Eh, not so much. Any system which tries to convince upstream to change their ways is going to be fraught, so we're always going to need another way to force the behaviour we want in spite of the upstream.