On Mar 18, 2012 3:52 PM, "Canek Peláez Valdés" <can...@gmail.com> wrote: > > If the config file doesn't exists, the service will not start, and you > can check the reason why with > > systemctl status sshd.service > > And of course you can set another mini sevice unit file to create the > hostkeys. But I repeat: I think those tasks belong into the package > manager, no the init script. >
Between installation by package manager and actual execution by the init system, things might happen on the required file(s). Gentoo's initscript guards against this possibility *plus* providing helpful error messages in /var/rc.log Or, said configuration files might be corrupted; the OpenRC initscript -- if written defensively -- will be able to detect that and (perhaps) fallback to something sane. systemd can't do that, short of putting all required intelligence into a script which it executes on boot. Now, if one has to put all the intelligence into a script file which gets executed by systemd, that results in a system that's more complex than plain OpenRC. Not only would one need to maintain the starting script, but one must also maintain systemd + dbus. So, the *only* benefit I can see about systemd is the smarter parallel startup of services. And believe me if I say that server guys (the ones handling tens or even hundreds of servers) would much prefer sequential startup of services than parallel ones. The former is deterministic, the latter is not. Rgds,
