On Thu, 22.07.10 19:59, Matthew Miller (mattdm@xxxxxxxxxx) wrote: > > On Fri, Jul 23, 2010 at 01:49:12AM +0200, Lennart Poettering wrote: > > > My impression from the documentation is that systemd-install enable will > > > cause the service to be enabled on the next reboot. Is that not > > > correct? > > Yes, unless you aks the init system to reload. > > Wait, am I correct in understanding that (pseudocode -- actual commands may > be wrong): > > systemctl enable apache.service > > will not cause apache to be started immediately, but > > systemctl enable postfix.service > systemctl daemon-reload > > will cause postfix to start, and as a side-effect also start the apache that > was enabled earlier but not intended to start? > > That would be surprising! Well, part of the changes I was now suggesting is that we do the init daemon configuration reload always and implicitly by default. I think doing that is smart since it removes the chance that people can go wrong and might be confused why the change that they just made is not taken into account. That would mean that the lines above would actually be mostly equivalent, except that the init daemon configuration in the first example is reloaded once, and in the second example twice. Note that "systemctl enable foo.service" will (with my suggested changes in place) result in foo.service to be started. For Fedora we generally wouldn't want that anyway except for very few niche cases. Other distros have other policies there, and for example on Debian servcies that are installed are started right-away. Those distros should then simply place an additional "systemctl start foo.service" in their %post section (or however that is called for .deb) Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
