Installation guide

• Turn environmental monitoring on or off during the system boot.
• Start or stop the envmond daemon after the system boot.
• Specify the frequency between queries of the system by the envmond
daemon.
• Set the highest threshold level that can be encountered before a
temperature event is signaled by the envmond daemon. Specify the
path of a user defined script that you want the envmond daemon to
execute when a high threshold level is encountered.
• Specify the grace period allotted to save data if a shutdown message
has been broadcasted.
• Display the values of the Environmental Monitoring variables.
13.7.1.3 Customizing Environmental Monitoring Messages
You can modify any messages broadcast or logged by the Environmental
Monitoring utility. The messages are located in the file:
/usr/share/sysman/envmon/EnvMon_UserDefinable_Msg.tcl.You
must be root to edit this file and you can edit any message included in
braces ({}). The instructions for editing this file are included in the
comment (#) fields and you should avoid altering any other data in this file.
For example, you can change the messages to specify the system name
(host name) and location as shown in the following example:
1. Save the file
/usr/share/sysman/envmon/EnvMon_UserDefinable_Msg.tcl to
a holding file in case of editing errors.
2. Edit the file using the editor of your choice (the /usr/bin/dt/dtpad
editor in CDE, for example).
3. Search for instances of EnvmMon_Ovrstr and locate the associated
text string that is contained in braces ({}).
4. Modify the string as required. For example, prefix messages with the
host name and location of the system by changing message strings as
shown in the following samples
Current message:
set EnvmMon_Ovrstr(ENVMON_EVENT_SAFE_MSG) {System temperature is normal
Edited message:
set EnvmMon_Ovrstr(ENVMON_EVENT_SAFE_MSG) {System ntcstr5 in room 1 aisle 4 -
temperature is normal
5. Save the file and exit. You may want to run differences (diff) on the
files to ensure that no other changes were made as an error in this file
Administering Events and Errors 13–29