comp.os.linux.networking

Dave Uhring escribió:
> On Tue, 08 Apr 2008 19:09:23 +0200, Àngel Català wrote:
>> Dave Uhring escribió:
>
>>> Then perhaps you should hack your /etc/init.d/ntp script to run ntpdate
>>> prior to starting the daemon.
>
>> I have tryed calling ntpdate (with time servers I have configured in
>> ntp.conf) prior to start ntpd in /etc/init.d/ntp (and a "sleep 2"
>> command between both calls) and it still fails.
>
> Stop ntpd, /etc/init.d/ntp stop
>
> Run ntpdate your_NTP_server just once, then 'date'. Does the correct
> time appear?

Yes, it works fine. I stop ntp daemon, then I call ntpdate with my NTP
server and "date" answers me with the right time (also clock is set
properly). So I think that configuration parameters are OK, but I can
not understand what is failing.

By the way, everytime time is set properly (with manual restarting ntp
daemon or by typing ntpdate), my screen becomes black with a big "X"
symbol inside. I don't know if this detail is important.

>
>> Currently I have Debian 4.0 'Etch' r3 i386 installed, but a month ago I
>> had Debian 4.0 'Etch' r0 x64 and it worked fine. It is driving me crazy.
>
> I upgrade from Etch r1 to Lenny as soon as I do the installation. Never
> once had a problem with NTP. I even run a local NTP server on my network
> and *it* is running Lenny and synced to one closest stratum 2 server plus
> two of the servers in the debian.pool.
>
> The other systems on the net are Solaris -several versions- , OpenBSD,
> FreeBSD, Slackware and Debian Lenny. All sync to the local NTP server
> and all keep the correct time.
>

Thanks again.