Bureaucrats, dave_user, Administrators
8,221
edits
Changes
→Wired interface
{{AppliesToAxelEsatta}}
{{AppliesToAxelLite}}
{{AppliesToAXEL Lite AN}}
{{AppliesToSMARX AN}}
{{AppliesToSBCX}}
{{AppliesToSBC Axel AN}}
{{InfoBoxBottom}}
systemd uses a slightly different configuration mechanism than SystemV. The configuration file is the following one with an example of configuration:
/etc/systemd/network/20-eth0.network
<pre>
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
</pre>
Activate the new network configuration restarting the <code>systemd</code> services:
systemctl restart systemd-networkd
systemctl restart systemd-resolved
==== Wireless interface ====
systemctl enable wpa_supplicant@wlan0
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>.
</pre>
Boot time analysis is one of the most important and interesting activity for an embedded system: systemd provide an userspace command called <code>systemd-analyze</code> to help in this (hard) task
<code>systemd-analyze</code> provides a good level of boot time information for further optimizations:
The <code>time</code> parameter gives the total amount of seconds used for starting the kernel and reaching the userspace.
</pre>
The <code>blame</code> parameter gives the list of started services and how long they took for starting:
</pre>
The <code>critical-chain</code> parameter shows the startup process flow and the time consumed by each service.
|}
For creating a new service the following file has to be created:
/etc/systemd/system/''<service_name>''.service
The following paragraph shows how to create a new service called <code>iperf3</code> executing the iperf3 command in server mode
</pre>
{| class="wikitable"
|}
Starting the service from userspace: