From: Tim Bishop Date: Wed, 10 Mar 2004 08:55:09 +0000 (+0000) Subject: This commit was manufactured by cvs2git to create tag 'PRE_WWW_REDESIGN'. X-Git-Tag: PRE_WWW_REDESIGN X-Git-Url: http://git.i-scream.org/?a=commitdiff_plain;ds=sidebyside;h=0711ba384bc48a540904eace7a6effe9e7137ac4;hp=28fd2cb88214745644a1b92687899e6739de7289;p=www.i-scream.org.git This commit was manufactured by cvs2git to create tag 'PRE_WWW_REDESIGN'. Sprout from master 2004-03-10 08:55:08 UTC Tim Bishop 'Minor wording change.' Delete: www/cms/acknowledgements.shtml www/cms/documentation/gettingstarted.shtml www/cms/documentation/gettingstarted.xhtml www/cms/documentation/index.shtml www/cms/documentation/index.xhtml www/cms/downloads/index.shtml www/cms/features.shtml www/cms/features.xhtml www/cms/javadoc/index.shtml www/cms/javadoc/index.xhtml www/cms/minutes.shtml www/cms/minutes.xhtml www/cms/oldtodo.shtml www/cms/probdomain.shtml www/cms/projectpapers.shtml www/cms/projectpapers.xhtml www/cms/quotes.shtml www/cms/screenshots/alerter-email.gif www/cms/screenshots/alerter-irc.gif www/cms/screenshots/conient-config.gif www/cms/screenshots/conient-main.gif www/cms/screenshots/conient-platform-info.gif www/cms/screenshots/conient-queues.gif www/cms/screenshots/ihost-main.gif www/cms/screenshots/index.shtml www/cms/screenshots/index.xhtml www/cms/screenshots/reports-alerts-all.gif www/cms/screenshots/reports-main.gif www/cms/screenshots/reports-public-autoscroll.gif www/cms/screenshots/reports-raptor-latest-misc.gif www/cms/screenshots/reports-raptor-load15.gif www/cms/screenshots/reports-raptor-users.gif www/cms/screenshots/server-main.gif www/cms/screenshots/thumbnail-alerter-email.gif www/cms/screenshots/thumbnail-alerter-irc.gif www/cms/screenshots/thumbnail-conient-config.gif www/cms/screenshots/thumbnail-conient-main.gif www/cms/screenshots/thumbnail-conient-platform-info.gif www/cms/screenshots/thumbnail-conient-queues.gif www/cms/screenshots/thumbnail-ihost-main.gif www/cms/screenshots/thumbnail-reports-alerts-all.gif www/cms/screenshots/thumbnail-reports-main.gif www/cms/screenshots/thumbnail-reports-public-autoscroll.gif www/cms/screenshots/thumbnail-reports-raptor-latest-misc.gif www/cms/screenshots/thumbnail-reports-raptor-load15.gif www/cms/screenshots/thumbnail-reports-raptor-users.gif www/cms/screenshots/thumbnail-server-main.gif www/cms/screenshots/thumbnail-winhost-main.gif www/cms/screenshots/winhost-main.gif www/cms/todo.shtml www/cvs.xhtml www/images/freebsdlogo.gif www/images/freebsdlogo_small.gif www/index.xhtml www/libstatgrab/index.xhtml www/license.xhtml www/mailinglists.xhtml www/pgpkey.xhtml www/support.xhtml www/who.xhtml --- diff --git a/www/cms/acknowledgements.shtml b/www/cms/acknowledgements.shtml deleted file mode 100644 index 639bd12..0000000 --- a/www/cms/acknowledgements.shtml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - - - i-scream acknowledgements and credits - - - - - - - - - - - -
- - - - - - - -
-
- - - - -
-

Acknowledgements

- -

We would like to thank all of - those who have made the i-scream distributed central monitoring system - possible, namely the programmers and those who have assisted in - development by testing our software and offering feedback.

-

The i-scream central - monitoring system started off as a final year Computer Science group - project at the University of Kent at Canterbury, UK.  Since finishing - their degrees, the main programmers have continued to develop the - system 

-
-

The Server

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

ihost

-

Paul Mutton
- Pete Saunders
- Tim Bishop

-

WinHost

-

Paul Mutton

-

Web Reports

-

Paul Mutton
- Tim Bishop

-

Conient

-

Alex Moore

-

Website

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Historical Reports

-

Paul Mutton
- Tim Bishop

-

System-wide - Utilities

-

Alex Moore
- Paul Mutton
- Tim Bishop

-

Testing and Feedback

-

Adam Sampson
- Alex Moore
- Ash Beeson
- Fred Barnes
- Ian Utting
- John Cinnamond
- Mark Wheadon
- Paul Mutton
- Phill Camp
- Tim Bishop

-

Ideas and Support

-

John Cinnamond
- Phill Camp
- Mark Wheadon
- Ian Utting

-

 

-

We would also like to thank - the UKC Computer Science department and the UKC Templeman Library for - allowing us to run and test the project on their machines, and all those - people that have supported us along the way.

- Finally we wish to commend the creators of - JacORB, without which, the project would not have achieved the goals we set - out to reach.

-
- - - -
- - - - diff --git a/www/cms/documentation/gettingstarted.shtml b/www/cms/documentation/gettingstarted.shtml deleted file mode 100644 index 9230179..0000000 --- a/www/cms/documentation/gettingstarted.shtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - Getting Started with the i-scream Central Monitoring System - - - - - - - - - - -
- - - - - - -

Getting Started with the i-scream Central Monitoring System

- -

1. Installing the corba services (pre-requisite for the server)

-

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.

-

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.

-

1. Installing the server

-

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:

-

http://www.i-scream.org/downloads

-

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).

-

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.

-

2. Configuring the server

-

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.

-

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.

-

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.

-

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.

-

2a. Setting up the database

-

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.

-

3. Starting the server

-

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.

-

4. Setting up hosts

-

Hosts can be run on either Unix (tested with Solaris, FreeBSD and some -Linux distributions) or Windows. Both are equally easy to setup.

-

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:

-
-
ihost.pl server.domain.com port
- -

ihost will then contact the server to obtain it's configuration and start -sending information.

-

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.

-

Full details of both of these hosts can be found in the relevant -documentation on the website.

-

5. Using Conient

-

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.

-

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.

-

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.

