Bug 2958 - ntpd does not set the date at start up
Summary: ntpd does not set the date at start up
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-07 00:02 CEST by Bernard MAUDRY
Modified: 2011-12-12 19:49 CET (History)
2 users (show)

See Also:
Source RPM: ntp-4.2.6p3-7.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bernard MAUDRY 2011-10-07 00:02:08 CEST 
Description of problem:
When started at boot time, ntpd does not set the date.
When restarted by "service ntpd restart", ntpd does not set the date.

Version-Release number of selected component (if applicable):
ntp-4.2.6p3-7.mga2

How reproducible:
Every time

Steps to Reproduce:
1. boot with a wrong date
2. wait for ntpd to start
3. the date is not updated
4. restart ntpd by "service ntpd restart"
5. the date is not updated
Comment 1 Bernard MAUDRY 2011-10-07 00:04:34 CEST 
"ntpdate 0.fr.pool.ntp.org" sets the correct date once ntpd is stopped.
Comment 2 Marja Van Waes 2011-12-07 20:14:46 CET 
From the description of ntp:

Ntp includes
ntpdate (a program for retrieving the date and time from remote machines
via a network) and 
ntpd (a daemon which continuously adjusts system time).


@ guillomovitch

Should ntpdate start while booting just like ntpd?

CC: (none) => guillomovitch, marja11

Comment 3 Guillaume Rousse 2011-12-08 16:22:17 CET 
ntpd set the date, but only if the difference is less than a given threshold (1000s). Otherwise, either -g option, or ntpdate program has to be used.

Deciding if ntpdate, ntpd, or any other service has to be run at boot time is a user decision, not a packaging issue. On end-users machines, especially on laptops, running ntpd is just overkill.
Comment 4 Marja Van Waes 2011-12-08 16:54:33 CET 
(In reply to comment #3)
> ntpd set the date, but only if the difference is less than a given threshold
> (1000s). Otherwise, either -g option, or ntpdate program has to be used.
> 
> Deciding if ntpdate, ntpd, or any other service has to be run at boot time is a
> user decision, not a packaging issue. On end-users machines, especially on
> laptops, running ntpd is just overkill.

@ Guillaume

Thanks for explaining.

@ Bernard,

How big was the difference between your system (date + time) and ntp server (date + time)?
Comment 5 Bernard MAUDRY 2011-12-12 16:45:51 CET 
The difference was 4 hours due to a problem in the handling of the hardwa
Comment 6 Bernard MAUDRY 2011-12-12 16:47:32 CET 
The difference was 4 hours due to a problem in the handling of the hardware clock by systemd now fixed.

I resimulate this time difference, and ntpd didn't set the correct date at start.
Comment 7 Marja Van Waes 2011-12-12 19:49:44 CET 
(In reply to comment #6)
> The difference was 4 hours due to a problem in the handling of the hardware
> clock by systemd now fixed.

Thanks for replying, Bernard.

4 hrs = 14400s, but for ntpd to set the date, the difference should be *less* than 1000s as stated by Guillaume in comment 3

So, although annoying, this isn't a bug

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.