continuous logged messages for 0.6.3 kdc on Solaris 8

[Kenneth Marshall <ktm@is.rice.edu>]

Has anyone else seen this behavior. The kdc starts and appears to
function correctly and successfully. In the kdc.log it logs the
following sequence of messages every second:

2005-03-16T13:53:02 No sockets!
2005-03-16T13:53:02 No sockets!
2005-03-16T13:53:03 bind: Address already in use
2005-03-16T13:53:03 bind: Address already in use
2005-03-16T13:53:03 bind: Address already in use
2005-03-16T13:53:03 bind: Address already in use
2005-03-16T13:53:03 no sockets to listen to - exiting
2005-03-16T13:53:03 no sockets to listen to - exiting
2005-03-16T13:53:03 bind(IPv4:127.0.0.1): Address already in use
2005-03-16T13:53:03 bind(IPv4:127.0.0.1): Address already in use
2005-03-16T13:53:03 bind(IPv4:128.42.5.60): Address already in use
2005-03-16T13:53:03 bind(IPv4:128.42.5.60): Address already in use
2005-03-16T13:53:03 No sockets!
2005-03-16T13:53:03 No sockets!
2005-03-16T13:53:04 bind: Address already in use
2005-03-16T13:53:04 bind: Address already in use
2005-03-16T13:53:04 bind: Address already in use
2005-03-16T13:53:04 bind: Address already in use
2005-03-16T13:53:04 no sockets to listen to - exiting
2005-03-16T13:53:04 no sockets to listen to - exiting
...

This is on a Solaris 8 machine. It looks like the problem
is in the loop() and init_sockets() functions. Has anyone
else seen this problem and if so how did you fix it.

Ken