On Thu, Aug 13, 2015 at 9:37 AM, Laurent Bercot <ska-skaware_at_skarnet.org> wrote:
>
> Eh... keep a backup of your current source, if you're using it in
> a half-serious environment. The current version uses automatically
> generated services, and the scripts haven't been tested yet, it's
> the first draft.
>
I run s6-rc on my laptop, which is about as half-serious an
environment as you get.
>
> I went back and changed the way s6-rc-compile handled producer/logger
> pairs, because logged services were too much of a pain to correctly
> manage in s6-rc-update: it became insanely complex to compute when
> a service directory can be kept and when the service has to be
> stopped and restarted. Doing away with logged services makes the
> update procedure more straightforward.
>
I may be missing something, but the auto-generated log service doesn't
seem to be a thing yet. Or is that all under-the-hood changes and the
filesystem interface hasn't changed.
>
>
> But since a pipeline now includes autogenerated services, there
> needs to be a bundle containing everything, for easy takedown. So,
> autogenerated bundle, too. It's beautiful and scary at the same
> time - I feel like complexity can get out of control fast.
>
Gotcha, makes sense. I'm still glad to get rid of my explicit
service-logger bundle directories. I'm assuming though that an
explicit bundle can call out an autogenerated bundle as a requirement?
So for example an autogenerated sshd bundle (containing sshd-srv and
sshd-log) can be called out in an explicit lan-services bundle. I'd
test it out, but I don't have time right now to re-do all my logger
producer/consumer files so a recompile will break.
Cheers!
--
"If the doors of perception were cleansed every thing would appear to
man as it is, infinite. For man has closed himself up, till he sees
all things thru' narrow chinks of his cavern."
-- William Blake
Received on Thu Aug 13 2015 - 17:44:25 UTC