Bug 627

Summary: Error during XNTP start
Product: [Retired] Red Hat Linux Reporter: Daniel Senie <dts>
Component: xntp3Assignee: Jeff Johnson <jbj>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-25 00:04:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Daniel Senie 1998-12-28 00:40:45 UTC
If the

     multicast client

command is included in the ntp.conf, the daemon generates an
error, and doesn't seem to ever synchronize time.

Result is non-functional ntp.

Comment 1 Jeff Johnson 1998-12-28 15:53:59 UTC
Syntax is
	multicastclient
or
	multicastclient 224.0.1.1

You need a kernel with multicast configured and
a multicast server for multicast NTP to synchronize.

Comment 2 Daniel Senie 1999-01-15 05:16:59 UTC
Just did a bunch more testing, and indeed the multicast DOES work,
despite the error message from xntpd at startup.

The error at startup is:

Jan 14 23:58:20 peanut xntpd[24535]: bind() fd 12, family 2, port 123,
addr e0000101, in_classd=1 flags=0 fails: Address already in use
Jan 14 23:58:20 peanut xntpd[24535]: ...multicast address 224.0.1.1
using wildcard socket

Since the code does go on and work, why the error message? Something
seems at least somewhat odd.

Comment 3 Jeff Johnson 1999-03-25 00:04:59 UTC
The error message is due to xntp dynamic probes that determine the
correct mode to run in.