Adam Williamson <awilliam <at> redhat.com> writes:
On Tue, 2011-08-23 at 07:29 -0700, Toshio Kuratomi wrote:
> > This is broken IMO ... there is nothing inherently wrong with on
> > demand loading ... actually it is the opposite. (i.e should be done
> > whenever possible).
> >
> On demand loading is great. But the system administrator needs to have
> control to be able to turn things on and off. So we need Lennart to give us
> information on how to do that.
I believe this has already been explained several times: if you
*disable* a service, rather than *stopping* it, socket activation won't
happen until you re-enable it.
It's only if you just stop a service that
socket activation will happily start it back up again. This is the
'three levels of 'off'' stuff, IIRC.
I would say this is not a good idea with how "stop" works.
I usually stop a service for a reason. Perhaps I follow it up with
a reconfiguration or do other related work. I would not want it be started
during that time by systemd's "magic".
JB