PPS: $ ps aux | grep dbus | grep -v grep dbus 347 0.0 0.0 25240 3348 ? Ss Oct22 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation lightdm 891 0.0 0.0 18028 1688 ? S Oct22 0:00 /usr/bin/dbus-launch --autolaunch a243f4e05c294b13ab6972bf4ff93907 --binary-syntax --close-stderr lightdm 892 0.0 0.0 24756 2120 ? Ss Oct22 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session lightdm 898 0.0 0.0 24756 2808 ? S Oct22 0:01 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 rocketm+ 937 0.0 0.0 18028 1828 ? S Oct22 0:00 dbus-launch --sh-syntax --exit-with-session rocketm+ 938 0.0 0.0 25012 2468 ? Ss Oct22 0:07 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session chuser 25434 0.0 0.0 18028 224 ? S Oct22 0:00 /usr/bin/dbus-launch --autolaunch a243f4e05c294b13ab6972bf4ff93907 --binary-syntax --close-stderr chuser 25435 0.0 0.0 24756 276 ? Ss Oct22 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
I guess pidof was the wrong command for trying to understand dbus. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
