On Thu, 31 Jul 2008 10:56:07 -0400 Guido Günther <agx@sigxcpu.org> wrote: > We might not want to use policy-rc.d as is in sysvinit of filerc > during startup but we might consider moving these policy decisions > "no I don't want this daemon at startup, yes I want that daemon > reloaded after resume" into a policy layer that is independent of the > underlying init mechanism and which can be queried by the different > tools be it during system startup/shutdown or after/before suspend > to/from ram/disk. Cheers, Is it really necessary? I'm not a big fan of abstraction layers. They usually complicate things instead of making them easier. So far for me the sysv init process with its start and kill links is sufficient for all purposes. It's a simple and stable system. Don't add complicated cruft on top of it. I never had the need to restart daemons on suspend/resume. But if this should be supported, then I'd prefer, if extra runlevels were defined for going into suspend (similar to rc0.d) and for resuming (similar to rcS.d) Cheers, harry
Attachment:
signature.asc
Description: PGP signature