Hi Steve,
On 08/11/15 20:40, Steve Litt wrote:
> On Tue, 11 Aug 2015 19:58:59 +0200
>
> Hi j,
>
> I just got done reading http://jjacky.com/anopa/ .
>
> I love the inclusion of the needs directory, as well as directory
> after.
>
> I love the way you distinquish one-shots from long-run by whether your
> script is start or run.
>
> Reading http://jjacky.com/anopa/ , it seems like all the one-shots are
> run by PID1, whereas all the long-runs are run by s6. Does this mean
> that all one-shots must be run before the first long-run? If so, I
> think that's a too-strict restriction. If not, Anopa + s6 sounds
> tremendously encouraging.
>
> So, does Anopa give one a way of running a long-term before a one-shot?
Of course. oneshots are run as children of aa-start, which on usual
fashion during boot would happen from stage2 (aa-stage2 that is).
Basically this is how it goes:
- you use aa-stage1 as init, so it will be your PID1 on boot. It will
fork & exec aa-stage2, which will block using the trick Laurent
described in s6 doc.
- back in PID1, we exec into s6-svscan, which will then start the
catch-all logger, thus unblocking aa-stage2
- aa-stage2 will then exec aa-start, where oneshots & longruns can be
started in any required order; so oneshot services can require for
longrun services to be started, or ready, before they're started.
Cheers,
-j
>
> Thanks,
>
> SteveT
>
> Steve Litt
> August 2015 featured book: Troubleshooting: Just the Facts
> http://www.troubleshooters.com/tjust
>
Received on Wed Aug 12 2015 - 11:50:19 UTC