Cumulus MX FAQ: Difference between revisions

1,036 bytes added ,  17:43, 23 May 2020
m
Line 29: Line 29:


== Questions ==
== Questions ==
=== Not watching the terminal or console window ===
Although the MX engine writes messages to the terminal or console (the terminology varies depending on the device) many people don't have a monitor connected to the device running MX (and if they do, they don't watch this output). Therefore it is easy to not to see messages, and not to know when MX is running or crashes.
One problem people have is stopping MX while it is busy, perhaps still doing catch-up from  your station's logger after restarting, perhaps doing an end of day or end of month rollover, maybe in the middle of some other task. It is not so easy to see when MX is running, nor when it is busy. MX does so many tasks now, that picking a moment when it is not doing something is harder.
Although MX is designed assuming it is left running all the time, it is permissible to stop, and restart it, just do that as few times as possible (once a day if you must). MX will run on a variety of devices, so can run on devices that are cheap to leave on all the time.


=== I have a message about web tags ===
=== I have a message about web tags ===
5,838

edits