To have it automatically restart on failure, you can add the following to your systemd unit:
[Service]
Restart=on-failure
RestartSec=5s
See this blog post for more information.
But to find the root cause of why it's failing, you can run systemctl status <service> when it fails to get the most recent logs and hopefully an error as to why it failed.
Still relatively beginner, but wouldn't 'journalctl -u .service' also give you in depth logs over a longer period of time?
Adding to this, journalctl -fu service will jump to the bottom of the log and effectively tail -F the log so any new output will be appended to your terminal
Well that's way easier than my utilization of less or watch or tail that Ive been doing.
Yeah it's pretty slick
I second journalctl -f -u SERVICE_NAME.service it's great and just works well. The .service isn't required, but it's a good habit to get into since systemd also has mounts and timers.
Yes, you can get the full log with journalctl.
I also would recommend to find out why the service crashes.
You can try to increase the verbosity of rtl-433 with the arguments -v, -vv, -vvv and -vvvv. With every „v“ you get more information on what the program does.
Maybe you can get a hint why it crashes.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0