-

Assuming data is displayed you have successfully setup the i-scream -central monitoring system. Well done!

-

This is explained in much more detail in the Conient documentation.

-

6. Setting up DBReporter

-

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.

-

Full instructions are available in the DBReporter documentation.

-

7. Setting up the Web Interface

-

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.

-

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.

-

Full instructions are available in the relevant documentation.

-

8. Further

-

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.

-

Some discussion about this is available in the server documentation.

-

If you have any questions about any of the above, please don't hesitate to -contact us at dev@i-scream.org. If you find we've missed something out, -again, please let us know.

-

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.

-

The i-scream team. - - - -

- - - diff --git a/www/cms/documentation/gettingstarted.xhtml b/www/cms/documentation/gettingstarted.xhtml deleted file mode 100644 index 9230179..0000000 --- a/www/cms/documentation/gettingstarted.xhtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - Getting Started with the i-scream Central Monitoring System - - - - - - - - - - -
- - - - - - -

Getting Started with the i-scream Central Monitoring System

- -

1. Installing the corba services (pre-requisite for the server)

-

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.

-

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.

-

1. Installing the server

-

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:

-

http://www.i-scream.org/downloads

-

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).

-

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.

-

2. Configuring the server

-

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.

-

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.

-

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.

-

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.

-

2a. Setting up the database

-

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.

-

3. Starting the server

-

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.

-

4. Setting up hosts

-

Hosts can be run on either Unix (tested with Solaris, FreeBSD and some -Linux distributions) or Windows. Both are equally easy to setup.

-

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:

-
-
ihost.pl server.domain.com port
- -

ihost will then contact the server to obtain it's configuration and start -sending information.

-

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.

-

Full details of both of these hosts can be found in the relevant -documentation on the website.

-

5. Using Conient

-

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.

-

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.

-

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.

-

Assuming data is displayed you have successfully setup the i-scream -central monitoring system. Well done!

-

This is explained in much more detail in the Conient documentation.

-

6. Setting up DBReporter

-

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.

-

Full instructions are available in the DBReporter documentation.

-

7. Setting up the Web Interface

-

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.

-

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.

-

Full instructions are available in the relevant documentation.

-

8. Further

-

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.

-

Some discussion about this is available in the server documentation.

-

If you have any questions about any of the above, please don't hesitate to -contact us at dev@i-scream.org. If you find we've missed something out, -again, please let us know.

-

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.

-

The i-scream team. - - - -

- - - diff --git a/www/cms/documentation/index.shtml b/www/cms/documentation/index.shtml deleted file mode 100644 index 6ff0e53..0000000 --- a/www/cms/documentation/index.shtml +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - i-scream documentation - - - - - - - - - - -
- - - - -

i-scream documentation

-

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.

- -

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.

- - -Commits to the "cms" CVS module since project completion (29/03/2001) - -
-

User guides

-(HTML) Getting Started with the i-scream Central Monitoring System
-(Word|PDF) Unix/Linux ihost user guide
-(Word|PDF) Windows WinHost user guide
-(Word|PDF) Conient client user guide
-(Word|PDF) Server user guide
-(Word|PDF) CORBA Services user guide
-(Word|PDF) Web reports user guide
-(Word|PDF) Database reporter user guide
- -

Maintenance documentation for developers

-(Word|PDF) Unix/Linux ihost maintenance
-(Word|PDF) Windows WinHost maintenance
-(Word|PDF) Conient maintenance
-(Word|PDF) Server maintenance
-(Word|PDF) Web reports maintenance
-(Word|PDF) Database reporter maintenance
- -

Specification documents

-(Word|PDF) Original specification & problem domain
-(Word|PDF) TCP Protocol specifications
-(Word|PDF) Expected XML data from host to server
-(Word|PDF) XML recommendations for host to server UDP packets
-(Word|PDF) Document standards
-(Word|PDF) Java coding standards
- -

Other documents

-(Word|PDF) Risk analysis
-(Word|PDF) Estimated time allocation
-(Word|PDF) Implementation phases for our plan
-(Word|PDF) Estimated time allocation (revised)
-(Word|PDF) Meeting Minutes
-(Word|PDF) Use of the website
-(Word|PDF) Use of CVS and automated software builds
-(Word|PDF) Comparison to Big Brother
-
-
- - -
- - - diff --git a/www/cms/documentation/index.xhtml b/www/cms/documentation/index.xhtml deleted file mode 100644 index 6ff0e53..0000000 --- a/www/cms/documentation/index.xhtml +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - - i-scream documentation - - - - - - - - - - -
- - - - -

i-scream documentation

-

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.

- -

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.

- - -Commits to the "cms" CVS module since project completion (29/03/2001) - -
-

User guides

-(HTML) Getting Started with the i-scream Central Monitoring System
-(Word|PDF) Unix/Linux ihost user guide
-(Word|PDF) Windows WinHost user guide
-(Word|PDF) Conient client user guide
-(Word|PDF) Server user guide
-(Word|PDF) CORBA Services user guide
-(Word|PDF) Web reports user guide
-(Word|PDF) Database reporter user guide
- -

Maintenance documentation for developers

-(Word|PDF) Unix/Linux ihost maintenance
-(Word|PDF) Windows WinHost maintenance
-(Word|PDF) Conient maintenance
-(Word|PDF) Server maintenance
-(Word|PDF) Web reports maintenance
-(Word|PDF) Database reporter maintenance
- -

Specification documents

-(Word|PDF) Original specification & problem domain
-(Word|PDF) TCP Protocol specifications
-(Word|PDF) Expected XML data from host to server
-(Word|PDF) XML recommendations for host to server UDP packets
-(Word|PDF) Document standards
-(Word|PDF) Java coding standards
- -

Other documents

-(Word|PDF) Risk analysis
-(Word|PDF) Estimated time allocation
-(Word|PDF) Implementation phases for our plan
-(Word|PDF) Estimated time allocation (revised)
-(Word|PDF) Meeting Minutes
-(Word|PDF) Use of the website
-(Word|PDF) Use of CVS and automated software builds
-(Word|PDF) Comparison to Big Brother
-
-
- - -
- - - diff --git a/www/cms/downloads/index.shtml b/www/cms/downloads/index.shtml deleted file mode 100644 index 4c19706..0000000 --- a/www/cms/downloads/index.shtml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - - - - - - i-scream software builds - - - - - - - - - - -
- - - - - - - - - - - - - - - - -
-

