Pigeon wrote:
[...]
>
>Like it... reminds me of "*Any* car can be made to do 0-60mph in under
>3 seconds - allow me to demonstrate with yours."
Achieving ~32 ft/sec^2 acceleration is not that difficult. Finding an
unobstructed 121 ft "dragstrip" with a non-blockaded starting line might
be more p
On Fri, Jan 31, 2003 at 04:02:37PM +, Stephanie Boyd wrote:
> ( Apparently this
> is because the master crystal is often uncalibrated, so the clock
> was advancing at the wrong rate.)
The hardware RTC relies on a 32.768kHz crystal. The vast majority of
32.768kHz crystals are designed for dig
Stephanie Boyd wrote:
>
> On Wed, Jan 29, 2003 at 02:50:00PM -0500, [EMAIL PROTECTED] wrote:
> > Hello all. I've got this weird problem with ntpd. Up until now I've never
> > had ntpd fail me. But on this one box I've got the clock speeding up by 30
> > minutes each day. I've got ntpd installed an
On Wed, Jan 29, 2003 at 02:50:00PM -0500, [EMAIL PROTECTED] wrote:
> Hello all. I've got this weird problem with ntpd. Up until now I've never
> had ntpd fail me. But on this one box I've got the clock speeding up by 30
> minutes each day. I've got ntpd installed and configured properly with
> work
ted all eight times, 003 means just connected last two
times, etc.
send the dmpeer output, and I'll try to give you a hand...
-Jeff
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Cc: [EMAIL PROTECTED]
Subject: Re: ntpd not keeping time
# ntptrace clock.psu.
This might be useful to someone out there..
Run as root on the problem system:
# ntptime
ntp_gettime() returns code 5 (ERROR)
time c1e3d62c.cf888000 Thu, Jan 30 2003 11:49:48.810, (.810677),
maximum error 16384000 us, estimated error 16 us
ntp_adjtime() returns code 5 (ERROR)
modes 0x0 ()
# ntptrace clock.psu.edu
otc2.psu.edu: stratum 2, offset -529.277338, synch distance 0.06970
ntptrace (and ntpdate) work fine, but ntpd still doesn't sync time. I
previously had a very restrictive firewall ruleset on the box, but I've
relaxed it quite a bit and still nothing. :(
I'm actually cons
hi ya debian
since ntpdate does sync w/ clock.psu.edu
and xntpd does not, you will need to fix your firewall rules
c ya
alvin
On Wed, 29 Jan 2003 [EMAIL PROTECTED] wrote:
> # ntpdate -udb clock.psu.edu
...
> 29 Jan 16:38:43 ntpdate[23213]: no server suitable for synchronization found
>
>
> #
Enabling the logfile in ntp.conf doesn't show anything special, just the
same start/stop stuff from daemon.log:
29 Jan 16:38:15 ntpd[23209]: frequency initialized 0.000 from /var/lib/ntp/ntp.drift
29 Jan 16:38:15 ntpd[23210]: signal_no_reset: signal 17 had flags 400
29 Jan 16:38:28 ntpd[23209]
hi ya
turn on logfile in your ntp.conf
-- run some ntptrace and ntpdate commands
and post its output
ntpdate -udb time.apple.com
( use your servers from your ntp.conf file )
ntptrace -dv time.apple.com
more ntp jibberish ( urls to other docs too )
http://www.Linux-Consult
> Hello all. I've got this weird problem with ntpd. Up until now I've never
> had ntpd fail me. But on this one box I've got the clock speeding up by 30
> minutes each day. I've got ntpd installed and configured properly with
> working ntp servers. In fact, ntpdate sets the clock properly, but ntpd
Hello all. I've got this weird problem with ntpd. Up until now I've never
had ntpd fail me. But on this one box I've got the clock speeding up by 30
minutes each day. I've got ntpd installed and configured properly with
working ntp servers. In fact, ntpdate sets the clock properly, but ntpd is
fail
12 matches
Mail list logo
