My clock is now _15 minutes_ late, after about 1 day with powerd running. ntpd is running also. Can nobody tell where the problem is here? m.
Martin Dieringer wrote:
> My clock is now _15 minutes_ late, after about 1 day with powerd
> running.
> ntpd is running also.
> Can nobody tell where the problem is here?
Are you sure that your /etc/ntp.conf ist correct?
Are there any messages from ntpd in /var/log/messages?
What's the output from "ntpq -p"?
Make sure that you have these two lines in /etc/rc.conf:
ntpd_enable="YES"
ntpd_sync_on_start="YES"
The second one is important -- it passes the -g option to
ntpd. Without that option, ntpd refuses to perform an
initial correction if the clock offset is too large.
If there are still problems, please show us the contents
of your /etc/ntp.conf file.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n-
chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
PI:
int f[9814],b,c=9814,g,i;long a=1e4,d,e,h;
main(){for(;b=c,c-=14;i=printf("%04d",e+d/a),e=d%a)
while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;}
On Tue, 8 May 2007 14:03:58 +0200 (CEST), Martin Dieringer wrote:> > > My clock is now _15 minutes_ late, after about 1 day with powerd > running. > ntpd is running also. > Can nobody tell where the problem is here?You say that ntpd is running, but what does the output of 'ntpq -p' show? Is syslog showing any messages from ntpd? -jav
On Thu, 10 May 2007, M. Warner Losh wrote:> In message: <20070508164234.L839@thinkpad.dieringer.dyndns.org> > Martin Dieringer <martin.dieringer@gmx.de> writes: > : well now it works without "restrict": > : # ntpq -p > : remote refid st t when poll reach delay offset jitter > : =============================================================================> : *time 192.53.103.108 2 u 19 64 77 91.454 301.926 860.104 > : > : > : and the clock is "only" 3 seconds late now... > > only 300ms late, or .3s you mean.Well it says so, but I meant 3 seconds, compared by eye to a radio clock. This is NOT a hardware problem. 1. I have this on 2 machines, 2. the problem is solved by switching to ACPI instead of APM m.