News for hackers. Stuff that matters.
Re:Systemd: The Biggest Myths by mfjordvald on Sunday January 27, 2013 @12:17PM (#5124820)
> 3. Easy to check which daemons are running and not.

How? This is one of the things that have really annoyed me as all the systemd services have gone from service --status-all.

Re:Systemd: The Biggest Myths by rmk2 on Sunday January 27, 2013 @12:30PM (#5124867)
Have you tried either

  systemctl | grep running
or

  systemctl --type=service
The first one gives you a list of all systemd services/sockets currently running, the second one gives you a list of all systemd services, both running and exited. Or you can use

  systemctl --type=service | grep running
for the best of both worlds.
Re:Systemd: The Biggest Myths by glogla on Sunday January 27, 2013 @03:34PM (#5125548)
htop?

I'm not linux admin anymore, but I when I was, I used various service status software thingies only to find out whether the system thinks the service is running, because they tend to be wrong, and just annoy you (not starting crashed server because it "is already running" or something similar). I think debian doesn't even track service states, but I'm not sure.

Of course, with systemd it will be even more fun.

Re:Systemd: The Biggest Myths by bkor on Monday January 28, 2013 @03:04PM (#5130343)
systemd tracks service status way more reliably than sysvinit. It also stops services more reliably. This due to the usage of cgroups.
Re:Systemd: The Biggest Myths by meaty on Sunday January 27, 2013 @03:55PM (#5125625)
+1 for htop. It's actually really useful and intuitive.