[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]
[0084]
[0085]
[0086]
[0087]
[0088]
[0089]
[0090]
[0091]
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099]
[0100]
[0101]
[0102]
[0103]
[0104]
[0105]
[0106]
[0107]
[0108]
[0109]
[0110]
[0111]
[0112]
[0113]
[0114]
[0115]
[0116]
[0117]
[0118]
[0119]
[0120]
[0121]
[0122]
[0123]
[0124]
[0125]
[0126]
[0127]
[0128]
[0129]
[0130]
[0131]
[0132]
[0133]
[0134]
[0135]
[0136]
[0137]
[0138]
[0139]
[0140]
[0141]
[0142]
[0143]
[0144]
[0145]
[0146]
[0147]
[0148]
[0149]
[0150]
[0151]
[0152]
<title>Utility directory read-me</title>
<style>
@media screen { a[target=_blank]::after { font-size:80%; content:"\2924"; } }
</style>
<div style="max-width:60em;">

<p> A small collection of utilities (and in some cases, scripts) useful in the
adminstration of a WASD site.

<P> Some are covered in greater detail in
<a target="_blank" href="/wasd_root/doc/features/">Features and Facilities</a>
document,
<a target="_blank" href="/wasd_root/doc/features/features_1200.html">Utilities and Facilities</a>
section.

<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>Comment</th></tr>

<tr>
<td>Calogs</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/calogs.c">calogs.c</a>
</td>
<td>
<i>Consolidate access logs</i> (pronounced the same as the breakfast cereal
brand <tt>:-)</tt> merges multiple HTTP server common and combined format
access logs into a single log file with records in time-order.
</td>
</tr>

<tr>
<td>CSPreport</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/cspreport.c">cspreport.c</a>
</td>
<td>
Content Security Policy Report[er]
<br><a target="_blank" target="_blank"
href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP">
https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP</a>
</td>
</tr>

<tr>
<td>HTAdmin</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/htadmin.c">htadmin.c</a>
</td>
<td>
Command-line administration of the WASD .$HTA authentication databases.
</td>
</tr>

<tr>
<td>HTTPdMon</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/httpdmon.c">httpdmon.c</a>
</td>
<td>
One of the fundamental tools for monitoring the status of the WASD server. 
This command-line utility continuously displays a number of key server process
quotas, server counters and latest request data.
Also see sHTTPDmon in&nbsp; 
<a target="_blank" href="/wasd_root/src/screper/"><tt>WASD_ROOT:[SRC.SCREPER]</tt></a>
</td>
</tr>

<tr>
<td>Proxy Munge<sup>**</sup></td>
<td>
<a target="_blank" href="/wasd_root/src/utils/proxymunge.c">proxymunge.c</a>
</td>
<td>
Script that munges (rewrites) URIs/URLs to provide a more effective
reverse-proxy.<br>
<i><sup>**</sup>Also check out the WASD v12.0.0 proxy=rework=.. capability.</i>
</td>
</tr>

<tr>
<td>Quick&nbsp;and&nbsp;Dirty<br>Log&nbsp;Statistics</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/qdlogstats.c">qdlogstats.c</a>
</td>
<td>
Useful command-line and script utility to generate quick snapshots and
elementary statistics of server usage from access logs. Intended for those
moments when we think &quot;I wonder how many times that new archive has been
downloaded?&quot;, &quot;How much data was transfered during November?&quot;,
&quot;How often is such-and-such a client using the authenticated so-and-so
service?&quot;, &quot;How much has the mail service been used?&quot; ... and
want the results in a matter of seconds (or at least a few tens of seconds
<tt>:-)<tt>
</td>
</tr>

<tr>
<td>Random Seed</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/randseed.c">randseed.c</a>
</td>
<td>
Small utility designed to populate a file with 2048 bytes of PRNG seed data. 
The seed should be high entropy. 
</td>
</tr>

<tr>
<td>Security&nbsp;.ch&nbsp;Army&nbsp;Knife</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/sechan.c">sechan.c</a>
</td>
<td>
(Pronounced "session") is used by SECURE.COM and associated procedures to
ensure package file system security settings are appropriate. It is also
available for direct use by the site administrator.
</td>
</tr>

<tr>
<td>WAStee</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/wastee.c">wastee.c</a>
</td>
<td>
WAStee is a utility to generate time-stamped log files containing intervals of
a long-lived WASD server process.  It is the tee in a PIPE sequence.
</td>
</tr>

<tr>
<td>Wot's Up?</td>
<td>
<a target="_blank" href="/wasd_root/src/utils/wotsup.c">wotsup.c</a>
</td>
<td>
The <i>WASD Over-The-Shoulder Uptime Picket</i> is designed to monitor WASD in
a production environment for the purpose of alerting operations staff to
conditions which might cause that production to be adversely impacted. The
utility runs in a detached process and monitors the server environment by
periodically polling various server data.  Alert reports can be delivered via
any combination of OPCOM message, MAIL, site-specific DCL command, and log file
entry.
</td>
</tr>

</table>
</div>