Would you like to migrate to systemd to control the wordclock as a service?

[oxivanisher]

I could help with that, if you would like that. Here are the things that work for me so far:

/etc/systemd/system/wordclock.service

[Unit]
Description=Wordclock
After=network.target

[Service]
ExecStart=/usr/bin/env python3 /home/pi/rpi_wordclock/wordclock.py
WorkingDirectory=/home/pi/rpi_wordclock/
Restart=always
RestartSec=5
KillSignal=SIGTERM
Type=simple
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=wordclock
NotifyAccess=all
User=root
Group=root
Nice=1

[Install]
WantedBy=multi-user.target

Systemd Howto

• The daemon needs to read the new service file after creation or it does not know it exists: systemctl daemon-reload
• The service can be started with: systemctl start wordclock.service
• The service can be enabled with (aka started at system boot): systemctl enable wordclock.service
• The last two commands can be combined into one: systemctl enable --now wordclock.service
• The current state of the service can be checked with: systemctl status wordclock.service
• The output can be watched with: journalctl -fu wordclock.service

IMHO (as a linux system engineer ^^) it would be nice to use a systemd unit, but I don't know if its seen as too complicated. Let me know what you think.

[bk1285]

Hey @oxivanisher, I like the idea pretty much!

Feel free to start your work on latest main branch and open a PR, whenever you're done. Please ensure, that the documentation is also adopted accordingly.

... final note: Any idea how/when to register the service in /etc/systemd/system? That's probably a manual approach as part of the instructions, right?