Has anyone ever seen this?
Igmar Palsenberg
maillist at chello.nl
Sat Nov 11 13:58:09 UTC 2000
> > > On the console the following message continues to scroll:
> > >
> > > error get_socket:
> > > Bind 49 address already in use
> > > Init: id "ta" respawning too fast: disabled for 5 minutes
> > >
> > > Any ideas on how I can get this corrected?
> >
> > Kick named OUT of /etc/inittab. Daemons like named don't belong there, it
> > is VERY, VERY, VERY, VERY UGLY.
>
> 1. It does not look to me that that is a BIND message. It looks more to me
> that it refers to the system-call bind(2) and could be any other program
> in inittab.
After the cafeine I see the 49 :)
>
> 2. Why is running bind from /etc/inittab bad? It has a -f option for just
> that purpose. A good way of making sure there always is a named up and running.
> (the other one is putting "ndc start" into a crontab executed every 10 or so
> minutes).
The only thing that belongs in inittab is a list of (min)getty's for the
terminal, and things like getty's for modems etc.
The rest should go in runlevels. I've seen strange things happen with
weard things in /etc/inittab
Igmar
More information about the bind-users
mailing list