sounds like it is already running, or something else is using the port.
As root try
# ntpq
and if it starts ok, at the ntpq prompt ">" type
> pe
this should list any machines you are communicating with and the status.
If ntpq has problems, see if ntp is running:
# pidof xntpd
you should get a process id back.
make sure you are using the correct script :
# /etc/rc.d/init.d/xntpd start
Somewhere along the line check to see what is running on port 123
#netstat -an
lookfor lines with :123
if it is there I would try
# netstat -a| less
and see if ntp is in there instead of the 123. If it looks funny, I
would kill xntpd with
# /etc/rc.d/initd/xntpd stop
Then try the netstat -an thing again to see if something is still there
on 123. If there is you will need to find out what it is. My guess is
that xntpd was already running to begin with.
If every thing looks OK then restart it
# /etc/rc.d/initd/xntpd start
and try it all again. If you still have probs post the results.
Hope this helps.
Bret
Wayne Dyer wrote:
> 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".
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
