Yocto startup scripts systemd: Difference between revisions
From embeddedTS Manuals
(Minor fixups) |
No edit summary |
||
Line 1: | Line 1: | ||
To have a custom headless application start up at boot | To have a custom headless application start up at boot a systemd service needs to be created. Create the file /etc/systemd/system/yourapp.service with contents similar to below: | ||
<source lang=ini> | <source lang=ini> | ||
[Unit] | [Unit] |
Revision as of 15:51, 4 August 2017
To have a custom headless application start up at boot a systemd service needs to be created. Create the file /etc/systemd/system/yourapp.service with contents similar to below:
[Unit]
Description=Run an application on the i.MX6
[Service]
Type=simple
ExecStart=/usr/local/bin/your_app_or_script
[Install]
WantedBy=multi-user.target
If you depend on networking you should add "After=network.target" in the Unit section. Once this file is in place, it cab be added to automatic startup with the following:
# Start your app on bootup, but will not start it now
systemctl enable yourapp.service
# Start your app now, but doesn't change auto startup
systemctl start yourapp.service
Note: | See the systemd documentation for in depth documentation on services. |
To set up a graphical application startup, change the file: /usr/bin/mini-x-session
At the end of the script replace "matchbox-terminal" with your application (absolute path may need to be specified):
matchbox-terminal&
exec matchbox-window-manager
The exec statement must be last in the script in order to take over this script's PID for correct operation.