i-scream software builds

- -

All downloads are licensed under the GPL.

-

All new builds will be signed with our PGP key.

-
-
-

current builds

- -

These builds are the latest development working copies. They are much - more developed than the downloads you'll find below. We recommend you - start here. This is the codebase from which we'll make a proper release - sometime in the future.

-

Snapshot Server

-
-
-

old (but unchanging) builds

- -

These builds are from the end of the project. Development is still - continuing and can be found in the section above. These downloads are - not changing, and will not be updated until a release is made. Unless - you are really sure you want this version, get the one above. - -

Full documentation can be found by following the "Documentation" - link on the left-hand bar. Downloads below are the same, apart from - the archive format - with one exception being the host application.

- -

You will be asked to enter some basic information before - downloading, although this is purely optional. We value feedback - from people testing the i-scream products, so please feel free to - contact us at dev@i-scream.org.

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build nameWindows downloads
(.zip format)
Unix downloads
(.tar.gz format)
i-scream Conient (GUI client)download download
i-scream host applicationdownload download
i-scream serverdownload download
i-scream PHP web reportsdownload download
i-scream historical database reporterdownload download
CORBA services managerdownload download
- - -
- - - diff --git a/www/cms/features.shtml b/www/cms/features.shtml deleted file mode 100644 index 99dc0ba..0000000 --- a/www/cms/features.shtml +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - - - - Overview and Features - - - - - - - - - - - - -
- - - - - - - - -
- - -

Key Features of The System

- -
    -
  • A centrally stored, dynamically reloaded, system wide configuration system
  • -
  • 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.
  • -
  • Central server and reporting tools all Java based for multi-platform portability
  • -
  • 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.
  • -
  • 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.
  • -
  • One location for all system messages, despite being distributed.
  • -
  • XML data protocol used to make data processing and analysing easily extendable
  • -
  • 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.
  • -
  • Simple and open end protocols to allow easy extension and platform porting of Hosts - and Clients.
  • -
  • 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).
  • -
  • 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
  • -
  • Large overhead monitor Helpdesk style displays for latest Alerting information
  • -
- -

An Overview of the i-scream Central Monitoring System

- -

- 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. -

- -

- 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. -

- -

- 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. -

- -

- 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. -

-
-
- - -
- - - - diff --git a/www/cms/features.xhtml b/www/cms/features.xhtml deleted file mode 100644 index 99dc0ba..0000000 --- a/www/cms/features.xhtml +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - - - - Overview and Features - - - - - - - - - - - - -
- - - - - - - - -
- - -

Key Features of The System

- -
    -
  • A centrally stored, dynamically reloaded, system wide configuration system
  • -
  • 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.
  • -
  • Central server and reporting tools all Java based for multi-platform portability
  • -
  • 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.
  • -
  • 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.
  • -
  • One location for all system messages, despite being distributed.
  • -
  • XML data protocol used to make data processing and analysing easily extendable
  • -
  • 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.
  • -
  • Simple and open end protocols to allow easy extension and platform porting of Hosts - and Clients.
  • -
  • 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).
  • -
  • 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
  • -
  • Large overhead monitor Helpdesk style displays for latest Alerting information
  • -
- -

An Overview of the i-scream Central Monitoring System

- -

- 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. -

- -

- 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. -

- -

- 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. -

- -

- 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. -

-
-
- - -
- - - - diff --git a/www/cms/javadoc/index.shtml b/www/cms/javadoc/index.shtml deleted file mode 100644 index 87189ba..0000000 --- a/www/cms/javadoc/index.shtml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - - - i-scream javadoc pages - - - - - - - - - -
- - - - -

Java Source code documentation

- -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. - -

Server javadoc pages

-

Conient javadoc pages

-

Corba Service Manager javadoc pages

-

Util Package javadoc pages

- - -
- - - diff --git a/www/cms/javadoc/index.xhtml b/www/cms/javadoc/index.xhtml deleted file mode 100644 index 87189ba..0000000 --- a/www/cms/javadoc/index.xhtml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - - - i-scream javadoc pages - - - - - - - - - -
- - - - -

Java Source code documentation

- -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. - -

Server javadoc pages

-

Conient javadoc pages

-

Corba Service Manager javadoc pages

-

Util Package javadoc pages

- - -
- - - diff --git a/www/cms/minutes.shtml b/www/cms/minutes.shtml deleted file mode 100644 index dc73cb2..0000000 --- a/www/cms/minutes.shtml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - - - i-scream meeting minutes - - - - - - - - - - -
- - - - -

i-scream meeting minutes

- -

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.

- -
-
- - - - - -
-

March 2001

- 19 March 2001
- 12 March 2001
- 09 March 2001
- 05 March 2001 - -

February 2001

- 26 February 2001
- 19 February 2001
- 12 February 2001
- 05 February 2001
- -

January 2001

- 29 January 2001
- 22 January 2001
- 15 January 2001
- 08 January 2001 - -

December 2000

- 11 December 2000
- 04 December 2000
-

November 2000

- 29 November 2000 (Sub meeting)
- 29 November 2000
- 28 November 2000 (Sub meeting)
- 27 November 2000
- 22 November 2000
- 20 November 2000
- 16 November 2000 (Sub meeting)
- 15 November 2000
- 13 November 2000 (Sub meeting)
- 13 November 2000
- 08 November 2000
- 06 November 2000
- 01 November 2000
- -

October 2000

- 30 October 2000
- 23 October 2000
- 18 October 2000
- 17 October 2000
- 05 October 2000
- -

September 2000

- 28 September 2000 -
-
-
- - -
- - - diff --git a/www/cms/minutes.xhtml b/www/cms/minutes.xhtml deleted file mode 100644 index dc73cb2..0000000 --- a/www/cms/minutes.xhtml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - - - i-scream meeting minutes - - - - - - - - - - -
- - - - -

i-scream meeting minutes

- -

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.

- -
-
- - - - - -
-

March 2001

- 19 March 2001
- 12 March 2001
- 09 March 2001
- 05 March 2001 - -

February 2001

- 26 February 2001
- 19 February 2001
- 12 February 2001
- 05 February 2001
- -

January 2001

- 29 January 2001
- 22 January 2001
- 15 January 2001
- 08 January 2001 - -

