MX on Linux: Difference between revisions

No change in size ,  22:31, 29 April 2022
m
Line 417: Line 417:
If you are a technical user, you might decide to edit this, you have to decide what is needed in your context.
If you are a technical user, you might decide to edit this, you have to decide what is needed in your context.


As an example, add a blank line after <nowiki>'''Documentation=https://cumuluswiki.org/a/Main_Page'''</nowiki> and in that blank line, type <code>Requires= time-sync.target  local-fs.target</code>. A standard raspberry pi computer does not have a real-time clock, so when you switch it on, the clock just continues from whatever the time was when it was switched off. If the computer has online access, then it can look up the correct time online and adjust its clock.  We don't want MX to start until after the time has been synced, and we want the local file-system to be ready for MX to update/store files. The example extra line ensures (Requires) these events have happened before MX can start.
As an example, add a blank line after '''<nowiki>Documentation=https://cumuluswiki.org/a/Main_Page</nowiki>''' and in that blank line, type <code>Requires= time-sync.target  local-fs.target</code>. A standard raspberry pi computer does not have a real-time clock, so when you switch it on, the clock just continues from whatever the time was when it was switched off. If the computer has online access, then it can look up the correct time online and adjust its clock.  We don't want MX to start until after the time has been synced, and we want the local file-system to be ready for MX to update/store files. The example extra line ensures (Requires) these events have happened before MX can start.




5,838

edits