Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Problem: Autoplay after start
#8
I think the command Tim was thinking of is systemd-analyze.

Here's the output for two different options running systemd-analyze on one of my moOde players (moode-r700-rc5) on an RPi-3B+ with a local (official Raspberry Pi) display and with the triggerhappy daemon enabled:


Code:
pi@RC5LD:~ $ systemd-analyze blame
        12.143s dhcpcd.service
         4.348s dev-sda2.device
         1.859s rc-local.service
         1.833s raspi-config.service
         1.825s nmbd.service
         1.472s man-db.service
         1.442s nginx.service
          694ms smbd.service
          658ms keyboard-setup.service
          604ms systemd-udev-trigger.service
          583ms systemd-fsck@dev-disk-by\x2dpartuuid-2fed7fee\x2d01.service
          575ms networking.service
          550ms systemd-timesyncd.service
          496ms systemd-logind.service
          456ms wpa_supplicant.service
          448ms avahi-daemon.service
          427ms winbind.service
          371ms user@1000.service
          344ms rsyslog.service
          328ms systemd-journald.service
          301ms systemd-fsck-root.service
          288ms polkit.service
          287ms systemd-udevd.service

pi@RC5LD:~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

multi-user.target @22.505s
└─smbd.service @21.807s +694ms
 └─winbind.service @21.373s +427ms
   └─nmbd.service @19.541s +1.825s
     └─network-online.target @19.534s
       └─network.target @19.522s
         └─dhcpcd.service @7.374s +12.143s
           └─basic.target @7.181s
             └─sockets.target @7.177s
               └─triggerhappy.socket @7.174s
                 └─sysinit.target @7.160s
                   └─systemd-timesyncd.service @6.605s +550ms
                     └─systemd-tmpfiles-setup.service @6.415s +161ms
                       └─local-fs.target @6.406s
                         └─boot.mount @6.325s +75ms
                           └─systemd-fsck@dev-disk-by\x2dpartuuid-2fed7fee\x2d01.service @5.730s +583ms
                             └─dev-disk-by\x2dpartuuid-2fed7fee\x2d01.device @5.307s

You can consult the man page for information about this output.

Regards,
Kent
Reply


Messages In This Thread
Autoplay after start - by fiorello - 11-29-2020, 03:07 PM
RE: Autoplay after start - by Tim Curtis - 11-29-2020, 03:58 PM
RE: Autoplay after start - by fiorello - 11-29-2020, 04:21 PM
RE: Autoplay after start - by Tim Curtis - 11-29-2020, 05:12 PM
RE: Autoplay after start - by fiorello - 11-30-2020, 08:56 AM
RE: Autoplay after start - by Tim Curtis - 11-30-2020, 12:33 PM
RE: Autoplay after start - by fiorello - 12-01-2020, 06:08 PM
RE: Autoplay after start - by TheOldPresbyope - 12-01-2020, 06:59 PM
RE: Autoplay after start - by fiorello - 12-06-2020, 04:27 PM
RE: Autoplay after start - by TheOldPresbyope - 12-06-2020, 06:18 PM

Forum Jump: