On Tue, Apr 17, 2018 at 08:58:06PM +0200, Reindl Harald wrote: > > > Am 17.04.2018 um 20:53 schrieb Zbigniew Jędrzejewski-Szmek: > > On Tue, Apr 17, 2018 at 11:00:55AM -0500, Ian Pilcher wrote: > >> On 04/17/2018 12:41 AM, Zbigniew Jędrzejewski-Szmek wrote: > >>> tl;dr: the proposal is to start services immediately during > >>> installation (in %post), iff they are enabled in presets and the > >>> system is live (not a chroot or such). > >>> > >>> This would mean that e.g. after 'dnf install gpm' gpm would be running > >>> when dnf exits. > >> > >> What if gpm is pulled in as a dependency? > >> > >> (gpm may not be the best example here, but Avahi definitely is pulled in > >> as a dependency sometimes.) > > > > Doesn't matter. Essentially, the thinking is that if it is safe and > > useful to start something after a reboot, it should be OK to start it > > immediately after installation too > > who tells you that i would reboot without disable said as dependency > pulled service before?? > > i could puke everytime something is pulled as dependency and started > without any use Can you give an example of such services? I see you would be impacted negatively by the proposed change, but you could either: - add a preset to override the enablement of such services, - or just do 'systemctl disable --now foo' instead of 'systemctl disable foo'. Services which are subject the guidelines allow to be enabled by default should be such that starting them briefly should not cause any permanent effects. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
