X-Git-Url: http://git.i-scream.org/?a=blobdiff_plain;ds=inline;f=www%2Fcontents.inc;fp=www%2Fcontents.inc;h=0000000000000000000000000000000000000000;hb=044ce3d999326b8748cd8f2821ed593298bb07ba;hp=5b6e4b55e53fb2e1ce315719f985bb258ddeb782;hpb=28fd2cb88214745644a1b92687899e6739de7289;p=www.i-scream.org.git diff --git a/www/contents.inc b/www/contents.inc deleted file mode 100644 index 5b6e4b5..0000000 --- a/www/contents.inc +++ /dev/null @@ -1,213 +0,0 @@ - - - -
-
-
- Project News
- Wednesday 10 March 2004
- Tuesday 15 July 2003
- Sunday 8 June 2003
- Tuesday 4 February 2003
- Saturday 1 June 2002
- Tuesday 21 May 2002
- Tuesday 8 Jan 2002 - About i-scream- - Details of the i-scream central monitoring system can be found - on the features and overview page. - A variety of screen shots from the - system show some of the key features in use. The reports demo - page provides a static example of what the i-scream reports (alerts, - historical graphs, and live data) could look like on a production system. - - -- - The latest source code is available in the CVS - repository, with binary downloads on the downloads page. The - documentation page has details of - installation, use and maintenance for the end user and developer. - We value feedback and comments from you, so please drop us an e-mail - to dev@i-scream.org. - - -- Current Work
- Extending monitoring facilites
- Server security
- Testing and Development - Project History- - The i-scream Distributed Central Monitoring System started off as - a final year project for a group of - Computer Science students at the - University of Kent at Canterbury, UK. The project was completed at - 4pm on 29 March 2001. It consisted of five lever-arch folders containing - mostly source code and documentation. The CVS repository was tagged to - signify this even, however, the project is still being developed by the - core development team. - - -- - As can be seen in our "problem domain" document, the project - was aimed at the UKC Computer Science department, and as such - we believed that a demonstration to the "customer" was important. The - feedback from our demonstation was more positive than we had - anticipated. We believe that the system may now be of interest - to anybody who wishes to monitor a number of machines on their - network using a central configuration. The i-scream central - monitoring system is now being used by the UKC Computer Science - department, and their feedback is being used to further improve - the product. - - -- - The name i-scream arose from a meeting whereupon one member - of the development team felt a strange urge to draw an ice cream on the discussion board. - It later became apparent that we had no name for our project (other - than 'The Project'). It seemed only natural to name our project after - the ice cream that had been oh-so-randomly drawn on the white board. - Copyright issues immediately ruled out anything involving Mr Whippy, - so we had to settle for i-scream. And thus, we were left with a cunning - play on words - it still sounded like ice cream, yet also - served as a functional description of our system - namely, one which - screams at somebody if something has gone wrong... - -- - - Searching i-scream |
-