Attachment 123023 Details for Bug 94508 – systemd-cgls output

systemd-cgls output

systemd-cgls (text/plain), 6.38 KB, created by Pacho Ramos on 2016-04-18 08:41:06 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Pacho Ramos

Created: 2016-04-18 08:41:06 UTC

Size: 6.38 KB

patch

obsolete

>Control group /:
>ââinit.scope
>â ââ1 /usr/lib/systemd/systemd
>ââsystem.slice
>â ââdbus.service
>â â ââ274 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfi...
>â ââwpa_supplicant.service
>â â ââ494 /usr/sbin/wpa_supplicant -u
>â ââaccounts-daemon.service
>â â ââ295 /usr/libexec/accounts-daemon
>â ââcolord.service
>â â ââ441 /usr/libexec/colord
>â ââsystemd-journald.service
>â â ââ109 /usr/lib/systemd/systemd-journald
>â ââudisks2.service
>â â ââ498 /usr/libexec/udisks2/udisksd --no-debug
>â ââupower.service
>â â ââ393 /usr/lib/upower/upowerd
>â ââsystemd-timesyncd.service
>â â ââ263 /usr/lib/systemd/systemd-timesyncd
>â ââcups.service
>â â ââ661 /usr/sbin/cupsd -l
>â ââsystemd-logind.service
>â â ââ271 /usr/lib/systemd/systemd-logind
>â ââsystem-getty.slice
>â â ââgetty@tty4.service
>â â â ââ291 /sbin/agetty --noclear tty4 linux
>â â ââgetty@tty6.service
>â â â ââ288 /sbin/agetty --noclear tty6 linux
>â â ââgetty@tty3.service
>â â â ââ289 /sbin/agetty --noclear tty3 linux
>â â ââgetty@tty5.service
>â â â ââ286 /sbin/agetty --noclear tty5 linux
>â â ââgetty@tty2.service
>â â   ââ283 /sbin/agetty --noclear tty2 linux
>â ââsystemd-udevd.service
>â â ââ141 /usr/lib/systemd/systemd-udevd
>â ââmcelog.service
>â â ââ268 /usr/sbin/mcelog --ignorenodev --daemon --foreground
>â ââpolkit.service
>â â ââ299 /usr/lib/polkit-1/polkitd --no-debug
>â ââNetworkManager.service
>â â ââ275 /usr/sbin/NetworkManager --no-daemon
>â â ââ345 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/d...
>â ââsmartd.service
>â â ââ273 /usr/sbin/smartd -n
>â ââcronie.service
>â â ââ292 /usr/sbin/crond -n
>â ââgdm.service
>â â ââ290 /usr/sbin/gdm
>â ââgpm.service
>â â ââ272 /usr/sbin/gpm -m /dev/input/mice -t exps2
>â âârtkit-daemon.service
>â   ââ442 /usr/libexec/rtkit-daemon
>ââuser.slice
>  ââuser-1000.slice
>  â ââsession-1.scope
>  â â ââ689 ibus-daemon --xim --panel disable
>  â â ââ694 /usr/libexec/ibus-dconf
>  â â ââ799 python2.7 /usr/bin/hp-systray -x
>  â â ââ800 python2.7 /usr/bin/hp-systray -x
>  â â ââ801 /usr/libexec/ibus-engine-simple
>  â ââuser@1000.service
>  â   ââgvfs-daemon.service
>  â   â ââ592 /usr/libexec/gvfsd
>  â   â ââ597 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
>  â   ââdbus.service
>  â   â ââ580 /usr/bin/dbus-daemon --session --address=systemd: --nofork --no...
>  â   â ââ606 /usr/libexec/at-spi-bus-launcher
>  â   â ââ611 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.c...
>  â   â ââ651 /usr/libexec/gconfd-2
>  â   â ââ676 /usr/libexec/gnome-shell-calendar-server
>  â   â ââ681 /usr/libexec/evolution-source-registry
>  â   â ââ688 /usr/libexec/goa-daemon
>  â   â ââ705 /usr/libexec/mission-control-5
>  â   â ââ751 /usr/libexec/tracker-store
>  â   â ââ782 /usr/libexec/evolution-calendar-factory
>  â   â ââ790 /usr/libexec/evolution-calendar-factory-subprocess --factory ca...
>  â   â ââ808 /usr/libexec/evolution-calendar-factory-subprocess --factory co...
>  â   â ââ820 /usr/libexec/evolution-addressbook-factory
>  â   â ââ832 /usr/libexec/evolution-addressbook-factory-subprocess --factory...
>  â   â ââ842 /usr/libexec/evolution-calendar-factory-subprocess --factory lo...
>  â   â ââ860 /usr/libexec/evolution-calendar-factory-subprocess --factory gt...
>  â   ââgvfs-goa-volume-monitor.service
>  â   â ââ728 /usr/libexec/gvfs-goa-volume-monitor
>  â   ââgvfs-metadata.service
>  â   â ââ713 /usr/libexec/gvfsd-metadata
>  â   ââinit.scope
>  â   â ââ540 /usr/lib/systemd/systemd --user
>  â   â ââ541 (sd-pam)
>  â   ââgvfs-udisks2-volume-monitor.service
>  â   â ââ720 /usr/libexec/gvfs-udisks2-volume-monitor
>  â   ââgvfs-gphoto2-volume-monitor.service
>  â     ââ724 /usr/libexec/gvfs-gphoto2-volume-monitor
>  ââuser-0.slice
>  â ââuser@0.service
>  â â ââinit.scope
>  â â   ââ1286 /usr/lib/systemd/systemd --user
>  â â   ââ1287 (sd-pam)
>  â ââsession-2.scope
>  â   ââ 276 /bin/login --
>  â   ââ1295 /usr/bin/gnome-keyring-daemon --daemonize --login
>  â   ââ1297 -bash
>  â   ââ1315 systemd-cgls
>  ââuser-117.slice
>    ââuser@117.service
>    â ââgvfs-daemon.service
>    â â ââ420 /usr/libexec/gvfsd
>    â â ââ425 /usr/libexec/gvfsd-fuse /run/user/117/gvfs -f -o big_writes
>    â ââdbus.service
>    â â ââ364 /usr/bin/dbus-daemon --session --address=systemd: --nofork --no...
>    â â ââ368 /usr/libexec/at-spi-bus-launcher
>    â â ââ374 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.c...
>    â â ââ377 /usr/libexec/at-spi2-registryd --use-gnome-session
>    â â ââ452 /usr/libexec/gconfd-2
>    â â ââ513 /usr/libexec/goa-daemon
>    â â ââ518 /usr/libexec/mission-control-5
>    â ââgvfs-goa-volume-monitor.service
>    â â ââ509 /usr/libexec/gvfs-goa-volume-monitor
>    â ââinit.scope
>    â â ââ336 /usr/lib/systemd/systemd --user
>    â â ââ337 (sd-pam)
>    â ââgvfs-udisks2-volume-monitor.service
>    â â ââ495 /usr/libexec/gvfs-udisks2-volume-monitor
>    â ââgvfs-gphoto2-volume-monitor.service
>    â   ââ505 /usr/libexec/gvfs-gphoto2-volume-monitor
>    ââsession-c1.scope
>      ââ308 gdm-session-worker [pam/gdm-launch-environment]
>      ââ342 /usr/libexec/gdm-x-session /usr/bin/gnome-session --autostart /us...
>      ââ344 /usr/bin/Xorg vt7 -displayfd 3 -auth /run/user/117/gdm/Xauthority...
>      ââ359 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/gree...
>      ââ385 /usr/libexec/gnome-settings-daemon
>      ââ435 gnome-shell --mode=gdm
>      ââ440 /usr/bin/pulseaudio --start --log-target=syslog
>      ââ450 /usr/libexec/pulse/gconf-helper
>      ââ476 ibus-daemon --xim --panel disable
>      ââ481 /usr/libexec/ibus-dconf
>      ââ485 /usr/libexec/ibus-x11 --kill-daemon
>      ââ528 /usr/libexec/ibus-engine-simple

Actions: View

Attachments on bug 94508: 123023

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.