[sgtcodfish]

Do you have an example of a situation where a problem in systemd required you to patch the source and recompile, or are you just making a general statement?

Specifically a problem that couldn't be fixed by changing systemd unit files?

(I don't mean for this to sound in bad faith; I'm genuinely curious as a user of systemd)

[johnr2]

> Do you have an example of a situation where a problem in systemd required you to patch the source and recompile, or are you just making a general statement?

General statement.

[PlutoIsAPlanet]

You could use that argument and say do you need to look at all the code for the dozen shell programs you're calling in that init file to diagnose problems.

[shawnz]

Don't forget the shell itself

[egberts1]

Yes, I do have a problem with systemd dhclient module.

It doesn’t work with Juniper routers that many large ISP providers use.

So I resort to ISC DHCP and its flexible DHCP OPTIONS.

[majewsky]

That issue is besides the point:

1. It's not relating to the service manager part of systemd. It sounds like a problem with systemd-networkd which is a component that is entirely optional and easily replaced even on a systemd-based system (as you admit yourself).

2. The original question was about bugs in systemd that require inspecting C code where the equivalent bug on a non-systemd system could be diagnosed by inspecting shell scripts. ISC DHCP is not written in shell script.

[vbernat]

So, you didn't need to recompile or debug anything. Just switch to another DHCP client.

[johnny22]

which distro uses the systemd dhcp client by default? Even Fedora doesn't do that.