On 01/25/2013 08:51 AM, Jan Litwiński wrote:
> Dnia piątek, 25 stycznia 2013 08:39:25 Ed Greshko pisze:
>> On 01/25/2013 07:46 AM, Jan Litwiński wrote:
>>> I have proglem with ntp service, I did:
>>>
>>> systemctl enable ntpd.service
>>> systemctl start ntpd.service
>>>
>>> but ntp don't start at boot, starting by hand works. As a solution I
>>> created rc.local and add to it systemctl start ntpd.service and it
> works.
>>> I
>>> think ntpd starts before NetworkManager, My question is what is
> correct
>>> solution ?
>> What version of fedora are you using? In F17 and F18 the default
> ntp
>> service is chronyd.service.
>>
>> Did you check the status after you started ntpd.service?
>>
>> systemctl status ntpd.service
>>
>> Did you check the logs?
> sorry I do't say, but I am using Fedora 18, but after adding ntpd to
> rc.local sereice start at boot
>
> [root@localhost ~]# systemctl status ntpd.service
> ntpd.service - Network Time Service
> Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
> Active: active (running) since pią 2013-01-25 00:11:47 CET; 1h
> 33min ago
> Process: 1458 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS
> (code=exited, status=0/SUCCESS)
> Main PID: 1462 (ntpd)
> CGroup: name=systemd:/system/ntpd.service
> └─1462 /usr/sbin/ntpd -u ntp:ntp -g
>
> sty 25 01:40:16 localhost.localdomain ntpd[1462]: 194.110.116.10
> interface 192.168....)
> sty 25 01:40:16 localhost.localdomain ntpd[1462]: 87.99.63.100
> interface 192.168.0....)
> sty 25 01:40:16 localhost.localdomain ntpd[1462]: 149.156.24.40
> interface 192.168.0...)
> sty 25 01:40:16 localhost.localdomain ntpd[1462]: peers refreshed
> sty 25 01:40:22 localhost.localdomain ntpd[1462]: Listen normally on
> 8 wlan0 192.16...3
> sty 25 01:40:22 localhost.localdomain ntpd[1462]: Listen normally on
> 9 wlan0 fe80::...3
> sty 25 01:40:22 localhost.localdomain ntpd[1462]: peers refreshed
> sty 25 01:40:22 localhost.localdomain ntpd[1462]: new interface(s)
> found: waking up...r
> sty 25 01:40:24 localhost.localdomain ntpd[1462]: 0.0.0.0 0628 08
> no_sys_peer
> sty 25 01:44:51 localhost.localdomain ntpd[1462]: 0.0.0.0 0613 03
> spike_detect +0.6...s
>
> I don't know nothing about chronyd.service, how to setup this service?
>
Yeah, my bad. You did what I asked..... But I meant to ask what the errors
were when it failed....
But, you then did say....
[root@localhost ~]# systemctl status ntpd.service
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
Active: inactive (dead)
So, what is in the logs at that time?
As for chronyd, I've always have it set up during install time and firstboot
time, automatically.
But it may be as simple as
yum install chrony
systemctl enable chronyd.service
FWIW, it is possible that you have both chronyd an ntpd enabled and trying to
start?
--
Programming today is a race between software engineers striving to build bigger
and better idiot-proof programs, and the Universe trying to produce bigger and
better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry
Compiled
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