December 2000

- 11 December 2000
- 04 December 2000
-

November 2000

- 29 November 2000 (Sub meeting)
- 29 November 2000
- 28 November 2000 (Sub meeting)
- 27 November 2000
- 22 November 2000
- 20 November 2000
- 16 November 2000 (Sub meeting)
- 15 November 2000
- 13 November 2000 (Sub meeting)
- 13 November 2000
- 08 November 2000
- 06 November 2000
- 01 November 2000
- -

October 2000

- 30 October 2000
- 23 October 2000
- 18 October 2000
- 17 October 2000
- 05 October 2000
- -

September 2000

- 28 September 2000 -
-
-
- - -
- - - diff --git a/www/cms/oldtodo.shtml b/www/cms/oldtodo.shtml deleted file mode 100644 index 4e96379..0000000 --- a/www/cms/oldtodo.shtml +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

(old) i-scream central monitoring system TODO list

- -This is the TODO list to be achieved by the end of the "project" period. -A -newer TODO list now exists to cover the future things -we plan to do with the development of the i-scream central monitoring system.

-Server

-
LocalClient Monitors: Users.
-
-Completed:
-----------
-22/03/2001 - FIX the major memory leak and deadlock issues.
-             LocalClient Monitors: Load, Processes, Queues.
-18/03/2001 - LocalClient Monitors: Disks/Memory need MB threshold
-15/03/2001 - Alert dumping needs to be organised better.
-             Running on Windows InetAddress.getHostName() doesn't return the FQDN.
-13/03/2001 - Thread naming, at least at a "what class it is" level.
-             Utilise the ConfigurationProxy throughout the server.
-             Sort out GC & Configuration objects (and CorbaHandlers).
-09/03/2001 - WebFeeder needs to dump Alerts to disk.
-08/03/2001 - WebFeeder needs to dump XML to disk
-             LocalClient Monitors: Disks, Service Checks
-07/03/2001 - Service Checks: FTP, POP3, IMAP, SSH, Telnet
-01/03/2001 - Make it easy to change flags to the java compiler.
-             Configuration groups need implementing.
-28/02/2001 - Queue identification ? Use a hash of the Queue ?
-             Fix the Queue "unlimited" size problem.
-27/02/2001 - (not needed) ClientInterface/DBInterface need to "pull" data ?
-             Builds on the website ?
-             Change build scripts to make iscream-server.java/tar.gz/zip
-25/02/2001 - Move checking of logging verbosity to the servant.
-23/02/2001 - print verbosity level with logging messages
-             functionality added to the LoggerServant
-23/02/2001 - Startup of components - eg. running DBInterface on another machine.
-             Now catches any problems relating to not finding a component if
-             a component has a dependancy.  The component manager will then
-             retry it after a given timeout.
-12/02/2001 - Logging of Queue.status() somehow.
-06/02/2001 - Make use of the PrintWriter "autoflush" feature :)
-28/01/2001 - Add dependency checking for the DOCOPY Makefile target.
-             Client Interface needs more functionality.
-             SQL Driver doesn't work in Windows.
-18/01/2001 - Heartbeats are still dropped.
-             CVS directories get added to build tar/zip file.
-             Problem on FreeBSD with zip file adding more files than it should.
-             Remove Component from util package -> ComponentManager.
-             Remove ReferenceManager from util package -> ComponentManager.
-             Add status methods to the Queue that return just values.
-             Clean up the util package, it shouldn't do logging etc.
-               -- done with the exception of ReferenceManager.
-16/01/2001 - Build a util package JAR file seperately.
-14/01/2001 - Javadoc pages on website ?
-               -- done for the server at least.
-12/01/2001 - Investigate the use of a Queue in the Filter, to replace the
-             current FilterThread setup.
-07/01/2001 - Makefile needs to copy non-java files to JAR (eg. images).
-02/01/2001 - Add making of Javadoc pages to make scripts.
-             Queuing system in the root filter.
-
- -

Conient

-
Completed:
-----------
-18/03/2001 - Switch to using the StringUtil class for the firewall command stuff.
-             Fix bug where it can take up to two packets to display
-             correct information.  This is most visible in service
-             checks, but can also be seen on disk, memory and anything
-             else that uses two data items from the packet for one
-             component.
-01/03/2001 - re-work host display and choosing mechanism (ie, make us 1.1 protocol)
-26/02/2001 - Rework system displaying of components for Swing Event Handling
-             Allow config to be written back to a local file
-             Allow local file config to be changed via the GUI
-05/02/2001 - allow disk components to alter their units
-             have some icons and the i-scream logo on display
-             show errors in windows rather than on the console
-             Fix error in packet stopping update of ALL hosts
-04/02/2001 - Write LOADS more data components
-03/02/2001 - Allow config to be obtained from the server
-30/01/2001 - Add option to handle firewalls
-29/01/2001 - Allow config to be obtained from a local file
-             Fix problem with memory display showing negative values at start
-             Ensure all Swing updates use the Swing Event Handling thread (partial - only data components)
-28/01/2001 - Tidy up network comms and link handling
-
- -

statgrab

-
Completed:
-----------
-20/03/2001 - Linux - CPU %'s not always right, 2 repititions ?
-19/03/2001 - Odd behaviour with more than 1000 processes, on Solaris at least
-             FreeBSD - grabbing memory total
-11/03/2001 - Solaris - If free memory changes to < 10Mb (?) it changes to K rather than M (thus not matched)
-
- -

C++ Host

-
UDP Packet size to 8Kb
-Porting to Linux/FreeBSD (Windows?)
-
- -

Winhost

-
Completed:
-----------
-19/03/2001 - Still needs to send the true uptime.
-             Processor ID should be packet.os.platform
-             Minor version joined with packet.os.version
-             Logo ? Pink icon ?
-             Solve OCX problem
-
- -

ihost

-
Completed:
-----------
-12/03/2001 - Produce a very quick "check script" which can be run by cron.
-
- -

Web Reports

-
Completed:
-----------
-22/03/2001 - Alert/System Summary Page (incl. helpdesk style)
-15/03/2001 - Individual Host Alert Summary Page(s)
-14/03/2001 - Individual Host Lastest Data Page(s) (including service checks)
-
- - -
- - - \ No newline at end of file diff --git a/www/cms/probdomain.shtml b/www/cms/probdomain.shtml deleted file mode 100644 index e62b53a..0000000 --- a/www/cms/probdomain.shtml +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - - The i-scream Project Problem Domain - - - - - - - - - - - - -
- - - - - - - - -
- - -

