Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!DHDIBM1!PASCH
From: PASCH@DHDIBM1.BITNET (Berthold Pasch +49 (6221) 404-242)
Newsgroups: bit.listserv.nodmgt-l
Subject: Re: Using NETSERV tools to update my node entry
Message-ID: <NODMGT-L%90021310504910@DEARN>
Date: 13 Feb 90 15:59:03 GMT
Sender: Node Management Discussion <NODMGT-L@BITNIC>
Reply-To: Node Management Discussion <NODMGT-L@BITNIC>
Lines: 13
Approved: NETNEWS@PSUVM.BITNET Gateway

Now I know why Netserv generates routing tables for aliases:
The failure is caused by the way how Netserv processes aliases:
it simply copies all attributes of the node entry to a dummy (internal)
entry for the alias node and treats this entry as if it were a real node.
Thus the :routtab tag is duplicated and the table is generated for the
real nodeid and for the alias nodeid.
This, and similar problems with aliases will disappear with the new
nodes file format in which aliases are unknown. (Another good reason
for dropping the alias tag.)
However, to avoid the routing table problem I shall modify Netserv
and suppress copying of the :routtab tag for the alias nodeid.

Regards, Berthold