Альтернатив systemd тред

$ 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.

graphical.target @1min 7.497s
└─multi-user.target @1min 7.497s
  └─ntp.service @17.403s +50.093s
    └─basic.target @17.177s
      └─paths.target @17.148s
        └─cups.path @17.148s
          └─sysinit.target @17.141s
            └─nfs-common.service @17.057s +83ms
              └─rpcbind.target @17.057s
                └─rpcbind.service @17.026s +30ms
                  └─network-online.target @17.026s
                    └─network.target @17.026s
                      └─ifup@eth1.service @17.025s
                        └─networking.service @1.736s +15.273s
                          └─bootcdflop.service @1.726s +8ms
                            └─local-fs.target @1.709s
                              └─run-rpc_pipefs.mount @17.135s
                                └─local-fs-pre.target @487ms
                                  └─systemd-remount-fs.service @469ms +17ms
                                    └─keyboard-setup.service @198ms +259ms
                                      └─systemd-udevd.service @192ms +4ms
                                        └─systemd-tmpfiles-setup-dev.service @160ms +31ms
                                          └─kmod-static-nodes.service @149ms +10ms
                                            └─system.slice @130ms
                                              └─-.slice @130ms