Original Problem

- -

- 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. -

- -

Centralised Machine Monitoring

- -

- 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. -

- -

- 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. -

- -

- 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. -

- -

- 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. -

- -

- John Cinnamond (email jc) whose idea this is, will provide technical - support for the project. -

- -
-
- - -
- - - - \ No newline at end of file diff --git a/www/cms/projectpapers.shtml b/www/cms/projectpapers.shtml deleted file mode 100644 index 4f81b07..0000000 --- a/www/cms/projectpapers.shtml +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - i-scream project papers & documentation - - - - - - - - - - -
- - - - -

i-scream project papers & documentation

- -

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.

- -
-
- - - - -
- - Feature List - the ongoing list of features
- - Time Allocation Plan - the course required us to produce a plan - of what we were going to spend time on
- - Implementation Phases - an initial plan of how we were going to - proceed with development
- - Documentation Strategy - documentation plan with status of each document
-
- - Realtime Spec Outline - an idea of how some parts of the system worked
- - Document Specs - requirements and specification for all documentation
- - XMLviaUDP Specs - format of data to be sent from hosts over UDP
- - System Configuration - details of the initial configuration system
- - Coding Standards - standards for Java code
- - Host: expected data - data the host is expected to send
- - Logging System - details of the logging system
- - Using the Queue - details of the queueing system
- - Protocol Specs - specifications of all the protocols used
-
- - Using CORBA - how to run the server in the corba environment
- - Using CVS (part 1) - how to use CVS (basic)
- - Using CVS (part 2) - how to use CVS (advanced)
- - WBEM, CIM? - some ideas about the WBEM technologies
-
-
-
- - -
- - - \ No newline at end of file diff --git a/www/cms/projectpapers.xhtml b/www/cms/projectpapers.xhtml deleted file mode 100644 index 4f81b07..0000000 --- a/www/cms/projectpapers.xhtml +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - i-scream project papers & documentation - - - - - - - - - - -
- - - - -

i-scream project papers & documentation

- -

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.

- -
-
- - - - -
- - Feature List - the ongoing list of features
- - Time Allocation Plan - the course required us to produce a plan - of what we were going to spend time on
- - Implementation Phases - an initial plan of how we were going to - proceed with development
- - Documentation Strategy - documentation plan with status of each document
-
- - Realtime Spec Outline - an idea of how some parts of the system worked
- - Document Specs - requirements and specification for all documentation
- - XMLviaUDP Specs - format of data to be sent from hosts over UDP
- - System Configuration - details of the initial configuration system
- - Coding Standards - standards for Java code
- - Host: expected data - data the host is expected to send
- - Logging System - details of the logging system
- - Using the Queue - details of the queueing system
- - Protocol Specs - specifications of all the protocols used
-
- - Using CORBA - how to run the server in the corba environment
- - Using CVS (part 1) - how to use CVS (basic)
- - Using CVS (part 2) - how to use CVS (advanced)
- - WBEM, CIM? - some ideas about the WBEM technologies
-
-
-
- - -
- - - \ No newline at end of file diff --git a/www/cms/quotes.shtml b/www/cms/quotes.shtml deleted file mode 100644 index c1a14dc..0000000 --- a/www/cms/quotes.shtml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - Memorable Project Quotes - - - - - - - - - - -
- - - - - -

Memorable Project Quotes

- -

-These are all genuine quotes that came about during our time -developing the i-scream server, hosts, clients and reporting -system. -

- -

-AJ doc'ing and taking the i-scream pun too far -

- "An i-scream client connects to the i-scream and ...." -
-

- -

-AJ -

- "I'm gonna be raptor! grr!" -
-

- -

-Tim -

- "I'm not going to draw on the board with some fizzy jerks." -
-

- -

-Tim -

- "It's just programming, innit?" -
-

- -

-Paul -

- "Let's sell one sock... Quality." -
-

- -

-Tim -

- "Break my hand... arghhh." -
-

- -

-AJ -

- "But we haven't got any children yet..." -
-

- -

-Tim -

- "Do you like my gender?" -
-

- -

-Paul -

- "Do away with the vowels, damnit. Oh, it's got a 'u' in it, hasn't it..." -
-

- -

-Tim -

- "Long is, in fact, long long." -
-

- -

-Paul -

- "And the fish do their little funky shit." -
-

- -

-Tim -

- "Bloody hell, what are your feet doing over here?!" -
-

- -

-Paul -

- "There's an 'L' in XML, isn't there?" -
-

- -

-AJ -

- "Yeah, we're not paying anything for it, either... we just pay them once a month." -
-

- -

-Ash -

- "Do you want some tissues now?" -
-

- - -

- - - - \ No newline at end of file diff --git a/www/cms/screenshots/alerter-email.gif b/www/cms/screenshots/alerter-email.gif deleted file mode 100644 index 456f270..0000000 Binary files a/www/cms/screenshots/alerter-email.gif and /dev/null differ diff --git a/www/cms/screenshots/alerter-irc.gif b/www/cms/screenshots/alerter-irc.gif deleted file mode 100644 index 01b935d..0000000 Binary files a/www/cms/screenshots/alerter-irc.gif and /dev/null differ diff --git a/www/cms/screenshots/conient-config.gif b/www/cms/screenshots/conient-config.gif deleted file mode 100644 index 13f9d7e..0000000 Binary files a/www/cms/screenshots/conient-config.gif and /dev/null differ diff --git a/www/cms/screenshots/conient-main.gif b/www/cms/screenshots/conient-main.gif deleted file mode 100644 index de70ef7..0000000 Binary files a/www/cms/screenshots/conient-main.gif and /dev/null differ diff --git a/www/cms/screenshots/conient-platform-info.gif b/www/cms/screenshots/conient-platform-info.gif deleted file mode 100644 index 052d06e..0000000 Binary files a/www/cms/screenshots/conient-platform-info.gif and /dev/null differ diff --git a/www/cms/screenshots/conient-queues.gif b/www/cms/screenshots/conient-queues.gif deleted file mode 100644 index 551f0d7..0000000 Binary files a/www/cms/screenshots/conient-queues.gif and /dev/null differ diff --git a/www/cms/screenshots/ihost-main.gif b/www/cms/screenshots/ihost-main.gif deleted file mode 100644 index 47e8ec1..0000000 Binary files a/www/cms/screenshots/ihost-main.gif and /dev/null differ diff --git a/www/cms/screenshots/index.shtml b/www/cms/screenshots/index.shtml deleted file mode 100644 index ef073f7..0000000 --- a/www/cms/screenshots/index.shtml +++ /dev/null @@ -1,241 +0,0 @@ - - - - - - - - i-scream screenshots / overview - - - - - - - - - - - - - -
- - - - - - - - -
-
- - - - -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

