Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

I'm running Gentoo with the default SysV-style OpenRC init system. The boot time is short enough to not bother me. Is there any reason to try systemd?

share|improve this question
    
No. It's not worse to use it. –  Eddy_Em Mar 17 '13 at 20:43
5  
See the copious documentation on systemd, there you will see lots of reasons to run systemd, particularly in the management of daemons. –  vonbrand Mar 17 '13 at 22:20
    
If Gnome 3.8 hadn't forced systemd migration, I would've happily kept living with OpenRC. systemd itself isn't bad though, it's the migration pain. –  lkraav Dec 27 '13 at 19:01
add comment

2 Answers

Systemd is pretty cool. I think a lot of users resent it just because it isn't SysV init -- I certainly did for a while when fedora first adopted it (I could care less about faster boot times too). Unfortunately, my resentment was so deep that I did not bothering to learn about it, which made the issue worse.

It probably is something someone should write a nice, friendly tutorial or guide aimed at the (non programmer, non sys admin) general user. I think there's a bit of an unacknowledged elitism in the linux world that way -- although to be fair, this is a maybe a consequence of scarce resources.

I haven't used gentoo in a while and I don't know the status of systemd there. If it doesn't matter to you for now and you have better things to do beyond pouring over the docs, then don't worry.

share|improve this answer
    
There are several such tutorials; for example, linux.com/learn/tutorials/… –  mattdm Mar 18 '13 at 17:02
add comment

Ther are multiple advantages of running systemd even after booting is done, some might interest you, some might not, a quick summary:

  • Service Monitoring: systemd can monitor services and restart them on failure while most clients will not even notice the service has restarted.
  • Clean management of services: in systemd your current environment variables do not influence the environment of a manually started service.
  • Watchdog support: if you are on server hardware or an embedded platform (or even on some desktop platforms) you can have systemd talk to the hardware watchdog and trigger a reboot when critical services fail.
  • Start less on startup: while this is mostly a boot speed improvement, it also minimizes memory usage since less services are loaded into memory.
  • The journal: An easy and reliable logging daemon which logs more metadata than your classic syslogd, and allows you to easy filter on this information
  • ...

for more information i redirect you to the systemd homepage

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.