Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
firmware
FFS Gluon
Commits
8402e979
Commit
8402e979
authored
10 years ago
by
hexa-
Browse files
Options
Downloads
Patches
Plain Diff
docs: configure ntp servers in site.conf, not site.mk
parent
ddd7c163
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/releases/v2014.3.rst
+1
-1
1 addition, 1 deletion
docs/releases/v2014.3.rst
with
1 addition
and
1 deletion
docs/releases/v2014.3.rst
+
1
−
1
View file @
8402e979
...
@@ -28,7 +28,7 @@ the probability will proportional to the time passed. I.e. the update probabilit
...
@@ -28,7 +28,7 @@ the probability will proportional to the time passed. I.e. the update probabilit
and slowly increase to 1 until ``PRIORITY`` days have passed. From then, the probability will be fixed at 1.
and slowly increase to 1 until ``PRIORITY`` days have passed. From then, the probability will be fixed at 1.
**Note:** For the new update logic to work, a valid NTP server reachable over the mesh (using IPv6) must
**Note:** For the new update logic to work, a valid NTP server reachable over the mesh (using IPv6) must
be configured in ``site.
mk
``. If the autoupdater is unable to determine the correct time, it will fall back to
be configured in ``site.
conf
``. If the autoupdater is unable to determine the correct time, it will fall back to
a behavior similar to the old implementation (i.e. hourly update attempts).
a behavior similar to the old implementation (i.e. hourly update attempts).
Seperation of announced data
Seperation of announced data
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment