From: Klaus Naumann <spock@mgnet.de>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com, "Maciej W . Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: Decstation broken Was: CVS Update@oss.sgi.com: linux
Date: Fri, 29 Sep 2000 07:50:35 +0200 [thread overview]
Message-ID: <20000929075035.A23290@spock> (raw)
In-Reply-To: <20000929013954.A8494@bacchus.dhis.org>; from ralf@oss.sgi.com on Fri, Sep 29, 2000 at 01:39:54 +0200
On Fri, 29 Sep 2000 01:39:54 Ralf Baechle wrote:
> On Thu, Sep 28, 2000 at 10:00:46PM +0200, Klaus Naumann wrote:
>
> > BTW: What did you actually fix ? ntpdate still doesn't work
> > while ntpd seems to work ok.
>
> The NTP API was outdated.
>
> What is the sympthom you observe with ntpdate?
When I call it it's sleeping for several seconds.
And after that I get
29 Sep 07:49:37 ntpdate[10880]: poll(): nfound = 0, error: Operation not
permitted
which seems to loop then.
If I would have a working strace on my box I could tell you more :/
> > But ntpdate would be a very good idea because ntpd doesn't handle
> > large offsets ...
> > And obviously the realtime clock of the Indigo2 doesn't work
> > correctly. So I was calling ntpdate at every bootup to get my
> > system in a usable state. Maciej, can you take a look at ntpdate
> > please ?
>
> I recently found that the Indigo2 apparently has a different realtime
> clock from the Indy. If that's true it explains your observation and
> is unrelated the other problems.
Yes, it's of course unrelated to the other problem - it's just
an explanation why ntpdate is of real use.
CU, Klaus
--
Full Name : Klaus Naumann | (http://www.mgnet.de/) (Germany)
Nickname : Spock | Org.: Mad Guys Network
Phone / FAX : ++49/177/7862964 | E-Mail: (spock@mgnet.de)
PGP Key : www.mgnet.de/keys/key_spock.txt
next prev parent reply other threads:[~2000-09-29 5:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000825213106Z42310-31375+267@oss.sgi.com>
2000-09-28 19:40 ` Decstation broken Was: CVS Update@oss.sgi.com: linux Florian Lohoff
2000-09-28 20:00 ` Klaus Naumann
2000-09-28 23:39 ` Ralf Baechle
2000-09-29 5:50 ` Klaus Naumann [this message]
2000-09-29 9:46 ` Maciej W. Rozycki
2000-09-29 9:36 ` Maciej W. Rozycki
2000-09-29 20:01 ` Florian Lohoff
2000-10-01 9:40 ` Geert Uytterhoeven
2000-10-01 10:27 ` Ralf Baechle
2000-10-03 10:34 ` Maciej W. Rozycki
2000-10-02 11:39 ` Maciej W. Rozycki
2000-09-29 20:22 ` Florian Lohoff
2000-10-02 11:46 ` Maciej W. Rozycki
2000-09-30 10:18 ` Ralf Baechle
2000-10-01 16:46 ` Florian Lohoff
2000-10-02 11:59 ` Maciej W. Rozycki
2000-10-02 23:44 ` Ralf Baechle
2000-10-03 10:08 ` Maciej W. Rozycki
2000-10-03 9:41 ` Harald Koerfgen
2000-10-03 10:31 ` Maciej W. Rozycki
2000-10-03 18:21 ` Harald Koerfgen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000929075035.A23290@spock \
--to=spock@mgnet.de \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox