Changes

Jump to: navigation, search

XELK-AN-008: How to use systemd on an Embedded system

13 bytes added, 12:39, 23 September 2019
no edit summary
Starting from [[Axel_Embedded_Linux_Kit_(XELK)#XELK_4.0.0|XELK 4.0.0]] the root file system generated by NXP Yocto recipes produces a root file system using [https://www.freedesktop.org/wiki/Software/systemd/ systemd].
Systemd systemd is a ''System and Service Manager'' which has enough different settings and configuration from SystemV(SysV) which was used on all XELK BSPs up to [[Axel_Embedded_Linux_Kit_(XELK)#XELK_3.0.0|XELK 3.0.0]].
This application note '''is not a complete systemd user's guide''' but collects some useful hints that can be used for getting familiar with Systemdsystemd. There is a plenty of documentation and User's Guide available for systemd, but some simple example - that can be found here below - may simplify the systemd approach for beginners.
== Brief description ==
Systemd systemd manages not only services but many different objects called '''Unit'''. Unit are related to the resources that systemd can manage. Unit configurations are defined into the ''Unit files''.
Units categoris (identified by the file extension) are:
{| class="wikitable"
|-
! Description !! SystemV (runlevel) !! Systemd systemd (target)
|-
| System halt || 0 || runlevel0.target, poweroff.target
notify:
the service will notify when completely initialized. Systemd systemd will wait for the notification before continuing with the following Units
idle:
systemctl enable myservice
=== From SystemV to Systemd systemd ===
==== start ====
</pre>
Systemdsystemd:
<pre>
== systemd-analyze ==
Systemd<code>systemd-analyze </code> provides a good level of boot time information for further optimizations:
=== time ===
== Logging ==
Systemd systemd has its own logging process called <code>journal</code> avoiding to start the ''syslog'' daemon. For the status information it is possible to use <code>journalctl</code>.
journalctl -f
8,154
edits

Navigation menu