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: Re: lcnode bug
Message-ID: <1573@nosc.NOSC.MIL>
Date: 7 Dec 89 20:14:40 GMT
References: <8912062227.AA00850@umix.cc.umich.edu>
Sender: nobody@nosc.NOSC.MIL
Lines: 18

After I said:

> ... commands like lcnode
> and lusr display only information for the local subnet. ...

jshoj@EARTH.LERC.NASA.GOV ("Jeffery Hojnicki") writes:

> ... the instance sited is
> easily fixed with the lcnet command.  Use lcnet to get a listing of the
> connected networks and then do an lcnode on each network.  A script to do
> just that follows.

Granted.  My point, though, is that you shouldn't *have* to write shell
scripts to do these kinds of things; basic system support tools should
be supplied as part of the system.

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