Path: utzoo!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!ucbvax!SAYSHELL.UMD.EDU!louie
From: louie@SAYSHELL.UMD.EDU ("Louis A. Mamakos")
Newsgroups: comp.protocols.time.ntp
Subject: Re: Xntpd doesn't start. Any ideas?
Message-ID: <9103181914.AA07601@sayshell.umd.edu>
Date: 18 Mar 91 19:14:08 GMT
References: <669322376.919228.RIC@RML2.SRI.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 12

It sounds like in the ntp_io.c module that the SIOCGIFCONF ioctl fails.  It
is not surprizing that this failed with xntpd as well as ntpd, as the code
is almost identical and derived from the ntpd code.  The daemon(s) are
attempting to get a list of all the network interfaces on the system and
their addresses.  It seems like the host/OS that you're using either doesn't
support this, or supports it in some different fashion.  

Look at xntpd/ntp_io.c for the gory details.

Or, look at ntpd/ntp_sock.c for the same sort of thing.

louie