i-scream - screenshots

-

(or the two minute - tour)

- -

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.

-

 

click to enlarge! -

 

Reports Centre - (Web)
- 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.
-

 

click to enlarge! -

 

Latest Information - (Web)
- 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.
-

 

click to enlarge! -

 

Conient (Multiplatform - real-time client)
-
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. -

 

click to enlarge! -

 

Conient (Viewing - extra data)
- 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.
-

 

click to enlarge! -

 

Conient - (Configuration)
- 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.
-

 

click to enlarge! -

 

ihost (Unix/Linux - host)
- 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.
-

 

click to enlarge! -

 

WinHost (Windows - host)
- 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.
-

 

click to enlarge! -

 

Alerts (Email)
- 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.
-

 

click to enlarge! -

 

Alerts (IRC bot)
- 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.
-

 

click to enlarge! -

 

Alerts (Web page)
- 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.
-

 

click to enlarge! -

 

Alerts (Public - helpdesk display)
-
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. -

 

click to enlarge! -

 

Conient (Server queue - monitoring)
-
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. 
click to enlarge! -

 

Historical reports - (Web)
-
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. -

 

click to enlarge! -

 

Historical reports - (Metadata)
-
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. -

 

click to enlarge! -

 

The i-scream server
-
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 ;-) -

 

-
-
- - - - -
- - - diff --git a/www/cms/screenshots/index.xhtml b/www/cms/screenshots/index.xhtml deleted file mode 100644 index ef073f7..0000000 --- a/www/cms/screenshots/index.xhtml +++ /dev/null @@ -1,241 +0,0 @@ - - - - - - - - i-scream screenshots / overview - - - - - - - - - - - - - -
- - - - - - - - -
-
- - - - -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-

i-scream - screenshots

-

(or the two minute - tour)

- -

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.

-

 

click to enlarge! -

 

Reports Centre - (Web)
- 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.
-

 

click to enlarge! -

 

Latest Information - (Web)
- 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.
-

 

click to enlarge! -

 

Conient (Multiplatform - real-time client)
-
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. -

 

click to enlarge! -

 

Conient (Viewing - extra data)
- 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.
-

 

click to enlarge! -

 

Conient - (Configuration)
- 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.
-

 

click to enlarge! -

 

ihost (Unix/Linux - host)
- 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.
-

 

click to enlarge! -

 

WinHost (Windows - host)
- 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.
-

 

click to enlarge! -

 

Alerts (Email)
- 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.
-

 

click to enlarge! -

 

Alerts (IRC bot)
- 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.
-

 

click to enlarge! -

 

Alerts (Web page)
- 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.
-

 

click to enlarge! -

 

Alerts (Public - helpdesk display)
-
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. -

 

click to enlarge! -

 

Conient (Server queue - monitoring)
-
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. 
click to enlarge! -

 

Historical reports - (Web)
-
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. -

 

click to enlarge! -

 

Historical reports - (Metadata)
-
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. -

 

click to enlarge! -

 

The i-scream server
-
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 ;-) -

 

-
-
- - - - -
- - - diff --git a/www/cms/screenshots/reports-alerts-all.gif b/www/cms/screenshots/reports-alerts-all.gif deleted file mode 100644 index bbed02b..0000000 Binary files a/www/cms/screenshots/reports-alerts-all.gif and /dev/null differ diff --git a/www/cms/screenshots/reports-main.gif b/www/cms/screenshots/reports-main.gif deleted file mode 100644 index 3cc4c28..0000000 Binary files a/www/cms/screenshots/reports-main.gif and /dev/null differ diff --git a/www/cms/screenshots/reports-public-autoscroll.gif b/www/cms/screenshots/reports-public-autoscroll.gif deleted file mode 100644 index 366c76a..0000000 Binary files a/www/cms/screenshots/reports-public-autoscroll.gif and /dev/null differ diff --git a/www/cms/screenshots/reports-raptor-latest-misc.gif b/www/cms/screenshots/reports-raptor-latest-misc.gif deleted file mode 100644 index 2df5d54..0000000 Binary files a/www/cms/screenshots/reports-raptor-latest-misc.gif and /dev/null differ diff --git a/www/cms/screenshots/reports-raptor-load15.gif b/www/cms/screenshots/reports-raptor-load15.gif deleted file mode 100644 index 068fb9e..0000000 Binary files a/www/cms/screenshots/reports-raptor-load15.gif and /dev/null differ diff --git a/www/cms/screenshots/reports-raptor-users.gif b/www/cms/screenshots/reports-raptor-users.gif deleted file mode 100644 index 7a84e3e..0000000 Binary files a/www/cms/screenshots/reports-raptor-users.gif and /dev/null differ diff --git a/www/cms/screenshots/server-main.gif b/www/cms/screenshots/server-main.gif deleted file mode 100644 index 7622e14..0000000 Binary files a/www/cms/screenshots/server-main.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-alerter-email.gif b/www/cms/screenshots/thumbnail-alerter-email.gif deleted file mode 100644 index e6e93c1..0000000 Binary files a/www/cms/screenshots/thumbnail-alerter-email.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-alerter-irc.gif b/www/cms/screenshots/thumbnail-alerter-irc.gif deleted file mode 100644 index d652765..0000000 Binary files a/www/cms/screenshots/thumbnail-alerter-irc.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-conient-config.gif b/www/cms/screenshots/thumbnail-conient-config.gif deleted file mode 100644 index 7b851ec..0000000 Binary files a/www/cms/screenshots/thumbnail-conient-config.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-conient-main.gif b/www/cms/screenshots/thumbnail-conient-main.gif deleted file mode 100644 index 592331f..0000000 Binary files a/www/cms/screenshots/thumbnail-conient-main.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-conient-platform-info.gif b/www/cms/screenshots/thumbnail-conient-platform-info.gif deleted file mode 100644 index ffcd3b1..0000000 Binary files a/www/cms/screenshots/thumbnail-conient-platform-info.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-conient-queues.gif b/www/cms/screenshots/thumbnail-conient-queues.gif deleted file mode 100644 index adf3425..0000000 Binary files a/www/cms/screenshots/thumbnail-conient-queues.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-ihost-main.gif b/www/cms/screenshots/thumbnail-ihost-main.gif deleted file mode 100644 index 3f23760..0000000 Binary files a/www/cms/screenshots/thumbnail-ihost-main.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-alerts-all.gif b/www/cms/screenshots/thumbnail-reports-alerts-all.gif deleted file mode 100644 index 3396177..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-alerts-all.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-main.gif b/www/cms/screenshots/thumbnail-reports-main.gif deleted file mode 100644 index 1c8624e..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-main.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-public-autoscroll.gif b/www/cms/screenshots/thumbnail-reports-public-autoscroll.gif deleted file mode 100644 index 5ad6dcd..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-public-autoscroll.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-raptor-latest-misc.gif b/www/cms/screenshots/thumbnail-reports-raptor-latest-misc.gif deleted file mode 100644 index 31dab42..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-raptor-latest-misc.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-raptor-load15.gif b/www/cms/screenshots/thumbnail-reports-raptor-load15.gif deleted file mode 100644 index 0f45ac6..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-raptor-load15.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-reports-raptor-users.gif b/www/cms/screenshots/thumbnail-reports-raptor-users.gif deleted file mode 100644 index c87b4bf..0000000 Binary files a/www/cms/screenshots/thumbnail-reports-raptor-users.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-server-main.gif b/www/cms/screenshots/thumbnail-server-main.gif deleted file mode 100644 index fddaa67..0000000 Binary files a/www/cms/screenshots/thumbnail-server-main.gif and /dev/null differ diff --git a/www/cms/screenshots/thumbnail-winhost-main.gif b/www/cms/screenshots/thumbnail-winhost-main.gif deleted file mode 100644 index 44e595e..0000000 Binary files a/www/cms/screenshots/thumbnail-winhost-main.gif and /dev/null differ diff --git a/www/cms/screenshots/winhost-main.gif b/www/cms/screenshots/winhost-main.gif deleted file mode 100644 index 13ad719..0000000 Binary files a/www/cms/screenshots/winhost-main.gif and /dev/null differ diff --git a/www/cms/todo.shtml b/www/cms/todo.shtml deleted file mode 100644 index f706cfd..0000000 --- a/www/cms/todo.shtml +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - - - i-scream TODO list - - - - - - - - - -
- - - - -

