On 21/01/2015 18:24, Olivier Brunel wrote:
I'll have to setup some scripts for different init stages, using
s6-svscan as stage 2, as you've described elsewhere. But I also want to
have a system to start (and stop) services in order. I see this whole
idea of order/dependency is something that is
On Wed, 21 Jan 2015 18:24:58 +0100
Olivier Brunel j...@jjacky.com wrote:
Hi Laurent,
So you mentioned breaking compatibility recently, and I figure that
might be a good time for me to mention something. I'd like to set up
my system around s6, and have been working on this lately.
I'll
On 01/21/15 19:03, Steve Litt wrote:
On Wed, 21 Jan 2015 18:24:58 +0100
Olivier Brunel j...@jjacky.com wrote:
Hi Laurent,
So you mentioned breaking compatibility recently, and I figure that
might be a good time for me to mention something. I'd like to set up
my system around s6, and have
On 01/21/15 00:27, Laurent Bercot wrote:
On 21/01/2015 00:20, Olivier Brunel wrote:
Cool; I see you've also added a tainstamp into the ready file, that's
good but you forgot to update the doc of s6-notifywhenup as well, which
still talks of empty file.
Fixed in current git.
So in the doc
On 21/01/2015 21:47, Olivier Brunel wrote:
The thing is, that you've referred to services oneshots, whereas I
would refer to longrun services oneshot services resp., i.e. I see
those as two types of services.
They are both services from a system management, higher-level, point
of view. From
On 1/21/2015 7:19 PM, post-sysv wrote:
I'm not sure what effective and worthwhile ways there are to express
service *relationships*,
however, or what that would exactly entail. I think service conflicts
and service bindings might
be flimsy to express without a formal system, though I don't
On 01/21/2015 06:09 PM, Wayne Marshall wrote:
4) in general, folks here are letting their panties get far too twisted
with the dependency problem. Actual material dependencies are
relatively few and can be easily (and best) accomodated directly in the
runscript of the dependent service. See