Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!psuvm!BRAZOS!SCHAFER From: schafer@BRAZOS.RICE.EDU (Richard A. Schafer) Newsgroups: bit.listserv.nodmgt-l Subject: Using NETSERV tools to update my node entry Message-ID: <4868@brazos.Rice.edu> Date: 9 Feb 90 22:33:46 GMT Sender: Node Management Discussion Reply-To: "Richard A. Schafer" Organization: Rice University Lines: 40 Approved: NETNEWS@PSUVM Gateway Comments: Warning -- original Sender: tag was root@RICE.EDU Comments: To: bit-listserv-nodmgt-l@cs.psu.edu I've heard the arguments about using NETSERV tools to update my node entry, and am not at all sure about a few things. Such as how to use them to change tags like routtab. Trying to update my routtab entry, I get told that I have more than 8 user tags (these turn out to be Inforep, Techrep, srv1id, srv1type, srv2id, tformat, tclass, cks, plus who knows what else). Since there are more than 8, NODESNAD refuses to display more than the first 8 tags, which presumably means I can't change the non-displayed tags, whatever they are. Is anyone going to update NODESNAD to recognize the newer tags? Am I using obsolete tools, and if so what should I be using? I got interested in this today when I found 3 routing tables in my reader: RICEVM1 NETINIT RICELIBR NETINIT RICE NETINIT Now I'll bet that my nodes entry for RICEVM1 and RICE don't contain :routtab. tags, which is why these were presumably generated by NETSERV. (Actually, looking at the VERS9002 NODUPD file, I find that someone has added :routtab tags saying that NETSERV is to generate the tables, and send them to me.) I've already sent in an update (too late for 9002; 9003?) to change RICEVM1 to indicate that I generate my own tables, thank you, and will also do that for RICELIBR and RICECSVM. But how on earth do I say not to generate a routing table for RICE, which is an alias of RICEVM1? This seems ludicrous, and seems to be a flaw in NETSERV's table generation process. Richard (TechRep for RICEVM1, RICECSVM, and RICELIBR. And also RICE?)