diff --git a/doc/adminguide.html b/doc/adminguide.html index a4ecc781..2ff6e75f 100755 --- a/doc/adminguide.html +++ b/doc/adminguide.html @@ -39,16 +39,50 @@ ELOG is being developed and tested under Linux, and is being used on (Sparc) Solaris workstations. It should also compile and run on other UNIX flavours.

+ +


Installation from the RPM file:

+ +Since version 2.0, ELOG contains a RPM file which eases the installation. Get the +file elog-x.x.x-x.i386.rpm from the download +section and execute as root "rpm -i elog-x.x.x-x.i386.rpm". This will +install the elogd daemon in /usr/local/sbin +and the elog and elconv programs in +/usr/local/bin. The sample configuration file elogd.cfg +together with the sample logbook will be installed under /usr/local/elog +and the documentation goes to /usr/share/doc. The elogd startup script +will be installed at /etc/rc.d/init.d/elogd. To start the daemon, enter + + + +It will listen under the port specified in /usr/local/elog/elogd.cfg +which is 8080 by default. So one can connect using any browser with the URL: + + + +To start the daemon automatically, enter: +
+ + +which will start the daemon on run levels 3,4 and 5 after the next reboot. +

+ +


Installation from the tarball:

+ Download the latest elog-x.x.x.tar.gz package.

Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which -creates the executables elogd and elog -. These executables can then be copied to a convenient place like +creates the executables elogd, elog and +elconv. These executables can then be copied to a convenient place like /usr/local/bin or ~/bin. Alternatively, -a make install will copy these files to DESTDIR -which is defined in the Makefile. +a "make install" will copy the daemon elogd +to SDESTDIR (by default /usr/local/sbin) and +the other files to DESTDIR (by default /usr/local/bin). +These directories can be changed in the Makefile. The elogd executable can be started manually for testing with :

@@ -64,7 +98,7 @@ could be that the network is not started on the Linux box. This can be checked with the /sbin/ifconfig program, which must show that eth0 is up and running.

-The distribution contains a sample configuration file elogd and +The distribution contains a sample configuration file elogd.cfg and a demo logbook in the demo subdirectory. If the elogd server is started in the elogd-x.x.x directory, the demo logbook can be directly accessed with a browser by specifying the URL http://localhost:8080 @@ -72,7 +106,7 @@ accessed with a browser by specifying the URL http://localhost:8080 started in some other directory, you must specify the full path of the elogd file with the "-c" flag and change the Data dir = option in the configuration file to a full path like -/usr/local/elogdata. +/usr/local/elog.

Once testing is complete, elogd will typically be started with the -D flag to run as a daemon in the background, like this : @@ -95,12 +129,6 @@ where <logbook> is the name of the logbook. The contents of the all-important configuration file elogd.cfg are described below.

-To start the daemon automatically, it can be run from the /etc/rc.d/init.d -system. Please consult your distribution to find out how to do that. -
-Under RedHat 6.x. I use a script which I put under /etc/rc.d/init.d. Then I call : -

-

  Running elogd under Apache