[0001]
[0002]
[0003]
[0004]
[0005]
[0006]
[0007]
[0008]
[0009]
[0010]
[0011]
[0012]
[0013]
[0014]
[0015]
[0016]
[0017]
[0018]
[0019]
[0020]
[0021]
[0022]
[0023]
[0024]
[0025]
[0026]
[0027]
[0028]
[0029]
[0030]
[0031]
[0032]
[0033]
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041]
[0042]
[0043]
[0044]
[0045]
[0046]
[0047]
[0048]
[0049]
[0050]
[0051]
[0052]
[0053]
[0054]
[0055]
[0056]
[0057]
[0058]
[0059]
[0060]
[0061]
[0062]
[0063]
[0064]
[0065]
[0066]
[0067]
[0068]
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075]
[0076]
[0077]
[0078]
[0079]
[0080]
[0081]
[0082]
[0083]
<title>Scr&eacute;per directory read-me</title>
<style>
@media screen { a[target=_blank]::after { font-size:80%; content:"\2924"; } }
</style>
<div style="max-width:60em;">

<p> A terminal screen screper, er scr&eacute;per, um scraper.

<p> Allows terminal-based application output (e.g. MONITOR utility) to be
displayed in a browser page.  A CGI script spawns a subprocess to execute
supplied DCL command(s) and the subprocess output is captured and converted to
HTML, continuously or one-off as required.  All example applications require
authorisation to activate.

<p>
<style>td,th{vertical-align:top;}</style>
<table cellpadding="5" cellspacing="0" border="1"
style="border-collapse:collapse;border:1px solid black;">

<tr><th>Name</th><th>Source&nbsp;Code</th><th>Example</th><th>Comment</th></tr>

<tr>
<td>scr&eacute;per</td>
<td>
<a target="_blank" href="/wasd_root/src/screper/screper.c">screper.c</a>
</td>
<td></td>
<td>
The fundamental terminal screen scraper module.  Built independently and the
object code linked with by an application (script).
</td>
</tr>

<tr>
<td>sadHoc</td>
<td>
<a target="_blank" href="/wasd_root/src/screper/sadhoc.c">sadhoc.c</a>
</td>
<td style="white-space:nowrap;">
<a target="_blank" href="/cgi-bin/sadhoc">/cgi-bin/sadhoc</a>
</td>
<td>
Allows ad hoc scr&eacute;per experimentation/configuration for up to four
terminal application displays on the one page.  Some familiarity with the
scr&eacute;per command syntax is required.  See 
<a target="_blank" href="/wasd_root/src/screper/screper.c">screper.c</a>
</td>
</tr>

<tr>
<td>sHTTPDmon</td>
<td>
<a target="_blank" href="/wasd_root/src/screper/shttpdmon.c">shttpdmon.c</a>
</td>
<td style="white-space:nowrap;">
<a target="_blank" href="/cgi-bin/shttpdmon">/cgi-bin/shttpdmon</a>
</td>
<td>
One of the fundamental tools for monitoring the status of the WASD server, this
time in a browser window.  Requires INSTALLation with privilege.
</td>
</tr>

<tr>
<td>sMONitor</td>
<td>
<a target="_blank" href="/wasd_root/src/screper/smonitor.c">smonitor.c</a>
</td>
<td style="white-space:nowrap;">
<a target="_blank" href="/cgi-bin/smonitor">/cgi-bin/smonitor</a>
</td>
<td>
The familiar CLI application MONITOR via browser.  When accessed without query
presents a page providing class and qualifier selection for up to six monitor
instances on a single browser page.  Interval and font size (allowing those six
to be crammed onto that single page) may also be specified.  A useful
application for those who might be used to MONITOR for surveilling system
activity.
</td>
</tr>

</table>
</div>