1 |
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
2 |
|
|
3 |
|
<!-- |
4 |
< |
probdomain.shtml |
5 |
< |
Created by tdb1 30/10/2000 |
6 |
< |
Last edited 30/10/2000 |
4 |
> |
$Author$ |
5 |
> |
$Id$ |
6 |
|
--> |
7 |
|
|
8 |
|
|
33 |
|
<center><h3>Original Problem</h3></center> |
34 |
|
|
35 |
|
<p align="justify"> |
36 |
< |
This is the original specification we were given when we took |
37 |
< |
on the project, and it seems an ideal basis for the problem |
38 |
< |
domain. |
36 |
> |
This is the original specification given to us when we |
37 |
> |
started the project. The i-scream central monitoring |
38 |
> |
system meets this specification, and aims to extend it |
39 |
> |
further. This is, however, where it all began. |
40 |
|
</p> |
41 |
|
|
42 |
|
<center><h3>Centralised Machine Monitoring</h3></center> |
43 |
|
|
44 |
|
<p align="justify"> |
45 |
< |
The Computer Science deparment has a number of different machines |
45 |
> |
The Computer Science department has a number of different machines |
46 |
|
running a variety of different operating systems. One of the tasks |
47 |
|
of the systems administrators is to make sure that the machines |
48 |
|
don't run out of resources. This involves watching processor loads, |