I will disagree with dobey. The best thing to do is to learn how to find it for yourself.
List all processes and their PID tree structure:
pstree
init─┬─ModemManager───2*[{ModemManager}]
├─NetworkManager─┬─2*[dhclient]
│ ├─dnsmasq
│ └─3*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─colord───2*[{colord}]
├─cron
├─cups-browsed
├─cupsd
├─dbus-daemon
....
So dbus-daemon is started by init
. However notice that there is more than one dbus-daemon running.
manos@box:~$ ps aux | grep dbus-daemon
message+ 845 0.0 0.0 40668 2620 ? Ss 10:48 0:03 dbus-daemon --system --fork
manos 2480 0.0 0.0 40248 2428 ? Ss 10:48 0:01 dbus-daemon --fork --session --address=unix:abstract=/tmp/dbus-o3GMKn9JC1
manos 2569 0.0 0.0 39248 2004 ? S 10:48 0:00 /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
There are namely (at least) two instances of dbus-daemon running. One is started by init and it's system wide and the other is started for the user when he logged in. Watching the full PID tree structure (with pstree
) you can visually locate exactly which process started the second instance.
pstree
andpstree -p
to see the actual PIDs