[3400] in SIPB bug reports
wafe & clients installed
daemon@ATHENA.MIT.EDU (Calvin Clark)
Tue Jan 5 07:23:01 1993
Date: Tue, 5 Jan 93 07:22:46 -0500
From: Calvin Clark <ckclark@mit.edu>
To: bug-sipb@Athena.MIT.EDU
Reply-To: ckclark@mit.edu
I installed wafe 0.92, and a few of the wafe applications in the sipb
locker. I have installed the wafe binary proper and the following
applications:
xiostats (1) - an x-based front end for iostat
xvmstats (1) - an x-based front end for vmstats
xwafedesign (1) - a design tool for wafe applications
xwafegopher (1) - a simple x-based gopher client
xwafenews (1) - an x-based NNTP news reader
Each of the above is written in perl. (Well, actually, the way this
works is as follows: you write a program called "foo" in any language
you like, and then you make a symlink from "xfoo" to wafe. When you run
"xfoo", wafe looks for the program "foo" and calls it as a subprocess as
the "backend" of the application. Aw, heck, just read the man page.
There are other applications distributed with wafe, but some of them are
either stupid (e.g., xwafeping, which does something so silly I dare not
mention it) or not applicable to our environment (e.g., xrupstats, which
requires ruptime(1).) One, xwafeftp, looks promising, but it has one
very obvious bug that I have to fix before I install it. The
applications I installed work, but are a bit rough around the edges;
they're more like examples than anything else.
For developers, the primary documentation is in
/mit/sipb/doc/wafedoc.tex. You might also want to learn Tcl. (Wafe
uses the tcl6.4 libraries and the 3-d Athena Widgets. I would have
liked to install these libraries with it because other applications
might use them, too, but the space in the sipb locker is too tight to
permit it.)
-Calvin