i-scream central monitoring system TODO list

- -

This page lists the things we plan to do with the -i-scream central monitoring system in the future.

- -

TODO: -

    -
  • monitoring of users logging in & out
  • -
  • web-based configuration system
  • -
  • cleaner separation of some of the CORE functions (such as configuration - and logging) as independent services
  • -
  • grouping of hosts in frontends using server config groups
  • -
  • security of filters - ACL's
  • -
- -

To view the older TODO list from the project -please click here.

- - -
- - - diff --git a/www/cvs.xhtml b/www/cvs.xhtml deleted file mode 100644 index 90ff671..0000000 --- a/www/cvs.xhtml +++ /dev/null @@ -1,127 +0,0 @@ - - - - - - - - - i-scream cvs repository - - - - - - - - - - - -
- - - - - -

i-scream CVS Repository

- -

The i-scream CVS Repository contains all code, -documentation, and other files pertaining to all i-scream projects.

- -

All code available in the CVS Repository is -licensed under the GPL.

- -

Web Access

- -

We use viewcvs 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.

- -

http://cvs.i-scream.org/

- -

We also have a facility to allow people to keep tabs on what's changed -recently. The following are available:

- -

Commits today: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=today
-Commits this week: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=thisweek
-Commits in the past 7 days: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=days&days=7
-Commits made since 29/03/2001: http://www.i-scream.org/cgi-bin/cvslog.cgi?period=since&date=2001/03/29

- -

Anonymous CVS Access (read-only)

- -

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.

-
- -
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]
- - -

When asked for a password, simply press enter. -Replace [module] with the section you wish to checkout.

- -

Developer CVS Access (write)

- -

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.

-
- -
CVS_RSH = ssh
-CVSROOT = :ext:username@cvs.i-scream.org:/cvs/i-scream
- - -

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.

- -

After this you will be able to work with CVS as -normal.

- -

Other means of accessing CVS

- -

We currently provide CVSup 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;

-
- -
*default host=cvsup.i-scream.org
-*default base=/home/user/sup
-*default prefix=/home/user/i-scream
-*default release=cvs
-*default delete use-rel-suffix
-*default compress
-i-scream.cms.source tag=.
- - -

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.

- -

CVS Statistics

- -

There are some statistics available on the cms module of the CVS -repository, generated by cvsplot, -that allow you to see the progress of development. They're not that exciting, -but do show when the work was done.

- -

http://www.i-scream.org/cvsplot

- -
- - -
- - - - diff --git a/www/images/freebsdlogo.gif b/www/images/freebsdlogo.gif deleted file mode 100644 index 79948b6..0000000 Binary files a/www/images/freebsdlogo.gif and /dev/null differ diff --git a/www/images/freebsdlogo_small.gif b/www/images/freebsdlogo_small.gif deleted file mode 100644 index 882c6fe..0000000 Binary files a/www/images/freebsdlogo_small.gif and /dev/null differ diff --git a/www/index.xhtml b/www/index.xhtml deleted file mode 100644 index e3f44ff..0000000 --- a/www/index.xhtml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - - - - - The i-scream Project - - - - - - - - - - - -
- - - - - - - - -
- - - - \ No newline at end of file diff --git a/www/libstatgrab/index.xhtml b/www/libstatgrab/index.xhtml deleted file mode 100644 index ef0f8fc..0000000 --- a/www/libstatgrab/index.xhtml +++ /dev/null @@ -1,237 +0,0 @@ - - - - - - - - i-scream libstatgrab homepage - - - - - - - - - -
- - - - - - -

libstatgrab

- - - -

News

- -

-To get notifications of new libstatgrab releases why not subscribe -to our project over on -freshmeat? -

