A few pieces of old way are still present and working as for example /etc/rc.local where all the applications that implement the system functionality are started.
A typical rc.local contains:
cat /etc/rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. cd /home/acmesystems /usr/bin/nohup /usr/sbin/python myapplication.py & exit 0
In this example a Python program is started from application's home directory, and left in background (using the trailing ampersand). That works passably well till our python application never crashes: in such unfortunate case, our system only chance has, in order to regain the lost functionality, is to be manually restarted by user (probably cycling the power...).
Usually, the quick and dirty solution suggested is to add our application to the /etc/inittab file, specifyng a respawn in the line:
in such case startup must be a proper script able to start out application (and probably it could be convenient to reuse this script as is even in /etc/rc.local).
With systemd a different and more integrated approach is feasible. Instead of adding something to a shell script and inittable, a proper service file can be created and added to the systemd.
Let's create a service file for our myaplication.py program. Create as root a file called myapplication.service in /lib/systemd/system directory.
sudo nano /lib/systemd/system/myapplication.service
then save inside it this content:
[Unit] Description=My Application as Service After=network.target [Service] Type=idle ExecStart=/usr/bin/python /home/acmesystems/myapplication.py Restart=always User=pi [Install] WantedBy=multi-user.target
Next systemd has to be configured, enabling the service so at the next reboot it will be started automatically. First off, though, the systemd itself has to be reloaded in order to detect the new service definition:
sudo systemctl daemon-reload
Next, enable the service
sudo systemctl enable myapplication.service
Check if it is enabled:
sudo systemctl list-unit-files | grep enabled
Of course, it can be started manually just now:
sudo systemctl start myapplication.service
The PID (process id) can be now checked:
ps -ef | grep myapplication pi 817 1 0 09:19 ? 00:00:00 /usr/bin/python myapplication.py
it is 817 (the number will be different in your case). Please note that it has been started from systemd process, in fact the PPID (parent process id) is 1.
In order to simulate a crash, we kill it manually:
sudo kill 817
Now we can check it was restarted looking again to the PID (process id):
ps -ef | grep myapplication pi 1037 1 0 09:19 ? 00:00:00 /usr/bin/python myapplication.py
it is now 1037 (PPID always 1), so, as it is different, that means has been restarted automatically after the kill.
Use the journalctl command, as in:
journalctl -u myapplication.service
Le attività del TanzoLab si svolgono ogni mercoledi sera, salvo casi speciali, dalle ore 18:30 presso i locali della Acme Systems srl e consistono in:
Le attività vengono coordinate tramite questo sito, in cui vengono pubblicati tutti i lavori svolti o in via di sviluppo, e tramite un gruppo Telegram con cui per interagire direttamente via chat con gli altri membri.
2017 Ⓒ TanzoLab