Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→Network Configuration
ExecStop=/usr/bin/myservice shutdown
</pre>
== systemd-analyze ==
Systemd-analyze provides a good level of boot time information for further optimizations:
=== time ===
<pre>
root@imx6qxelk:~# systemd-analyze time
Startup finished in 5.109s (kernel) + 4.771s (userspace) = 9.880s
</pre>
=== blame ===
<pre>
root@imx6qxelk:~# systemd-analyze blame
3.608s dev-mmcblk0p2.device
547ms systemd-remount-fs.service
545ms systemd-vconsole-setup.service
544ms kmod-static-nodes.service
503ms systemd-udev-trigger.service
426ms systemd-journal-flush.service
407ms tmp.mount
371ms systemd-logind.service
327ms systemd-journald.service
317ms systemd-networkd.service
275ms systemd-timesyncd.service
257ms systemd-sysctl.service
204ms ofono.service
203ms systemd-modules-load.service
194ms sys-kernel-config.mount
188ms sys-kernel-debug.mount
177ms sshd.socket
161ms psplash-start.service
138ms systemd-random-seed.service
138ms sys-fs-fuse-connections.mount
129ms systemd-udevd.service
129ms systemd-update-utmp.service
128ms systemd-tmpfiles-setup-dev.service
124ms rc-local.service
98ms systemd-tmpfiles-setup.service
91ms psplash-quit.service
90ms systemd-resolved.service
89ms systemd-backlight@backlight:backlight.service
63ms dev-mmcblk0p1.device
41ms var-volatile.mount
33ms systemd-update-utmp-runlevel.service
</pre>
=== critical-chain ===
[[File:Systemd-analyze-critical-chain.png|800px]]
== Network Configuration ==
