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
2119fec6
Commit
2119fec6
authored
10 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
docs: formatting fixes
parent
f2c3446a
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/releases/v2014.3.rst
+10
-6
10 additions, 6 deletions
docs/releases/v2014.3.rst
with
10 additions
and
6 deletions
docs/releases/v2014.3.rst
+
10
−
6
View file @
2119fec6
...
...
@@ -13,13 +13,17 @@ New autoupdater
The autoupdater has been rewritten and now limits the time in which updates are
performed normally to the span from 04:00 to 05:00.
The manifest now has two new fields: DATE specifies the time the update was released
and is set automatically by ``make manifest``. PRIORITY specifies the maximum number of
days until the update should be performed (thus lower numbers mean the priority is higher). It must
be set either in ``site.mk`` or on the ``make manifest`` command line.
The manifest now has two new fields:
During the days specified by PRIORITY the update probability will start at 0 and slowly rise to 1
after all PRIORITY days have passed. If more than PRIORITY+1 days have passed, the updater will fall back
``DATE``
Specifies the time the update was released and is set automatically by ``make manifest``.
``PRIORITY``
Specifies the maximum number of days until the update should be performed (thus lower numbers
mean the priority is higher). It must be set either in ``site.mk`` or on the ``make manifest`` command line.
During the days specified by ``PRIORITY`` the update probability will start at 0 and slowly rise to 1
after all ``PRIORITY`` days have passed. If more than ``PRIORITY+1`` days have passed, the updater will fall back
to hourly update attempts so nodes which are never active between 04:00 and 05:00 also get an update eventually.
**Note:** For the new update logic to work, a valid NTP server reachable over the mesh (over IPv6) must
...
...
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