MX on Linux: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search

MX on Linux (view source)

Revision as of 05:12, 19 March 2022

78 bytes added ,  19 March 2022
m
→‎Technical users - optional edit to "[Unit]" section: Discovered that <pre> does not work within bullets!
m (Minor rephrasing and layout improvement re release 3.15.1 change)
m (→‎Technical users - optional edit to "[Unit]" section: Discovered that <pre> does not work within bullets!)
=====Technical users - optional edit to "[Unit]" section=====
 
The content of the "[Unit]" section of the service description file described here has evolved slightly as MX develops. The onlyfile changewas isfirst added to the MX release package in referencesPatch torelease '''network-online3.target''':8.4 - b3094 (14 September 2020)
The only change is in references to '''network-online.target''':
# The file was first added to the MX release package in Patch release 3.8.4 - b3094 (14 September 2020)
#* In that first version of the file <code>After=network-online.target</code> was the only mention.
#**Note: That means that '''after''' "systemd" has started the "cumulusmx" service, it can start the network service. (Note that the terminology ''after'' does not guarantee the network online detection service will be started.)
* From release 3.15.1 build 3170 (19 March 2022) a second mention was added, so the content became:
#** Note that the terminology ''after'' does not guarantee the network online detection service will be started.
# From release 3.15.1 build 3170 (19 March 2022) a second mention was added, so the content became: <pre>Wants=network-online.target
After=network-online.target</pre>
#*Note: The "wants" line tells "systemd" that the "cumulusmx" service wants the network online detection service to be started. (Note that the terminology ''wants'' means MX can still start even if the network service is not running, or if the attempt to start the network service fails).
#** Note that the terminology ''wants'' means MX can still start even if the network service is not running, or if the attempt to start the network service fails
 
 
 
'''Please follow these steps if you do need to make the suggested change here:'''
# Within the editor navigate to '''[Unit]''' section
# As mentioned above, the content of this section depends upon which MX release you are using.
#*#* That means without this target being included, a newly booted-up RPi will tell Cumulus MX the time is just after when the computer was shut down, that might be very different to the true current time. It means your Cumulus MX on restarting will skip the catch-up of historic data (should your weather station settings make that available). Some measurements will then get logged against the wrong time.
#*#* When the Raspberry Pi does do a time-sync, the time will suddenly jump, this is serious if this means the "rollover" time has been skipped over, as it implies the "dayfile.txt" will miss a line, and many measurements will be logged to wrong day.
 
 
=====Technical users - Saving the file and making it available to "systemd"=====
Sfws
5,838

edits

Retrieved from "https://www.cumuluswiki.org/a/Special:MobileDiff/10250"

Navigation menu