IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей

Страница: 203 / 310

this problem, ensure that the
secureMain lock
command with the -g option has
been previously run. See the "Securing your IBM Tivoli Monitoring installation on
Linux or UNIX" appendix in the IBM Tivoli Monitoring Installation and Setup
Guide for further details.
If the agent is running as root, and that is not the desired user ID, then use the
following steps to restart the agent:
1. Log in as root.
2. Run the itmcmd agent stop command.
3. Log in (or 'su') to the user ID that you want the agent to run as.
4.
Run the
itmcmd agent start
command.
If the agent was running as root because of a system reboot, then complete the
following steps so that the appropriate user ID is used the next time the system is
rebooted. Editing the startup file is no longer supported. Instead you must modify
the
config/kcirunas.cfg
file and then run
bin/UpdateAutoRun.sh
:
1. Edit
install_dir/config/kcirunas.cfg
.
2. Add a section, after the
agent
line, to specify the agent or agent instance that
you want to start as a specific user ID. To specify the user ID to start a
non-instance agent, or to start all instances of an agent, use the following
syntax:
<productCode>product_code</productCode>
<default>
<user>user_name</user>
</default>
To specify different user IDs to start different instances of an agent, use the
following syntax:
<productCode>product_code</productCode>
<instance>
<name>instance_name1</name>
<user>user_name</user>
</instance>
<instance>
<name>instance_name2</name>
<user>user_name</user>
</instance>
Where:
product_code
2-character product code for the agent, for example,
ux
for the Unix OS
monitoring agent.
user_name
Name of the user to run the agent as.
instance_name1
Name of an instance.
instance_name2
Name of another instance.
Examples:
For the Unix OS monitoring agent, to run as itmuser:
Chapter 10. Monitoring agent troubleshooting
185