6 ms·

> 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 ser

• rmk2 14y ago
  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.
• glogla 14y ago
  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.
  • meaty 14y ago
    +1 for htop. It's actually really useful and intuitive.
  • bkor 14y ago
    systemd tracks service status way more reliably than sysvinit. It also stops services more reliably. This due to the usage of cgroups.