supervision  

Messages by Thread

• • Re: process supervisor - considerations for docker Gorka Lertxundi
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker John Albietz
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Gorka Lertxundi
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker Gorka Lertxundi
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Gorka Lertxundi
  • Re: process supervisor - considerations for docker Gorka Lertxundi
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker Laurent Bercot
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker Dreamcat4
  • Re: process supervisor - considerations for docker John Regan
  • Re: process supervisor - considerations for docker John Regan
• [PATCH] runsv: Fix bug in existence check for log/supervise/control. James Byrne
• from multiple sources to multiple destinations using s6-log Gorka Lertxundi
  • Re: from multiple sources to multiple destinations using s6-log Laurent Bercot
  • Re: from multiple sources to multiple destinations using s6-log Gorka Lertxundi
  • Re: from multiple sources to multiple destinations using s6-log Gorka Lertxundi
  • Re: from multiple sources to multiple destinations using s6-log Laurent Bercot
  • Re: from multiple sources to multiple destinations using s6-log Gorka Lertxundi
  • Re: from multiple sources to multiple destinations using s6-log Gorka Lertxundi
• [announce] skalibs-2.3.0.0, execline-2.0.2.1, s6-2.1.1.0 Laurent Bercot
  • RE: [announce] skalibs-2.3.0.0, execline-2.0.2.1, s6-2.1.1.0 James Powell
  • Re: [announce] skalibs-2.3.0.0, execline-2.0.2.1, s6-2.1.1.0 Laurent Bercot
• s6, musl and ENOENT Gorka Lertxundi
  • Re: s6, musl and ENOENT Laurent Bercot
  • Re: s6, musl and ENOENT Gorka Lertxundi
  • Re: s6, musl and ENOENT Laurent Bercot
• mailing list archive semi-broken Buck Evan
  • Re: mailing list archive semi-broken Avery Payne
  • Re: mailing list archive semi-broken Laurent Bercot
  • Re: mailing list archive semi-broken Laurent Bercot
  • Re: mailing list archive semi-broken Buck Evan
• "Waiting for $DEPS" loop (was: [patch: sv check should wait when svrun is not ready]) Buck Evan
• patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Crest
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Colin Booth
  • Re: patch: sv check should wait when svrun is not ready Avery Payne
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Colin Booth
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Avery Payne
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Avery Payne
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: patch: sv check should wait when svrun is not ready Avery Payne
  • RE: patch: sv check should wait when svrun is not ready James Byrne
  • runit maintenance - Re: patch: sv check should wait when svrun is not ready Gerrit Pape
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Buck Evan
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Gerrit Pape
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Lasse Kliemann
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Avery Payne
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Lasse Kliemann
  • slashpackage (was: runit maintenance) Laurent Bercot
  • Re: runit maintenance - Re: patch: sv check should wait when svrun is not ready Avery Payne
• runit source control? Buck Evan
  • Re: runit source control? Laurent Bercot
  • Re: runit source control? Steve Litt
  • Re: runit source control? Avery Payne
  • Re: runit source control? Jameson Graef Rollins
  • Re: runit source control? Buck Evan
• Fwd: sv check exit code not always helpful Buck Evan
  • Re: sv check exit code not always helpful Colin Booth
  • Re: sv check exit code not always helpful Laurent Bercot
  • Re: sv check exit code not always helpful Buck Evan
  • Re: sv check exit code not always helpful James Byrne
  • Re: sv check exit code not always helpful Buck Evan
  • Re: sv check exit code not always helpful Buck Evan
  • Re: sv check exit code not always helpful James Byrne
• supervision scripts, 2015-01 Avery Payne
• [PATCH] ignore missing processor input, tolerate backward clock jump Mike Pomraning
• [announce] s6-2.1.0.1 Laurent Bercot
• svlogd copytruncate Peter Flood
• [announce] s6-2.1.0.0 Laurent Bercot
  • Re: [announce] s6-2.1.0.0 post-sysv
  • Re: [announce] s6-2.1.0.0 Laurent Bercot
  • Re: [announce] s6-2.1.0.0 Casper Ti. Vector
  • Re: [announce] s6-2.1.0.0 Casper Ti. Vector
• Could s6-scscan ignore non-servicedir folders? Olivier Brunel
  • Re: Could s6-scscan ignore non-servicedir folders? Steve Litt
  • Re: Could s6-scscan ignore non-servicedir folders? Olivier Brunel
  • Re: Could s6-scscan ignore non-servicedir folders? Laurent Bercot
  • Re: Could s6-scscan ignore non-servicedir folders? Steve Litt
  • Re: Could s6-scscan ignore non-servicedir folders? Laurent Bercot
  • Re: Could s6-scscan ignore non-servicedir folders? Wayne Marshall
  • Re: Could s6-scscan ignore non-servicedir folders? post-sysv
  • Re: Could s6-scscan ignore non-servicedir folders? Avery Payne
  • Re: Could s6-scscan ignore non-servicedir folders? [provides-needs deps] post-sysv
  • Re: Could s6-scscan ignore non-servicedir folders? [provides-needs deps] Avery Payne
  • Re: Could s6-scscan ignore non-servicedir folders? [provides-needs deps] post-sysv
  • Re: Could s6-scscan ignore non-servicedir folders? [provides-needs deps] post-sysv
  • Re: Could s6-svscan ignore non-servicedir folders? Laurent Bercot
  • Re: Could s6-svscan ignore non-servicedir folders? Olivier Brunel
  • Re: Could s6-svscan ignore non-servicedir folders? Laurent Bercot
  • Re: Could s6-svscan ignore non-servicedir folders? Olivier Brunel
  • Fwd: Re: Could s6-scscan ignore non-servicedir folders? Avery Payne
  • RE: Could s6-scscan ignore non-servicedir folders? James Powell
• Using runit-init on debian/Jessie in place of sysvinit/systemd Jonathan de Boyne Pollard
  • Re: Using runit-init on debian/Jessie in place of sysvinit/systemd Jonathan de Boyne Pollard
• [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • [PATCH 3/4] Add info on why process is down to statusfile Olivier Brunel
  • [PATCH 4/4] svstat: Show signal name as well Olivier Brunel
  • [PATCH 2/4] supervise: Document arguments to ./finish Olivier Brunel
  • [PATCH 1/4] supervise: Fix arguments to finish Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Olivier Brunel
  • Re: [PATCH 0/4] Add info on why process is down to statusfile Laurent Bercot
• [PATCH] svstat: Account for file "ready" Olivier Brunel
• first round of optional dependency support Avery Payne
  • RE: first round of optional dependency support James Powell
  • Re: first round of optional dependency support Avery Payne
  • Re: first round of optional dependency support Avery Payne
• I need your advice on this web page Steve Litt
  • Re: I need your advice on this web page post-sysv
  • Re: I need your advice on this web page Laurent Bercot
  • Re: I need your advice on this web page Steve Litt
  • Re: I need your advice on this web page Wayne Marshall
• runit and "sv check" for dependencies James Byrne
  • Re: runit and "sv check" for dependencies Wayne Marshall
  • Re: runit and "sv check" for dependencies Charlie Brady
  • Re: runit and "sv check" for dependencies Wayne Marshall
  • Re: runit and "sv check" for dependencies Charlie Brady
  • Re: runit and "sv check" for dependencies Colin Booth
  • Re: runit and "sv check" for dependencies Crest
  • Re: runit and "sv check" for dependencies James Byrne
• [announce] s6-2.0.1.0 Laurent Bercot
  • RE: [announce] s6-2.0.1.0 James Powell
• redoing the layout of things Avery Payne
  • RE: redoing the layout of things James Powell
• Re: Logging daemon with ISO8601 filenames Vallo Kallaste
• RE: s6 init-stage1 James Powell
• Execline: was s6 init-stage1 Steve Litt
• Re: thoughts on rudimentary dependency handling John Albietz
  • Re: thoughts on rudimentary dependency handling Jonathan de Boyne Pollard
  • Re: thoughts on rudimentary dependency handling Avery Payne
  • Re: thoughts on rudimentary dependency handling Laurent Bercot
  • Re: thoughts on rudimentary dependency handling Steve Litt
  • Re: thoughts on rudimentary dependency handling Avery Payne
  • Re: thoughts on rudimentary dependency handling Jonathan de Boyne Pollard
  • RE: thoughts on rudimentary dependency handling James Powell
  • Re: thoughts on rudimentary dependency handling Luke Diamand
  • Re: thoughts on rudimentary dependency handling Laurent Bercot
  • Good news for BSD Jonathan de Boyne Pollard
  • RE: thoughts on rudimentary dependency handling James Powell
  • Re: thoughts on rudimentary dependency handling Luke Diamand
  • Re: thoughts on rudimentary dependency handling Steve Litt
  • RE: thoughts on rudimentary dependency handling Avery Payne
  • Re: thoughts on rudimentary dependency handling Laurent Bercot
  • Re: thoughts on rudimentary dependency handling Avery Payne
  • Re: thoughts on rudimentary dependency handling Laurent Bercot
  • Re: thoughts on rudimentary dependency handling Jonathan de Boyne Pollard
  • Re: thoughts on rudimentary dependency handling Luke Diamand
  • Re: thoughts on rudimentary dependency handling Avery Payne
  • Re: thoughts on rudimentary dependency handling Luke Diamand
  • Re: thoughts on rudimentary dependency handling Steve Litt
  • Re: thoughts on rudimentary dependency handling Avery Payne
  • RE: thoughts on rudimentary dependency handling Jonathan de Boyne Pollard
  • RE: thoughts on rudimentary dependency handling James Powell
  • thoughts on rudimentary dependency handling Jonathan de Boyne Pollard
  • Re: thoughts on rudimentary dependency handling Avery Payne

• Later messages