On Tue, Aug 23, 2011 at 01:12:31PM +0200, drago01 wrote: > On Mon, Aug 22, 2011 at 6:45 PM, Tom Callaway <tcallawa@xxxxxxxxxx> wrote: > > On 08/18/2011 06:28 AM, Lennart Poettering wrote: > >> On Wed, 17.08.11 16:43, Tim Waugh (twaugh@xxxxxxxxxx) wrote: > >> > >>> Oh, I just noticed this: > >>> > >>> https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd#Socket_activation > >>> "Since Fedora currently doesn't want any services to do on-demand > >>> loading, all socket activated services must autostart." > >> > >> Uh, oh. I think CUPS is definitely something we should lazily socket > >> activate instead of run it unconditionally. > >> > >> Spot, Bill, what's the reason for this wording in the guidelines? As > >> CUPS is something we really should start only when needed, why do we > >> have this wording in the guidelines? Can we relax this? > > > > I think FESCo needs to decide what its policies are wrt on-demand > > loading, then we can adjust the Packaging Guidelines appropriately. > > 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. Lennart also needs to give us information on how to write .socket files. With those in hand, guidelines would and fesco would be able to ship with on-demand-loading that was off by default (does nt load at all) but the system administrator would be able to enable the service so that it would start to load on-demand rather than at boot. -Toshio
Attachment:
pgpUuBe8D4IEx.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
