chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
f31faa1
)
NEWS: update
author
Kay Sievers
<kay@vrfy.org>
Sat, 24 May 2014 06:50:17 +0000
(14:50 +0800)
committer
Kay Sievers
<kay@vrfy.org>
Sat, 24 May 2014 06:50:58 +0000
(14:50 +0800)
NEWS
patch
|
blob
|
history
diff --git
a/NEWS
b/NEWS
index a7db5293eeee81eac012d28e1b74118bc5d31e93..aee3ba0a6993d7266fc0a5f8f40713936b4bd441 100644
(file)
--- a/
NEWS
+++ b/
NEWS
@@
-3,11
+3,11
@@
systemd System and Service Manager
CHANGES WITH 213:
* A new "systemd-timesyncd" daemon has been added for
CHANGES WITH 213:
* A new "systemd-timesyncd" daemon has been added for
- snchronizing the system clock across the network. It
+ s
y
nchronizing the system clock across the network. It
implements an SNTP client. In contrast to NTP
implementations such as chrony or the NTP reference server
this only implements a client side, and does not bother with
implements an SNTP client. In contrast to NTP
implementations such as chrony or the NTP reference server
this only implements a client side, and does not bother with
- the full NTP complexity, focus
s
ing only on querying time
+ the full NTP complexity, focusing only on querying time
from one remote server and synchronizing the local clock to
it. Unless you intend to serve NTP to networked clients or
want to connect to local hardware clocks this simple NTP
from one remote server and synchronizing the local clock to
it. Unless you intend to serve NTP to networked clients or
want to connect to local hardware clocks this simple NTP
@@
-17,13
+17,13
@@
CHANGES WITH 213:
network connectivity is available. The daemon saves the
current clock to disk every time a new NTP sync has been
acquired, and uses this to possibly correct the system clock
network connectivity is available. The daemon saves the
current clock to disk every time a new NTP sync has been
acquired, and uses this to possibly correct the system clock
- early at bootup, in order to accomodate for systems that
+ early at bootup, in order to accom
m
odate for systems that
lack an RTC such as the Raspberry Pi and embedded devices,
and make sure that time monotonically progresses on these
systems, even if it is not always correct.
lack an RTC such as the Raspberry Pi and embedded devices,
and make sure that time monotonically progresses on these
systems, even if it is not always correct.
- * The
"seqnum" interface of libudev has been disabled, as it
-
was generally incompatible with device nam
spacing as
+ * The
queue "seqnum" interface of libudev has been disabled, as
+
it was generally incompatible with device name
spacing as
sequence numbers of devices go "missing" if the devices are
part of a different namespace.
sequence numbers of devices go "missing" if the devices are
part of a different namespace.
@@
-91,7
+91,7
@@
CHANGES WITH 213:
* Two new service options StartupCPUShares= and
StartupBlockIOWeight= have been added that work similar to
CPUShares= and BlockIOWeight= however only apply during
* Two new service options StartupCPUShares= and
StartupBlockIOWeight= have been added that work similar to
CPUShares= and BlockIOWeight= however only apply during
- system startup. This is useful to priorize certain services
+ system startup. This is useful to priori
ti
ze certain services
differently during bootup than during normal runtime.
Contributions from: Ali H. Caliskan, Alison Chaiken, Bas van
differently during bootup than during normal runtime.
Contributions from: Ali H. Caliskan, Alison Chaiken, Bas van