1 |
i-scream central monitoring system - idar README |
2 |
http://www.i-scream.org.uk |
3 |
|
4 |
$Id: README,v 1.1 2003/03/29 19:27:36 tdb Exp $ |
5 |
|
6 |
Description |
7 |
----------- |
8 |
|
9 |
idar is an i-scream client. |
10 |
|
11 |
Building and Installation |
12 |
------------------------- |
13 |
|
14 |
First download and install libxml2 and libukcprog. libxml2 is available |
15 |
from www.xmlsoft.org. libukcprog should be available from the same |
16 |
place as idar. curses/ncurses is also required, but should be standard |
17 |
on most systems. |
18 |
|
19 |
After downloading and extracting idar, configure and build as follows; |
20 |
|
21 |
./configure |
22 |
make |
23 |
|
24 |
Then install as root; |
25 |
|
26 |
make install |
27 |
|
28 |
You may wish to use one of the following configure options to change |
29 |
aspects of this process; |
30 |
|
31 |
--with-libukcprog-prefix=PATH |
32 |
--with-curses-prefix=PATH |
33 |
--with-xml-prefix=PFX |
34 |
--with-ncurses |
35 |
|
36 |
The first three should be used if any of the required libraries are |
37 |
installed in non-standard locations. The last one insists on ncurses |
38 |
(curses is used by default). |
39 |
|
40 |
There are, of course, the usual GNU-style configure options; |
41 |
|
42 |
--prefix=PREFIX |
43 |
|
44 |
For more documentation on the installation process, please read the |
45 |
INSTALL document. |
46 |
|
47 |
Running idar |
48 |
------------ |
49 |
|
50 |
Running idar with the -h flag will provide a list of options. You will |
51 |
need to know the address and port number of your i-scream server. |
52 |
These details should be given on the command line to idar. |
53 |
|
54 |
Problems? |
55 |
--------- |
56 |
|
57 |
Please send all questions, problems, and bugs to dev@i-scream.org.uk. We |
58 |
will do our best to help. |
59 |
|
60 |
Thank-you for using i-scream software. |