Red Hat Bugzilla – Bug 157485
ntp - timesync blocks whole boot process
Last modified: 2007-11-30 17:11:05 EST
Description of problem:
fc4test3-DVD, selected ntp timesync at bootup, but selected the wrong network
interface to be active on start. So no connection to the internet was there. The
ntp-service blocked the whole boot-process for more than two minutes, I think.
The timeout should be reduced to FIVE(!) seconds at most. Or the process should
do his sync-work in the background - also on boot-up!
It can easily happen that no internet-connection is there - and then it steals
you precious time. Really annoying!
ntpd cannot block anything.
See -> ntpd/ntpd.c -> main() -> ntpdmain()
We call there:
See man-pages (launch at the command prompt):
man 3 daemon
puuuh, then call it "delay", if you don't like the word "block" - it was like I
the daemon does not block, but ntpdate does. this is called by the initscript:
65 # Synchronize with servers if step-tickers exists
66 # or the -x option is used
67 echo -n $"$prog: Synchronizing with time server: "
68 /usr/sbin/ntpdate $dropstr -s -b -p 8 $tickers 2>/dev/null
this blocks for a long while if there are connectivity problems.
i believe this bug should be reopened. Can the reporter reopen it?
Thanks for these details, reopened
Created attachment 121579 [details]
We does not call 'ntpdate' in FEDORA CORE 4.
a) Log in (as 'root')
b) Launch at the command prompt:
cp ./my-ntpd-init-d-rc-d-etc /etc/rc.d/init.d/ntpd
c) Launch at the command prompt:
d) Restart you machnine
e) See for '--------->'
[avi@firebolt ~]$ cat /etc/ntp/step-tickers
[avi@firebolt ~]$ sudo /sbin/service ntpd restart
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: We try to launch |-------------------->
After |--------------------> ntpdate
[ OK ]
We try to launch --------------------> ntpd
After --------------------> ntpd [ OK ]
Looks like we do call ntpdate in FC4. Please reopen. Please fix if at all
Created attachment 121635 [details]
cat /etc/ntp/step-tickers imeserver.iix.net.il
What is your current directory ? I do not need an answer.
Again: if we launch at the command promt (in FEDORA CORE 4, as 'root'):
service ntpd restart
we does not launch 'ntpdate'.But this is not important too. Back to your issue.
I will send you *src.rpm (including auto-trace). Please, instll this *.src.rpm
and restart your machine.
It creates /tmp/ntpd.PID (and ?) /tmp/ntpdate.PID logs.
Please, send me this files (to see if ntpdate blocks anything).
ntpdate is only called when /etc/ntp/step-tickers exists and is not empty.
system-config-date creates the file. As ntpd is called with -g the best solution
is to not create the file at all. Reassigning to system-config-date component.
system-config-date-1.8.2-1 lets you configure whether to use ntpdate at startup
or not (default==off).