Sprout from master 2004-03-10 08:55:08 UTC Tim Bishop <tim@bishnet.net> 'Minor wording change.'
Delete:
www/cms/acknowledgements.shtml
www/cms/documentation/gettingstarted.shtml
www/cms/documentation/gettingstarted.xhtml
www/cms/documentation/index.shtml
www/cms/documentation/index.xhtml
www/cms/downloads/index.shtml
www/cms/features.shtml
www/cms/features.xhtml
www/cms/javadoc/index.shtml
www/cms/javadoc/index.xhtml
www/cms/minutes.shtml
www/cms/minutes.xhtml
www/cms/oldtodo.shtml
www/cms/probdomain.shtml
www/cms/projectpapers.shtml
www/cms/projectpapers.xhtml
www/cms/quotes.shtml
www/cms/screenshots/alerter-email.gif
www/cms/screenshots/alerter-irc.gif
www/cms/screenshots/conient-config.gif
www/cms/screenshots/conient-main.gif
www/cms/screenshots/conient-platform-info.gif
www/cms/screenshots/conient-queues.gif
www/cms/screenshots/ihost-main.gif
www/cms/screenshots/index.shtml
www/cms/screenshots/index.xhtml
www/cms/screenshots/reports-alerts-all.gif
www/cms/screenshots/reports-main.gif
www/cms/screenshots/reports-public-autoscroll.gif
www/cms/screenshots/reports-raptor-latest-misc.gif
www/cms/screenshots/reports-raptor-load15.gif
www/cms/screenshots/reports-raptor-users.gif
www/cms/screenshots/server-main.gif
www/cms/screenshots/thumbnail-alerter-email.gif
www/cms/screenshots/thumbnail-alerter-irc.gif
www/cms/screenshots/thumbnail-conient-config.gif
www/cms/screenshots/thumbnail-conient-main.gif
www/cms/screenshots/thumbnail-conient-platform-info.gif
www/cms/screenshots/thumbnail-conient-queues.gif
www/cms/screenshots/thumbnail-ihost-main.gif
www/cms/screenshots/thumbnail-reports-alerts-all.gif
www/cms/screenshots/thumbnail-reports-main.gif
www/cms/screenshots/thumbnail-reports-public-autoscroll.gif
www/cms/screenshots/thumbnail-reports-raptor-latest-misc.gif
www/cms/screenshots/thumbnail-reports-raptor-load15.gif
www/cms/screenshots/thumbnail-reports-raptor-users.gif
www/cms/screenshots/thumbnail-server-main.gif
www/cms/screenshots/thumbnail-winhost-main.gif
www/cms/screenshots/winhost-main.gif
www/cms/todo.shtml
www/cvs.xhtml
www/images/freebsdlogo.gif
www/images/freebsdlogo_small.gif
www/index.xhtml
www/libstatgrab/index.xhtml
www/license.xhtml
www/mailinglists.xhtml
www/pgpkey.xhtml
www/support.xhtml
www/who.xhtml
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>i-scream acknowledgements and credits</title>
- <meta name="description" content="A list of those who helped to develop the i-scream central monitoring system.">
- <meta name="keywords" content="i-scream, project, credits, central,monitoring,system, unix, linux, nt, server, alert, acknowledgements">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000000">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-
-
-
-<div align="center">
- <center>
- <table border="0" width="500">
- <tr>
- <td>
- <h1 align="center"><font face="Arial" color="#000066">Acknowledgements</font></h1>
- </center>
- <p align="left"><font face="Arial" size="2">We would like to thank all of
- those who have made the i-scream distributed central monitoring system
- possible, namely the programmers and those who have assisted in
- development by testing our software and offering feedback.</font></p>
- <p align="left"><font face="Arial" size="2">The i-scream central
- monitoring system started off as a final year Computer Science group
- project at the University of Kent at Canterbury, UK. Since finishing
- their degrees, the main programmers have continued to develop the
- system </font></p>
- <center>
- <h2 align="center"><font face="Arial" color="#000066">The Server</font></h2>
- <p align="center"><font face="Arial" size="2">Alex Moore<br>
- Paul Mutton<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">ihost</font></h2>
- <p align="center"><font face="Arial" size="2">Paul Mutton<br>
- Pete Saunders<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">WinHost</font></h2>
- <p align="center"><font face="Arial" size="2">Paul Mutton</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Web Reports</font></h2>
- <p align="center"><font face="Arial" size="2">Paul Mutton<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Conient</font></h2>
- <p align="center"><font face="Arial" size="2">Alex Moore</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Website</font></h2>
- <p align="center"><font face="Arial" size="2">Alex Moore<br>
- Paul Mutton<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Historical Reports</font></h2>
- <p align="center"><font face="Arial" size="2">Paul Mutton<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">System-wide
- Utilities</font></h2>
- <p align="center"><font face="Arial" size="2">Alex Moore<br>
- Paul Mutton<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Testing and Feedback</font></h2>
- <p align="center"><font face="Arial" size="2">Adam Sampson<br>
- Alex Moore<br>
- Ash Beeson<br>
- Fred Barnes<br>
- Ian Utting<br>
- John Cinnamond<br>
- Mark Wheadon<br>
- Paul Mutton<br>
- Phill Camp<br>
- Tim Bishop</font></p>
- <h2 align="center"><font face="Arial" color="#000066">Ideas and Support</font></h2>
- <p align="center"><font face="Arial" size="2">John Cinnamond<br>
- Phill Camp<br>
- Mark Wheadon<br>
- Ian Utting</font></p>
- <p align="left"> </p>
- <p align="left"><font face="Arial" size="2">We would also like to thank
- the UKC Computer Science department and the UKC Templeman Library for
- allowing us to run and test the project on their machines, and all those
- people that have supported us along the way.</font><p align="left">
- <font face="Arial" size="2">Finally we wish to commend the creators of
- <a href="http://www.jacorb.org/">JacORB</a>, without which, the project would not have achieved the goals we set
- out to reach.</font></td>
- </tr>
- </table>
-</div>
-
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- gettingstarted.shtml
- Created by tdb1 27/05/2001
- Last edited 27/05/2001
--->
-
-<html>
-
-<head>
- <title>Getting Started with the i-scream Central Monitoring System</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<font face="arial,sans-serif" size="2">
-
-<h2>Getting Started with the i-scream Central Monitoring System</h2>
-
-<h3>1. Installing the corba services (pre-requisite for the server)</h3>
-<p>The server requires a CORBA Naming Service to run. It may be that you already
-have such a system running, in which case you can use that. Simply edit the
-jacorb.properties file to point to your Naming service. If you don't have a
-naming service running you could just set up your own manually, but if like us
-you want the easy approach, install our corba services program.</p>
-<p>This program runs the naming service and provides a builtin webserver to
-serve requests to the server application. The documentation details how to get
-this running. It should simply be a case of extracting and running.</p>
-<h3>1. Installing the server</h3>
-<p>The first stage is to download and install the server application. The
-latest versions of all i-scream applications can be found at the following
-URL:</p>
-<p><a href="http://www.i-scream.org/downloads">http://www.i-scream.org/downloads</a></p>
-<p>Once downloaded, the archive should be extracted to a directory of your
-choice. The server will run on most Java enabled platforms (including
-Windows, Linux and FreeBSD).</p>
-<p>The archive consists of only a few files and directories. The main file is
-the iscream-server.jar archive which contains all the binary code for the
-server. The lib directory contains other JAR archives which the server
-requires to run. The etc directory contains (or will contain)
-configuration for most of the i-scream central monitoring system. The next
-step is to configure the server to suit your requirements.</p>
-<h3>2. Configuring the server</h3>
-<p>The configuration is split into two main files. The first,
-default.properties can be considered a bootstrap configuration. This means
-that it provides basic configuration to get the server started, after
-which point the main configuration system takes over. This file should be
-checked through, and is pretty well explained by comments.</p>
-<p>The rest of the server configuration is based on system.conf. This can
-hold the entire system configuration, including hosts. It may also specify
-other configuration files to be included in the main configuration. This
-file is also commented extensively.</p>
-<p>This step may well take some time to get right, and you can come back to
-it at any point. Lots of the configuration can be changed "on the fly"
-as well.</p>
-<p>For fuller and complete details of the configuration system, and the
-server in general, please see the Server User Guide in the documentation
-section of the website.</p>
-<h3>2a. Setting up the database</h3>
-<p>The i-scream central monitoring system can make use of a database for
-generating historical reports. The documentation explains how you would
-configure the system to do this. You will need to create a single basic
-table yourself, this is also explained in the documentation.</p>
-<h3>3. Starting the server</h3>
-<p>Starting up the server is a trivial task. Usually you can just get away
-with running the run script provided. This will boot the server up
-displaying some basic information to the console. If something goes wrong,
-the error message should point to the cause.</p>
-<h3>4. Setting up hosts</h3>
-<p>Hosts can be run on either Unix (tested with Solaris, FreeBSD and some
-Linux distributions) or Windows. Both are equally easy to setup.</p>
-<p>Firstly, the Unix host is called "ihost". This can be downloaded from the
-i-scream website. Once extracted it just needs to be started up. You need two
-pieces of information to do this: the filtermanager (part of the server) host
-and port number. If you haven't changed much in terms of configuration this will
-be the machine the server is running on, and port 4567. To start ihost you
-simply type:</p>
-</font>
-<pre>ihost.pl server.domain.com port</pre>
-<font face="arial,sans-serif" size="2">
-<p>ihost will then contact the server to obtain it's configuration and start
-sending information.</p>
-<p>The windows host, winhost, is very similar. All you need to do is install it
-using the provided installer in the download, and then edit the ini file to
-provide the two bits of information above. Running the application starts up
-communication with the server and data sending commences.</p>
-<p>Full details of both of these hosts can be found in the relevant
-documentation on the website.</p>
-<h3>5. Using Conient</h3>
-<p>Conient allows you to view, in real time, the data being sent by the
-hosts. This is a perfect way to test that all the above steps have
-successfully been completed.</p>
-<p>At present Conient is simply another archive which can be extracted and
-run. However, in the near future we hope to have an installer to make life
-easier. Conient is a Java application and will run on most Java enabled
-platforms.</p>
-<p>After extracting, the run script can be used to start Conient, or in some
-cases the JAR file can be executed manually. The GUI will then load. The
-configuration section requires you to enter a host and port for the
-server. By default this will be the machine on which the server is running
-and port 4510. Conient will then connect upon request and start displaying
-information.</p>
-<p>Assuming data is displayed you have successfully setup the i-scream
-central monitoring system. Well done!</p>
-<p>This is explained in much more detail in the Conient documentation.</p>
-<h3>6. Setting up DBReporter</h3>
-<p>If you are making use of a database you can setup the DBReporter to
-generate web-based reports of the information collected. This is just a
-case of extracting the archive to a suitable location, configuring it, and
-setting it to run on a regular basis (we suggest daily). DBReporter will
-also ensure the database is kept relatively clean.</p>
-<p>Full instructions are available in the DBReporter documentation.</p>
-<h3>7. Setting up the Web Interface</h3>
-<p>The Web interface allows you to view various aspects of the i-scream
-central monitoring system's output. These include realtime viewing of data
-(much like Conient), links to the DBReporter above, and full displaying of
-the alerts that can be generated by the server.</p>
-<p>The archive contains a series of PHP scripts which should be placed on
-your PHP enabled web server. The configuration files allow you to tailor
-the setup to suit your needs.</p>
-<p>Full instructions are available in the relevant documentation.</p>
-<h3>8. Further</h3>
-<p>You may decide to expand your setup to cover a larger network. For example, a
-distributed filter arrangement could cut down on the amount of traffic
-being sent around the network. The server itself can be distributed to suit your
-needs. You may wish to run the database section of the server on the same
-machine as the database, while running the rest on another machine.</p>
-<p>Some discussion about this is available in the server documentation.</p>
-<p>If you have any questions about any of the above, please don't hesitate to
-contact us at <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>. If you find we've missed something out,
-again, please let us know.</p>
-<p>Finally, we'd like to thank you for trying this i-scream product. We realise
-that it's still at an early stage, and we therefore appreciate you taking
-the time to try it out.</p>
-<p>The i-scream team.
-
-</font>
-
-<!--#include virtual="../bottom.inc" --></td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- gettingstarted.shtml
- Created by tdb1 27/05/2001
- Last edited 27/05/2001
--->
-
-<html>
-
-<head>
- <title>Getting Started with the i-scream Central Monitoring System</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<font face="arial,sans-serif" size="2">
-
-<h2>Getting Started with the i-scream Central Monitoring System</h2>
-
-<h3>1. Installing the corba services (pre-requisite for the server)</h3>
-<p>The server requires a CORBA Naming Service to run. It may be that you already
-have such a system running, in which case you can use that. Simply edit the
-jacorb.properties file to point to your Naming service. If you don't have a
-naming service running you could just set up your own manually, but if like us
-you want the easy approach, install our corba services program.</p>
-<p>This program runs the naming service and provides a builtin webserver to
-serve requests to the server application. The documentation details how to get
-this running. It should simply be a case of extracting and running.</p>
-<h3>1. Installing the server</h3>
-<p>The first stage is to download and install the server application. The
-latest versions of all i-scream applications can be found at the following
-URL:</p>
-<p><a href="http://www.i-scream.org/downloads">http://www.i-scream.org/downloads</a></p>
-<p>Once downloaded, the archive should be extracted to a directory of your
-choice. The server will run on most Java enabled platforms (including
-Windows, Linux and FreeBSD).</p>
-<p>The archive consists of only a few files and directories. The main file is
-the iscream-server.jar archive which contains all the binary code for the
-server. The lib directory contains other JAR archives which the server
-requires to run. The etc directory contains (or will contain)
-configuration for most of the i-scream central monitoring system. The next
-step is to configure the server to suit your requirements.</p>
-<h3>2. Configuring the server</h3>
-<p>The configuration is split into two main files. The first,
-default.properties can be considered a bootstrap configuration. This means
-that it provides basic configuration to get the server started, after
-which point the main configuration system takes over. This file should be
-checked through, and is pretty well explained by comments.</p>
-<p>The rest of the server configuration is based on system.conf. This can
-hold the entire system configuration, including hosts. It may also specify
-other configuration files to be included in the main configuration. This
-file is also commented extensively.</p>
-<p>This step may well take some time to get right, and you can come back to
-it at any point. Lots of the configuration can be changed "on the fly"
-as well.</p>
-<p>For fuller and complete details of the configuration system, and the
-server in general, please see the Server User Guide in the documentation
-section of the website.</p>
-<h3>2a. Setting up the database</h3>
-<p>The i-scream central monitoring system can make use of a database for
-generating historical reports. The documentation explains how you would
-configure the system to do this. You will need to create a single basic
-table yourself, this is also explained in the documentation.</p>
-<h3>3. Starting the server</h3>
-<p>Starting up the server is a trivial task. Usually you can just get away
-with running the run script provided. This will boot the server up
-displaying some basic information to the console. If something goes wrong,
-the error message should point to the cause.</p>
-<h3>4. Setting up hosts</h3>
-<p>Hosts can be run on either Unix (tested with Solaris, FreeBSD and some
-Linux distributions) or Windows. Both are equally easy to setup.</p>
-<p>Firstly, the Unix host is called "ihost". This can be downloaded from the
-i-scream website. Once extracted it just needs to be started up. You need two
-pieces of information to do this: the filtermanager (part of the server) host
-and port number. If you haven't changed much in terms of configuration this will
-be the machine the server is running on, and port 4567. To start ihost you
-simply type:</p>
-</font>
-<pre>ihost.pl server.domain.com port</pre>
-<font face="arial,sans-serif" size="2">
-<p>ihost will then contact the server to obtain it's configuration and start
-sending information.</p>
-<p>The windows host, winhost, is very similar. All you need to do is install it
-using the provided installer in the download, and then edit the ini file to
-provide the two bits of information above. Running the application starts up
-communication with the server and data sending commences.</p>
-<p>Full details of both of these hosts can be found in the relevant
-documentation on the website.</p>
-<h3>5. Using Conient</h3>
-<p>Conient allows you to view, in real time, the data being sent by the
-hosts. This is a perfect way to test that all the above steps have
-successfully been completed.</p>
-<p>At present Conient is simply another archive which can be extracted and
-run. However, in the near future we hope to have an installer to make life
-easier. Conient is a Java application and will run on most Java enabled
-platforms.</p>
-<p>After extracting, the run script can be used to start Conient, or in some
-cases the JAR file can be executed manually. The GUI will then load. The
-configuration section requires you to enter a host and port for the
-server. By default this will be the machine on which the server is running
-and port 4510. Conient will then connect upon request and start displaying
-information.</p>
-<p>Assuming data is displayed you have successfully setup the i-scream
-central monitoring system. Well done!</p>
-<p>This is explained in much more detail in the Conient documentation.</p>
-<h3>6. Setting up DBReporter</h3>
-<p>If you are making use of a database you can setup the DBReporter to
-generate web-based reports of the information collected. This is just a
-case of extracting the archive to a suitable location, configuring it, and
-setting it to run on a regular basis (we suggest daily). DBReporter will
-also ensure the database is kept relatively clean.</p>
-<p>Full instructions are available in the DBReporter documentation.</p>
-<h3>7. Setting up the Web Interface</h3>
-<p>The Web interface allows you to view various aspects of the i-scream
-central monitoring system's output. These include realtime viewing of data
-(much like Conient), links to the DBReporter above, and full displaying of
-the alerts that can be generated by the server.</p>
-<p>The archive contains a series of PHP scripts which should be placed on
-your PHP enabled web server. The configuration files allow you to tailor
-the setup to suit your needs.</p>
-<p>Full instructions are available in the relevant documentation.</p>
-<h3>8. Further</h3>
-<p>You may decide to expand your setup to cover a larger network. For example, a
-distributed filter arrangement could cut down on the amount of traffic
-being sent around the network. The server itself can be distributed to suit your
-needs. You may wish to run the database section of the server on the same
-machine as the database, while running the rest on another machine.</p>
-<p>Some discussion about this is available in the server documentation.</p>
-<p>If you have any questions about any of the above, please don't hesitate to
-contact us at <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>. If you find we've missed something out,
-again, please let us know.</p>
-<p>Finally, we'd like to thank you for trying this i-scream product. We realise
-that it's still at an early stage, and we therefore appreciate you taking
-the time to try it out.</p>
-<p>The i-scream team.
-
-</font>
-
-<!--#include virtual="../bottom.inc" --></td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- index.shtml
- Created by pjm2 24/03/2001
- Last edited 24/03/2001
--->
-
-<html>
-
-<head>
- <title>i-scream documentation</title>
-</head>
-
-<basefont face="arial, sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-<font size="2">
-<h3>i-scream documentation</h3>
-<p>This is the offical documentation for the i-scream central monitoring
-system. They should be considered "correct" over any other older
-documentation that still exists on the website. They are currently only
-available in either Microsoft Word or PDF format.</p>
-
-<p>These documents are correct for the version of code available for download
-from this website. However, there may be changes in the CVS version which
-are not documented in the code. The link below shows what changes have been
-made since the project completion date.</p>
-
-<a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29&module=cms">
-Commits to the "cms" CVS module since project completion (29/03/2001)</a>
-
-<hr>
-<h4>User guides</h4>
-(<a href="/documentation/gettingstarted.shtml">HTML</a>) Getting Started with the i-scream Central Monitoring System<br>
-(<a href="/documentation/printable/host/ihost/ihost_user_guide.doc">Word</a>|<a href="/documentation/printable/host/ihost/ihost_user_guide.pdf">PDF</a>) Unix/Linux ihost user guide<br>
-(<a href="/documentation/printable/host/winhost/winhost_user_guide.doc">Word</a>|<a href="/documentation/printable/host/winhost/winhost_user_guide.pdf">PDF</a>) Windows WinHost user guide<br>
-(<a href="/documentation/printable/client/conient_user_guide.doc">Word</a>|<a href="/documentation/printable/client/conient_user_guide.pdf">PDF</a>) Conient client user guide<br>
-(<a href="/documentation/printable/server/server_user_guide.doc">Word</a>|<a href="/documentation/printable/server/server_user_guide.pdf">PDF</a>) Server user guide<br>
-(<a href="/documentation/printable/server/corba_services.doc">Word</a>|<a href="/documentation/printable/server/corba_services.pdf">PDF</a>) CORBA Services user guide<br>
-(<a href="/documentation/printable/reports/web_user_guide.doc">Word</a>|<a href="/documentation/printable/reports/web_user_guide.pdf">PDF</a>) Web reports user guide<br>
-(<a href="/documentation/printable/reports/dbreporter_user_guide.doc">Word</a>|<a href="/documentation/printable/reports/dbreporter_user_guide.pdf">PDF</a>) Database reporter user guide<br>
-
-<h4>Maintenance documentation for developers</h4>
-(<a href="/documentation/printable/host/ihost/ihost_maintenance.doc">Word</a>|<a href="/documentation/printable/host/ihost/ihost_maintenance.pdf">PDF</a>) Unix/Linux ihost maintenance<br>
-(<a href="/documentation/printable/host/winhost/winhost_maintenance.doc">Word</a>|<a href="/documentation/printable/host/winhost/winhost_maintenance.pdf">PDF</a>) Windows WinHost maintenance<br>
-(<a href="/documentation/printable/client/conient_maintenance.doc">Word</a>|<a href="/documentation/printable/client/conient_maintenance.pdf">PDF</a>) Conient maintenance<br>
-(<a href="/documentation/printable/server/server_maintenance.doc">Word</a>|<a href="/documentation/printable/server/server_maintenance.pdf">PDF</a>) Server maintenance<br>
-(<a href="/documentation/printable/reports/web_reports_maintenance.doc">Word</a>|<a href="/documentation/printable/reports/web_reports_maintenance.pdf">PDF</a>) Web reports maintenance<br>
-(<a href="/documentation/printable/reports/dbreporter_maintenance.doc">Word</a>|<a href="/documentation/printable/reports/dbreporter_maintenance.pdf">PDF</a>) Database reporter maintenance<br>
-
-<h4>Specification documents</h4>
-(<a href="/documentation/printable/spec/domain/problem_domain.doc">Word</a>|<a href="/documentation/printable/spec/domain/problem_domain.pdf">PDF</a>) Original specification & problem domain<br>
-(<a href="/documentation/printable/spec/protocols/protocols.doc">Word</a>|<a href="/documentation/printable/spec/protocols/protocols.pdf">PDF</a>) TCP Protocol specifications<br>
-(<a href="/documentation/printable/spec/xml/xml_expected_data.doc">Word</a>|<a href="/documentation/printable/spec/xml/xml_expected_data.pdf">PDF</a>) Expected XML data from host to server<br>
-(<a href="/documentation/printable/spec/xml/xml_recommendations.doc">Word</a>|<a href="/documentation/printable/spec/xml/xml_recommendations.pdf">PDF</a>) XML recommendations for host to server UDP packets<br>
-(<a href="/documentation/printable/spec/docs/document_standards.doc">Word</a>|<a href="/documentation/printable/spec/docs/document_standards.pdf">PDF</a>) Document standards<br>
-(<a href="/documentation/printable/spec/code/java_coding_standards.doc">Word</a>|<a href="/documentation/printable/spec/code/java_coding_standards.pdf">PDF</a>) Java coding standards<br>
-
-<h4>Other documents</h4>
-(<a href="/documentation/printable/plan/risk_analysis.doc">Word</a>|<a href="/documentation/printable/plan/risk_analysis.pdf">PDF</a>) Risk analysis<br>
-(<a href="/documentation/printable/plan/est_time_allocation.doc">Word</a>|<a href="/documentation/printable/plan/est_time_allocation.pdf">PDF</a>) Estimated time allocation<br>
-(<a href="/documentation/printable/plan/implementation_phases.doc">Word</a>|<a href="/documentation/printable/plan/implementation_phases.pdf">PDF</a>) Implementation phases for our plan<br>
-(<a href="/documentation/printable/plan/est_time_allocation_revised.doc">Word</a>|<a href="/documentation/printable/plan/est_time_allocation_revised.pdf">PDF</a>) Estimated time allocation (revised)<br>
-(<a href="/documentation/printable/process/meeting_minutes.doc">Word</a>|<a href="/documentation/printable/process/meeting_minutes.pdf">PDF</a>) Meeting Minutes<br>
-(<a href="/documentation/printable/process/use_of_website.doc">Word</a>|<a href="/documentation/printable/process/use_of_website.pdf">PDF</a>) Use of the website<br>
-(<a href="/documentation/printable/process/cvs_softwarebuilds.doc">Word</a>|<a href="/documentation/printable/process/cvs_softwarebuilds.pdf">PDF</a>) Use of CVS and automated software builds<br>
-(<a href="/documentation/printable/analysis/comparison_big_brother.doc">Word</a>|<a href="/documentation/printable/analysis/comparison_big_brother.pdf">PDF</a>) Comparison to Big Brother<br>
-<hr>
-</font>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- index.shtml
- Created by pjm2 24/03/2001
- Last edited 24/03/2001
--->
-
-<html>
-
-<head>
- <title>i-scream documentation</title>
-</head>
-
-<basefont face="arial, sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-<font size="2">
-<h3>i-scream documentation</h3>
-<p>This is the offical documentation for the i-scream central monitoring
-system. They should be considered "correct" over any other older
-documentation that still exists on the website. They are currently only
-available in either Microsoft Word or PDF format.</p>
-
-<p>These documents are correct for the version of code available for download
-from this website. However, there may be changes in the CVS version which
-are not documented in the code. The link below shows what changes have been
-made since the project completion date.</p>
-
-<a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29&module=cms">
-Commits to the "cms" CVS module since project completion (29/03/2001)</a>
-
-<hr>
-<h4>User guides</h4>
-(<a href="/documentation/gettingstarted.shtml">HTML</a>) Getting Started with the i-scream Central Monitoring System<br>
-(<a href="/documentation/printable/host/ihost/ihost_user_guide.doc">Word</a>|<a href="/documentation/printable/host/ihost/ihost_user_guide.pdf">PDF</a>) Unix/Linux ihost user guide<br>
-(<a href="/documentation/printable/host/winhost/winhost_user_guide.doc">Word</a>|<a href="/documentation/printable/host/winhost/winhost_user_guide.pdf">PDF</a>) Windows WinHost user guide<br>
-(<a href="/documentation/printable/client/conient_user_guide.doc">Word</a>|<a href="/documentation/printable/client/conient_user_guide.pdf">PDF</a>) Conient client user guide<br>
-(<a href="/documentation/printable/server/server_user_guide.doc">Word</a>|<a href="/documentation/printable/server/server_user_guide.pdf">PDF</a>) Server user guide<br>
-(<a href="/documentation/printable/server/corba_services.doc">Word</a>|<a href="/documentation/printable/server/corba_services.pdf">PDF</a>) CORBA Services user guide<br>
-(<a href="/documentation/printable/reports/web_user_guide.doc">Word</a>|<a href="/documentation/printable/reports/web_user_guide.pdf">PDF</a>) Web reports user guide<br>
-(<a href="/documentation/printable/reports/dbreporter_user_guide.doc">Word</a>|<a href="/documentation/printable/reports/dbreporter_user_guide.pdf">PDF</a>) Database reporter user guide<br>
-
-<h4>Maintenance documentation for developers</h4>
-(<a href="/documentation/printable/host/ihost/ihost_maintenance.doc">Word</a>|<a href="/documentation/printable/host/ihost/ihost_maintenance.pdf">PDF</a>) Unix/Linux ihost maintenance<br>
-(<a href="/documentation/printable/host/winhost/winhost_maintenance.doc">Word</a>|<a href="/documentation/printable/host/winhost/winhost_maintenance.pdf">PDF</a>) Windows WinHost maintenance<br>
-(<a href="/documentation/printable/client/conient_maintenance.doc">Word</a>|<a href="/documentation/printable/client/conient_maintenance.pdf">PDF</a>) Conient maintenance<br>
-(<a href="/documentation/printable/server/server_maintenance.doc">Word</a>|<a href="/documentation/printable/server/server_maintenance.pdf">PDF</a>) Server maintenance<br>
-(<a href="/documentation/printable/reports/web_reports_maintenance.doc">Word</a>|<a href="/documentation/printable/reports/web_reports_maintenance.pdf">PDF</a>) Web reports maintenance<br>
-(<a href="/documentation/printable/reports/dbreporter_maintenance.doc">Word</a>|<a href="/documentation/printable/reports/dbreporter_maintenance.pdf">PDF</a>) Database reporter maintenance<br>
-
-<h4>Specification documents</h4>
-(<a href="/documentation/printable/spec/domain/problem_domain.doc">Word</a>|<a href="/documentation/printable/spec/domain/problem_domain.pdf">PDF</a>) Original specification & problem domain<br>
-(<a href="/documentation/printable/spec/protocols/protocols.doc">Word</a>|<a href="/documentation/printable/spec/protocols/protocols.pdf">PDF</a>) TCP Protocol specifications<br>
-(<a href="/documentation/printable/spec/xml/xml_expected_data.doc">Word</a>|<a href="/documentation/printable/spec/xml/xml_expected_data.pdf">PDF</a>) Expected XML data from host to server<br>
-(<a href="/documentation/printable/spec/xml/xml_recommendations.doc">Word</a>|<a href="/documentation/printable/spec/xml/xml_recommendations.pdf">PDF</a>) XML recommendations for host to server UDP packets<br>
-(<a href="/documentation/printable/spec/docs/document_standards.doc">Word</a>|<a href="/documentation/printable/spec/docs/document_standards.pdf">PDF</a>) Document standards<br>
-(<a href="/documentation/printable/spec/code/java_coding_standards.doc">Word</a>|<a href="/documentation/printable/spec/code/java_coding_standards.pdf">PDF</a>) Java coding standards<br>
-
-<h4>Other documents</h4>
-(<a href="/documentation/printable/plan/risk_analysis.doc">Word</a>|<a href="/documentation/printable/plan/risk_analysis.pdf">PDF</a>) Risk analysis<br>
-(<a href="/documentation/printable/plan/est_time_allocation.doc">Word</a>|<a href="/documentation/printable/plan/est_time_allocation.pdf">PDF</a>) Estimated time allocation<br>
-(<a href="/documentation/printable/plan/implementation_phases.doc">Word</a>|<a href="/documentation/printable/plan/implementation_phases.pdf">PDF</a>) Implementation phases for our plan<br>
-(<a href="/documentation/printable/plan/est_time_allocation_revised.doc">Word</a>|<a href="/documentation/printable/plan/est_time_allocation_revised.pdf">PDF</a>) Estimated time allocation (revised)<br>
-(<a href="/documentation/printable/process/meeting_minutes.doc">Word</a>|<a href="/documentation/printable/process/meeting_minutes.pdf">PDF</a>) Meeting Minutes<br>
-(<a href="/documentation/printable/process/use_of_website.doc">Word</a>|<a href="/documentation/printable/process/use_of_website.pdf">PDF</a>) Use of the website<br>
-(<a href="/documentation/printable/process/cvs_softwarebuilds.doc">Word</a>|<a href="/documentation/printable/process/cvs_softwarebuilds.pdf">PDF</a>) Use of CVS and automated software builds<br>
-(<a href="/documentation/printable/analysis/comparison_big_brother.doc">Word</a>|<a href="/documentation/printable/analysis/comparison_big_brother.pdf">PDF</a>) Comparison to Big Brother<br>
-<hr>
-</font>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- index.shtml
- Created by tdb1 27/02/2001
- Last edited 27/05/2001
--->
-
-<!-- pjm2: set the time format -->
-<!--#config timefmt="%d %B %Y" -->
-
-<html>
-
-<head>
- <title>i-scream software builds</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<table width="480" border="0">
- <tr>
- <td>
- <h2>i-scream software builds</h2>
- <font size="2">
- <p>All downloads are <a href="/license.shtml">licensed</a> under the GPL.</p>
- <p>All new builds will be signed with our <a href="/pgpkey.shtml">PGP key</a>.</p>
- </font>
- </td>
- </tr>
-
- <tr>
- <td>
- <h3>current builds</h3>
- <font size="2">
- <p>These builds are the latest development working copies. They are much
- more developed than the downloads you'll find below. We recommend you
- start here. This is the codebase from which we'll make a proper release
- sometime in the future.</p>
- <p><a href="http://snapshots.i-scream.org">Snapshot Server</a></p>
- </font>
- </td>
- </tr>
-
- <tr>
- <td>
- <h3>old (but unchanging) builds</h3>
- <font size="2">
- <p>These builds are from the end of the project. Development is still
- continuing and can be found in the section above. These downloads are
- not changing, and will not be updated until a release is made. Unless
- you are really sure you want this version, get the one above.
-
- <p>Full documentation can be found by following the "Documentation"
- link on the left-hand bar. Downloads below are the same, apart from
- the archive format - with one exception being the host application.</p>
-
- <p>You will be asked to enter some basic information before
- downloading, although this is purely optional. We value feedback
- from people testing the i-scream products, so please feel free to
- contact us at dev@i-scream.org.</p>
- </font>
- </td>
- </tr>
-</table>
-
-<table border="1" cellspacing="0" cellpadding="4" bgcolor="#000066">
- <tr bgcolor="#000066">
- <td><b><font color="white">Build name</font></b></td>
- <td><b><font color="white">Windows downloads<br>(.zip format)</font></b></td>
- <td><b><font color="white">Unix downloads<br>(.tar.gz format)</font></b></td>
- </tr>
- <tr bgcolor="white">
- <td>i-scream Conient (GUI client)</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-conient-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-conient-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-conient-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-conient-HEAD.tar.gz"--></font></td>
- </tr>
- <tr bgcolor="#ccccff">
- <td>i-scream host application</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-winhost-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-winhost-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-ihost-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-ihost-HEAD.tar.gz"--></font></td>
- </tr>
- <tr bgcolor="white">
- <td>i-scream server</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-server-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-server-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-server-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-server-HEAD.tar.gz"--></font></td>
- </tr>
- <tr bgcolor="#ccccff">
- <td>i-scream PHP web reports</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-webreports-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-webreports-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-webreports-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-webreports-HEAD.tar.gz"--></font></td>
- </tr>
- <tr bgcolor="white">
- <td>i-scream historical database reporter</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-dbreporter-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-dbreporter-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-dbreporter-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-dbreporter-HEAD.tar.gz"--></font></td>
- </tr>
- <tr bgcolor="#ccccff">
- <td>CORBA services manager</td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-corbaservices-HEAD.zip">download</a> <font size="2"><!--#fsize file="iscream-corbaservices-HEAD.zip"--></font></td>
- <td><a href="/cgi-bin/download.cgi?file_name=iscream-corbaservices-HEAD.tar.gz">download</a> <font size="2"><!--#fsize file="iscream-corbaservices-HEAD.tar.gz"--></font></td>
- </tr>
-</table>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>Overview and Features</title>
- <meta name="description" content="The i-scream Project is a central monitoring system for Unix, Linux and NT servers.">
- <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, server, alert">
- <meta name="generator" content="notepad on acid, aye.">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
- <table border="0" width="500">
- <tr>
- <td>
- <font size="2" face="arial,sans-serif">
-
- <center><h3>Key Features of The System</h3></center>
-
- <ul>
- <li>A centrally stored, dynamically reloaded, system wide configuration system</li>
- <li>A totally extendable monitoring system, nothing except the Host (which
- generates the data) and the Clients (which view it) know any details about
- the data being sent, allowing data to be modified without changes to the
- server architecture.</li>
- <li>Central server and reporting tools all Java based for multi-platform portability</li>
- <li>Distribution of core server components over CORBA to allow appropriate components
- to run independently and to allow new components to be written to conform with the
- CORBA interfaces.</li>
- <li>Use of CORBA to create a hierarchical set of data entry points to the system
- allowing the system to handle event storms and remote office locations.</li>
- <li>One location for all system messages, despite being distributed.</li>
- <li>XML data protocol used to make data processing and analysing easily extendable</li>
- <li>A stateless server which can be moved and restarted at will, while Hosts,
- Clients, and reporting tools are unaffected and simply reconnect when the
- server is available again.</li>
- <li>Simple and open end protocols to allow easy extension and platform porting of Hosts
- and Clients.</li>
- <li>Self monitoring, as all data queues within the system can be monitored and raise
- alerts to warn of event storms and impending failures (should any occur).</li>
- <li>A variety of web based information displays based on Java/SQL reporting and
- PHP on-the-fly page generation to show the latest alerts and data</li>
- <li>Large overhead monitor Helpdesk style displays for latest Alerting information</li>
- </ul>
-
- <center><h3>An Overview of the i-scream Central Monitoring System</h3></center>
-
- <p align="left">
- The i-scream system monitors status and performance information
- obtained from machines feeding data into it and then displays
- this information in a variety of ways.
- </p>
-
- <p align="left">
- This data is obtained through the running of small applications
- on the reporting machines. These applications are known as
- "Hosts". The i-scream system provides a range of hosts which are
- designed to be small and lightweight in their configuration and
- operation. See the website and appropriate documentation to
- locate currently available Host applications. These hosts are
- simply told where to contact the server at which point they are
- totally autonomous. They are able to obtain configuration from
- the server, detect changes in their configuration, send data
- packets (via UDP) containing monitoring information, and send
- so called "Heartbeat" packets (via TCP) periodically to indicate
- to the server that they are still alive.
- </p>
-
- <p align="left">
- It is then fed into the i-scream server. The server then splits
- the data two ways. First it places the data in a database system,
- typically MySQL based, for later extraction and processing by the
- i-scream report generation tools. It then passes it onto to
- real-time "Clients" which handle the data as it enters the system.
- The system itself has an internal real-time client called the "Local
- Client" which has a series of Monitors running which can analyse the
- data. One of these Monitors also feeds the data off to a file
- repository, which is updated as new data comes in for each machine,
- this data is then read and displayed by the i-scream web services
- to provide a web interface to the data. The system also allows TCP
- connections by non-local clients (such as the i-scream supplied
- Conient), these applications provide a real-time view of the data
- as it flows through the system.
- </p>
-
- <p align="left">
- The final section of the system links the Local Client Monitors to
- an alerting system. These Monitors can be configured to detect
- changes in the data past threshold levels. When a threshold is
- breached an alert is raised. This alert is then escalated as the
- alert persists through four live levels, NOTICE, WARNING, CAUTION
- and CRITICAL. The alerting system keeps an eye on the level and
- when a certain level is reached, certain alerting mechanisms fire
- through whatever medium they are configured to send.
- </p>
- </font>
- </td>
- </tr>
- </table>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>Overview and Features</title>
- <meta name="description" content="The i-scream Project is a central monitoring system for Unix, Linux and NT servers.">
- <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, server, alert">
- <meta name="generator" content="notepad on acid, aye.">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
- <table border="0" width="500">
- <tr>
- <td>
- <font size="2" face="arial,sans-serif">
-
- <center><h3>Key Features of The System</h3></center>
-
- <ul>
- <li>A centrally stored, dynamically reloaded, system wide configuration system</li>
- <li>A totally extendable monitoring system, nothing except the Host (which
- generates the data) and the Clients (which view it) know any details about
- the data being sent, allowing data to be modified without changes to the
- server architecture.</li>
- <li>Central server and reporting tools all Java based for multi-platform portability</li>
- <li>Distribution of core server components over CORBA to allow appropriate components
- to run independently and to allow new components to be written to conform with the
- CORBA interfaces.</li>
- <li>Use of CORBA to create a hierarchical set of data entry points to the system
- allowing the system to handle event storms and remote office locations.</li>
- <li>One location for all system messages, despite being distributed.</li>
- <li>XML data protocol used to make data processing and analysing easily extendable</li>
- <li>A stateless server which can be moved and restarted at will, while Hosts,
- Clients, and reporting tools are unaffected and simply reconnect when the
- server is available again.</li>
- <li>Simple and open end protocols to allow easy extension and platform porting of Hosts
- and Clients.</li>
- <li>Self monitoring, as all data queues within the system can be monitored and raise
- alerts to warn of event storms and impending failures (should any occur).</li>
- <li>A variety of web based information displays based on Java/SQL reporting and
- PHP on-the-fly page generation to show the latest alerts and data</li>
- <li>Large overhead monitor Helpdesk style displays for latest Alerting information</li>
- </ul>
-
- <center><h3>An Overview of the i-scream Central Monitoring System</h3></center>
-
- <p align="left">
- The i-scream system monitors status and performance information
- obtained from machines feeding data into it and then displays
- this information in a variety of ways.
- </p>
-
- <p align="left">
- This data is obtained through the running of small applications
- on the reporting machines. These applications are known as
- "Hosts". The i-scream system provides a range of hosts which are
- designed to be small and lightweight in their configuration and
- operation. See the website and appropriate documentation to
- locate currently available Host applications. These hosts are
- simply told where to contact the server at which point they are
- totally autonomous. They are able to obtain configuration from
- the server, detect changes in their configuration, send data
- packets (via UDP) containing monitoring information, and send
- so called "Heartbeat" packets (via TCP) periodically to indicate
- to the server that they are still alive.
- </p>
-
- <p align="left">
- It is then fed into the i-scream server. The server then splits
- the data two ways. First it places the data in a database system,
- typically MySQL based, for later extraction and processing by the
- i-scream report generation tools. It then passes it onto to
- real-time "Clients" which handle the data as it enters the system.
- The system itself has an internal real-time client called the "Local
- Client" which has a series of Monitors running which can analyse the
- data. One of these Monitors also feeds the data off to a file
- repository, which is updated as new data comes in for each machine,
- this data is then read and displayed by the i-scream web services
- to provide a web interface to the data. The system also allows TCP
- connections by non-local clients (such as the i-scream supplied
- Conient), these applications provide a real-time view of the data
- as it flows through the system.
- </p>
-
- <p align="left">
- The final section of the system links the Local Client Monitors to
- an alerting system. These Monitors can be configured to detect
- changes in the data past threshold levels. When a threshold is
- breached an alert is raised. This alert is then escalated as the
- alert persists through four live levels, NOTICE, WARNING, CAUTION
- and CRITICAL. The alerting system keeps an eye on the level and
- when a certain level is reached, certain alerting mechanisms fire
- through whatever medium they are configured to send.
- </p>
- </font>
- </td>
- </tr>
- </table>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream javadoc pages</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<h2>Java Source code documentation</h2>
-
-The whole of the server, and parts of the rest of the system have been
-written in Java. Making use of the javadoc tool the following pages of
-documentation have been automatically generated.
-
-<p><a href="/javadoc/server/">Server javadoc pages</a></p>
-<p><a href="/javadoc/conient/">Conient javadoc pages</a></p>
-<p><a href="/javadoc/corbaservices/">Corba Service Manager javadoc pages</a></p>
-<p><a href="/javadoc/util/">Util Package javadoc pages</a></p>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream javadoc pages</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<h2>Java Source code documentation</h2>
-
-The whole of the server, and parts of the rest of the system have been
-written in Java. Making use of the javadoc tool the following pages of
-documentation have been automatically generated.
-
-<p><a href="/javadoc/server/">Server javadoc pages</a></p>
-<p><a href="/javadoc/conient/">Conient javadoc pages</a></p>
-<p><a href="/javadoc/corbaservices/">Corba Service Manager javadoc pages</a></p>
-<p><a href="/javadoc/util/">Util Package javadoc pages</a></p>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream meeting minutes</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2>i-scream meeting minutes</h2>
-
-<p>These are the minutes from all the meetings that took
-place during development of the project. It is not expected
-that there will be any further meetings during the continued
-development of they i-scream central monitoring system.</p>
-
-<div align="center">
- <center>
- <table border="0" width="90%">
- <tr>
- <td valign="top" width="50%">
- <h3>March 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010319.txt">19 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010312.txt">12 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010309.txt">09 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010305.txt">05 March 2001</a>
-
- <h3>February 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010226.txt">26 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010219.txt">19 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010212.txt">12 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010205.txt">05 February 2001</a><br>
-
- <h3>January 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010129.txt">29 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010122.txt">22 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010115.txt">15 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010108.txt">08 January 2001</a>
-
- <h3>December 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001211.txt">11 December 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001204.txt">04 December 2000</a></td>
- <td valign="top" width="50%">
- <h3>November 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001129b.txt">29 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001129.txt">29 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001128.txt">28 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001127.txt">27 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001122.txt">22 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001120.txt">20 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001116.txt">16 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001115.txt">15 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001113b.txt">13 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001113.txt">13 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001108.txt">08 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001106.txt">06 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001101.txt">01 November 2000</a><br>
-
- <h3>October 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001030.txt">30 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001023.txt">23 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001018.txt">18 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001017.txt">17 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001005.txt">05 October 2000</a><br>
-
- <h3>September 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20000928.txt">28 September 2000</a>
- </td>
- </tr>
- </table>
- </center>
-</div>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream meeting minutes</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2>i-scream meeting minutes</h2>
-
-<p>These are the minutes from all the meetings that took
-place during development of the project. It is not expected
-that there will be any further meetings during the continued
-development of they i-scream central monitoring system.</p>
-
-<div align="center">
- <center>
- <table border="0" width="90%">
- <tr>
- <td valign="top" width="50%">
- <h3>March 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010319.txt">19 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010312.txt">12 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010309.txt">09 March 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010305.txt">05 March 2001</a>
-
- <h3>February 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010226.txt">26 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010219.txt">19 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010212.txt">12 February 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010205.txt">05 February 2001</a><br>
-
- <h3>January 2001</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010129.txt">29 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010122.txt">22 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010115.txt">15 January 2001</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20010108.txt">08 January 2001</a>
-
- <h3>December 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001211.txt">11 December 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001204.txt">04 December 2000</a></td>
- <td valign="top" width="50%">
- <h3>November 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001129b.txt">29 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001129.txt">29 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001128.txt">28 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001127.txt">27 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001122.txt">22 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001120.txt">20 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001116.txt">16 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001115.txt">15 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001113b.txt">13 November 2000 (Sub meeting)</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001113.txt">13 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001108.txt">08 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001106.txt">06 November 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001101.txt">01 November 2000</a><br>
-
- <h3>October 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001030.txt">30 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001023.txt">23 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001018.txt">18 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001017.txt">17 October 2000</a><br>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20001005.txt">05 October 2000</a><br>
-
- <h3>September 2000</h3>
- <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20000928.txt">28 September 2000</a>
- </td>
- </tr>
- </table>
- </center>
-</div>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream TODO list</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2><font face="Arial">(old) i-scream central monitoring system TODO list</font></h2>
-
-<font face="Arial" size="2">This is the TODO list to be achieved by the end of the "project" period.
-A
-<a href="/todo.shtml">newer TODO list</a> now exists to cover the future things
-we plan to do with the development of the i-scream central monitoring system.</font><h3>
-<font face="Arial">Server</font></h3>
-<pre>LocalClient Monitors: Users.
-
-Completed:
-----------
-22/03/2001 - FIX the major memory leak and deadlock issues.
- LocalClient Monitors: Load, Processes, Queues.
-18/03/2001 - LocalClient Monitors: Disks/Memory need MB threshold
-15/03/2001 - Alert dumping needs to be organised better.
- Running on Windows InetAddress.getHostName() doesn't return the FQDN.
-13/03/2001 - Thread naming, at least at a "what class it is" level.
- Utilise the ConfigurationProxy throughout the server.
- Sort out GC & Configuration objects (and CorbaHandlers).
-09/03/2001 - WebFeeder needs to dump Alerts to disk.
-08/03/2001 - WebFeeder needs to dump XML to disk
- LocalClient Monitors: Disks, Service Checks
-07/03/2001 - Service Checks: FTP, POP3, IMAP, SSH, Telnet
-01/03/2001 - Make it easy to change flags to the java compiler.
- Configuration groups need implementing.
-28/02/2001 - Queue identification ? Use a hash of the Queue ?
- Fix the Queue "unlimited" size problem.
-27/02/2001 - (not needed) ClientInterface/DBInterface need to "pull" data ?
- Builds on the website ?
- Change build scripts to make iscream-server.java/tar.gz/zip
-25/02/2001 - Move checking of logging verbosity to the servant.
-23/02/2001 - print verbosity level with logging messages
- functionality added to the LoggerServant
-23/02/2001 - Startup of components - eg. running DBInterface on another machine.
- Now catches any problems relating to not finding a component if
- a component has a dependancy. The component manager will then
- retry it after a given timeout.
-12/02/2001 - Logging of Queue.status() somehow.
-06/02/2001 - Make use of the PrintWriter "autoflush" feature :)
-28/01/2001 - Add dependency checking for the DOCOPY Makefile target.
- Client Interface needs more functionality.
- SQL Driver doesn't work in Windows.
-18/01/2001 - Heartbeats are still dropped.
- CVS directories get added to build tar/zip file.
- Problem on FreeBSD with zip file adding more files than it should.
- Remove Component from util package -> ComponentManager.
- Remove ReferenceManager from util package -> ComponentManager.
- Add status methods to the Queue that return just values.
- Clean up the util package, it shouldn't do logging etc.
- -- done with the exception of ReferenceManager.
-16/01/2001 - Build a util package JAR file seperately.
-14/01/2001 - Javadoc pages on website ?
- -- done for the server at least.
-12/01/2001 - Investigate the use of a Queue in the Filter, to replace the
- current FilterThread setup.
-07/01/2001 - Makefile needs to copy non-java files to JAR (eg. images).
-02/01/2001 - Add making of Javadoc pages to make scripts.
- Queuing system in the root filter.
-</pre>
-
-<h3><font face="Arial">Conient</font></h3>
-<pre>Completed:
-----------
-18/03/2001 - Switch to using the StringUtil class for the firewall command stuff.
- Fix bug where it can take up to two packets to display
- correct information. This is most visible in service
- checks, but can also be seen on disk, memory and anything
- else that uses two data items from the packet for one
- component.
-01/03/2001 - re-work host display and choosing mechanism (ie, make us 1.1 protocol)
-26/02/2001 - Rework system displaying of components for Swing Event Handling
- Allow config to be written back to a local file
- Allow local file config to be changed via the GUI
-05/02/2001 - allow disk components to alter their units
- have some icons and the i-scream logo on display
- show errors in windows rather than on the console
- Fix error in packet stopping update of ALL hosts
-04/02/2001 - Write LOADS more data components
-03/02/2001 - Allow config to be obtained from the server
-30/01/2001 - Add option to handle firewalls
-29/01/2001 - Allow config to be obtained from a local file
- Fix problem with memory display showing negative values at start
- Ensure all Swing updates use the Swing Event Handling thread (partial - only data components)
-28/01/2001 - Tidy up network comms and link handling
-</pre>
-
-<h3><font face="Arial">statgrab</font></h3>
-<pre>Completed:
-----------
-20/03/2001 - Linux - CPU %'s not always right, 2 repititions ?
-19/03/2001 - Odd behaviour with more than 1000 processes, on Solaris at least
- FreeBSD - grabbing memory total
-11/03/2001 - Solaris - If free memory changes to < 10Mb (?) it changes to K rather than M (thus not matched)
-</pre>
-
-<h3><font face="Arial">C++ Host</font></h3>
-<pre>UDP Packet size to 8Kb
-Porting to Linux/FreeBSD (Windows?)
-</pre>
-
-<h3><font face="Arial">Winhost</font></h3>
-<pre>Completed:
-----------
-19/03/2001 - Still needs to send the true uptime.
- Processor ID should be packet.os.platform
- Minor version joined with packet.os.version
- Logo ? Pink icon ?
- Solve OCX problem
-</pre>
-
-<h3><font face="Arial">ihost</font></h3>
-<pre>Completed:
-----------
-12/03/2001 - Produce a very quick "check script" which can be run by cron.
-</pre>
-
-<h3><font face="Arial">Web Reports</font></h3>
-<pre>Completed:
-----------
-22/03/2001 - Alert/System Summary Page (incl. helpdesk style)
-15/03/2001 - Individual Host Alert Summary Page(s)
-14/03/2001 - Individual Host Lastest Data Page(s) (including service checks)
-</pre>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>The i-scream Project Problem Domain</title>
- <meta name="description" content="The i-scream Project is a central monitoring system for Unix, Linux and NT servers.">
- <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, server, alert">
- <meta name="generator" content="notepad on acid, aye.">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
- <table border="0" width="500">
- <tr>
- <td>
- <font size="2" face="arial,sans-serif">
-
- <center><h3>Original Problem</h3></center>
-
- <p align="justify">
- This is the original specification given to us when we
- started the project. The i-scream central monitoring
- system meets this specification, and aims to extend it
- further. This is, however, where it all began.
- </p>
-
- <center><h3>Centralised Machine Monitoring</h3></center>
-
- <p align="justify">
- The Computer Science department has a number of different machines
- running a variety of different operating systems. One of the tasks
- of the systems administrators is to make sure that the machines
- don't run out of resources. This involves watching processor loads,
- available disk space, swap space, etc.
- </p>
-
- <p align="justify">
- It isn't practicle to monitor a large number of machines by logging
- on and running commands such as 'uptime' on the unix machines, or
- by using performance monitor for NT servers. Thus this project is
- to write monitoring software for each platform supported which
- reports resource usage back to one centralized location. System
- Administrators would then be able to monitor all machines from this
- centralised location.
- </p>
-
- <p align="justify">
- Once this basic functionality is implemented it could usefully be
- expanded to include logging of resource usage to identify longterm
- trends/problems, alerter services which can directly contact
- sysadmins (or even the general public) to bring attention to problem
- areas. Ideally it should be possible to run multiple instances of
- the reporting tool (with all instances being updated in realtime)
- and to to be able to run the reporting tool as both as stand alone
- application and embeded in a web page.
- </p>
-
- <p align="justify">
- This project will require you to write code for the unix and Win32
- APIs using C and knowledge of how the underlying operating systems
- manage resources. It will also require some network/distributed
- systems code and a GUI front end for the reporting tool. It is
- important for students undertaking this project to understand the
- importance of writing efficient and small code as the end product
- will really be most useful when machines start run out of processing
- power/memory/disk.
- </p>
-
- <p align="justify">
- John Cinnamond (email jc) whose idea this is, will provide technical
- support for the project.
- </p>
-
- </font>
- </td>
- </tr>
- </table>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream project papers & documentation</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2>i-scream project papers & documentation</h2>
-
-<p>These are documents created during the development of the project.
-Many of them are now out of date, and have been superceeded by the
-official documentation. Please select the documentation link on the
-left to find the official documentation.</p>
-
-<div align="center">
- <center>
- <table border="0" width="90%">
- <tr>
- <td valign="top">
- <a href="/cgi-bin/docs.cgi?doc=plan/feature_list.txt">
- Feature List</a> - the ongoing list of features<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/time_allocation.txt">
- Time Allocation Plan</a> - the course required us to produce a plan
- of what we were going to spend time on<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/implementation-phases.txt">
- Implementation Phases</a> - an initial plan of how we were going to
- proceed with development<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/doc_strategy.txt">
- Documentation Strategy</a> - documentation plan with status of each document<br>
- <br>
- <a href="/cgi-bin/docs.cgi?doc=specification/spec-realtime.txt">
- Realtime Spec Outline</a> - an idea of how some parts of the system worked<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/doc_spec.txt">
- Document Specs</a> - requirements and specification for all documentation<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/xml_via_udp.txt">
- XMLviaUDP Specs</a> - format of data to be sent from hosts over UDP<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/configuration.txt">
- System Configuration</a> - details of the initial configuration system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/coding_standards.txt">
- Coding Standards</a> - standards for Java code<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/expected_data.txt">
- Host: expected data</a> - data the host is expected to send<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/logging.txt">
- Logging System</a> - details of the logging system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/using_queue.txt">
- Using the Queue</a> - details of the queueing system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/protocols.txt">
- Protocol Specs</a> - specifications of all the protocols used<br>
- <br>
- <a href="/cgi-bin/docs.cgi?doc=papers/corba.txt">
- Using CORBA</a> - how to run the server in the corba environment<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/cvs-1.txt">
- Using CVS (part 1)</a> - how to use CVS (basic)<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/cvs-2.txt">
- Using CVS (part 2)</a> - how to use CVS (advanced)<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/wbem.txt">
- WBEM, CIM?</a> - some ideas about the WBEM technologies<br>
- </td>
- </tr>
- </table>
- </center>
-</div>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream project papers & documentation</title>
-</head>
-
-<basefont face="arial,sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2>i-scream project papers & documentation</h2>
-
-<p>These are documents created during the development of the project.
-Many of them are now out of date, and have been superceeded by the
-official documentation. Please select the documentation link on the
-left to find the official documentation.</p>
-
-<div align="center">
- <center>
- <table border="0" width="90%">
- <tr>
- <td valign="top">
- <a href="/cgi-bin/docs.cgi?doc=plan/feature_list.txt">
- Feature List</a> - the ongoing list of features<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/time_allocation.txt">
- Time Allocation Plan</a> - the course required us to produce a plan
- of what we were going to spend time on<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/implementation-phases.txt">
- Implementation Phases</a> - an initial plan of how we were going to
- proceed with development<br>
- <a href="/cgi-bin/docs.cgi?doc=plan/doc_strategy.txt">
- Documentation Strategy</a> - documentation plan with status of each document<br>
- <br>
- <a href="/cgi-bin/docs.cgi?doc=specification/spec-realtime.txt">
- Realtime Spec Outline</a> - an idea of how some parts of the system worked<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/doc_spec.txt">
- Document Specs</a> - requirements and specification for all documentation<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/xml_via_udp.txt">
- XMLviaUDP Specs</a> - format of data to be sent from hosts over UDP<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/configuration.txt">
- System Configuration</a> - details of the initial configuration system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/coding_standards.txt">
- Coding Standards</a> - standards for Java code<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/expected_data.txt">
- Host: expected data</a> - data the host is expected to send<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/logging.txt">
- Logging System</a> - details of the logging system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/using_queue.txt">
- Using the Queue</a> - details of the queueing system<br>
- <a href="/cgi-bin/docs.cgi?doc=specification/protocols.txt">
- Protocol Specs</a> - specifications of all the protocols used<br>
- <br>
- <a href="/cgi-bin/docs.cgi?doc=papers/corba.txt">
- Using CORBA</a> - how to run the server in the corba environment<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/cvs-1.txt">
- Using CVS (part 1)</a> - how to use CVS (basic)<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/cvs-2.txt">
- Using CVS (part 2)</a> - how to use CVS (advanced)<br>
- <a href="/cgi-bin/docs.cgi?doc=papers/wbem.txt">
- WBEM, CIM?</a> - some ideas about the WBEM technologies<br>
- </td>
- </tr>
- </table>
- </center>
-</div>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-<head>
- <title>Memorable Project Quotes</title>
- <!-- do not meta tag this page -->
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td align="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-
-<h3>Memorable Project Quotes</h3>
-
-<p>
-These are all genuine quotes that came about during our time
-developing the i-scream server, hosts, clients and reporting
-system.
-</p>
-
-<p>
-<b>AJ doc'ing and taking the i-scream pun too far</b>
- <blockquote>
- <i>"An i-scream client connects to the i-scream and ...."</i>
- </blockquote>
-<p>
-
-<p>
-<b>AJ</b>
- <blockquote>
- <i>"I'm gonna be raptor! grr!"</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"I'm not going to draw on the board with some fizzy jerks."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"It's just programming, innit?"</i>
- </blockquote>
-<p>
-
-<p>
-<b>Paul</b>
- <blockquote>
- <i>"Let's sell one sock... Quality."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"Break my hand... arghhh."</i>
- </blockquote>
-<p>
-
-<p>
-<b>AJ</b>
- <blockquote>
- <i>"But we haven't got any children yet..."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"Do you like my gender?"</i>
- </blockquote>
-<p>
-
-<p>
-<b>Paul</b>
- <blockquote>
- <i>"Do away with the vowels, damnit. Oh, it's got a 'u' in it, hasn't it..."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"Long is, in fact, long long."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Paul</b>
- <blockquote>
- <i>"And the fish do their little funky shit."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Tim</b>
- <blockquote>
- <i>"Bloody hell, what are your feet doing over here?!"</i>
- </blockquote>
-<p>
-
-<p>
-<b>Paul</b>
- <blockquote>
- <i>"There's an 'L' in XML, isn't there?"</i>
- </blockquote>
-<p>
-
-<p>
-<b>AJ</b>
- <blockquote>
- <i>"Yeah, we're not paying anything for it, either... we just pay them once a month."</i>
- </blockquote>
-<p>
-
-<p>
-<b>Ash</b>
- <blockquote>
- <i>"Do you want some tissues now?"</i>
- </blockquote>
-<p>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- index.shtml
- Created by pjm2 25/05/2001
- Last edited 25/05/2001
--->
-
-<html>
-
-<head>
- <title>i-scream screenshots / overview</title>
- <meta name="description" content="The i-scream central monitoring system runs distributed on Unix, Linux and Windows NT/2000 servers.">
- <meta name="keywords" content="i-scream, screenshots, distributed, central, monitoring, system, project, unix, linux, nt, 2000, server, alert, email, winhost, ihost, conient">
- <meta name="generator" content="Microsoft FrontPage 4.0">
-</head>
-
-<basefont face="arial, sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000000">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-<font size="2">
-
-
-
-
-<div align="center">
- <center>
- <table border="0" cellspacing="10" width="500" cellpadding="0">
- <tr>
- <td valign="top" colspan="2">
- <h1 align="center"><font face="Arial" color="#000066">i-scream
- screenshots</font></h1>
- <h3 align="center"><font face="Arial" color="#000066">(or the two minute
- tour)</font></h3>
- </center>
- <p><font size="2" face="Arial">This page provides a sequence of
- screenshots to help you to gain a better understanding of the i-scream
- distributed central monitoring system and how it may be applied in
- networked environments. Click on the thumbnails to view the full
- size screenshots.</font></p>
- <p> </td>
- </tr>
- <center>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-main.gif"><img border="0" src="thumbnail-reports-main.gif" alt="click to enlarge!" width="100" height="77"></a></font>
- <p> </td>
- <td valign="top"><font color="#000066"><font face="Arial"><b>Reports Centre</b></font><b><font face="Arial">
- (Web)</font></b></font><font size="2" face="Arial"><br>
- The i-scream reports centre provides a central access point to all
- web-based reports that are provided by the i-scream system. Reports
- are available to display information about the current status of an
- individual machine and any alerts pertaining to either an individual
- machine, or a summary of alerts for all machines. Historical
- information about monitored machines may also be accessed from this point.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-latest-misc.gif"><img border="0" src="thumbnail-reports-raptor-latest-misc.gif" alt="click to enlarge!" width="100" height="104"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Latest Information
- (Web)</font></b><font size="2" face="Arial"><br>
- Here we are viewing the latest information provided by a host. Bars
- are used to represent values such as disk space and free memory as this
- makes it easier to spot casual problems. The small graph icons link
- to historical reports of each field for the previous day. The choice
- of fields to display on this page is stored in a separate configuration
- file.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-main.gif"><img border="0" src="thumbnail-conient-main.gif" alt="click to enlarge!" width="100" height="110"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial"><font color="#000066">Conient (Multiplatform
- real-time client)</font><br>
- </font></b><font size="2" face="Arial">Conient is a real-time client that
- can hook into an i-scream server to allow the user to view host
- information as it passes through the server. The client displays
- information provided by the hosts as well as the results of service checks
- performed by the server on each host (eg FTP, Telnet, etc). Conient
- is written in Java and can thus be run on most operating systems.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-platform-info.gif"><img border="0" src="thumbnail-conient-platform-info.gif" alt="click to enlarge!" width="100" height="59"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient (Viewing
- extra data)</font></b><font size="2" face="Arial"><br>
- Less important host information may be viewed in a seperate window to
- avoid clutter in Conient's display. Details of the protocol for
- host-to-server communications are freely available to developers.
- The protocol itself is extensible and client programs such as Conient
- display even unrecognised data from modified host programs.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-config.gif"><img border="0" src="thumbnail-conient-config.gif" alt="click to enlarge!" width="100" height="48"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient
- (Configuration)</font></b><font size="2" face="Arial"><br>
- Conient is fully configurable from within the program itself.
- Multiple configurations may be saved. Conient can also be configured
- to connect to a server through a firewall via an SSH tunnel or suchlike.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="ihost-main.gif"><img border="0" src="thumbnail-ihost-main.gif" alt="click to enlarge!" width="100" height="51"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">ihost (Unix/Linux
- host)</font></b><font size="2" face="Arial"><br>
- The ihost is currently the main Unix/Linux/FreeBSD host application for
- i-scream. ihost is centrally configured by the server it connects to
- and periodically sends information about the machine on which it is
- running. The ihost is written in Perl, so can be easily altered to
- send extra information to your i-scream server.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="winhost-main.gif"><img border="0" src="thumbnail-winhost-main.gif" alt="click to enlarge!" width="100" height="62"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">WinHost (Windows
- host)</font></b><font size="2" face="Arial"><br>
- The WinHost is similar in concept to the ihost, however, this one runs on
- Windows NT/2000 servers. Again, the configuration is dynamically
- obtained from the server. The WinHost is typically only present in
- the Windows system tray. Double clicking on the system tray icon
- will bring up a small window that allows data to be viewed and to force
- reconfiguration with the server.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="alerter-email.gif"><img border="0" src="thumbnail-alerter-email.gif" alt="click to enlarge!" width="100" height="74"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Email)</font></b><font size="2" face="Arial"><br>
- The i-scream server includes many alerting mechanisms. Simple email
- alerts may be sent out if desired. Alert levels and frequencies may
- be configured for the server. This screenshot shows the format of a
- typical alert; the contents of which are of course configurable.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="alerter-irc.gif"><img border="0" src="thumbnail-alerter-irc.gif" alt="click to enlarge!" width="100" height="95"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (IRC bot)</font></b><font size="2" face="Arial"><br>
- Another i-scream alerter comes in the form of an interactive IRC bot.
- This may reside in an IRC (Internet relay chat) channel and broadcasts
- alerts if told to do so. This screenshot shows a typical interaction
- with a user in the "Bersirc" IRC client.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-alerts-all.gif"><img border="0" src="thumbnail-reports-alerts-all.gif" alt="click to enlarge!" width="100" height="96"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Web page)</font></b><font size="2" face="Arial"><br>
- Individual alerts and a summary of all alerts raised by the i-scream
- server may be viewed on the alerts web pages. These show the
- different levels of alerts in configurable colours and provides specific
- details about the alerts being raised for each machine.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-public-autoscroll.gif"><img border="0" src="thumbnail-reports-public-autoscroll.gif" alt="click to enlarge!" width="100" height="78"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Public
- helpdesk display)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The reports centre also provides a
- page that may be useful in configuring non-interactive public displays of
- alerts. These displays automatically refresh the page periodically
- and supported web browsers may also automatically scroll the page to allow
- a large font to be employed for easier reading from a distance.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-queues.gif"><img border="0" src="thumbnail-conient-queues.gif" alt="click to enlarge!" width="100" height="159"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient (Server queue
- monitoring)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The Conient client may also be used
- to monitor information about the i-scream server itself. Here we are
- viewing the status of the internal queues within the server. This
- shows that the server is performing healthily and that there are no
- bottlenecks. </font></td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-load15.gif"><img border="0" src="thumbnail-reports-raptor-load15.gif" alt="click to enlarge!" width="100" height="107"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Historical reports
- (Web)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">Historical information is collated
- by the i-scream server into (typically) a MySQL database. A separate
- program is used to produce the historical web reports These may be browsed
- via this web-based interface (see screenshot). The reports to be
- generated for each machine and the size of the page are of course
- configurable.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-users.gif"><img border="0" src="thumbnail-reports-raptor-users.gif" alt="click to enlarge!" width="100" height="96"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Historical reports
- (Metadata)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The historical report generation
- also produces a number of other files that may be useful for third party
- analysis tools. The chart itself is written as a GIF image, as well
- as a small file suitable for including on PHP pages that specifies the
- minimum and maximum values during the 24 hour period. A file
- containing the raw plot data is also produced to enable the use of third
- party on-the-fly plotting tools.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="server-main.gif"><img border="0" src="thumbnail-server-main.gif" alt="click to enlarge!" width="100" height="100"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">The i-scream server</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The server is distributed and may
- therefore have multiple points of data entry and run on more than one
- machine. This helps to reduce the amount of host traffic over large
- networks and reduces potential bottlenecks. The server is written in
- Java to allow it to run on most operating systems. This exciting
- screenshot shows the i-scream server running ;-)</font>
- <p> </td>
- </tr>
- </table>
- </center>
-</div>
-
-
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- index.shtml
- Created by pjm2 25/05/2001
- Last edited 25/05/2001
--->
-
-<html>
-
-<head>
- <title>i-scream screenshots / overview</title>
- <meta name="description" content="The i-scream central monitoring system runs distributed on Unix, Linux and Windows NT/2000 servers.">
- <meta name="keywords" content="i-scream, screenshots, distributed, central, monitoring, system, project, unix, linux, nt, 2000, server, alert, email, winhost, ihost, conient">
- <meta name="generator" content="Microsoft FrontPage 4.0">
-</head>
-
-<basefont face="arial, sans-serif" size="2">
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000000">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-<font size="2">
-
-
-
-
-<div align="center">
- <center>
- <table border="0" cellspacing="10" width="500" cellpadding="0">
- <tr>
- <td valign="top" colspan="2">
- <h1 align="center"><font face="Arial" color="#000066">i-scream
- screenshots</font></h1>
- <h3 align="center"><font face="Arial" color="#000066">(or the two minute
- tour)</font></h3>
- </center>
- <p><font size="2" face="Arial">This page provides a sequence of
- screenshots to help you to gain a better understanding of the i-scream
- distributed central monitoring system and how it may be applied in
- networked environments. Click on the thumbnails to view the full
- size screenshots.</font></p>
- <p> </td>
- </tr>
- <center>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-main.gif"><img border="0" src="thumbnail-reports-main.gif" alt="click to enlarge!" width="100" height="77"></a></font>
- <p> </td>
- <td valign="top"><font color="#000066"><font face="Arial"><b>Reports Centre</b></font><b><font face="Arial">
- (Web)</font></b></font><font size="2" face="Arial"><br>
- The i-scream reports centre provides a central access point to all
- web-based reports that are provided by the i-scream system. Reports
- are available to display information about the current status of an
- individual machine and any alerts pertaining to either an individual
- machine, or a summary of alerts for all machines. Historical
- information about monitored machines may also be accessed from this point.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-latest-misc.gif"><img border="0" src="thumbnail-reports-raptor-latest-misc.gif" alt="click to enlarge!" width="100" height="104"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Latest Information
- (Web)</font></b><font size="2" face="Arial"><br>
- Here we are viewing the latest information provided by a host. Bars
- are used to represent values such as disk space and free memory as this
- makes it easier to spot casual problems. The small graph icons link
- to historical reports of each field for the previous day. The choice
- of fields to display on this page is stored in a separate configuration
- file.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-main.gif"><img border="0" src="thumbnail-conient-main.gif" alt="click to enlarge!" width="100" height="110"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial"><font color="#000066">Conient (Multiplatform
- real-time client)</font><br>
- </font></b><font size="2" face="Arial">Conient is a real-time client that
- can hook into an i-scream server to allow the user to view host
- information as it passes through the server. The client displays
- information provided by the hosts as well as the results of service checks
- performed by the server on each host (eg FTP, Telnet, etc). Conient
- is written in Java and can thus be run on most operating systems.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-platform-info.gif"><img border="0" src="thumbnail-conient-platform-info.gif" alt="click to enlarge!" width="100" height="59"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient (Viewing
- extra data)</font></b><font size="2" face="Arial"><br>
- Less important host information may be viewed in a seperate window to
- avoid clutter in Conient's display. Details of the protocol for
- host-to-server communications are freely available to developers.
- The protocol itself is extensible and client programs such as Conient
- display even unrecognised data from modified host programs.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-config.gif"><img border="0" src="thumbnail-conient-config.gif" alt="click to enlarge!" width="100" height="48"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient
- (Configuration)</font></b><font size="2" face="Arial"><br>
- Conient is fully configurable from within the program itself.
- Multiple configurations may be saved. Conient can also be configured
- to connect to a server through a firewall via an SSH tunnel or suchlike.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="ihost-main.gif"><img border="0" src="thumbnail-ihost-main.gif" alt="click to enlarge!" width="100" height="51"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">ihost (Unix/Linux
- host)</font></b><font size="2" face="Arial"><br>
- The ihost is currently the main Unix/Linux/FreeBSD host application for
- i-scream. ihost is centrally configured by the server it connects to
- and periodically sends information about the machine on which it is
- running. The ihost is written in Perl, so can be easily altered to
- send extra information to your i-scream server.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="winhost-main.gif"><img border="0" src="thumbnail-winhost-main.gif" alt="click to enlarge!" width="100" height="62"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">WinHost (Windows
- host)</font></b><font size="2" face="Arial"><br>
- The WinHost is similar in concept to the ihost, however, this one runs on
- Windows NT/2000 servers. Again, the configuration is dynamically
- obtained from the server. The WinHost is typically only present in
- the Windows system tray. Double clicking on the system tray icon
- will bring up a small window that allows data to be viewed and to force
- reconfiguration with the server.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="alerter-email.gif"><img border="0" src="thumbnail-alerter-email.gif" alt="click to enlarge!" width="100" height="74"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Email)</font></b><font size="2" face="Arial"><br>
- The i-scream server includes many alerting mechanisms. Simple email
- alerts may be sent out if desired. Alert levels and frequencies may
- be configured for the server. This screenshot shows the format of a
- typical alert; the contents of which are of course configurable.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="alerter-irc.gif"><img border="0" src="thumbnail-alerter-irc.gif" alt="click to enlarge!" width="100" height="95"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (IRC bot)</font></b><font size="2" face="Arial"><br>
- Another i-scream alerter comes in the form of an interactive IRC bot.
- This may reside in an IRC (Internet relay chat) channel and broadcasts
- alerts if told to do so. This screenshot shows a typical interaction
- with a user in the "Bersirc" IRC client.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-alerts-all.gif"><img border="0" src="thumbnail-reports-alerts-all.gif" alt="click to enlarge!" width="100" height="96"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Web page)</font></b><font size="2" face="Arial"><br>
- Individual alerts and a summary of all alerts raised by the i-scream
- server may be viewed on the alerts web pages. These show the
- different levels of alerts in configurable colours and provides specific
- details about the alerts being raised for each machine.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-public-autoscroll.gif"><img border="0" src="thumbnail-reports-public-autoscroll.gif" alt="click to enlarge!" width="100" height="78"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Alerts (Public
- helpdesk display)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The reports centre also provides a
- page that may be useful in configuring non-interactive public displays of
- alerts. These displays automatically refresh the page periodically
- and supported web browsers may also automatically scroll the page to allow
- a large font to be employed for easier reading from a distance.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="conient-queues.gif"><img border="0" src="thumbnail-conient-queues.gif" alt="click to enlarge!" width="100" height="159"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Conient (Server queue
- monitoring)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The Conient client may also be used
- to monitor information about the i-scream server itself. Here we are
- viewing the status of the internal queues within the server. This
- shows that the server is performing healthily and that there are no
- bottlenecks. </font></td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-load15.gif"><img border="0" src="thumbnail-reports-raptor-load15.gif" alt="click to enlarge!" width="100" height="107"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Historical reports
- (Web)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">Historical information is collated
- by the i-scream server into (typically) a MySQL database. A separate
- program is used to produce the historical web reports These may be browsed
- via this web-based interface (see screenshot). The reports to be
- generated for each machine and the size of the page are of course
- configurable.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="reports-raptor-users.gif"><img border="0" src="thumbnail-reports-raptor-users.gif" alt="click to enlarge!" width="100" height="96"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">Historical reports
- (Metadata)</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The historical report generation
- also produces a number of other files that may be useful for third party
- analysis tools. The chart itself is written as a GIF image, as well
- as a small file suitable for including on PHP pages that specifies the
- minimum and maximum values during the 24 hour period. A file
- containing the raw plot data is also produced to enable the use of third
- party on-the-fly plotting tools.</font>
- <p> </td>
- </tr>
- <tr>
- <td valign="top" width="100"><font size="2" face="Arial"><a href="server-main.gif"><img border="0" src="thumbnail-server-main.gif" alt="click to enlarge!" width="100" height="100"></a></font>
- <p> </td>
- <td valign="top"><b><font face="Arial" color="#000066">The i-scream server</font><font size="2" face="Arial"><br>
- </font></b><font size="2" face="Arial">The server is distributed and may
- therefore have multiple points of data entry and run on more than one
- machine. This helps to reduce the amount of host traffic over large
- networks and reduces potential bottlenecks. The server is written in
- Java to allow it to run on most operating systems. This exciting
- screenshot shows the i-scream server running ;-)</font>
- <p> </td>
- </tr>
- </table>
- </center>
-</div>
-
-
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream TODO list</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2><font face="Arial">i-scream central monitoring system TODO list</font></h2>
-
-<p><font face="Arial" size="2">This page lists the things we plan to do with the
-i-scream central monitoring system in the future.</font></p>
-
-<p><font face="Arial" size="2">TODO:
-<ul>
- <li>monitoring of users logging in & out</li>
- <li>web-based configuration system</li>
- <li>cleaner separation of some of the CORE functions (such as configuration
- and logging) as independent services</li>
- <li>grouping of hosts in frontends using server config groups</li>
- <li>security of filters - ACL's</li>
-</ul></font>
-
-<p><font face="Arial" size="2">To view the older TODO list from the project
-please click <a href="oldtodo.shtml">here</a>.</font></p>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>i-scream cvs repository</title>
- <meta name="description" content="A list of those who helped to develop the i-scream central monitoring system.">
- <meta name="keywords" content="i-scream, project, credits, central,monitoring,system, unix, linux, nt, server, alert, acknowledgements">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<font face="Arial" size="2">
-<h2>i-scream CVS Repository</h2>
-
-<p>The i-scream CVS Repository contains all code,
-documentation, and other files pertaining to all i-scream projects.</p>
-
-<p>All code available in the CVS Repository is <a href="/license.shtml">
-licensed</a> under the GPL.</p>
-
-<h3>Web Access</h3>
-
-<p>We use <a href="http://viewcvs.sourceforge.net/">viewcvs</a> to provide a
-visual frontend to the CVS Repository. It allows you to browse around the
-repository, viewing any version of a file, and the differences between different
-versions. There is also a link to download the latest version of any section.</p>
-
-<p><a href="http://cvs.i-scream.org/">http://cvs.i-scream.org/</a></p>
-
-<p>We also have a facility to allow people to keep tabs on what's changed
-recently. The following are available:</p>
-
-<p>Commits today: <a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today</a><br>
-Commits this week: <a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek</a><br>
-Commits in the past 7 days: <a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7</a><br>
-Commits made since 29/03/2001: <a href="http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29</a></p>
-
-<h3>Anonymous CVS Access (read-only)</h3>
-
-<p>Anyone can access the i-scream CVS repository in
-anonymous mode read-only mode. The following commands will allow you to check
-out a portion of the CVS repository. To see what is available it is recommended
-that you first look at the web frontend.</p>
-</font>
-
-<pre>cvs -d :pserver:anonymous@cvs.i-scream.org:/cvs/i-scream login
-cvs -d :pserver:anonymous@cvs.i-scream.org:/cvs/i-scream checkout [module]</pre>
-
-<font face="Arial" size="2">
-<p>When asked for a password, simply press enter.
-Replace [module] with the section you wish to checkout.</p>
-
-<h3>Developer CVS Access (write)</h3>
-
-<p>The i-scream development team have full write
-access to the CVS repository. This is only available over SSH, and can be done
-on most clients. First the following environment variables need to be set.</p>
-</font>
-
-<pre>CVS_RSH = ssh
-CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream</pre>
-
-<font face="Arial" size="2">
-<p>You should know your username and password
-already. After setting these you will need to enter your password each time you
-use a CVS command. Obviously this is a time wasting event, so an RSA key can be
-generated and placed on the server for you. Please view the relevant ssh
-manpages on how to generate an RSA key pair.</p>
-
-<p>After this you will be able to work with CVS as
-normal.</p>
-
-<h3>Other means of accessing CVS</h3>
-
-<p>We currently provide <a href="http://www.polstra.com/projects/freeware/CVSup/"> CVSup</a> access to the repository, either for mirroring or
-for maintaining an up-to-date local copy. You will probably want to create a
-supfile that looks something like this;</p>
-</font>
-
-<pre>*default host=cvsup.i-scream.org
-*default base=/home/user/sup
-*default prefix=/home/user/i-scream
-*default release=cvs
-*default delete use-rel-suffix
-*default compress
-i-scream.cms.source tag=.</pre>
-
-<font face="Arial" size="2">
-<p>The last item in that list is the collection you which to get. The collection
-"i-scream" is simply the whole repository, and is best used with no
-tag specified for mirroring. It is most likely that you will want to do that
-given above, which gets the latest copy of the i-scream source code.</p>
-
-<h3>CVS Statistics</h3>
-
-<p>There are some statistics available on the cms module of the CVS
-repository, generated by <a href="http://cvsplot.sourceforge.net/">cvsplot</a>,
-that allow you to see the progress of development. They're not that exciting,
-but do show when the work was done.</p>
-
-<p><a href="http://www.i-scream.org/cvsplot">http://www.i-scream.org/cvsplot</a></p>
-
-</font>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>The i-scream Project</title>
- <meta name="description" content="The i-scream Project is a central monitoring system for Solaris, Linux, FreeBSD and Windows servers.">
- <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, solaris, server, freebsd, alert">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-<!--#include virtual="welcome.inc" -->
-
-<!--#include virtual="contents.inc" -->
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream libstatgrab homepage</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="../left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="../title.inc" -->
-
-<font size="2" face="arial,sans-serif">
-
-<h1>libstatgrab</h1>
-
-<ul>
-<li><a href="#news">News</a></li>
-<li><a href="#what">What is libstatgrab?</a></li>
-<li><a href="#download">Downloading</a></li>
-<li><a href="#documentation">Documentation</a></li>
-<li><a href="#screenshot">Screenshot</a></li>
-</ul>
-
-<a name="news"><h2>News</h2></a>
-
-<p>
-To get notifications of new libstatgrab releases why not subscribe
-to our project over on <a href="http://freshmeat.net/projects/libstatgrab/">
-freshmeat</a>?
-</p>
-
-<p>
-<b>Wednesday 10 March 2004</b><br><br>
-Version 0.9 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.9.tar.gz">here</a>.
-This release brings new features and new platforms. We've added
-information about network interfaces (duplex, speed, etc) along
-with further statistics such as i/o packets, i/o errors, and
-collisions. Support has also been added for OpenBSD and DragonFly
-BSD. Finally some work has been done to reduce the platforms on
-which libstatgrab needs elevated privileges. See the NEWS file for
-more information.
-</p>
-
-<p>
-<b>Wednesday 11 February 2004</b><br><br>
-Version 0.8.2 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.8.2.tar.gz">here</a>.
-The main focus of this release is adding support for Solaris 6.
-We've also added python bindings so you can use libstatgrab directly
-from python (see the extras directory). Finally, we've tidied up a
-few bits of the code.
-</p>
-
-<p>
-<b>Wednesday 21 January 2004</b><br><br>
-Version 0.8.1 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.8.1.tar.gz">here</a>.
-This release primarily fixes bugs. On Linux a file descriptor leak was
-fixed. On Solaris some significant speed increases were made to the
-disk mapping code, along with some bug fixes for Solaris 7 platforms.
-Also, the library part of libstatgrab (but not the tools) is now
-released under the LGPL instead of the GPL.
-</p>
-
-<p>
-<b>Tuesday 6 January 2004</b><br><br>
-Version 0.8 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.8.tar.gz">here</a>.
-This release brings support for Linux 2.6 and partial support for Cygwin.
-On Solaris libstatgrab now returns disk names using cNtNdNsN names rather
-than the older sdN names. There are also a bunch of fixes and optimisations
-in various places. Finally, a new function has been added to make it
-quicker to drop any elevated privileges libstatgrab may require on some
-operating systems.
-</p>
-
-<p>
-<b>Wednesday 22 October 2003</b><br><br>
-Version 0.7 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.7.tar.gz">here</a>.
-The most significant change in this release is support for NetBSD
-1.6.x. Parts of the FreeBSD code have been optimised, and an initialise
-function has been added to allow programs to drop any extra privileges
-libstatgrab needs. The list of known file systems has been increased,
-and libstatgrab has been tested on even more platforms. Finally,
-saidar has been tweaked to work even if it can't get all the
-statistics.
-</p>
-
-<p>
-<b>Saturday 18 October 2003</b><br><br>
-Version 0.6.1 of libstatgrab has been released.<br>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.6.1.tar.gz">here</a>.
-This release brings support for FreeBSD 5 on sparc 64, and some
-bugfixes in FreeBSD memory statistics. Also, some fixes to saidar,
-and statgrab.
-</p>
-
-<p>
-<b>Friday 10 October 2003</b><br><br>
-Version 0.6 of libstatgrab has been released.<br>
-You can download it from our mirror site
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.6.tar.gz">here</a>.
-This release includes some exciting new tools, support for FreeBSD
-5.1, and documentation in manpages. Plus some major bugfixes and
-packaging enhancements.
-</p>
-
-<p>
-<b>Tuesday 09 September 2003</b><br><br>
-We're pleased to announce a new release of libstatgrab.<br>
-You can download version 0.5.1 from
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.5.1.tar.gz">here</a>.
-</p>
-
-<p>
-<b>Monday 25 August 2003</b><br><br>
-We're pleased to announce a new release of libstatgrab.<br>
-You can download version 0.5 from
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab/libstatgrab-0.5.tar.gz">here</a>.
-This release provides both documentation and examples, which
-we hope will make the package more useable. Stay tuned for the
-next release with some useful tools.
-</p>
-
-<a name="what"><h2>What is libstatgrab?</h2></a>
-
-<p>
-libstatgrab is a library that provides cross platform access to
-statistics about the system on which it's run. It's written in C and
-presents a selection of useful interfaces which can be used to access
-key system statistics. The current list of statistics includes CPU
-usage, memory utilisation, disk usage, process counts, network
-traffic, disk I/O, and more.
-</p>
-
-<p>
-The current list of platforms is Solaris 2.x, Linux 2.2/2.4/2.6,
-FreeBSD 4.x/5.x, NetBSD 1.6.x, OpenBSD 3.x, DragonFly BSD 1.0, and
-Cygwin. The aim is to extend this to include as many operating
-systems as possible.
-</p>
-
-<p>
-The package also includes a couple of useful tools. The first,
-<a href="#screenshot">saidar</a>, provides a curses-based interface to
-viewing the current state of the system. The second, statgrab, gives a
-sysctl-style interface to the statistics gathered by libstatgrab. This
-extends the use of libstatgrab to people writing scripts or anything
-else that can't easily make C function calls. Included with statgrab is
-a script to generate an <a href="http://www.mrtg.org">MRTG</a>
-configuration file to use statgrab.
-</p>
-
-<a name="download"><h2>Downloading</h2></a>
-
-<p>
-The latest version of libstatgrab can be downloaded from our
-primary download
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/libstatgrab">mirror</a>.
-All downloads are pgp signed using our <a href="/pgpkey.shtml">PGP Key</a>.
-</p>
-
-<p>
-For installation instructions see the README and INSTALL files
-contained within the archive. If you're using
-<a href="http://www.freebsd.org">FreeBSD</a> you can make use of the
-<a href="http://www.freshports.org/devel/libstatgrab">devel/libstatgrab</a>
-port to install libstatgrab for you.
-</p>
-
-<a name="documentation"><h2>Documentation</h2></a>
-
-<p>
-The only online documentation we have at the moment is the manual
-pages converted in to HTML format. It's probably best to start with
-the overview manual page:
-
-<ul>
-<li><a href="statgrab.html">statgrab(3)</a></li>
-</ul>
-</p>
-
-<p>
-Then we have the manual pages for each function:
-
-<ul>
-<li><a href="cpu_percent_usage.html">cpu_percent_usage(3)</a></li>
-<li><a href="get_diskio_stats.html">get_diskio_stats(3)</a></li>
-<li><a href="get_general_stats.html">get_general_stats(3)</a></li>
-<li><a href="get_load_stats.html">get_load_stats(3)</a></li>
-<li><a href="get_memory_stats.html">get_memory_stats(3)</a></li>
-<li><a href="get_network_iface_stats.html">get_network_iface_stats(3)</a></li>
-<li><a href="get_network_stats.html">get_network_stats(3)</a></li>
-<li><a href="get_page_stats.html">get_page_stats(3)</a></li>
-<li><a href="get_process_stats.html">get_process_stats(3)</a></li>
-<li><a href="get_user_stats.html">get_user_stats(3)</a></li>
-</ul>
-</p>
-
-<a name="screenshot"><h2>Screenshot</h2></a>
-
-<p>
-Here's what saidar looks like when it's running:
-</p>
-<p>
-<img src="saidar.png" alt="saidar screenshot">
-</p>
-
-</font>
-
-<!--#include virtual="../bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream licensing</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2><font face="Arial">i-scream central monitoring system licensing</font></h2>
-
-<p><font face="Arial" size="2">
-Unless explicitly mentioned the i-scream central monitoring system is
-licensed under the GNU General Public License (GPL). The full license
-can be found <a href="http://www.gnu.org/licenses/gpl.txt">here</a>, but
-is also given below for reference.
-</font></p>
-
-<pre>
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-\f
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-\f
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-\f
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-\f
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-\f
- How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) <year> <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) year name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
-</pre>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>i-scream mailing lists</title>
- <meta name="description" content="A list of i-scream mailing lists.">
- <meta name="keywords" content="i-scream, project, credits, central,monitoring,system, unix, linux, nt, server, alert, acknowledgements">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<font face="Arial" size="2">
-<h2>i-scream Mailing Lists</h2>
-
-<p>i-scream runs a number of mailing lists geared towards both developers and
-users of i-scream products. At the present time the lists are generic to all
-products, but if the volume of e-mail rises it may become necessary to create
-per-project mailing lists. Here are a current lists.</p>
-
-<h3>dev@i-scream.org</h3>
-
-<p>
-<b>Information:</b> <a href="http://lists.i-scream.org/mailman/listinfo/dev">http://lists.i-scream.org/mailman/listinfo/dev</a><br>
-<b>State:</b> Closed<br>
-<b>Purpose:</b> A discussion forum for developers only. This can also be used to
-contact the development team as a whole.
-</p>
-
-<h3>commits@i-scream.org</h3>
-
-<p>
-<b>Information:</b> <a href="http://lists.i-scream.org/mailman/listinfo/commits">http://lists.i-scream.org/mailman/listinfo/commits</a><br>
-<b>State:</b> Open for subscription, but no posts should be sent here.<br>
-<b>Purpose:</b> Daily commit logs from the i-scream CVS repository are sent to this
-list. If you wish to keep up on development, join this list.
-</p>
-
-<h3>cvs-all@i-scream.org</h3>
-
-<p>
-<b>Information:</b> <a href="http://lists.i-scream.org/mailman/listinfo/cvs-all">http://lists.i-scream.org/mailman/listinfo/cvs-all</a><br>
-<b>State:</b> Open for subscription, but no posts should be sent here.<br>
-<b>Purpose:</b> Emails are sent to this list whenever a commit happens to the i-scream
-cvs repository. If you want to be informed about commits as they happen, join
-this list.
-</p>
-
-<h3>users@i-scream.org</h3>
-
-<p>
-<b>Information:</b> <a href="http://lists.i-scream.org/mailman/listinfo/users">http://lists.i-scream.org/mailman/listinfo/users</a><br>
-<b>State:</b> Open for subscription and posts.<br>
-<b>Purpose:</b> For discussion between users, developers, and anyone else. This is the
-place to ask questions and get support.
-</p>
-
-<h3>Subscribing</h3>
-
-<p>
-If you wish to join one of the open lists, follow the information link by
-by the relevant link above. You can also email listname-request@i-scream.org,
-where listname is one of the lists above, with subscribe in the body.
-</p>
-
-<h3>Archives</h3>
-
-<p>
-We now have archives of the lists, from May 2003. A link to the archives can
-be found on the information page for each list above.
-</p>
-
-<h3>Viruses and Spam</h3>
-
-<p>
-All lists are scanned using <a href="http://www.mailscanner.info">
-MailScanner</a> to remove viruses before they get sent out to list members.
-We also use MailScanner to tag spam messages accordingly, and ensure that such
-messages are moderated.
-</p>
-
-</font>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-<html>
-
-<head>
- <title>i-scream developer pgp key</title>
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<h2><font face="Arial">i-scream developer pgp key</font></h2>
-
-<p><font face="Arial" size="2">
-This is the public key we use for signing i-scream
-software releases.<br>You can also download a copy
-<a href="i-scream-dev.asc">here</a>.
-</font></p>
-
-<table border="1" cellpadding="5" cellspacing="0">
- <tr>
- <td align="left" style="{background-color: #F0F0F0;}">
- <pre>
-<!--#include virtual="i-scream-dev.asc" --></pre>
- </td>
- </tr>
-</table>
-
-<h2><font face="Arial">i-scream automated build pgp key</font></h2>
-
-<p><font face="Arial" size="2">
-This is the public key we use for signing automated
-builds on our build server. This key is less trusted
-as it has no passphrase. We will only use this to
-sign things such as snapshot builds - all proper
-releases will be signing with the main key given
-above.<br>You can also download a copy
-<a href="i-scream-autobuild.asc">here</a>.
-</font></p>
-
-<table border="1" cellpadding="5" cellspacing="0">
- <tr>
- <td align="left" style="{background-color: #F0F0F0;}">
- <pre>
-<!--#include virtual="i-scream-autobuild.asc" --></pre>
- </td>
- </tr>
-</table>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>i-scream Support</title>
- <meta name="description" content="How to get support or submit bugs for i-scream.">
- <meta name="keywords" content="i-scream, project, credits, central,monitoring,system, unix, linux, nt, server, alert">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
-<font face="Arial" size="2">
-<h2>i-scream Support</h2>
-
-<p>i-scream uses <a href="http://www.bestpractical.com/rt/">RT</a> to track
-support requests. We've set up two addresses to help seperate the two main
-types of requests.</a>
-
-<h3>bugs@i-scream.org</h3>
-
-<p>
-If you have found a bug or problem with an i-scream program send an
-email to this address. Your message will be logged and one of the developers
-will get back to you with more information. Hopefully we'll be able to fix
-the bug.
-</p>
-
-<h3>support@i-scream.org</h3>
-
-<p>
-If you need some assistance with an i-scream program you should email
-this address. One of the developers will be able to help attempt to
-sort out you problem. Please make sure you read the documentation
-<em>before</em> sending us an email.
-</p>
-
-<p>
-Once your email has been received you will get an acknowledgement by
-email and details of how to view your tickets over the web.
-</p>
-
-</font>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- $Author$
- $Id$
--->
-
-
-<html>
-
-<head>
- <title>Who We Are</title>
- <meta name="description" content="The i-scream Project is a central monitoring system for Unix, Linux and NT servers.">
- <meta name="keywords" content="i-scream, project, central monitoring system, unix, linux, nt, server, alert">
- <meta name="generator" content="notepad on acid, aye.">
-</head>
-
-<body bgcolor="#ffffff" link="#0000ff" alink="#3333cc" vlink="#3333cc" text="#000066">
-
-<table border="0" cellpadding="2" cellspacing="2">
- <tr>
- <td valign="top">
-<!--#include virtual="left.inc" -->
- </td>
- <td valign="top">
-<!--#include virtual="title.inc" -->
-
- <table border="0" width="500">
- <tr>
- <td>
- <font size="2" face="arial,sans-serif">
-
- <center><h3>Who We Are</h3></center>
-
- <p align="left">
- We started as a group of four 3rd year
- <a href="http://www.cs.kent.ac.uk">Computer Science</a> students
- at the University of Kent doing our final year project. Since
- then we've had a few changes in developers, but we're moving
- the project on. Here's who we are.
- </p>
-
- <h4>Current developers</h4>
-
- <p align="left">
- <b>Tim Bishop</b> - tim@i-scream.org
- <ul>
- <li><a href="http://www.bishnet.net/tim/">Homepage</a>
- <li><a href="http://www.cs.kent.ac.uk/people/staff/tdb/">Work</a>
- <li><a href="http://www.bishnet.net/tim/cv.shtml">View my C.V.</a>
- </ul>
- </p>
-
- <p align="left">
- <b>Alex Moore</b> - aj@i-scream.org
- </p>
-
- <p align="left">
- <b>Adam Sampson</b> - ats@i-scream.org
- <ul>
- <li><a href="http://www.offog.org/">Homepage</a>
- </ul>
- </p>
-
- <p align="left">
- <b>Pete Saunders</b> - pajs@i-scream.org
- <ul>
- <li><a href="http://www.cs.kent.ac.uk/people/staff/pajs/">Work</a>
- </ul>
- </p>
-
- <p align="left">
- Group Mailing List - <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>
- </p>
-
- </font>
- </td>
- </tr>
- </table>
-
-<!--#include virtual="bottom.inc" -->
- </td>
- </tr>
-</table>
-
-</body>
-
-</html>
i-scream / www.i-scream.org.git / commitdiff
