5 ms·
> legacy init scripts do not actually function very well. They function as well as they're written. Some people just shouldn't be writing shell scripts that ot
by rascul 4y ago
> legacy init scripts do not actually function very well.
They function as well as they're written. Some people just shouldn't be writing shell scripts that other people use at their current level.
- theamk 4y agoHow about apache authors? The problem of runaway CGI sub-processes is one of my favorite examples of traditional init scripts falling short.
- rascul 4y agoIs that an issue with the init script or with Apache?
- Spivak 4y agoThat’s kinda the point, just run your process with no regard to daemonizing, write to stdout, stderr, crash normally with panics, don’t bother forking, don’t clean up fds, don’t think at all about privs, what’s a pid file?, what’s /dev/log?, what’s a scheduler?, and let systemd do all of this correctly for all services regardless of how well written they are.
- none_to_remain 4y agoSome times I have looked at what it takes to write an actually somewhat portable shell script and I decided was one of those people Luckily I've never been called upon to write a shell script that went beyond "works on the bash we have"