AlarmMail command line options

Configuration Interface (AlarmMail -I)

The configuration interface allows enabling of specific alert message types for specified addresses. After settings are edited and saved the AlarmMail process will re-read the configuration database and apply the changes. Subsequent generated alert messages are sent to those users enabled to receive such messages. .

The alert types are as follows :

1. Alerts A, C, D and G – Exceedance.

2. Alert B – Ellipse Boundaries.

3. Alert F – Step Change

4. Alert H – Gradient

5. Alert P – Prodict

Alert A :- Level Exceedance

Five warning amplitude levels and five alarm amplitude levels are available for each dynamic channel of each plant item. They correspond to the alert levels for each of the first 4 orders and the overall level.

Alert B :- Ellipse Boundary

A warning and alarm elliptical boundary are available for each of the first 4 orders. Boundaries are defined in terms of the ellipse centre (X_ref,Y_ref), the length of the major and minor axes (major, minor) and the orientation angle of the major axis (angle).

Alert C :- Non-synchronous vibration not measured in the standard components

A warning and alarm difference level are available for each dynamic channel of each plant item. The measurement is the difference between the overall level and the summation of the amplitude levels of the first 4 orders and the subsynchronous component.

Alert D :- Subsynchronous Amplitude Level

Identical to Alert A but corresponding to the subsynchronous component.

Alert F :- Step Change

A warning and alarm level corresponding to changes in the average level for each of the first 4 orders and the overall level.

Alert G :- Special Order Alert

Identical to Alert A but corresponding the special fifth order. This may be any order and by default is 5. Care must be taken when specifying this order (using Config process) as the highest order available is dictated by the number of samples acquired per revolution of the plant item.

Alert H :- Gradient Alert

The user specifies the maximum gradient for a particular channel and parameter over a specified bnumber of days. If the average rate of increase for that channel and parameter is found to be greater than that specified then an alarm is generated.

Alert P :- Proclass Alert

A multi-parameter enhancement to the elliptical boundary alarms described above (Alert B ). Historical data is analysed and machine states identified using Bayesian classification techniques for multiple static channels. For each of these states vibration data is identified and alarm boundaries calculated.

In order to run the Apache web server on a system you will firstly need to install the suitable RPM using a command of the form:

rpm --install --nodeps --replacefiles --replacepkgs  apache-1.3.23-11.i386.rpm

Installation of the RPM creates the binary

 /usr/sbin/httpd

and the setup and configuration directory

 /etc/httpd

the default access directories

 /var/www

and the service startup,stop and restart script

 /etc/init.d/httpd

Configuration

The main configuration of apache is controlled by the file /etc/httpd/conf/httpd.conf. The most probable options which will need changing are likely to be :

 *DocumentRoot

The root directory for all files to be accessed is defined. By default this is set to /var/www/html

 *Alias

A number of aliases may be created ( relative to DocumentRoot) these are typically cgi-bin and icons. A further alias for images is often useful.

 *Directory

A number of <Directory> </Directory> blocks are included to define access information associated with individual directories. For each directory block a number of options may be defined. Options which often need adding are :

     ExecCGI          to enable execution of cgi scripts especially

                      for directory /var/www/cgi-bin

     FollowSymLinks   to follow symbolic links. Again needed for

                      /var/www/cgi-bin if CGI scripts are links to

                      pl files.

Startup

You can startup the server using the command

service httpd start

User Files

A simple way of accessing a users set of files is to create a directory within the users directory such as :

      /home/protor/website

and then to create a link to this directory from within the document root.

      cd /var/www/html

      ln -s /home/protor/website protor

You may then access any user files by starting a web browser and pointing to the URL:

       http://localhost/protor

This problem was resolved by disabling Direct Rendering for this particular graphics card.

This is done by editting the file /etc/X11/XF96Config-4 . Find the Module section. Comment out the option to Load dri or direct rendering. You may also comment out support for OpenGL with the command Load glx.

        Section "Module"
                Load  "GLcore"
                Load  "dbe"
                Load  "extmod"
                Load  "fbdevhw"
