All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Bdale Garbee <bdale@gag.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ntpd fails on mlockall()
Date: Wed, 11 Oct 2000 13:09:57 +0100	[thread overview]
Message-ID: <20001011130957.N9399@linuxcare.com> (raw)
In-Reply-To: <8766n0ynjw.fsf@rover.gag.com>; from bdale@gag.com on Tue, Oct 10, 2000 at 11:06:11PM -0600

On Tue, Oct 10, 2000 at 11:06:11PM -0600, Bdale Garbee wrote:
> rhirst@linuxcare.com (Richard Hirst) writes:
> 
> > I've changed the kernel to grow the user stack dynamically, so
> > hopefully your ntpd will work now.
> 
> Still dies, but without the mlockall() error, so that seems fixed.  The dmesg
> output when it fails is

Thought I'd better investigate in case it was my stack changes...
(configured and built ntp natively, btw).
Turns out this crash is caused by the call to timer_create() in
ntpd/ntp_timer.c.

timer_create() is in librt.a - anyone know whether we expect this to
work or not atm?

Anyway, if you undefine HAVE_TIMER_CREATE and HAVE_TIMER_SETTIME
in config.h and rebuild it, it does better.  I now get:

11 Oct 05:21:13 ntpd[3141]: logging to file /tmp/ntpd.log
11 Oct 05:21:13 ntpd[3141]: ntpd 4.0.99g Wed Oct 11 05:17:40 MDT 2000 (5)
11 Oct 05:21:13 ntpd[3141]: precision = 10000 usec
11 Oct 05:21:13 ntpd[3141]: kern_enable is 1
11 Oct 05:21:13 ntpd[3141]: init_socket_sig: ioctl(I_SETSIG, S_INPUT) failed: Bad address

So, I undefined USE_UDP_SIGPOLL, and now ntpd runs and talks to remote
ntp servers.  Don't know whether it is doing what it should though...

Richard

  parent reply	other threads:[~2000-10-11 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-10  2:57 [parisc-linux] ntpd fails on mlockall() Bdale Garbee
2000-10-10 11:08 ` Richard Hirst
2000-10-10 20:53   ` Richard Hirst
     [not found]     ` <8766n0ynjw.fsf@rover.gag.com>
2000-10-11 12:09       ` Richard Hirst [this message]
2000-10-11 14:47         ` David Huggins-Daines

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=20001011130957.N9399@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=bdale@gag.com \
    --cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.