Re: staggering runsv startup

2015-06-06 Thread Wayne Marshall
Off the top of my head an easy solution in perp that requires no special or supplemental scripting, flagfile tricks, etc. For multiple service instances of /usr/bin/myserv -- named myserv00, myserv01, myserv01, ..., myservNN -- deploy the following set of service definitions. First, basic

RE: staggering runsv startup

2015-06-04 Thread James Powell
: Steve Littmailto:sl...@troubleshooters.com Sent: ‎6/‎4/‎2015 3:33 PM To: supervision@list.skarnet.orgmailto:supervision@list.skarnet.org Subject: Re: staggering runsv startup On Fri, 05 Jun 2015 00:10:05 +0200 Laurent Bercot ska-supervis...@skarnet.org wrote: What you really want is a real

Re: staggering runsv startup

2015-06-04 Thread Steve Litt
On Fri, 05 Jun 2015 00:10:05 +0200 Laurent Bercot ska-supervis...@skarnet.org wrote: What you really want is a real service manager that works on top of a process supervision system and that would managed a complete, ordered initialization sequence for you. Steve is saying that process

Re: staggering runsv startup

2015-06-04 Thread Laurent Bercot
On 04/06/2015 22:41, Jameson Graef Rollins wrote: What I would like is to somehow stagger the startup of the processes, to avoid the resource contention. I could do this by putting a random sleep into the ./run scripts, but this would also cause random startup delays on subsequent process

Re: staggering runsv startup

2015-06-04 Thread Steve Litt
On Thu, 04 Jun 2015 13:41:12 -0700 Jameson Graef Rollins jroll...@finestructure.net wrote: Hi, all. I am using runit to supervise a large set of nearly identical processes. Each process accesses certain IO-bound shared resources (e.g. NFS mount) at startup. At system initialization, when

Re: staggering runsv startup

2015-06-04 Thread Jameson Graef Rollins
On Thu, Jun 04 2015, Steve Litt sl...@troubleshooters.com wrote: In the 1 script, put down files in every directory under /service except one called order. Then, the order process is called, and it erases the down file from one at a time, sleeping 1 second after each. When all of them have

Re: staggering runsv startup

2015-06-04 Thread Steve Litt
On Thu, 04 Jun 2015 14:44:38 -0700 Jameson Graef Rollins jroll...@finestructure.net wrote: On Thu, Jun 04 2015, Lucy Pseudonym ne.tet...@gmail.com wrote: You can create `down` files in the service dirs as described in [1] and enable the services from a script at boot time. Hi, Lucy.

Re: staggering runsv startup

2015-06-04 Thread Jameson Graef Rollins
On Thu, Jun 04 2015, Lucy Pseudonym ne.tet...@gmail.com wrote: You can create `down` files in the service dirs as described in [1] and enable the services from a script at boot time. Hi, Lucy. That's an interesting suggestion. It would require building out more/other infrastructure, though,

Re: staggering runsv startup

2015-06-04 Thread Laurent Bercot
What you really want is a real service manager that works on top of a process supervision system and that would managed a complete, ordered initialization sequence for you. Steve is saying that process supervisors are lacking real service management capabilities, and he's right. Process