I had this until I took out the multicast line in /etc/ntp/ntp.conf (the one
where is says it defaults to 224.0.1.1 which I definitely don't need). Look
at the IP address in your logfile again.
-----Original Message-----
From: Wayne Dyer [mailto:[EMAIL PROTECTED]]
Sent: 19 March 2000 06:49
To: [EMAIL PROTECTED]
Subject: Re: Do you use ntp to set your time?
Vidiot wrote:
> >One question, as I'm a timid user of other folks'
resources. It mentions
> >in the NTP FAQ that one should notify the timeserver
owners that you're
> >planning on using them as an ntp user.
>
> Correct. That is exactly what I did with the three sites
that I use.
>
> >How much traffic does ntp generate? If I ran a network,
I'd feel OK
> >hooking up this way, but as just some schmo with
(effectively) a singles
> >system, I don't want to waste their resources.
>
> I don't remember how often ntp goes out and gets a hit.
>
> If you have a LAN, you use one of your machines to lock to
one of the
> resources. You have all of your internal machines lock
onto you. The
> public resources are there for you to use. Just don't
have all of your
> local network machines all sync to the resource.
However, I've hit a possible snag. When I start xntpd (I'm
using the
6.1-provided package), I get:
xntpd[10987]: xntpd 3-5.93e Mon Aug 16 20:55:26 EDT 1999 (1)
xntpd[10987]: tickadj = 5, tick = 10000, tvu_maxslew = 495,
est. hz = 100
xntpd[10987]: precision = 14 usec
xntpd[10987]: read drift of 0 from /etc/ntp/drift
xntpd[10987]: bind() fd 12, family 2, port 123, addr
e0000101, in_classd=1
flags=0 fails: Address already in use
xntpd[10987]: ...multicast address 224.0.1.1 using wildcard
socket
xntpd: xntpd startup succeeded
What worries me is the bind() line and that glaring "fails".
-W-
Who's turned it off for now.
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
