4 ms·
> A noisy network service turned on by default... It's not installed by default in the author's example; they specifically install it in the Docker image. > I
by rlpb 6y ago
> A noisy network service turned on by default...
It's not installed by default in the author's example; they specifically install it in the Docker image.
> In my opinion, modern systems shouldn't run services in case something needs them, they should be dynamically loaded and unloaded (isn't this what dbus is for??).
That's exactly how it works in Debian today.
> ...how systemd was forced on unwilling users because of features like this...
systemd wasn't forced on anyone. If you're an "unwilling user", use a distribution that doesn't use systemd! But systemd does support socket activation, which is the exact feature you're claiming doesn't exist!
- badrabbit 6y agoI meant on distros not on OP's example. > systemd wasn't forced on anyone. If you're an "unwilling user", use a distribution that doesn't use systemd! But systemd does support socket activation, which is the exact feature you're claiming doesn't exist! It was forced on existing users. If someone gives you the choice between moving to a different house or accepting something and staying where you are, if you don't like that thing you just got forced out of your house,if you accept that thing you were forced into accepting it. If someone puts a gun to your head and asks for your money, the fact that you can chose to die does not mean your money was not taken from you by force when you opt to live. I did not claim socket activation does not exist, I even mentiones dbus as a way. I said it was not being used, services are just left running. Even GPG has a service that just idles.