[trasz]

But they only provide fixed functionality, while shell scripts allow for practically unlimited customization.

As for 500 lines - take a look at proper rc scripts, eg the ones in FreeBSD. They are mostly declarative; it’s nothing like Linux’ sysv scripts, which were in some ways already obsolete when first introduced (runlevels? In ‘90s, seriously?)

[lordgroff]

Yeah, this conversation seems a bit like people arguing past each other. But it's a result of the fact that the story on Linux was stuck for so long (e.g., sysvinit on Debian, Upstart with some sharp edged hacks on Ubuntu). Systemd as the solution seems to have sucked out all the air out of the room: either it's great and people are idiots, or it's the worst thing on the planet and people using it are sheep.

[passthejoe]

Yes. Exactly.

[crazy_hombre]

If you need extra customization capabilities, just run a shell script via the ExecStart= parameter and boom, you have all the power of systemd and the shell combined.

[Spivak]

You can even do one better since systemd can natively run rc scripts. If you're on a systemd based distro peak at /etc/init.d. You can even manage services with /etc/init.d and the service command.

The amount of effort systemd went through to make existing software work is genuinely heroic.

[dralley]

> But they only provide fixed functionality, while shell scripts allow for practically unlimited customization.

Why is unlimited customization a good thing in the context of a system init?

[trasz]

For the same reason it’s a good thing in other contexts. It’s the main reason Unix got popular - because it can be made to fit whatever requirement you have.

[matthewmacleod]

But they only provide fixed functionality, while shell scripts allow for practically unlimited customization.

This is the exact opposite of a good thing.