Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!aramis.rutgers.edu!athos.rutgers.edu!hedrick From: hedrick@athos.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.appletalk Subject: Re: Rutgers CAP/ethertalk configuration Message-ID: Date: 13 Nov 90 06:48:45 GMT References: <4836@spdcc.SPDCC.COM> <4837@spdcc.SPDCC.COM> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 13 Cc: rapatel nis_node and nis_net are set correctly if you let atis figure out the network number by listening to RTMP broadcasts from the bridges. Sounds like insufficient testing of the code for running on networks without bridges. The reason it might work in a simple test is that nis_node and nis_net are mapped into locations in /etc/cap.ether.shared. Suppose the code was debugged on a network that has bridges. They would have gotten correctly set. If we shifted to a configuration that didn't listen to RTMP, but didn't zero /etc/cap.ether.shared, the correct values would have remained in the file from the other configuration. Thus the fact that they didn't get set would not show up. We're planning a new release of CAP/ethertalk anyway, to fix various reliability issues that we discovered over some period of use. This sounds easy enough to fix.