#               Load  "dri"
#               Load  "glx"
                Load  "pex5"
                Load  "record"
                Load  "xie"
        EndSection

Read the full article here (PDF)

Read the full article here (PDF)

The choice of Display Manager is specified within the file /etc/sysconfig/desktop.

By default this file simply contains the line

        Desktop=""

On startup of X for RedHat 7.2 this will by default start the GDM Display Manager.

Edit this file to control the Display Manager to start. Use

         Desktop = "KDE"               to start KDM

         Desktop = "GNOME"             to explicitly start GDM

         Desktop = AnotherLevel        to start XDM

If using XDM then the appearance of the login box is controlled by the file /etc/X11/xdm/Xresources . To improve the appearance of the login box edit this file and remove references to the XFree86 logos.

The selection and startup of an appropriate display manager is controlled by the script /etc/X11/prefdm which is referenced from /etc/inittab. On later versions of Redhat, references to AnotherLevel and hence the startup of XDM are removed. See the additional note on configuring /etc/X11/prefdm for XDM.

The following example shows the procedures required to create a boot sector file from a Linux system and how to modify the NT Boot Loader configuration to add an option to boot Linux. This example assumes that Windows NT has been loaded onto the first partition on the hard disk ( C:\ ). The disk has been partitioned such that Linux is loaded onto the second partion ( /dev/hda2 ) with a Linux swap partition on a third ( /dev/hda3 ).

It is advisable to ensure you have Windows NT repair disks for the system before proceeding.

Linux Details

Assuming Linux has been loaded and configured it is advisable , before starting this process , to test the system by creating a boot floppy and checking that the system boots OK before continuing. Also check at this stage that you can still boot Windows NT. We now need to prepare a boot sector for Linux from the system. The best way of doing this is to use the Linux Loader (LILO). For this example configuration, Windows NT owns the system’s Master Boot Record (MBR) and we do not wish to overwrite this with LILO. Modify the LILO configuration file /etc/lilo.conf so that it looks something like :

     delay=5
     boot=/dev/hda2
     map=/boot/map
     install=/boot/boot.b
     linear
     image=/boot/vmlinuz-2.4.7-10
          label=linux
          initrd=/boot/initrd-2.4.7-10.img
          read-only
          root=/dev/hda2

The main things to check are that the boot-device and root device are both set to point to your Linux installation ( /dev/hda2 in this example ). This ensured that LILO will create the boot sector on our second partition and will not touch the Master Boot Record.The other items are system specific. You may find that you need the linear or the lba32 option when using a large capacity harddisk. Now run LILO and check that there are no errors. We can now strip the bootsector from our second partition with the command.

               dd if=/dev/hda2 of=bootsect.lnx bs=512 count=1

Now copy this file to the Windows NT partition either by mounting the partition or by using an MS-DOS formatted floppy.

Windows NT Details

The Windows NT Boot Loader is controlled by the file C:\BOOT.INI. This file will have attributes set so that it is read-only and hidden. In order to change this file then you will need to issue the command:

               attrib -s -h -r c:\boot.ini

The file should look something like :

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT
    Workstation Version 4.00"
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT
    Workstation Version 4.00 [VGA mode]" /basevideo /sos

You can now edit the file using a suitable text editor such as notepad. Assuming we have copied the Linux bootsector file we created above to C:\ then modify this file to add the option to boot Linux.

    [boot loader]
    timeout=30
    default=C:\BOOTSECT.LNX
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT
    Workstation Version 4.00"
    multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT
    Workstation Version 4.00 [VGA mode]" /basevideo /sos
    C:\BOOTSECT.LNX="PROTOR (Linux)"

Note that we have also changed the default line so that the system boots Linux by default.

You now need to set back the attributes on the boot.ini file.

           attrib +s +h +r c:\boot.ini

When the system next boots then you should see the NT Boot Loader menu which will contain three options. Booting Linux will be the third option and will also be the default if no action is taken within 30 seconds.

Read the full article here (PDF)