HP Insight Control Software for Linux - Manual (Page 193)

Options Defines generic information such as reconnection timeouts, FIFO size limits,
and so on.
Sources Defines the different sources from which messages are obtained.
Filters Defines the rules to segregate messages. For example, messages can be
separated by host, severity, facility, and so on.
Destinations Contains the devices and files where the messages are sent or saved.
Logs Combines the sources, filters, and destination into specific rules to handle the
different messages.
You can use a text editor such as emacs or vi to read the log files, and you can use a variety of
text manipulation commands to find, sort, and format these log files.
23.7.3 Modifying the syslog-ng rules files
Insight Control for Linux supplies a default configuration for the syslog-ng rules. You can modify
the syslog-ng rules configuration by modifying template files.
The syslog-ng rules are contained in the following template:
Global Template
Dictates the syslog-ng rules. The full path name is /opt/hptc/
syslog-ng/etc/global/syslog_ng_global_template
For more information on the parameters that make up these templates, see the syslog-ng
documentation at the following website:
http://www.balabit.com/products/syslog_ng/
The syslog-ng nconfigure script uses these template files to build the /opt/hptc/
syslog-ng/etc/syslog-ng/syslog-ng.conf
file.
To modify the syslog-ng rules, follow these steps:
1.
Log in to the CMS as root.
2. Change to the /opt/hptc/syslog-ng/etc directory:
# cd /opt/hptc/syslog-ng/etc
3. Make a backup copy of the template file:
# cp global/syslog_ng_global_template global/template_backup
4. Use a text editor to modify the template file.
5. Restart the syslog-ng service:
# /etc/init.d/syslog-ng restart
23.8 Changing the number of concurrent tasks
The number of concurrent tasks that Insight Control for Linux can run depends on the following:
•
The type of task being run.
Each task is assigned a certain weight value. The /opt/mx/icle/icelx.execution.xml
file lists the weight values for each type of task.
•
The value of MAX_CONCUR_CHAINS variable in the /opt/mx/icle/icle.properties
file.
The default value is 64.
The sum of the weight values for all the tasks running concurrently cannot exceed the value of the
MAX_CONCUR_CHAINS
variable.
For example, if you wanted to run several Deploy Linux Image tasks (each of these tasks
carries a weight of 6), the sum of the first ten tasks is 60. The eleventh task would exceed the value
of the MAX_CONCUR_CHAINS variable. That eleventh task remains in a Pending state until one of
the other running tasks completes.
23.8 Changing the number of concurrent tasks 193