On 08.04.15 at 13:18, Lennart Poettering wrote:
On Tue, 07.04.15 19:26, Jakub Klinkovský (j@gmx.com) wrote:
After looking at the code more thoroughly, I must say that this commit [1]
is
not entirely correct and might bring some more confusion. There are two
different states being
On 08.04.15 at 18:35, Lennart Poettering wrote:
On Wed, 08.04.15 16:11, Jakub Klinkovský (j@gmx.com) wrote:
That's not what I meant. The man page for 'timedatectl status' currently
says:
Show current settings of the system clock and RTC, including whether
network time
On 07.04.15 at 16:40, Lennart Poettering wrote:
On Sun, 05.04.15 13:25, Jakub Klinkovský (j@gmx.com) wrote:
As per systemd 216 NEWS [1], alternative NTP implementations should add
Conflicts=systemd-timesyncd.service to be recognized by systemd, which
ntpd.service on Arch Linux does
As per systemd 216 NEWS [1], alternative NTP implementations should add
Conflicts=systemd-timesyncd.service to be recognized by systemd, which
ntpd.service on Arch Linux does. But still, active ntpd.service does not seem
to be recognized by timedatectl:
$ timedatectl
...
NTP enabled: no
NTP
not use -x.
So, if the -x option is not-so-wanted, why is the unit not identified by its
name in the default output? This would also make the default journal output
unambiguous regardless of the units' descriptions.
Regards,
Jakub Klinkovský
pgpU8sf5Dkc5o.pgp
Description: PGP signature
