systemd -- inquiring minds want to know

Emerson · 08-27-2015, 03:57 PM

Quote:

Originally Posted by sundialsvcs

Classic Unix/Linux does have one management-problem: "lots and lots of independent config-files, owned by lots and lots of independent processes, all supposed to be 'working together.'" Even though sysadmins have gotten good at this ... even have gotten used to it ... the situation is far from ideal. When you multiply the problem by "hundreds of blade computers in a modern computer center" (I still prefer mainframes, myself ...), it becomes very expensive and risky.

What does that mean? What is expensive and risky?

Head_on_a_Stick · 08-27-2015, 03:58 PM

Quote:

Originally Posted by SaintDanBert

how is someone supposed to know which package is doing the work?

Read:

Code:

man init

unSpawn · 08-27-2015, 06:35 PM

Please keep this discussion on topic.
The OPs question is on how to determine which init is running.
So this thread shouldn't derail into another {end,use}less systemd yes-or-no srt of monologues.
Thanks in advance.

*If you don't dig what I mean please have a look at the various systemd threads we've hosted the past years and see if your opinion wasn't voiced already. Chances are it was. A gazillion times over and over and over.