On Tue, Apr 17, 2018 at 2:53 PM, Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > 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. It's very application and local configuration specific. The "nginx" software, for example, may expect some very real configuration dependencies before startup to avoid conflicting with an active webserver on the same port. When configuration tools like chef or ansible install new configurations, the default configuration may not even be compatible with what they have previously set up, and the service restart would thus fail.until the rest of the deployment is completed. But if the rpm installation reports failure because of the failed service start, the configuration software may never be able to get past that reported failure. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
