in Ideas, Done · 125 words

A supervise-like tool that's a bit more flexible and didn't need svscan (you'd start and stop it by hand) or svc (make it respond properly to SIGTERM, SIGHUP etc., and write the supervisor's PID to a pidfile). You could even do svscan-style logging by having, say, a -e switch that made it redirect its child's stderr to its stdout, and then just piping the output to another instance of it. There's probably no need for supervise's "down" functionality -- if you don't want the child running, then don't run the supervisor. An option to specify the delay in seconds before restarting the child would be useful.

Implemented; see batvise. I've gone back to freedt since, to avoid the huge trees of do-very-little processes this method required.