3 ms·

First, there's no requirement to use bash. Any shell that has an exec equivalent and can redirect stderr to stdout will work. There's not even a requirement for

by dsr_ 4y ago

First, there's no requirement to use bash. Any shell that has an exec equivalent and can redirect stderr to stdout will work. There's not even a requirement for it to be a script -- daemontools-style supervisors don't parse the run program, they execute it. It's pretty convenient to use the setuidgid tool, though. So if you want to run starlark, or oil, or your favorite lisp dialect, go ahead. In summation: bash isn't the problem here.

dijit 4y ago
That's a really good point actually; Nothing prevents us using alternative interpreters for rc.d, ones with hooks for process supervision, hooks for something akin to cgroups, centralised logging and so on. But as a user who makes init scripts: you can do anything, which is pretty liberating when you really think about it.