On Feb 10, 2014, at 10:23 , Eero Volotinen wrote:

> 2014-02-10 9:08 GMT+02:00 Andrew Z <[log in to unmask]>:
> 
>> Hello,
>> i finally caved in and started reading on systemd. It apperas it (
>> systemd) will be enabled by default on EL7.
>> Does it mean i'll have to manually move all init scripts i wrote over the
>> years ? I think the short answer is "no", but just want to clarify.
>> // old unhappy guy ramblings
>> Especially since i'm not too happy about these thousands of files to
>> support systemd...
>> // ramblings off.
>> 
>> 
> You also need to use firewalld and network manager also on servers...

No you don't. Please, no FUD here. It helps nobody.

Systemd, on the other hand, will be impossible (or just very hard?) to
avoid. But it seems to work as advertised, is very well documented, and
does have a few advantages over sysvinit (and upstart in compatibility
mode).

I've found one case so far where an old init script didn't work: There's
a timeout of 10 (or 5?) minutes for each service to start up. If you
have an init script that could take longer, a unit file is the only
solution because only for those the timeout can be changed or disabled.
Creating a systemd unit file simply reusing the old script without
any modification and disabling the timeout was pretty simple in our
actual case though.

-- 
Stephan