From chris@softway.sw.oz Thu Aug 18 12:15:59 1988
Date: 18 Aug 88 12:16:31 +1000 (Thu)
From: chris@softway.oz (Chris Maltby)
>From neilb@spectrum.eecs.unsw.oz  Thu Aug 18 10:29:28 1988
Date: Thu, 18 Aug 88 10:29:28 aes
From: neilb@spectrum.eecs.unsw.oz (Neil Brown)
To: chris@softway.oz
Subject: Add ons for SUNIII

Chris,
 In a recent news article you expressed an interest in extras for
SUNIII, so I am sending you a little something I wiped up a while
ago.

 It is a version of linkstats that has been broken up into a server
and a client so that a linkstats can be done remotely over a UDP/IP.
 The reason I wrote this is that on our Apollo workstation rings,
remote filesystem access is only _almost_ completely transparent and unix
like. One of the gotchas is that if a process (like ENdaemon) on one
machine (like the machine holding the ACSnet link) has a file (like
the status file) open for writing, a process (like linkstats) on another
machine cannot open that file for reading. Basically, across machines,
its strictly one writer xor n readers.

So, i get inetd on the server to listen on port acsstats (I chose 6123)
and run /usr/spool/ACSnet/_lib/linkstatd when appropriate.
Then linkstats asks linkstatd what links exists, and then queries it
for the status information.

The AUSAM ifdefs are for a local version of udp/ip that I hacked into
out V7 kernals so that the old machines could talk on the ether net to
the new.

I currently have a window on my workstation that show a short linkstats
for all the links out of 5 of our machines - vey useful for monitoring the
network.

I'm not entirely happy with the code yet, linkstatd should do a bit
more cacheing so it only every scans the directory tree once.

Hope you find this at least interesting.

NeilBrown
neilb:{elecvax,*}.eecs.unsw.oz