- -

-Wednesday 10 March 2004

-Version 0.9 of libstatgrab has been released.
-Download it -here. -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. -

- -

-Wednesday 11 February 2004

-Version 0.8.2 of libstatgrab has been released.
-Download it -here. -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. -

- -

-Wednesday 21 January 2004

-Version 0.8.1 of libstatgrab has been released.
-Download it -here. -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. -

- -

-Tuesday 6 January 2004

-Version 0.8 of libstatgrab has been released.
-Download it -here. -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. -

- -

-Wednesday 22 October 2003

-Version 0.7 of libstatgrab has been released.
-Download it -here. -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. -

- -

-Saturday 18 October 2003

-Version 0.6.1 of libstatgrab has been released.
-Download it -here. -This release brings support for FreeBSD 5 on sparc 64, and some -bugfixes in FreeBSD memory statistics. Also, some fixes to saidar, -and statgrab. -

- -

-Friday 10 October 2003

-Version 0.6 of libstatgrab has been released.
-You can download it from our mirror site -here. -This release includes some exciting new tools, support for FreeBSD -5.1, and documentation in manpages. Plus some major bugfixes and -packaging enhancements. -

- -

-Tuesday 09 September 2003

-We're pleased to announce a new release of libstatgrab.
-You can download version 0.5.1 from -here. -

- -

-Monday 25 August 2003

-We're pleased to announce a new release of libstatgrab.
-You can download version 0.5 from -here. -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. -

- -

What is libstatgrab?

- -

-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. -

- -

-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. -

- -

-The package also includes a couple of useful tools. The first, -saidar, 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 MRTG -configuration file to use statgrab. -

- -

Downloading

- -

-The latest version of libstatgrab can be downloaded from our -primary download -mirror. -All downloads are pgp signed using our PGP Key. -

- -

-For installation instructions see the README and INSTALL files -contained within the archive. If you're using -FreeBSD you can make use of the -devel/libstatgrab -port to install libstatgrab for you. -

- -

Documentation

- -

-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: - -

-

- -

-Then we have the manual pages for each function: - -

-

- -

Screenshot

- -

-Here's what saidar looks like when it's running: -

-

-saidar screenshot -

- -
- - -
- - - diff --git a/www/license.xhtml b/www/license.xhtml deleted file mode 100644 index 0acebd1..0000000 --- a/www/license.xhtml +++ /dev/null @@ -1,382 +0,0 @@ - - - - - - - - i-scream licensing - - - - - - - - - -
- - - - -

i-scream central monitoring system licensing

- -

-Unless explicitly mentioned the i-scream central monitoring system is -licensed under the GNU General Public License (GPL). The full license -can be found here, but -is also given below for reference. -

- -
-		    GNU GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-			    Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-		    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-			    NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-		     END OF TERMS AND CONDITIONS
-
-	    How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program; if not, write to the Free Software
-    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
-
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Library General
-Public License instead of this License.
-
- - -
- - - diff --git a/www/mailinglists.xhtml b/www/mailinglists.xhtml deleted file mode 100644 index bab6884..0000000 --- a/www/mailinglists.xhtml +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - - - - i-scream mailing lists - - - - - - - - - - - -
- - - - - -

i-scream Mailing Lists

- -

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.

- -

dev@i-scream.org

- -

-Information: http://lists.i-scream.org/mailman/listinfo/dev
-State: Closed
-Purpose: A discussion forum for developers only. This can also be used to -contact the development team as a whole. -

- -

commits@i-scream.org

- -

-Information: http://lists.i-scream.org/mailman/listinfo/commits
-State: Open for subscription, but no posts should be sent here.
-Purpose: 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. -

- -

cvs-all@i-scream.org

- -

-Information: http://lists.i-scream.org/mailman/listinfo/cvs-all
-State: Open for subscription, but no posts should be sent here.
-Purpose: 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. -

- -

users@i-scream.org

- -

-Information: http://lists.i-scream.org/mailman/listinfo/users
-State: Open for subscription and posts.
-Purpose: For discussion between users, developers, and anyone else. This is the -place to ask questions and get support. -

- -

Subscribing

- -

-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. -

- -

Archives

- -

-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. -

- -

Viruses and Spam

- -

-All lists are scanned using -MailScanner 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. -

- -
- - -
- - - - diff --git a/www/pgpkey.xhtml b/www/pgpkey.xhtml deleted file mode 100644 index 94a945e..0000000 --- a/www/pgpkey.xhtml +++ /dev/null @@ -1,68 +0,0 @@ - - - - - - - - i-scream developer pgp key - - - - - - - - - -
- - - - -

i-scream developer pgp key

- -

-This is the public key we use for signing i-scream -software releases.
You can also download a copy -here. -

- - - - - -
-
-
-
- -

i-scream automated build pgp key

- -

-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.
You can also download a copy -here. -

- - - - - -
-
-
-
- - -
- - - diff --git a/www/support.xhtml b/www/support.xhtml deleted file mode 100644 index eb070af..0000000 --- a/www/support.xhtml +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - - - - i-scream Support - - - - - - - - - - - -
- - - - - -

i-scream Support

- -

i-scream uses RT to track -support requests. We've set up two addresses to help seperate the two main -types of requests. - -

bugs@i-scream.org

- -

-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. -

- -

support@i-scream.org

- -

-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 -before sending us an email. -

- -

-Once your email has been received you will get an acknowledgement by -email and details of how to view your tickets over the web. -

- -
- - -
- - - - diff --git a/www/who.xhtml b/www/who.xhtml deleted file mode 100644 index 071aa10..0000000 --- a/www/who.xhtml +++ /dev/null @@ -1,88 +0,0 @@ - - - - - - - - - Who We Are - - - - - - - - - - - - -
- - - - - - - - -
- - -

Who We Are

- -

- We started as a group of four 3rd year - Computer Science students - at the University of Kent doing our final year project. Since - then we've had a few changes in developers, but we're moving - the project on. Here's who we are. -

- -

Current developers

- -

- Tim Bishop - tim@i-scream.org -

-

- -

- Alex Moore - aj@i-scream.org -

- -

- Adam Sampson - ats@i-scream.org -

-

- -

- Pete Saunders - pajs@i-scream.org -

-

- -

- Group Mailing List - dev@i-scream.org -

- -
-
- - -
- - - -