5,838
edits
MX on Linux: Difference between revisions
m
→Running Cumulus
|
That is simple if your Pi is in your home, and you can go back to the Pi when you need to stop MX (perhaps to update it to a new release). But maybe you are running Pi headless, or it is in a remote location, in that case instead of starting and stopping MX in a terminal session, you will want to issue commands that connect to a separate session for starting MX so you can disconnect from that session without causing MX to close. As I type this a new release is allowing MX to run as a service, and a future release is planned to change the associated script, so anything I write here might become obsolete, and the next paragraph gives you some links to the support forum. Hopefully, someone will edit this article, when instructions have settled down and won't change on next release.
In the Cumulus Support forum, there are articles about a [https://cumulus.hosiene.co.uk/viewtopic.php?p=139779#p139779 stop/start routine], a [https://cumulus.hosiene.co.uk/viewtopic.php?p=141514#p141514 backup routine], and [https://cumulus.hosiene.co.uk/viewtopic.php?p=146028#p146028 how to run MX as a service]. I will let you hunt for and read the relevant topics, as you may find details in more than one place. This article
# Use '''start/stop routine''' (see earlier link), this effectively starts a separate session for MX to run in and leaves the standard terminal session free.
# Run MX as an '''init service''' (see the earlier post in the service link above), be aware that this is a new feature in the new release of MX 3.8.0, again this starts MX outside your terminal session
| |||