On 05/28/13 00:01, G.Wolfe Woodbury wrote:
On 05/27/13 03:42, Ed Greshko wrote:
> On 05/27/13 15:02, poma wrote:
>> $ timedatectl set-ntp false/true
>> Failed to issue method call: No such file or directory
> Maybe it is a simple case of "not yet implemented" in F18?
>
> [egreshko@meimei ~]$ timedatectl
> Local time: Mon 2013-05-27 15:40:31 CST
> Universal time: Mon 2013-05-27 07:40:31 UTC
> RTC time: Mon 2013-05-27 07:39:55
> Timezone: Asia/Taipei (CST, +0800)
> NTP enabled: n/a
> NTP synchronized: yes
> RTC in local TZ: no
> DST active: n/a
>
>
> NTP enabled: n/a ???
The NTP packages are not installed by default, using the chrony
set instead (for a lighter weight implementation?) and the timedatectl
stuff wants the "ntp*" commands explicitly.
Well, FWIW, in F19 the command "timedatectl set-ntp false/true" will
disable/enable chronyd.
[root@localhost ~]# timedatectl
Local time: Tue 2013-05-28 04:27:27 CST
Universal time: Mon 2013-05-27 20:27:27 UTC
RTC time: Tue 2013-05-28 04:27:28
Timezone: Asia/Taipei (CST, +0800)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
[root@localhost ~]# systemctl status chronyd.service
chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
Active: active (running) since Mon 2013-05-27 15:43:40 CST; 12h ago
Main PID: 2318 (chronyd)
CGroup: name=systemd:/system/chronyd.service
└─2318 /usr/sbin/chronyd -u chrony
[root@localhost ~]# timedatectl set-ntp false
[root@localhost ~]# timedatectl
Local time: Tue 2013-05-28 04:28:24 CST
Universal time: Mon 2013-05-27 20:28:24 UTC
RTC time: Tue 2013-05-28 04:28:25
Timezone: Asia/Taipei (CST, +0800)
NTP enabled: no
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
[root@localhost ~]# systemctl status chronyd.service
chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled)
Active: inactive (dead)
--
The only thing worse than a poorly asked question is a cryptic answer.