English
Ask Your Question
3

Which service is doing what?

asked 2012-02-16 12:28:00 +0000

Benjamin gravatar image

In another question I was concerned about the iSCSI service taking precious boot time away, while I did not need this service at all.

I have also found that to improve boot time I could use systemd and systemctl:

  • systemd-analyze blame
    returns a list of various services launched at boot and the time it took to launch them and do their thing in milliseconds.
  • systemd-analyze plot > plot.svg
    creates a graphic plot of the latest boot in SVG format.
  • systemctl stop SERVICENAME.service and systemctl disable SERVICENAME.service
    stop a running service and disable it at boot respectively.

etc. more on this post.

Now I removed some services based on the suggestion of more experienced and knowledgeable users. My boot dramatically was shortened by almost 60 % (from 62s to 26s!). Some of the services I removed were:

  • sendmail.service
  • sm-client.service
  • iscsi.service
  • udev-settle.service
  • fedora-wait-storage.service

It is also suggested I should remove:

  • fcoe.service

It seems that much services are running while I do not need them. On the other hand I have hardly any information about those services. Some are obvious in their use like the sendmail.service, others are more obscure like the fedora-wait-storage.service.

If I now run systemd-analyze blame it returns a list of services launched at boot. How can I find out what service does what? Is there a way to query these services about their identity and activity? Is there documentation? How to determine what service I need and which one I don't?


11885ms fedora-storage-init.service
  4966ms fedora-loadmodules.service
  3499ms systemd-vconsole-setup.service
  2744ms fedora-readonly.service
  2574ms remount-rootfs.service
  2436ms media.mount
  2416ms sys-kernel-debug.mount
  2405ms dev-hugepages.mount
  2397ms sys-kernel-security.mount
  2387ms dev-mqueue.mount
  1934ms udev-trigger.service
  1807ms netfs.service
  1679ms mdmonitor-takeover.service
  1622ms fcoe.service
  1608ms udev.service
  1493ms systemd-remount-api-vfs.service
   784ms sys-kernel-config.mount
   503ms fedora-storage-init-late.service
   492ms NetworkManager.service
   490ms systemd-sysctl.service
   410ms lvm2-monitor.service
   389ms avahi-daemon.service
   337ms console-kit-log-system-start.service
   291ms rsyslog.service
   256ms systemd-logind.service
   239ms livesys.service
   233ms ip6tables.service
   230ms iptables.service
   216ms systemd-readahead-replay.service
   213ms auditd.service
   211ms boot.mount
   207ms systemd-readahead-collect.service
   199ms sshd-keygen.service
   176ms irqbalance.service
   147ms abrt-vmcore.service
   146ms systemd-tmpfiles-setup.service
   134ms mcelog.service
   122ms abrt-ccpp.service
   114ms dbus.service
    79ms console-kit-daemon.service
    60ms sandbox.service
    37ms home.mount
    30ms livesys-late.service
    12ms systemd-user-sessions.service
     7ms rtkit-daemon.service
     7ms accounts-daemon.service
     0ms sys-fs-fuse-connections.mount
edit retag flag offensive close delete

Comments

fcoe should be Fiber Channel Over Ethernet, I guess...

ztank1013 ( 2012-02-16 14:10:42 +0000 )edit

@skytux: nope. Only those I mentioned.

Benjamin ( 2012-02-16 19:16:05 +0000 )edit

I found it now, It took 79ms in your system, but it took 25075ms in my system!! Do you know why?

skytux ( 2012-02-16 19:24:46 +0000 )edit

@skytux: no sorry, as I said, I hardly know any of these services and I don't know what console-kit-daemon does. I have read there is a way to run a debug mode to find out what makes a process slow, I forgot where, if I find a link I will share.

Benjamin ( 2012-02-16 19:29:55 +0000 )edit

@Benjamin: ConsoleKit is required to have stuff like audio, PackageKit, device mounting/hotplug actually work.

jcape@ignore-your.tv ( 2012-04-11 14:18:22 +0000 )edit

3 Answers

Sort by ยป oldest newest most voted
1

answered 2012-02-27 21:29:02 +0000

mooninite gravatar image

You can find out the service description by calling: $ systemctl status foo.service

You can find out what package contains the service by calling: $ rpm -qf /lib/systemd/system/foo.service

You should be able to conclude what service is doing what from those two commands.

edit flag offensive delete publish link more
1

answered 2013-02-14 16:45:54 +0000

lennart gravatar image

This will give you a quick description of what a service does:

systemctl status foo.service

For many services (including all services systemd itself ships), you can also use this:

systemctl help foo.service

Which will get you longer help texts about the specific service.

edit flag offensive delete publish link more
0

answered 2012-02-16 14:45:57 +0000

skytux gravatar image

Did you disable console-kit-daemon.service? Because in my Fedora 16 it is the first in the output of "systemd-analyze blame": 25057ms console-kit-daemon.service... 25 seconds!!!

edit flag offensive delete publish link more

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!

Add answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers to your questions.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Question tools

Follow
3 followers

Stats

Asked: 2012-02-16 12:28:00 +0000

Seen: 10,301 times

Last updated: Feb 14 '13