Re: Option for runsv/runsvdir to specify how many times to restart a service in a certain time period before giving up?

[Alex Smith <alex@alex-smith.me.uk>]

Alex Efros wrote:
> Hi!
> 
> On Mon, Oct 30, 2006 at 01:13:21PM +0100, Dra?en Ka?ar wrote:
>> Sure, but if something's a common need for a large group of users, then
>> they call it a feature. Some of those who don't need such feature call it
>> a bloat, but I don't think that's a valid argument.
> 
> No. Bloat isn't equal to 'new feature'. Bloated software isn't equal to
> feature-rich software. But if software has wrong features added in wrong
> places (from architecture view) then it's become bloated very quickly.
> 
> Maybe it's good idea to include additional script in runit package (or
> distribute it separately) which can be used from ./finish script this way:
> 
>     # add 5 minutes timeout if service was started 5 times in last 10 sec
>     restart-timeout --interval 10 --tries 5 300
> 
> But adding this functionality to runit is a bad idea just because you
> already can develop that restart-timeout script using current runit,
> and adding this feature to runit doesn't provide any additional gains.
> After all, it's a Unix Way.
> 

Ok, I could try to write something like this myself, but just one 
question - if the services is running ./finish, what does sv start try 
to do? I mean, the documentation on runit's website says to use sv start 
for dependencies. If a service is started that runs sv start 
some_service, and some_service is running ./finish, what would happen?

Thanks,
Alex

-- 
Alex Smith
Frugalware Linux developer - http://www.frugalware.org