Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!helios.ee.lbl.gov!nosc!Peanuts!dennis
From: dennis@Peanuts (Dennis Cottel)
Newsgroups: comp.sys.apollo
Subject: lcnode bug (was Handy Aegis Script)
Message-ID: <1565@nosc.NOSC.MIL>
Date: 6 Dec 89 16:03:14 GMT
References: <6354@hacgate.UUCP> <6355@hacgate.UUCP>
Sender: nobody@nosc.NOSC.MIL
Lines: 26

Warning: Apollo complaint follows.

lori@hacgate.UUCP (Lori Barfield) sends us a nifty shell script including
some constructions like:

>    /com/lcnode -b -id | /com/fpat -i -c -rm 2 ^node | read num_matches

The trouble with this is that if you have an Apollo internet--for
instance, several rings connected via Ethernet--commands like lcnode
and lusr display only information for the local subnet.  There is no
option on them to display all the connected nodes in the Apollo
internetwork.

This means that when you go to an internetwork, suddenly all the shell
scripts in which you used tricks like the above to find all the nodes,
or update all the disks in the network, don't work anymore and have to
be modified.  And changed again when you add another subnet.  Some of
the nice network transparency that is Apollo's strength has been
taken away.

I complained about this to the Apollo hotline, as well as submitted an
APR.  Apollo's response was essentially, "That's the way it works."
Nuts.

	Dennis Cottel  Naval Ocean Systems Center, San Diego, CA  92152
	(619) 553-1645      dennis@nosc.MIL      sdcsvax!noscvax!dennis