[1178] in SIPB_Linux_Development
Re: SIPB locker
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Fri Dec 8 23:29:16 1995
Date: Fri, 8 Dec 1995 23:27:24 -0500
To: Brett W Vasconcellos <brettv@MIT.EDU>
Cc: warlord@MIT.EDU, linux-help@MIT.EDU, linux-dev@MIT.EDU
From: Salvatore Valente <svalente@MIT.EDU>
Hi. You wrote:
I am having trouble with the SIPB locker, /mit/sipb. It seems that
sometimes when I add (or attach) it, /mit/sipb/linuxbin exits and
other times it does not. Is there a reason this is happening?
Derek wrote:
You are probably running an old version of named with is
round-robining Hesiod entries. Since there are two entries for the
sipb filsys entry, your machine keeps swapping which one it uses,
instead of using the proper order.
The fix is to upgrade your named binary.
I'm not sure that this answer is completely correct, or completely useful.
I'm not sure it's completely correct because round-robining is a
relatively new feature. To my knowledge, there has not been an
official version of named since round-robining was added that handles
hesiod entries correctly. In other words, the problem is not that
your named is too old, it's that your named is too new. An older
version of named would work.
But that's a minor technicality. At any rate, the solution is to fix
your named binary.
I've built a version of named that handles hesiod entries correctly,
and placed it in /mit/linux/named. If you want to compile this
yourself, the source tree is /mit/linux/bind/bind-4.9.3-BETA9/.
[Note to linux-dev people: There are probably lots of people out there
with broken named's. I guess we should probably put the named binary
in the mit-named package, to get around this problem.]
Have a nice day.
-Sal.
