Re: Respawn limit for runsv?

[Gerrit Pape <pape@smarden.org>]

On Fri, Feb 11, 2005 at 11:21:20PM -0600, Charles Duffy wrote:
> On Fri, 11 Feb 2005 22:13:43 -0500, Charlie Brady wrote:
> > You say that respawning software is a reasonably common problem. Whenever
> > I've seen it, it was a configuration problem. Or rather, there was a
> > configuration problem, and the respawning was a symptom. I didn't see the
> > respawning as a problem. The automated respawning is a feature.
> 
> Certainly, when it occurs, it's a symptom of a larger problem. That's not
> to say that it wouldn't be useful to have more configurable respawning --
> ranging from the simple "no more than N times in M minutes" to backoff
> algorithms akin to those used for TCP.
> 
> Putting these more complex algorithms into runit, I agree, isn't
> necessarily appropriate -- but that's why he mentioned having a second
> process responsible for implementing them.

I also think a separate program is appropriate for such special
services.  Another solution to the problem with log messages getting
out-rotated is to have the startup and failing messages of the service
written to a different log directory maintained by the same svlogd
service.

Regards, Gerrit.