Anton Aylward wrote:
On 10/01/2014 11:41 AM, Andreas Mahel wrote:
One more word to units: I've got the impression that you, like some other people on this list, view units like some reimplementation of the service by systemd, which would make systemd a big, monolithic something. However, after looking at some of these units, I see that they are merely configuration files providing the information needed to start,stop, etc. the service. Here you can find the executable that will be run (i. e. /usr/bin/cron), command line parameters, PID file location, etc. This information is used to run a general service control flow, whose logic probably very much resembles what you also find in the init.d scripts (if you compare them, you'll find that most of them are very similar, at least the service control scripts). On top, the unit config file provides dependency information to allow parallel start of independent services.
All in all it's mainly "only" a different way to start/stop the same service executables.
An analogy here is the old favourite Xinetd. It uses similar "unit" files for the services it dispatches and each one has the name of the executable that applies.
And xinitd has long been regarded as a graceless way to solve the problem, but tolerated because it's small and doesn't get in the way of things. That is NOT grounds to grow xinetd into THE init system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org