ResourceService doesn't start LogService

[bblackham]

Is there any reason why it shouldn't? (It's currently hard-coded not to).

If you want to start LogService yourself, you can.
If you don't want LogService at all, you can remove it from cms.conf.

(Motivated by the desire for an init script to just be able to start one program - cmsResourceService).

[stefano-maggiolo]

My motivation was that you always want to start logservice alone because if you start everything else with RS then you have no other way to see the logs while they are happening. I think at the time AWS did not pick the important logs from LS.

Since LS does also other things, especially now, and since it is easy to start it alone even when all others are started by RS, we can remove the hardcoding. If you feel inspired, you could add a new standard option to the services that tries to tell RS to toggle the autorun from that service and kill it, before going on.

But feel free to close this as soon as you remove the hardcoding of LS :)