OK, I want to tackle this problem once and for all, because it
has been gnawing at the edges of my mind for some time, and Olivier
forced me to look it in the face, and it's not pretty.
The situation is this: we have a parent process P (itself child
of a grandparent process G) spawning a child
On 18/02/2015 00:22, Olivier Brunel wrote:
- First off, I found the doc to be a bit confusing, because you
alternate between talking about when loopwhilex keeps running prog, and
when it stops/exits.
Yes, it's confusing, but it's still accurate.
In fact, it's confusing enough that you yours
Hi,
Couple of things regarding loopwhilex:
- First off, I found the doc to be a bit confusing, because you
alternate between talking about when loopwhilex keeps running prog, and
when it stops/exits.
In fact, it's confusing enough that you yourself got it wrong :p
"
-n : negate the test: run pro
On 17/02/2015 20:34, Roy Lanek wrote:
The problem is w/ the regular express. W/ s6-2.1.1.0 s6-log (...)
What's that s6-2.1.1.0 you're speaking of ? Nobody has heard of
that around here...
The latest release is s6-2.1.1.1, and I cannot reproduce that
problem with s6-log here.
(In all serious
The following worked up to s6-2.1.0.1:
...
/command/export PATH /command:/etc...
multisubstitute {
define LOGS /var/log/s6/socklog-klog
define IDX \[[0-9]+\]
define SID SID[0-9]+
define LBL \[[[:space:]]*[0-9]+\.[0-9]+\]
define KRN_ANY kern\.[[:alnum:]]+
Paul Jarc wrote:
> Colin Booth wrote:
> > It did necessitate breaking the Freebsd port of Paul Jarc's runwhen.
>
> I have a new version in the works that will build with the latest
> skalibs.
Good to hear :)
-- Daniel
