Luadch which is an Advance Direct Connect (ADC) server hub software is not friendly to daemonize but with the following luadch.service file, you’re able to atleast start/stop/restart luadch with systemd.
[Unit]
Description=luadch service
After=network.target
[Service]
Type=simple
User=luadch
Group=luadch
WorkingDirectory=/home/luadch
ExecStart=/home/luadch/luadch
RemainAfterExit=no
[Install]
WantedBy=multi-user.target
Hi. I don’t know Linux very well, but I’ve used this line in the past and it has worked as far as I know:
Restart=always
I haven’t had the problem I’ve had lately with luadch throwing exceptions left & right since the hubs I’ve hosted had been upgraded and then downgraded from 2.24 back to 2.23 – It’s a messy story.
But one problem that’s been occurring is that inside luadch, the command !shutdown and !restart has not successfully done its job, but instead it’s just been frozen or at the very best delayed with several minutes before it’s actually done what it was supposed to do.
This has also been due to corrupted ASCII encoding, UTF8-something and variables/arrays been changed between versions of some scripts that caused these errors, and possibly the functionality of luadch.
These hubs runs on Raspberry Pi OS, on both 32 and 64 bits Pi Zero W, W2 and Pi4 if that has anything to do with anything…