While shell based RC systems do offer flexibility they also have downsides including copy and paste leading to subtly different behaviour across units. Dependency resolution was also a bit of a hack on top of scripts to deal with concepts like run levels.
The declarative approach of a proper configuration is a better and more scalable solution.
in systemd runlevels are basically just targets (it still sets rc?.d symlinks in /etc akaik) which have services they want and are wanted by, it’s the basis for dependency handling
plus you get cool security features like syscall filtering, capability limits, user switching, etc
You can end up with a lot of boiler plate code and with duplication you run the risk that one unit tweaks the boiler plate in a way that behaves differently. This isn’t insurmountable and a lot of rc scripts source a library of common functions shared between units. However from the point of view of the executor each unit is it’s own whole ball of shell script code.
While shell based RC systems do offer flexibility they also have downsides including copy and paste leading to subtly different behaviour across units. Dependency resolution was also a bit of a hack on top of scripts to deal with concepts like run levels.
The declarative approach of a proper configuration is a better and more scalable solution.
deleted by creator
in systemd runlevels are basically just targets (it still sets rc?.d symlinks in /etc akaik) which have services they want and are wanted by, it’s the basis for dependency handling plus you get cool security features like syscall filtering, capability limits, user switching, etc
deleted by creator
You can end up with a lot of boiler plate code and with duplication you run the risk that one unit tweaks the boiler plate in a way that behaves differently. This isn’t insurmountable and a lot of rc scripts source a library of common functions shared between units. However from the point of view of the executor each unit is it’s own whole ball of shell script code.
deleted by creator