ALARMPROGRAM
Posted in 2000
Topics: Storage & Space Management, Server Administration
Hi,
Can the alarmprogram be used if LTAPEDEV is set to /dev/null? This is a
portion of my onconfig :
Diagnostics
MSGPATH /opt/informix/log/online.log # System message log file
path
CONSOLE /dev/console # System console message path
ALARMPROGRAM /opt/informix/etc/log_full.sh # Alarm program path
TBLSPACE_STATS 1 # Maintain tblspace statistics
# System Archive Tape Device
#TAPEDEV /dev/tapedev # Tape device path
TAPEDEV /dev/null # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape
(Kbytes)
# Log Archive Tape Device
#LTAPEDEV /dev/tapedev # Log tape device path
LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE
Thanks.
Marco
Sent via Deja.com http://www.deja.com/
Before you buy.
yes, the engine will still send the alarmprogram the documented messages.
the two are unrelated...
mdelerme@my-deja.com wrote:
> Hi,
>
> Can the alarmprogram be used if LTAPEDEV is set to /dev/null? This is a
> portion of my onconfig :
>
> Diagnostics
>
> MSGPATH /opt/informix/log/online.log # System message log file
> path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /opt/informix/etc/log_full.sh # Alarm program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics>
> # System Archive Tape Device
>
> #TAPEDEV /dev/tapedev # Tape device path
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape
> (Kbytes)>
> # Log Archive Tape Device
>
> #LTAPEDEV /dev/tapedev # Log tape device path
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE>
> Thanks.
>
> Marco
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
mdelerme@my-deja.com wrote:
> Hi,
>
> Can the alarmprogram be used if LTAPEDEV is set to /dev/null? This is a
> portion of my onconfig :
Yes, however, you do not NEED the ALARMPROGRAM to be set to log_full.sh
especially if you are trashing the logs to /dev/null. You can blank it
out, or substitute
some other program or script that will do more and ignore the Log Complete
messages that the log_full.sh script was designed exclusively to handle.
See my
eventalarm.c program that is designed to work as the ALARMPROGRAM which,
in addition to backing up the logical logs using ontape -a if LTAPEDEV is
NOT set
to /dev/null (yes it knows enough not to try if it IS set to /dev/null),
emails the
administrator(s) (my eventalarm.cfg actually specifies that it also email
my cell phone
so I can worry all the home in the evening until I can login and check it
out).
Eventalarm.c is part of my package utils3_ak available for download from
the IIUG
Software Repository.
Art S. Kagel
>
> Diagnostics
>
> MSGPATH /opt/informix/log/online.log # System message log file
> path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /opt/informix/etc/log_full.sh # Alarm program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics>
> # System Archive Tape Device
>
> #TAPEDEV /dev/tapedev # Tape device path
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape
> (Kbytes)>
> # Log Archive Tape Device
>
> #LTAPEDEV /dev/tapedev # Log tape device path
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE>
> Thanks.
>
> Marco
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.