<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>Getting Started with the i-scream Central Monitoring System</title>
+ <head>
+ <title>
+ Getting Started with the i-scream Central Monitoring System
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">Getting Started</h1>
-
-<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.</p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ Getting Started
+ </h1>
+ <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.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/cms/">
+ http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/cms/</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>
+ <pre>
+ihost.pl server.domain.com port
+</pre>
+ <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.
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream CMS documentation</title>
+ <head>
+ <title>
+ i-scream CMS documentation
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream documentation</h1>
-<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="/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>
-
-<h3>User guides</h3>
-(<a href="gettingstarted.xhtml">HTML</a>) Getting Started with the i-scream Central Monitoring System<br>
-(<a href="printable/host/ihost/ihost_user_guide.doc">Word</a>|<a href="printable/host/ihost/ihost_user_guide.pdf">PDF</a>) Unix/Linux ihost user guide<br>
-(<a href="printable/host/winhost/winhost_user_guide.doc">Word</a>|<a href="printable/host/winhost/winhost_user_guide.pdf">PDF</a>) Windows WinHost user guide<br>
-(<a href="printable/client/conient_user_guide.doc">Word</a>|<a href="printable/client/conient_user_guide.pdf">PDF</a>) Conient client user guide<br>
-(<a href="printable/server/server_user_guide.doc">Word</a>|<a href="printable/server/server_user_guide.pdf">PDF</a>) Server user guide<br>
-(<a href="printable/server/corba_services.doc">Word</a>|<a href="printable/server/corba_services.pdf">PDF</a>) CORBA Services user guide<br>
-(<a href="printable/reports/web_user_guide.doc">Word</a>|<a href="printable/reports/web_user_guide.pdf">PDF</a>) Web reports user guide<br>
-(<a href="printable/reports/dbreporter_user_guide.doc">Word</a>|<a href="printable/reports/dbreporter_user_guide.pdf">PDF</a>) Database reporter user guide<br>
-
-<h3>Maintenance documentation for developers</h3>
-(<a href="printable/host/ihost/ihost_maintenance.doc">Word</a>|<a href="printable/host/ihost/ihost_maintenance.pdf">PDF</a>) Unix/Linux ihost maintenance<br>
-(<a href="printable/host/winhost/winhost_maintenance.doc">Word</a>|<a href="printable/host/winhost/winhost_maintenance.pdf">PDF</a>) Windows WinHost maintenance<br>
-(<a href="printable/client/conient_maintenance.doc">Word</a>|<a href="printable/client/conient_maintenance.pdf">PDF</a>) Conient maintenance<br>
-(<a href="printable/server/server_maintenance.doc">Word</a>|<a href="printable/server/server_maintenance.pdf">PDF</a>) Server maintenance<br>
-(<a href="printable/reports/web_reports_maintenance.doc">Word</a>|<a href="printable/reports/web_reports_maintenance.pdf">PDF</a>) Web reports maintenance<br>
-(<a href="printable/reports/dbreporter_maintenance.doc">Word</a>|<a href="printable/reports/dbreporter_maintenance.pdf">PDF</a>) Database reporter maintenance<br>
-
-<h3>Specification documents</h3>
-(<a href="printable/spec/domain/problem_domain.doc">Word</a>|<a href="printable/spec/domain/problem_domain.pdf">PDF</a>) Original specification & problem domain<br>
-(<a href="printable/spec/protocols/protocols.doc">Word</a>|<a href="printable/spec/protocols/protocols.pdf">PDF</a>) TCP Protocol specifications<br>
-(<a href="printable/spec/xml/xml_expected_data.doc">Word</a>|<a href="printable/spec/xml/xml_expected_data.pdf">PDF</a>) Expected XML data from host to server<br>
-(<a href="printable/spec/xml/xml_recommendations.doc">Word</a>|<a href="printable/spec/xml/xml_recommendations.pdf">PDF</a>) XML recommendations for host to server UDP packets<br>
-(<a href="printable/spec/docs/document_standards.doc">Word</a>|<a href="printable/spec/docs/document_standards.pdf">PDF</a>) Document standards<br>
-(<a href="printable/spec/code/java_coding_standards.doc">Word</a>|<a href="printable/spec/code/java_coding_standards.pdf">PDF</a>) Java coding standards<br>
-
-<h3>Other documents</h3>
-(<a href="printable/plan/risk_analysis.doc">Word</a>|<a href="printable/plan/risk_analysis.pdf">PDF</a>) Risk analysis<br>
-(<a href="printable/plan/est_time_allocation.doc">Word</a>|<a href="printable/plan/est_time_allocation.pdf">PDF</a>) Estimated time allocation<br>
-(<a href="printable/plan/implementation_phases.doc">Word</a>|<a href="printable/plan/implementation_phases.pdf">PDF</a>) Implementation phases for our plan<br>
-(<a href="printable/plan/est_time_allocation_revised.doc">Word</a>|<a href="printable/plan/est_time_allocation_revised.pdf">PDF</a>) Estimated time allocation (revised)<br>
-(<a href="printable/process/meeting_minutes.doc">Word</a>|<a href="printable/process/meeting_minutes.pdf">PDF</a>) Meeting Minutes<br>
-(<a href="printable/process/use_of_website.doc">Word</a>|<a href="printable/process/use_of_website.pdf">PDF</a>) Use of the website<br>
-(<a href="printable/process/cvs_softwarebuilds.doc">Word</a>|<a href="printable/process/cvs_softwarebuilds.pdf">PDF</a>) Use of CVS and automated software builds<br>
-(<a href="printable/analysis/comparison_big_brother.doc">Word</a>|<a href="printable/analysis/comparison_big_brother.pdf">PDF</a>) Comparison to Big Brother<br>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream documentation
+ </h1>
+ <p>
+ This is the documentation produced for the CMS at the
+ end of the project. It should be consider correct only
+ concerning the software builds available from the same
+ time.
+ </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="/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>
+ <h3>
+ User guides
+ </h3>
+ <p>
+ (<a href="gettingstarted.xhtml">HTML</a>) Getting Started
+ with the i-scream Central Monitoring System<br />
+ (<a href="printable/host/ihost/ihost_user_guide.doc">Word</a>
+ |<a href="printable/host/ihost/ihost_user_guide.pdf">PDF</a>)
+ Unix/Linux ihost user guide<br />
+ (<a href="printable/host/winhost/winhost_user_guide.doc">Word</a>
+ |<a href="printable/host/winhost/winhost_user_guide.pdf">PDF</a>)
+ Windows WinHost user guide<br />
+ (<a href="printable/client/conient_user_guide.doc">Word</a>
+ |<a href="printable/client/conient_user_guide.pdf">PDF</a>)
+ Conient client user guide<br />
+ (<a href="printable/server/server_user_guide.doc">Word</a>
+ |<a href="printable/server/server_user_guide.pdf">PDF</a>)
+ Server user guide<br />
+ (<a href="printable/server/corba_services.doc">Word</a>
+ |<a href="printable/server/corba_services.pdf">PDF</a>)
+ CORBA Services user guide<br />
+ (<a href="printable/reports/web_user_guide.doc">Word</a>
+ |<a href="printable/reports/web_user_guide.pdf">PDF</a>)
+ Web reports user guide<br />
+ (<a href="printable/reports/dbreporter_user_guide.doc">Word</a>
+ |<a href="printable/reports/dbreporter_user_guide.pdf">PDF</a>)
+ Database reporter user guide<br />
+ </p>
+ <h3>
+ Maintenance documentation for developers
+ </h3>
+ <p>
+ (<a href="printable/host/ihost/ihost_maintenance.doc">Word</a>
+ |<a href="printable/host/ihost/ihost_maintenance.pdf">PDF</a>)
+ Unix/Linux ihost maintenance<br />
+ (<a href="printable/host/winhost/winhost_maintenance.doc">Word</a>
+ |<a href="printable/host/winhost/winhost_maintenance.pdf">PDF</a>)
+ Windows WinHost maintenance<br />
+ (<a href="printable/client/conient_maintenance.doc">Word</a>
+ |<a href="printable/client/conient_maintenance.pdf">PDF</a>)
+ Conient maintenance<br />
+ (<a href="printable/server/server_maintenance.doc">Word</a>
+ |<a href="printable/server/server_maintenance.pdf">PDF</a>)
+ Server maintenance<br />
+ (<a href="printable/reports/web_reports_maintenance.doc">Word</a>
+ |<a href="printable/reports/web_reports_maintenance.pdf">PDF</a>)
+ Web reports maintenance<br />
+ (<a href="printable/reports/dbreporter_maintenance.doc">Word</a>
+ |<a href="printable/reports/dbreporter_maintenance.pdf">PDF</a>)
+ Database reporter maintenance<br />
+ </p>
+ <h3>
+ Specification documents
+ </h3>
+ <p>
+ (<a href="printable/spec/domain/problem_domain.doc">Word</a>
+ |<a href="printable/spec/domain/problem_domain.pdf">PDF</a>)
+ Original specification & problem domain<br />
+ (<a href="printable/spec/protocols/protocols.doc">Word</a>
+ |<a href="printable/spec/protocols/protocols.pdf">PDF</a>)
+ TCP Protocol specifications<br />
+ (<a href="printable/spec/xml/xml_expected_data.doc">Word</a>
+ |<a href="printable/spec/xml/xml_expected_data.pdf">PDF</a>)
+ Expected XML data from host to server<br />
+ (<a href="printable/spec/xml/xml_recommendations.doc">Word</a>
+ |<a href="printable/spec/xml/xml_recommendations.pdf">PDF</a>)
+ XML recommendations for host to server UDP packets<br />
+ (<a href="printable/spec/docs/document_standards.doc">Word</a>
+ |<a href="printable/spec/docs/document_standards.pdf">PDF</a>)
+ Document standards<br />
+ (<a href="printable/spec/code/java_coding_standards.doc">Word</a>
+ |<a href="printable/spec/code/java_coding_standards.pdf">PDF</a>)
+ Java coding standards<br />
+ </p>
+ <h3>
+ Other documents
+ </h3>
+ <p>
+ (<a href="printable/plan/risk_analysis.doc">Word</a>
+ |<a href="printable/plan/risk_analysis.pdf">PDF</a>)
+ Risk analysis<br />
+ (<a href="printable/plan/est_time_allocation.doc">Word</a>
+ |<a href="printable/plan/est_time_allocation.pdf">PDF</a>)
+ Estimated time allocation<br />
+ (<a href="printable/plan/implementation_phases.doc">Word</a>
+ |<a href="printable/plan/implementation_phases.pdf">PDF</a>)
+ Implementation phases for our plan<br />
+ (<a href="printable/plan/est_time_allocation_revised.doc">Word</a>
+ |<a href="printable/plan/est_time_allocation_revised.pdf">PDF</a>)
+ Estimated time allocation (revised)<br />
+ (<a href="printable/process/meeting_minutes.doc">Word</a>
+ |<a href="printable/process/meeting_minutes.pdf">PDF</a>)
+ Meeting Minutes<br />
+ (<a href="printable/process/use_of_website.doc">Word</a>
+ |<a href="printable/process/use_of_website.pdf">PDF</a>)
+ Use of the website<br />
+ (<a href="printable/process/cvs_softwarebuilds.doc">Word</a>
+ |<a href="printable/process/cvs_softwarebuilds.pdf">PDF</a>)
+ Use of CVS and automated software builds<br />
+ (<a href="printable/analysis/comparison_big_brother.doc">Word</a>
+ |<a href="printable/analysis/comparison_big_brother.pdf">PDF</a>)
+ Comparison to Big Brother<br />
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>CMS Features</title>
+ <head>
+ <title>
+ CMS Features
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-
- <h1 class="top">CMS Features</h1>
-
- <h2>Problem Specification</h2>
-
- <h3>Original Problem</h3>
-
- <p>
- 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>
-
- <h3>Centralised Machine Monitoring</h3>
-
- <p>
- 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>
- 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>
- 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>
- 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>
- John Cinnamond (email jc) whose idea this is, will provide technical
- support for the project.
- </p>
-
- <h2>Features</h2>
-
- <h3>Key Features of The System</h3>
-
- <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>
-
- <h3>An Overview of the i-scream Central Monitoring System</h3>
-
- <p>
- 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>
- 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>
- 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>
- 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>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ CMS Features
+ </h1>
+ <h2>
+ Problem Specification
+ </h2>
+ <h3>
+ Original Problem
+ </h3>
+ <p>
+ 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>
+ <h3>
+ Centralised Machine Monitoring
+ </h3>
+ <p>
+ 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>
+ 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>
+ 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>
+ 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>
+ John Cinnamond (email jc) whose idea this is, will provide
+ technical support for the project.
+ </p>
+ <h2>
+ Features
+ </h2>
+ <h3>
+ Key Features of The System
+ </h3>
+ <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>
+ <h3>
+ An Overview of the i-scream Central Monitoring System
+ </h3>
+ <p>
+ 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>
+ 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>
+ 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>
+ 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>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream CMS homepage</title>
+ <head>
+ <title>
+ i-scream CMS homepage
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">i-scream CMS homepage</h1>
-
- <div id="topnav">
- <ul>
- <li><a href="#overview">Overview</a></li>
- <li><a href="#screenshots">Screen Shots</a></li>
- <li><a href="#demo">Reports Demo</a></li>
- <li><a href="#downloads">Downloads</a></li>
- <li><a href="#documentation">Documentation</a></li>
- <li><a href="#history">Project History</a></li>
- </ul>
- </div>
-
- <h2><a name="overview">Overview</a></h2>
- <p>
- The i-scream central monitoring system provides a free, centrally
- configurable distributed server to monitor the status and
- performance of Solaris, Linux, FreeBSD and Windows machines
- on a network. The server can raise alerts using email, IRC or
- a large public information display. Information may also be
- browsed interactively via the web or using our multi-platform
- client.
- </p>
- <ul>
- <li><a href="features.xhtml">Features</a></li>
- </ul>
- <p>
- Follow the link above for the original problem specification
- we were given to develop the i-scream CMS, and the feature set
- of the CMS after it was finished.
- </p>
-
- <h2><a name="screenshots">Screen Shots</a></h2>
- <ul>
- <li><a href="screenshots/">Screen Shots</a></li>
- </ul>
- <p>
- These screenshots were taken at the end of the project, and
- therefore show the old build given below, and none of our new
- features.
- </p>
-
- <h2><a name="demo">Reports Demo</a></h2>
- <ul>
- <li><a href="reports/">Demo</a></li>
- </ul>
- <p>
- This is a demo of the web-based reports that the i-scream system
- can do. It's taken from the old builds, so doesn't show any of
- the new RRDTool based features.
- </p>
-
- <h2><a name="downloads">Downloads</a></h2>
-
- <h3>Snapshot Builds</h3>
- <ul>
- <li><a href="http://snapshots.i-scream.org">Snapshots</a></li>
- </ul>
- <p>
- Since the project was completed various changes have happened
- in the CMS. These are undocumented, but fairly straightforward.
- We'd strongly suggest you use this version of the CMS rather
- than the builds from the end of the project.
- </p>
- <p>
- We've done a fair amount of work on the graphing/database side
- of the CMS, and fixed numerous bugs. Also, the new ihost/libstatgrab
- combination requires the snapshot builds.
- </p>
-
- <h3>Old Builds (from project completion)</h3>
- <ul>
- <li><a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/cms/">Old Builds</a></li>
- </ul>
- <p>
- These builds were completed at the end of the project itself.
- They match with the documentation below, and work. But we've
- done a fair amount of work since creating them.
- </p>
-
- <h2><a name="documentation">Documentation</a></h2>
-
- <h3>Product documentation</h3>
- <ul>
- <li><a href="documentation/">Documentation</a></li>
- </ul>
- <p>
- This documentation was written as the CMS project was completed.
- It therefore applies to the downloads available from the time
- the project finished. There will definately be descrepences
- between this documentation and the snapshot builds.
- </p>
-
- <h3>Javadoc documentation</h3>
- <ul>
- <li><a href="javadoc/">Javadoc</a></li>
- </ul>
- <p>
- Each component of the CMS written in java has fairly extensive
- javadoc documentation that helps to explain the code and API's.
- </p>
-
- <h3>Process documentation</h3>
- <ul>
- <li><a href="minutes.xhtml">Meeting Minutes</a></li>
- <li><a href="projectpapers.xhtml">Documentation</a></li>
- </ul>
- <p>
- Various pieces of documentation were generated during the project
- that were intended for internal use. They're not required reading
- for running the CMS, but might be interesting if you're curious
- about the project itself.
- </p>
-
- <h2><a name="history">Project History</a></h2>
-
- <p>
- The i-scream Distributed Central Monitoring System started off
- as a final year project for a group of <a
- href="http://www.cs.kent.ac.uk/"> Computer Science</a> students
- at the <a href="http://www.kent.ac.uk/"> University of Kent</a>,
- UK. The project was completed at 4pm on 29 March 2001. It
- consisted of five lever-arch folders containing mostly source
- code and documentation. The CVS repository was tagged to signify
- this event, however.
- </p>
- <p>
- As can be seen in our "<a href="features.xhtml">problem
- domain</a>" document, the project was aimed at the UKC
- Computer Science department, and as such we believed that a
- demonstration to the "customer" was important. The
- feedback from our demonstation was more positive than we had
- anticipated. We believe that the system may now be of interest
- to anybody who wishes to monitor a number of machines on their
- network using a central configuration. The i-scream central
- monitoring system is now being used by the UKC Computer Science
- department, and their feedback is being used to further improve
- the product.
- </p>
- <p>
- The name <i>i-scream</i> arose from a meeting whereupon one
- member of the development team felt a strange urge to draw an
- ice cream on the discussion board. It later became apparent
- that we had no name for our project (other than 'The Project').
- It seemed only natural to name our project after the ice cream
- that had been oh-so-randomly drawn on the white board. Copyright
- issues immediately ruled out anything involving Mr Whippy, so
- we had to settle for <i>i-scream</i>. And thus, we were left
- with a cunning play on words - it still sounded like <i>ice
- cream</i>, yet also served as a functional description of our
- system - namely, one which screams at somebody if something has
- gone wrong...
- </p>
-
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream CMS homepage
+ </h1>
+ <div id="topnav">
+ <ul>
+ <li>
+ <a href="#overview">Overview</a>
+ </li>
+ <li>
+ <a href="#screenshots">Screen Shots</a>
+ </li>
+ <li>
+ <a href="#demo">Reports Demo</a>
+ </li>
+ <li>
+ <a href="#downloads">Downloads</a>
+ </li>
+ <li>
+ <a href="#documentation">Documentation</a>
+ </li>
+ <li>
+ <a href="#history">Project History</a>
+ </li>
+ </ul>
+ </div>
+ <h2>
+ <a id="overview">Overview</a>
+ </h2>
+ <p>
+ The i-scream central monitoring system provides a free,
+ centrally configurable distributed server to monitor the
+ status and performance of Solaris, Linux, FreeBSD and
+ Windows machines on a network. The server can raise alerts
+ using email, IRC or a large public information display.
+ Information may also be browsed interactively via the web
+ or using our multi-platform client.
+ </p>
+ <ul>
+ <li>
+ <a href="features.xhtml">Features</a>
+ </li>
+ </ul>
+ <p>
+ Follow the link above for the original problem
+ specification we were given to develop the i-scream CMS,
+ and the feature set of the CMS after it was finished.
+ </p>
+ <h2>
+ <a id="screenshots">Screen Shots</a>
+ </h2>
+ <ul>
+ <li>
+ <a href="screenshots/">Screen Shots</a>
+ </li>
+ </ul>
+ <p>
+ These screenshots were taken at the end of the project, and
+ therefore show the old build given below, and none of our
+ new features.
+ </p>
+ <h2>
+ <a id="demo">Reports Demo</a>
+ </h2>
+ <ul>
+ <li>
+ <a href="reports/">Demo</a>
+ </li>
+ </ul>
+ <p>
+ This is a demo of the web-based reports that the i-scream
+ system can do. It's taken from the old builds, so doesn't
+ show any of the new RRDTool based features.
+ </p>
+ <h2>
+ <a id="downloads">Downloads</a>
+ </h2>
+ <h3>
+ Snapshot Builds
+ </h3>
+ <ul>
+ <li>
+ <a href="http://snapshots.i-scream.org">Snapshots</a>
+ </li>
+ </ul>
+ <p>
+ Since the project was completed various changes have
+ happened in the CMS. These are undocumented, but fairly
+ straightforward. We'd strongly suggest you use this version
+ of the CMS rather than the builds from the end of the
+ project.
+ </p>
+ <p>
+ We've done a fair amount of work on the graphing/database
+ side of the CMS, and fixed numerous bugs. Also, the new
+ ihost/libstatgrab combination requires the snapshot builds.
+ </p>
+ <h3>
+ Old Builds (from project completion)
+ </h3>
+ <ul>
+ <li>
+ <a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/cms/">
+ Old Builds</a>
+ </li>
+ </ul>
+ <p>
+ These builds were completed at the end of the project
+ itself. They match with the documentation below, and work.
+ But we've done a fair amount of work since creating them.
+ </p>
+ <h2>
+ <a id="documentation">Documentation</a>
+ </h2>
+ <h3>
+ Product documentation
+ </h3>
+ <ul>
+ <li>
+ <a href="documentation/">Documentation</a>
+ </li>
+ </ul>
+ <p>
+ This documentation was written as the CMS project was
+ completed. It therefore applies to the downloads available
+ from the time the project finished. There will definately
+ be descrepences between this documentation and the snapshot
+ builds.
+ </p>
+ <h3>
+ Javadoc documentation
+ </h3>
+ <ul>
+ <li>
+ <a href="javadoc/">Javadoc</a>
+ </li>
+ </ul>
+ <p>
+ Each component of the CMS written in java has fairly
+ extensive javadoc documentation that helps to explain the
+ code and API's.
+ </p>
+ <h3>
+ Process documentation
+ </h3>
+ <ul>
+ <li>
+ <a href="minutes.xhtml">Meeting Minutes</a>
+ </li>
+ <li>
+ <a href="projectpapers.xhtml">Documentation</a>
+ </li>
+ </ul>
+ <p>
+ Various pieces of documentation were generated during the
+ project that were intended for internal use. They're not
+ required reading for running the CMS, but might be
+ interesting if you're curious about the project itself.
+ </p>
+ <h2>
+ <a id="history">Project History</a>
+ </h2>
+ <p>
+ The i-scream Distributed Central Monitoring System
+ started off as a final year project for a group of
+ <a href="http://www.cs.kent.ac.uk/">Computer Science</a>
+ students at the <a href="http://www.kent.ac.uk/">University
+ of Kent</a>, UK. The project was completed at 4pm on
+ 29 March 2001. It consisted of five lever-arch folders
+ containing mostly source code and documentation. The
+ CVS repository was tagged to signify this event, however.
+ </p>
+ <p>
+ As can be seen in our "<a href="features.xhtml">problem
+ domain</a>" document, the project was aimed at the UKC
+ Computer Science department, and as such we believed that a
+ demonstration to the "customer" was important. The feedback
+ from our demonstation was more positive than we had
+ anticipated. We believe that the system may now be of
+ interest to anybody who wishes to monitor a number of
+ machines on their network using a central configuration.
+ The i-scream central monitoring system is now being used by
+ the UKC Computer Science department, and their feedback is
+ being used to further improve the product.
+ </p>
+ <p>
+ The name <i>i-scream</i> arose from a meeting whereupon one
+ member of the development team felt a strange urge to draw
+ an ice cream on the discussion board. It later became
+ apparent that we had no name for our project (other than
+ 'The Project'). It seemed only natural to name our project
+ after the ice cream that had been oh-so-randomly drawn on
+ the white board. Copyright issues immediately ruled out
+ anything involving Mr Whippy, so we had to settle for
+ <i>i-scream</i>. And thus, we were left with a cunning play
+ on words - it still sounded like <i>ice cream</i>, yet also
+ served as a functional description of our system - namely,
+ one which screams at somebody if something has gone
+ wrong...
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream CMS javadoc</title>
+ <head>
+ <title>
+ i-scream CMS javadoc
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream CMS javadoc</h1>
-
-<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="server/">Server javadoc pages</a></p>
-<p><a href="conient/">Conient javadoc pages</a></p>
-<p><a href="corbaservices/">Corba Service Manager javadoc pages</a></p>
-<p><a href="util/">Util Package javadoc pages</a></p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream CMS javadoc
+ </h1>
+ <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="server/">Server javadoc pages</a>
+ </p>
+ <p>
+ <a href="conient/">Conient javadoc pages</a>
+ </p>
+ <p>
+ <a href="corbaservices/">Corba Service Manager javadoc
+ pages</a>
+ </p>
+ <p>
+ <a href="util/">Util Package javadoc pages</a>
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream meeting minutes</title>
+ <head>
+ <title>
+ i-scream meeting minutes
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">i-scream meeting minutes</h1>
-<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>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream meeting minutes
+ </h1>
+ <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>
+ <h3>
+ Meetings held in 2001
+ </h3>
+ <p>
+ <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>
+ </p>
+ <p>
+ <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 />
+ </p>
+ <p>
+ <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>
+ </p>
+ <h3>
+ Meetings held in 2000
+ </h3>
+ <p>
+ <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>
+ </p>
+ <p>
+ <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 />
+ </p>
+ <p>
+ <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 />
+ </p>
+ <p>
+ <a href="/cgi-bin/docs.cgi?doc=minutes/minutes-20000928.txt">28 September 2000</a>
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>project papers</title>
+ <head>
+ <title>
+ project papers
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">project papers</h1>
-
-<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>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ project papers
+ </h1>
+ <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>
+ <p>
+ <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 />
+ </p>
+ <p>
+ <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 />
+ </p>
+ <p>
+ <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 />
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>CMS Screen Shots</title>
-<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
-<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">CMS Screen Shots</h1>
-
-<div align="center">
- <center>
- <table border="0" cellspacing="10" width="500" cellpadding="0">
- <tr>
- <td valign="top" colspan="2">
- <h2 align="center"><font face="Arial" color="#000066">i-scream
- screenshots</font></h2>
- <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>
-
-</div>
-
+ <head>
+ <title>
+ CMS Screen Shots
+ </title><!--#include virtual="/style.inc" -->
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
+ <!--#include virtual="/header.inc" -->
+ <div id="contents">
+ <h1 class="top">
+ CMS Screen Shots
+ </h1>
+ <h2>
+ i-scream screenshots
+ </h2>
+ <p>
+ 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.
+ </p>
+ <p>
+ <b>Reports Centre (Web)</b><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.
+ </p>
+ <p>
+ <a href="reports-main.gif">
+ <img src="thumbnail-reports-main.gif" alt="click to enlarge!" width="100" height="77" />
+ </a>
+ </p>
+ <p>
+ <b>Latest Information (Web)</b><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.
+ </p>
+ <p>
+ <a href="reports-raptor-latest-misc.gif">
+ <img src="thumbnail-reports-raptor-latest-misc.gif" alt="click to enlarge!" width="100" height="104" />
+ </a>
+ </p>
+ <p>
+ <b>Conient (Multiplatform real-time client)</b><br />
+ 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.
+ </p>
+ <p>
+ <a href="conient-main.gif">
+ <img src="thumbnail-conient-main.gif" alt="click to enlarge!" width="100" height="110" />
+ </a>
+ </p>
+ <p>
+ <b>Conient (Viewing extra data)</b><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.
+ </p>
+ <p>
+ <a href="conient-platform-info.gif">
+ <img src="thumbnail-conient-platform-info.gif" alt="click to enlarge!" width="100" height="59" />
+ </a>
+ </p>
+ <p>
+ <b>Conient (Configuration)</b><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.
+ </p>
+ <p>
+ <a href="conient-config.gif">
+ <img src="thumbnail-conient-config.gif" alt="click to enlarge!" width="100" height="48" />
+ </a>
+ </p>
+ <p>
+ <b>ihost (Unix/Linux host)</b><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.
+ </p>
+ <p>
+ <a href="ihost-main.gif">
+ <img src="thumbnail-ihost-main.gif" alt="click to enlarge!" width="100" height="51" />
+ </a>
+ </p>
+ <p>
+ <b>WinHost (Windows host)</b><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.
+ </p>
+ <p>
+ <a href="winhost-main.gif">
+ <img src="thumbnail-winhost-main.gif" alt="click to enlarge!" width="100" height="62" />
+ </a>
+ </p>
+ <p>
+ <b>Alerts (Email)</b><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.
+ </p>
+ <p>
+ <a href="alerter-email.gif">
+ <img src="thumbnail-alerter-email.gif" alt="click to enlarge!" width="100" height="74" />
+ </a>
+ </p>
+ <p>
+ <b>Alerts (IRC bot)</b><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.
+ </p>
+ <p>
+ <a href="alerter-irc.gif">
+ <img src="thumbnail-alerter-irc.gif" alt="click to enlarge!" width="100" height="95" />
+ </a>
+ </p>
+ <p>
+ <b>Alerts (Web page)</b><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.
+ </p>
+ <p>
+ <a href="reports-alerts-all.gif">
+ <img src="thumbnail-reports-alerts-all.gif" alt="click to enlarge!" width="100" height="96" />
+ </a>
+ </p>
+ <p>
+ <b>Alerts (Public helpdesk display)</b><br />
+ 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.
+ </p>
+ <p>
+ <a href="reports-public-autoscroll.gif">
+ <img src="thumbnail-reports-public-autoscroll.gif" alt="click to enlarge!" width="100" height="78" />
+ </a>
+ </p>
+ <p>
+ <b>Conient (Server queue monitoring)</b><br />
+ 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.
+ </p>
+ <p>
+ <a href="conient-queues.gif">
+ <img src="thumbnail-conient-queues.gif" alt="click to enlarge!" width="100" height="159" />
+ </a>
+ </p>
+ <p>
+ <b>Historical reports (Web)</b><br />
+ 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.
+ </p>
+ <p>
+ <a href="reports-raptor-load15.gif">
+ <img src="thumbnail-reports-raptor-load15.gif" alt="click to enlarge!" width="100" height="107" />
+ </a>
+ </p>
+ <p>
+ <b>Historical reports (Metadata)</b><br />
+ 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.
+ </p>
+ <p>
+ <a href="reports-raptor-users.gif">
+ <img src="thumbnail-reports-raptor-users.gif" alt="click to enlarge!" width="100" height="96" />
+ </a>
+ </p>
+ <p>
+ <b>The i-scream server</b><br />
+ 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 ;-)
+ </p>
+ <p>
+ <a href="server-main.gif">
+ <img src="thumbnail-server-main.gif" alt="click to enlarge!" width="100" height="100" />
+ </a>
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream cvs repository</title>
+ <head>
+ <title>
+ i-scream cvs repository
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream CVS Repository</h1>
-
-<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.xhtml">
-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="/cgi-bin/cvslog.cgi?period=today">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today</a><br/>
-Commits this week: <a href="/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="/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="/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>
-
-<pre>
+ <div id="contents">
+ <h1 class="top">
+ i-scream CVS Repository
+ </h1>
+ <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.xhtml">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="/cgi-bin/cvslog.cgi?period=today">http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today</a><br />
+ Commits this week: <a href="/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="/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="/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>
+ <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>
-
-<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>
-
-<pre>
+ <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>
+ <pre>
CVS_RSH = ssh
CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
</pre>
-
-<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.cvsup.org/">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>
-
-<pre>
+ <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.cvsup.org/">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>
+ <pre>
*default host=cvsup.i-scream.org
*default base=/home/user/sup
*default prefix=/home/user/i-scream
*default compress
i-scream.cms.source tag=.
</pre>
-
-<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="/cvsplot/">http://www.i-scream.org/cvsplot/</a>
-</p>
-</div>
-
+ <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="/cvsplot/">http://www.i-scream.org/cvsplot/</a>
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream cvs statistics</title>
+ <head>
+ <title>
+ i-scream cvs statistics
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream cvs statistics</h1>
-<p>This webpage shows a graphical representation of the <i>file count</i> and <i>line
-count</i> for the source files.<br>
-Only the files in the cms module of cvs are listed.
-This page is updated at 7am daily.</p>
-<p>You can also <a href="http://cvs.i-scream.org/cms">browse</a> the cvs
-repository.</p>
-<h3>file count</h3>
-<p>Count of the number of files since the start of the project.</p>
-<p>Textual representation: <a href="filedata.txt">filedata.txt</a></p>
-<p><img border="0" src="filedata.png" width="640" height="480"></p>
-<h3>line count</h3>
-<p>Count of the number of lines of code and documentation since the start of the project.</p>
-<p>Textual representation: <a href="linedata.txt">linedata.txt</a></p>
-<p><img border="0" src="linedata.png" width="640" height="480"></p>
-<h3>credits</h3>
-<p>These images were generated using the cvsplot program, which can be found <a href="http://cvsplot.sourceforge.net">here</a>.</p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream cvs statistics
+ </h1>
+ <p>
+ This webpage shows a graphical representation of the
+ <i>file count</i> and <i>line count</i> for the source
+ files.<br />
+ Only the files in the cms module of cvs are listed. This
+ page is updated at 7am daily.
+ </p>
+ <p>
+ You can also <a href="http://cvs.i-scream.org/cms/">browse</a>
+ the cvs repository.
+ </p>
+ <h3>
+ file count
+ </h3>
+ <p>
+ Count of the number of files since the start of the
+ project.
+ </p>
+ <p>
+ Textual representation: <a href="filedata.txt">filedata.txt</a>
+ </p>
+ <p>
+ <img src="filedata.png" width="640" height="480" alt="number of files" />
+ </p>
+ <h3>
+ line count
+ </h3>
+ <p>
+ Count of the number of lines of code and documentation
+ since the start of the project.
+ </p>
+ <p>
+ Textual representation: <a href="linedata.txt">linedata.txt</a>
+ </p>
+ <p>
+ <img src="linedata.png" width="640" height="480" alt="lines of code" />
+ </p>
+ <h3>
+ credits
+ </h3>
+ <p>
+ These images were generated using the cvsplot program,
+ which can be found
+ <a href="http://cvsplot.sourceforge.net">here</a>.
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\ No newline at end of file
-<div id="footer">
- <p>
- © 2000-2004 i-scream »
- <a href="http://www.i-scream.org/">http://www.i-scream.org/</a> «
- dev@i-scream.org
- </p>
-</div>
+ <div id="footer">
+ <p>
+ © 2000-2004 i-scream »
+ <a href="http://www.i-scream.org/">http://www.i-scream.org/</a> «
+ dev@i-scream.org
+ </p>
+ </div>
\ No newline at end of file
-<div id="header">
-</div>
+ <div id="header">
+ </div>
\ No newline at end of file
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream homepage</title>
+ <head>
+ <title>
+ i-scream homepage
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">i-scream homepage</h1>
-
- <div id="topnav">
- <ul>
- <li><a href="#news">News</a></li>
- <li><a href="#projects">Projects</a></li>
- <li><a href="#about">About</a></li>
- <li><a href="#search">Search</a></li>
- </ul>
- </div>
-
- <h2><a id="news">News</a></h2>
-
- <h3>
- Sunday 21 March 2004
- </h3>
- <h4>
- pystatgrab 0.1 released
- </h4>
- <p>
- <a href="/pystatgrab/">pystatgrab</a> 0.1 has been released. This
- is the first release of pystatgrab; a set of Python bindings for
- libstatgrab.
- </p>
-
- <h3>
- Wednesday 10 March 2004
- </h3>
- <h4>
- libstatgrab 0.9 released
- </h4>
- <p>
- <a href="/libstatgrab/">libstatgrab</a> 0.9
- has been released and includes new features and support for new
- platforms.
- </p>
-
- <h3>
- Wednesday 11 February 2004
- </h3>
- <h4>
- libstatgrab 0.8.2 released
- </h4>
- <p>
- <a href="/libstatgrab/">libstatgrab</a>
- version 0.8.2 brings further platform support and Python bindings.
- </p>
-
- <h3>
- Tuesday 15 July 2003
- </h3>
- <h4>
- i-scream support changes
- </h4>
- <p>
- We have moved the i-scream support and bug tracking to a new
- facility on the i-scream server. For further details please
- see our <a href="/support.xhtml">support</a>
- page.
- </p>
-
- <h3>
- Sunday 8 June 2003
- </h3>
- <h4>
- server move
- </h4>
- <p>
- The i-scream website, email, and CVS facilities are now all
- run from a <a href="http://www.freebsd.org/">FreeBSD</a> server.
- </p>
-
- <h2><a id="projects">Projects</a></h2>
-
- <h3>
- libstatgrab
- </h3>
- <ul>
- <li><a href="/libstatgrab/">libstatgrab homepage</a></li>
- </ul>
- <p>
- libstatgrab is a library and tool set for acquiring system
- statistics from the operating system. An API is provided for
- other applications to easily accesses a variety of system
- statistics, including, amongst other things, CPU usage, VM
- usage, disk statistics, and network interface usage.
- </p>
- <p>
- A handful of tools are also provided to make this information
- more readily available to users. A curses based tool gives users
- a "top like" view of the current state of their system, and a
- "sysctl like" tool gives easy access to the statistics for other
- applications that can't easily used the C API.
- </p>
- <p>
- Finally scripts are provided to quickly setup MRTG to use
- libstatgrab for generating graphs of the available statistics.
- </p>
-
- <h3>
- pystatgrab
- </h3>
- <ul>
- <li><a href="/pystatgrab/">pystatgrab homepage</a></li>
- </ul>
- <p>
- pystatgrab is a set of Python bindings for the libstatgrab
- library. It provides a set of function calls identical to those
- of libstatgrab, and returns data in structures that logically
- map on to those of libstatgrab.
- </p>
-
- <h3>
- Laroona
- </h3>
- <ul>
- <li><a href="/laroona/">Laroona homepage</a></li>
- </ul>
- <p>
- Laroona is the new central monitoring system. It's still very
- much in the early stages of development, and doesn't have any
- code available for download yet. Look at the project page for
- more on the development process.
- </p>
-
- <h3>
- CMS - Central Monitoring System
- </h3>
- <ul>
- <li><a href="/cms/">CMS homepage</a></li>
- </ul>
- <p>
- i-scream originally started out with just the CMS (Central
- Monitoring System) project. Since then it's moved on to have
- other related projects, as well as the CMS.
- </p>
- <p>
- The CMS is no longer being developed. We are now putting our
- time into a new project redeveloping the CMS. We're taking the
- good ideas from the old CMS, improving some of the weaknesses,
- and we'll hopefully produce are far superior product.
- </p>
-
- <h2><a id="about">About</a></h2>
-
- <p>
- The i-scream group is a causual team of individuals with a
- variety of personal interests, working together to produce
- software, tools, and libraries that might be of use or interest
- to others.
- </p>
-
- <p>
- To find out more about who we are see the <a href="/who.xhtml">Who
- We Are</a> webpage.
- </p>
-
- <h2><a id="search">Search</a></h2>
-
- <p>
- Use this form to search the whole i-scream website, courtesy
- of Google.
- </p>
- <form method="get" action="http://www.google.com/custom">
- <p>
- <a href="http://www.google.com/search">
- <img src="http://www.google.com/logos/Logo_40wht.gif" alt="Google" />
- </a>
- <input type="hidden" name="domains" value="i-scream.org" />
- <input type="hidden" name="sitesearch" value="i-scream.org" />
- <input type="text" name="q" size="31" maxlength="255" value="" />
- <input type="submit" name="sa" value="Search" />
- <input type="hidden" name="cof" value="S:http://www.i-scream.org/;GL:0;VLC:#3333cc;AH:left;BGC:#ffffff;LH:37;LC:#0000ff;L:http://www.i-scream.org/i-scream.gif;ALC:#3333cc;LW:502;T:#000066;AWFID:d646a9fd69e7d9cb;" />
- </p>
- </form>
-
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream homepage
+ </h1>
+ <div id="topnav">
+ <ul>
+ <li>
+ <a href="#news">News</a>
+ </li>
+ <li>
+ <a href="#projects">Projects</a>
+ </li>
+ <li>
+ <a href="#about">About</a>
+ </li>
+ <li>
+ <a href="#search">Search</a>
+ </li>
+ </ul>
+ </div>
+ <h2>
+ <a id="news">News</a>
+ </h2>
+ <h3>
+ Sunday 21 March 2004
+ </h3>
+ <h4>
+ pystatgrab 0.1 released
+ </h4>
+ <p>
+ <a href="/pystatgrab/">pystatgrab</a> 0.1 has been
+ released. This is the first release of pystatgrab; a set of
+ Python bindings for libstatgrab.
+ </p>
+ <h3>
+ Wednesday 10 March 2004
+ </h3>
+ <h4>
+ libstatgrab 0.9 released
+ </h4>
+ <p>
+ <a href="/libstatgrab/">libstatgrab</a> 0.9 has been
+ released and includes new features and support for new
+ platforms.
+ </p>
+ <h3>
+ Wednesday 11 February 2004
+ </h3>
+ <h4>
+ libstatgrab 0.8.2 released
+ </h4>
+ <p>
+ <a href="/libstatgrab/">libstatgrab</a> version 0.8.2
+ brings further platform support and Python bindings.
+ </p>
+ <h3>
+ Tuesday 15 July 2003
+ </h3>
+ <h4>
+ i-scream support changes
+ </h4>
+ <p>
+ We have moved the i-scream support and bug tracking to a
+ new facility on the i-scream server. For further details
+ please see our <a href="/support.xhtml">support</a> page.
+ </p>
+ <h3>
+ Sunday 8 June 2003
+ </h3>
+ <h4>
+ server move
+ </h4>
+ <p>
+ The i-scream website, email, and CVS facilities are now all
+ run from a <a href="http://www.freebsd.org/">FreeBSD</a>
+ server.
+ </p>
+ <h2>
+ <a id="projects">Projects</a>
+ </h2>
+ <h3>
+ libstatgrab
+ </h3>
+ <ul>
+ <li>
+ <a href="/libstatgrab/">libstatgrab homepage</a>
+ </li>
+ </ul>
+ <p>
+ libstatgrab is a library and tool set for acquiring system
+ statistics from the operating system. An API is provided
+ for other applications to easily accesses a variety of
+ system statistics, including, amongst other things, CPU
+ usage, VM usage, disk statistics, and network interface
+ usage.
+ </p>
+ <p>
+ A handful of tools are also provided to make this
+ information more readily available to users. A curses based
+ tool gives users a "top like" view of the current state of
+ their system, and a "sysctl like" tool gives easy access to
+ the statistics for other applications that can't easily
+ used the C API.
+ </p>
+ <p>
+ Finally scripts are provided to quickly setup MRTG to use
+ libstatgrab for generating graphs of the available
+ statistics.
+ </p>
+ <h3>
+ pystatgrab
+ </h3>
+ <ul>
+ <li>
+ <a href="/pystatgrab/">pystatgrab homepage</a>
+ </li>
+ </ul>
+ <p>
+ pystatgrab is a set of Python bindings for the libstatgrab
+ library. It provides a set of function calls identical to
+ those of libstatgrab, and returns data in structures that
+ logically map on to those of libstatgrab.
+ </p>
+ <h3>
+ Laroona
+ </h3>
+ <ul>
+ <li>
+ <a href="/laroona/">Laroona homepage</a>
+ </li>
+ </ul>
+ <p>
+ Laroona is the new central monitoring system. It's still
+ very much in the early stages of development, and doesn't
+ have any code available for download yet. Look at the
+ project page for more on the development process.
+ </p>
+ <h3>
+ CMS - Central Monitoring System
+ </h3>
+ <ul>
+ <li>
+ <a href="/cms/">CMS homepage</a>
+ </li>
+ </ul>
+ <p>
+ i-scream originally started out with just the CMS (Central
+ Monitoring System) project. Since then it's moved on to
+ have other related projects, as well as the CMS.
+ </p>
+ <p>
+ The CMS is no longer being developed. We are now putting
+ our time into a new project redeveloping the CMS. We're
+ taking the good ideas from the old CMS, improving some of
+ the weaknesses, and we'll hopefully produce are far
+ superior product.
+ </p>
+ <h2>
+ <a id="about">About</a>
+ </h2>
+ <p>
+ The i-scream group is a causual team of individuals with a
+ variety of personal interests, working together to produce
+ software, tools, and libraries that might be of use or
+ interest to others.
+ </p>
+ <p>
+ To find out more about who we are see the
+ <a href="/who.xhtml">Who We Are</a> webpage.
+ </p>
+ <h2>
+ <a id="search">Search</a>
+ </h2>
+ <p>
+ Use this form to search the whole i-scream website,
+ courtesy of Google.
+ </p>
+ <form method="get" action="http://www.google.com/custom">
+ <p>
+ <a href="http://www.google.com/search">
+ <img src="http://www.google.com/logos/Logo_40wht.gif" alt="Google" />
+ </a>
+ <input type="hidden" name="domains" value="i-scream.org" />
+ <input type="hidden" name="sitesearch" value="i-scream.org" />
+ <input type="text" name="q" size="31" maxlength="255" value="" />
+ <input type="submit" name="sa" value="Search" />
+ <input type="hidden" name="cof" value="S:http://www.i-scream.org/;GL:0;VLC:#3333cc;AH:left;BGC:#ffffff;LH:37;LC:#0000ff;L:http://www.i-scream.org/i-scream.gif;ALC:#3333cc;LW:502;T:#000066;AWFID:d646a9fd69e7d9cb;" />
+ </p>
+ </form>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream Laroona homepage</title>
+ <head>
+ <title>
+ i-scream Laroona homepage
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-
-<h1 class="top">i-scream Laroona homepage</h1>
-
-<div id="topnav">
- <ul>
- <li><a href="#news">News</a></li>
- <li><a href="#what">What is Laroona?</a></li>
- <li><a href="#development">Development</a></li>
- </ul>
-</div>
-
-<h2><a name="news">News</a></h2>
-
-<h3>Sunday 21 March 2004</h3>
-<p>
-Laroona project page created.
-</p>
-
-<h2><a name="what">What is Laroona?</a></h2>
-
-<p>
-Laroona is a rewrite of the <a href="/cms/">CMS</a>.
-</p>
-
-
-<h2><a name="development">Development</a></h2>
-
-<ul>
- <li><a href="http://wiki.i-scream.org/">i-scream wiki</a></li>
-</ul>
-<p>
-Laroona is currently in the early stages of development. Much of our development work is being done on
-the i-scream Wiki.
-</p>
-
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream Laroona homepage
+ </h1>
+ <div id="topnav">
+ <ul>
+ <li>
+ <a href="#news">News</a>
+ </li>
+ <li>
+ <a href="#what">What is Laroona?</a>
+ </li>
+ <li>
+ <a href="#development">Development</a>
+ </li>
+ </ul>
+ </div>
+ <h2>
+ <a id="news">News</a>
+ </h2>
+ <h3>
+ Sunday 21 March 2004
+ </h3>
+ <p>
+ Laroona project page created.
+ </p>
+ <h2>
+ <a id="what">What is Laroona?</a>
+ </h2>
+ <p>
+ Laroona is a rewrite of the <a href="/cms/">CMS</a>.
+ </p>
+ <h2>
+ <a id="development">Development</a>
+ </h2>
+ <ul>
+ <li>
+ <a href="http://wiki.i-scream.org/">i-scream wiki</a>
+ </li>
+ </ul>
+ <p>
+ Laroona is currently in the early stages of development.
+ Much of our development work is being done on the i-scream
+ Wiki.
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream libstatgrab homepage</title>
+ <head>
+ <title>
+ i-scream libstatgrab homepage
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-
-<h1 class="top">i-scream libstatgrab homepage</h1>
-
-<div id="topnav">
- <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>
-</div>
-
-<h2><a name="news">News</a></h2>
-
-<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>
-
-<h3>Sunday 21 March 2004</h3>
-<p>
-pystatgrab, a new package containing a set of Python bindings,
-has been released. Check out it's <a href="/pystatgrab/">project
-page</a>.
-</p>
-
-<h3>Wednesday 10 March 2004</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Wednesday 11 February 2004</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Wednesday 21 January 2004</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Tuesday 6 January 2004</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Wednesday 22 October 2003</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Saturday 18 October 2003</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h3>Friday 10 October 2003</h3>
-<p>
-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>.
-</p>
-<p>
-This release includes some exciting new tools, support for FreeBSD
-5.1, and documentation in manpages. Plus some major bugfixes and
-packaging enhancements.
-</p>
-
-<h3>Tuesday 09 September 2003</h3>
-<p>
-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>
-
-<h3>Monday 25 August 2003</h3>
-<p>
-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>.
-</p>
-<p>
-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>
-
-<h2><a name="what">What is libstatgrab?</a></h2>
-
-<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>
-
-<h2><a name="download">Downloading</a></h2>
-
-<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.xhtml">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>
-
-<h2><a name="documentation">Documentation</a></h2>
-
-<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:
-</p>
-
-<ul>
-<li><a href="statgrab.html">statgrab(3)</a></li>
-</ul>
-
-<p>
-Then we have the manual pages for each function:
-</p>
-
-<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>
-
-<h2><a name="screenshot">Screenshot</a></h2>
-
-<p>
-Here's what saidar looks like when it's running:
-</p>
-<p>
-<img src="saidar.png" alt="saidar screenshot" />
-</p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream libstatgrab homepage
+ </h1>
+ <div id="topnav">
+ <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>
+ </div>
+ <h2>
+ <a id="news">News</a>
+ </h2>
+ <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>
+ <h3>
+ Sunday 21 March 2004
+ </h3>
+ <p>
+ pystatgrab, a new package containing a set of Python
+ bindings, has been released. Check out it's
+ <a href="/pystatgrab/">project page</a>.
+ </p>
+ <h3>
+ Wednesday 10 March 2004
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Wednesday 11 February 2004
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Wednesday 21 January 2004
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Tuesday 6 January 2004
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Wednesday 22 October 2003
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Saturday 18 October 2003
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h3>
+ Friday 10 October 2003
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ This release includes some exciting new tools, support for
+ FreeBSD 5.1, and documentation in manpages. Plus some major
+ bugfixes and packaging enhancements.
+ </p>
+ <h3>
+ Tuesday 09 September 2003
+ </h3>
+ <p>
+ 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>
+ <h3>
+ Monday 25 August 2003
+ </h3>
+ <p>
+ 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>.
+ </p>
+ <p>
+ 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>
+ <h2>
+ <a id="what">What is libstatgrab?</a>
+ </h2>
+ <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>
+ <h2>
+ <a id="download">Downloading</a>
+ </h2>
+ <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.xhtml">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>
+ <h2>
+ <a id="documentation">Documentation</a>
+ </h2>
+ <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:
+ </p>
+ <ul>
+ <li>
+ <a href="statgrab.html">statgrab(3)</a>
+ </li>
+ </ul>
+ <p>
+ Then we have the manual pages for each function:
+ </p>
+ <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>
+ <h2>
+ <a id="screenshot">Screenshot</a>
+ </h2>
+ <p>
+ Here's what saidar looks like when it's running:
+ </p>
+ <p>
+ <img src="saidar.png" alt="saidar screenshot" />
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream licensing</title>
+ <head>
+ <title>
+ i-scream licensing
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream software licensing</h1>
-
-<p>
-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.
-</p>
-
-<pre>
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
+ <div id="contents">
+ <h1 class="top">
+ i-scream software licensing
+ </h1>
+ 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.
+ </p>
+ 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
+ Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
The precise terms and conditions for copying, distribution and
modification follow.
-\f
- GNU GENERAL PUBLIC LICENSE
+
+ GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
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
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
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
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
- NO WARRANTY
+ 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
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
+ END OF TERMS AND CONDITIONS
+
+ 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
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
</pre>
-</div>
-
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream mailing lists</title>
+ <head>
+ <title>
+ i-scream mailing lists
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream Mailing Lists</h1>
-
-<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>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream Mailing Lists
+ </h1>
+ <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>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
-<div id="menu">
- <h3 class="heading">
- <img src="http://nwww.i-scream.org/cgi-bin/logo.jpg" class="cornerlogo" alt="a random image"/>
- Main
- </h3>
-
- <p>
- <a href="http://nwww.i-scream.org/">i-scream Home</a><br/>
- <a href="http://nwww.i-scream.org/#news">News</a><br/>
- <a href="http://nwww.i-scream.org/#search">Search</a><br/>
- </p>
-
- <h3 class="heading">Projects</h3>
-
- <p>
- <a href="http://nwww.i-scream.org/libstatgrab/">libstatgrab</a><br/>
- <a href="http://nwww.i-scream.org/pystatgrab/">pystatgrab</a><br/>
- <a href="http://nwww.i-scream.org/laroona/">Laroona</a><br/>
- <a href="http://nwww.i-scream.org/cms/">CMS</a><br/>
- <br/>
- <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">Java TCP/UDP ACL's</a><br/>
- </p>
-
- <h3 class="heading">Resources</h3>
-
- <p>
- <a href="http://nwww.i-scream.org/cvs.xhtml">CVS Repository</a><br/>
- <a href="http://wiki.i-scream.org/">Wiki</a><br/>
- <br/>
- <a href="http://nwww.i-scream.org/mailinglists.xhtml">Mailing Lists</a><br/>
- <a href="http://nwww.i-scream.org/support.xhtml">Support</a><br/>
- <a href="http://nwww.i-scream.org/support.xhtml">Bug Tracking</a><br/>
- <br/>
- <a href="http://nwww.i-scream.org/license.xhtml">Licensing</a><br/>
- </p>
-
- <h3 class="heading">i-scream</h3>
-
- <p>
- <a href="http://nwww.i-scream.org/who.xhtml">Who We Are</a><br/>
- <a href="http://nwww.i-scream.org/pgpkey.xhtml">PGP Key</a><br/>
- </p>
-
- <h3 class="heading">Contact Us</h3>
-
- <p>
- <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>
- </p>
-
- <p class="logo">
- <a href="http://www.freebsd.org/">
- <img src="http://nwww.i-scream.org/images/freebsdlogo_small.gif" alt="Powered By FreeBSD" />
- </a>
- </p>
-</div>
+ <div id="menu">
+ <h3 class="heading">
+ <img src="http://nwww.i-scream.org/cgi-bin/logo.jpg" class="cornerlogo" alt="a random image"/>
+ Main
+ </h3>
+ <p>
+ <a href="http://nwww.i-scream.org/">i-scream Home</a><br />
+ <a href="http://nwww.i-scream.org/#news">News</a><br />
+ <a href="http://nwww.i-scream.org/#search">Search</a><br />
+ </p>
+ <h3 class="heading">
+ Projects
+ </h3>
+ <p>
+ <a href="http://nwww.i-scream.org/libstatgrab/">libstatgrab</a><br />
+ <a href="http://nwww.i-scream.org/pystatgrab/">pystatgrab</a><br />
+ <a href="http://nwww.i-scream.org/laroona/">Laroona</a><br />
+ <a href="http://nwww.i-scream.org/cms/">CMS</a><br />
+ <br />
+ <a href="http://www.cs.kent.ac.uk/people/staff/tdb/#acl">Java TCP/UDP ACL's</a><br />
+ </p>
+ <h3 class="heading">
+ Resources
+ </h3>
+ <p>
+ <a href="http://nwww.i-scream.org/cvs.xhtml">CVS Repository</a><br />
+ <a href="http://wiki.i-scream.org/">Wiki</a><br />
+ <br />
+ <a href="http://nwww.i-scream.org/mailinglists.xhtml">Mailing Lists</a><br />
+ <a href="http://nwww.i-scream.org/support.xhtml">Support</a><br />
+ <a href="http://nwww.i-scream.org/support.xhtml">Bug Tracking</a><br />
+ <br />
+ <a href="http://nwww.i-scream.org/license.xhtml">Licensing</a><br />
+ </p>
+ <h3 class="heading">
+ i-scream
+ </h3>
+ <p>
+ <a href="http://nwww.i-scream.org/who.xhtml">Who We Are</a><br />
+ <a href="http://nwww.i-scream.org/pgpkey.xhtml">PGP Key</a><br />
+ </p>
+ <h3 class="heading">
+ Contact Us
+ </h3>
+ <p>
+ <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>
+ </p>
+ <p class="logo">
+ <a href="http://www.freebsd.org/">
+ <img src="http://nwww.i-scream.org/images/freebsdlogo_small.gif" alt="Powered By FreeBSD" />
+ </a>
+ </p>
+ </div>
\ No newline at end of file
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream PGP keys</title>
+ <head>
+ <title>
+ i-scream PGP keys
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream pgp keys</h1>
-
-<h2 class="top">i-scream developer pgp key</h2>
-
-<p>
-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>.
-</p>
-
-<pre>
+ <div id="contents">
+ <h1 class="top">
+ i-scream pgp keys
+ </h1>
+ <h2 class="top">
+ i-scream developer pgp key
+ </h2>
+ <p>
+ 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>.
+ </p>
+ <pre>
<!--#include virtual="i-scream-dev.asc" -->
</pre>
-
-<h2>i-scream automated build pgp key</h2>
-
-<p>
-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>.
-</p>
-
-<pre>
+ <h2>
+ i-scream automated build pgp key
+ </h2>
+ <p>
+ 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>.
+ </p>
+ <pre>
<!--#include virtual="i-scream-autobuild.asc" -->
</pre>
-</div>
-
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream pystatgrab homepage</title>
+ <head>
+ <title>
+ i-scream pystatgrab homepage
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-
-<h1 class="top">i-scream pystatgrab homepage</h1>
-
-<div id="topnav">
- <ul>
- <li><a href="#news">News</a></li>
- <li><a href="#what">What is pystatgrab?</a></li>
- <li><a href="#download">Downloading</a></li>
- </ul>
-</div>
-
-<h2><a name="news">News</a></h2>
-
-<p>
-To get notifications of new pystatgrab releases why not subscribe
-to our project over on <a href="http://freshmeat.net/projects/pystatgrab/">
-freshmeat</a>?
-</p>
-
-<h3>Sunday 21 March 2004</h3>
-<p>
-Version 0.1 of pystatgrab has been released.<br/>
-Download it
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/pystatgrab/pystatgrab-0.1.tar.gz">here</a>.
-</p>
-<p>
-This is the first release of pystatgrab; a set of Python bindings
-for the <a href="/libstatgrab/">libstatgrab</a> library. Although
-lacking in documentation, it's fairly complete feature wise.
-</p>
-
-<h2><a name="what">What is pystatgrab?</a></h2>
-
-<p>
-pystatgrab is a set of Python bindings for the <a href="/libstatgrab/">
-libstatgrab</a> library. It installs as a module and provides a set of
-function calls with identical names to the libstatgrab functions. The
-returned data types also map logically on to the structures returned
-by libstatgrab.
-</p>
-
-<p>
-pystatgrab should work on any platform that libstatgrab will work on.
-Currently, pystatgrab requires version 0.9 of libstatgrab to function.
-</p>
-
-<h2><a name="download">Downloading</a></h2>
-
-<p>
-The latest version of pystatgrab can be downloaded from our
-primary download
-<a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/pystatgrab/">mirror</a>.
-All downloads are pgp signed using our <a href="/pgpkey.xhtml">PGP Key</a>.
-</p>
-
-<p>
-For installation instructions see the README file
-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/py-statgrab">devel/py-statgrab</a>
-port to install pystatgrab (and libstatgrab) for you.
-</p>
-
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream pystatgrab homepage
+ </h1>
+ <div id="topnav">
+ <ul>
+ <li>
+ <a href="#news">News</a>
+ </li>
+ <li>
+ <a href="#what">What is pystatgrab?</a>
+ </li>
+ <li>
+ <a href="#download">Downloading</a>
+ </li>
+ </ul>
+ </div>
+ <h2>
+ <a id="news">News</a>
+ </h2>
+ <p>
+ To get notifications of new pystatgrab releases why not
+ subscribe to our project over on
+ <a href="http://freshmeat.net/projects/pystatgrab/">freshmeat</a>?
+ </p>
+ <h3>
+ Sunday 21 March 2004
+ </h3>
+ <p>
+ Version 0.1 of pystatgrab has been released.<br />
+ Download it
+ <a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/pystatgrab/pystatgrab-0.1.tar.gz">
+ here</a>.
+ </p>
+ <p>
+ This is the first release of pystatgrab; a set of Python
+ bindings for the <a href="/libstatgrab/">libstatgrab</a>
+ library. Although lacking in documentation, it's fairly
+ complete feature wise.
+ </p>
+ <h2>
+ <a id="what">What is pystatgrab?</a>
+ </h2>
+ <p>
+ pystatgrab is a set of Python bindings for the
+ <a href="/libstatgrab/">libstatgrab</a> library. It installs
+ as a module and provides a set of function calls with
+ identical names to the libstatgrab functions. The returned
+ data types also map logically on to the structures returned
+ by libstatgrab.
+ </p>
+ <p>
+ pystatgrab should work on any platform that libstatgrab
+ will work on. Currently, pystatgrab requires version 0.9 of
+ libstatgrab to function.
+ </p>
+ <h2>
+ <a id="download">Downloading</a>
+ </h2>
+ <p>
+ The latest version of pystatgrab can be downloaded from our
+ primary download
+ <a href="http://www.mirror.ac.uk/sites/ftp.i-scream.org/pub/i-scream/pystatgrab/">
+ mirror</a>. All downloads are pgp signed using our
+ <a href="/pgpkey.xhtml">PGP Key</a>.
+ </p>
+ <p>
+ For installation instructions see the README file 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/py-statgrab">
+ devel/py-statgrab</a> port to install pystatgrab (and
+ libstatgrab) for you.
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>skeleton</title>
+ <head>
+ <title>
+ skeleton
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">Skeleton Page</h1>
- <h2>Section</h2>
- <h3>Content</h3>
- <p>Body Text</p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ Skeleton Page
+ </h1>
+ <h2>
+ Section
+ </h2>
+ <h3>
+ Content
+ </h3>
+ <p>
+ Body Text
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
-<link rel="stylesheet" href="http://nwww.i-scream.org/styles/style.css" type="text/css" media="screen"/>
-<link rel="stylesheet" href="http://nwww.i-scream.org/styles/print.css" type="text/css" media="print"/>
+ <link rel="stylesheet" href="http://nwww.i-scream.org/styles/style.css" type="text/css" media="screen"/>
+ <link rel="stylesheet" href="http://nwww.i-scream.org/styles/print.css" type="text/css" media="print"/>
\ No newline at end of file
border-bottom: 1px solid #000066;
}
#contents pre {
- border-left: 2px solid #ffffff;
+ border-left: 2px solid #ff0000;
margin-left: 5px;
padding-left: 5px;
background: #f0f0f0;
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>i-scream support</title>
+ <head>
+ <title>
+ i-scream support
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
-<h1 class="top">i-scream Support</h1>
-
-<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.</p>
-
-<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>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ i-scream Support
+ </h1>
+ <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.
+ </p>
+ <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>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
<!--#include virtual="/doctype.inc" -->
-
-<head>
-<title>skeleton</title>
+ <head>
+ <title>
+ skeleton
+ </title>
<!--#include virtual="/style.inc" -->
-</head>
-
-<body>
-
-<div id="container">
-
-<div id="main">
-
+ </head>
+ <body>
+ <div id="container">
+ <div id="main">
<!--#include virtual="/header.inc" -->
-
-<div id="contents">
- <h1 class="top">Who We Are</h1>
-
- <p>
- We started out as a group of four final year <a href="http://www.cs.kent.ac.uk">Computer
- Science</a> students at the University of Kent doing our final year project. During that year
- we developed the <a href="/cms/">CMS</a> package more or less as it stands today.
- </p>
- <p>
- Since the end of that year we've had a few changes in members, but we're still developing
- software. We've taken the <a href="/cms/">CMS</a> and developed it further, and we've written
- libraries to support it. We're now working on a new system to replace it known currently as <a
- href="/laroona/">Laroona</a>.
- </p>
-
- <h2>Current team</h2>
-
- <p>
- <b>Tim Bishop</b> - tdb@i-scream.org
- </p>
- <ul>
- <li><a href="http://www.bishnet.net/tim/">Homepage</a></li>
- <li><a href="http://www.cs.kent.ac.uk/people/staff/tdb/">Work</a></li>
- <li><a href="http://www.bishnet.net/tim/cv.shtml">View my C.V.</a></li>
- </ul>
-
- <p>
- <b>Alex Moore</b> - ajm@i-scream.org
- </p>
-
- <p>
- <b>Adam Sampson</b> - ats@i-scream.org
- </p>
- <ul>
- <li><a href="http://www.offog.org/">Homepage</a></li>
- </ul>
-
- <p>
- <b>Peter Saunders</b> - pajs@i-scream.org
- </p>
- <ul>
- <li><a href="http://www.cs.kent.ac.uk/people/staff/pajs/">Work</a></li>
- </ul>
-
- <p>
- Group Mailing List - <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>
- </p>
-</div>
-
+ <div id="contents">
+ <h1 class="top">
+ Who We Are
+ </h1>
+ <p>
+ We started out as a group of four final year
+ <a href="http://www.cs.kent.ac.uk">Computer Science</a>
+ students at the University of Kent doing our final year
+ project. During that year we developed the
+ <a href="/cms/">CMS</a> package more or less as it stands
+ today.
+ </p>
+ <p>
+ Since the end of that year we've had a few changes in
+ members, but we're still developing software. We've taken
+ the <a href="/cms/">CMS</a> and developed it further, and
+ we've written libraries to support it. We're now working on
+ a new system to replace it known currently as
+ <a href="/laroona/">Laroona</a>.
+ </p>
+ <h2>
+ Current team
+ </h2>
+ <p>
+ <b>Tim Bishop</b> - tdb@i-scream.org
+ </p>
+ <ul>
+ <li>
+ <a href="http://www.bishnet.net/tim/">Homepage</a>
+ </li>
+ <li>
+ <a href="http://www.cs.kent.ac.uk/people/staff/tdb/">Work</a>
+ </li>
+ <li>
+ <a href="http://www.bishnet.net/tim/cv.shtml">View my
+ C.V.</a>
+ </li>
+ </ul>
+ <p>
+ <b>Alex Moore</b> - ajm@i-scream.org
+ </p>
+ <p>
+ <b>Adam Sampson</b> - ats@i-scream.org
+ </p>
+ <ul>
+ <li>
+ <a href="http://www.offog.org/">Homepage</a>
+ </li>
+ </ul>
+ <p>
+ <b>Peter Saunders</b> - pajs@i-scream.org
+ </p>
+ <ul>
+ <li>
+ <a href="http://www.cs.kent.ac.uk/people/staff/pajs/">Work</a>
+ </li>
+ </ul>
+ <p>
+ Group Mailing List -
+ <a href="mailto:dev@i-scream.org">dev@i-scream.org</a>
+ </p>
+ </div>
<!--#include virtual="/footer.inc" -->
-
-</div>
-
+ </div>
<!--#include virtual="/menu.inc" -->
-
-</div>
-
-</body>
+ </div>
+ </body>
</html>
i-scream / www.i-scream.org.git / commitdiff
