Thanks to all the peeps who replied, including:
Gary Barber <gbarber_at_telecom.ie>
Simon Greaves <S.J.Greaves_at_hw.ac.uk>
Chandra R. Chegireddy <chandra_at_phys.ufl.edu>
Robert Honore <robert_at_digi-data.com>
Carlos A M dos Santos <casantos_at_urano.cpmet.ufpel.tche.br>
Diezi Markus <Markus.Diezi_at_berner.ch>
John P. Speno <speno_at_swarthmore.edu>
As most of you realised, the problem was due to a daemon (joind) already
running and conflicting with the inetd entry for joind in the inetd.conf
file. Apparently the joind daemon hadn't died correctly during a change
in run level, rather that having been started at bootime.
Further investigation revealed that the only reason joind was running was
due to a no longer needed requirement to boot an X-terminal, so I
actually commented it out of inetd.conf. Killing the already running
joind and sending inetd a HUP signal had cured the error messages though.
Many thanks for sorting that one out for me guys.
Chris
--
Dr Chris Stoddart * I've had it with reality:
Systems Manager, Dept. of Physics, * I want a Fairy Godmother
The Open University, U.K. * http://physics.open.ac.uk/~cstoddar/
** Original Problem **
I had cause to reboot one of our machines earlier this week and the
daemon.log in /var/adm/syslog.dated is now filling up with messages of
the form:
Jul 2 16:29:28 ASSP01 inetd[22092]: bootps/udp: bind: Address already
in use
Every 10 mins or so. I can't figure out for the life of me what's
causing this. has anyone got any ideas?
****
Received on Mon Jul 07 1997 - 18:05:05 NZST