How does km itm monitor start and stop command records

This article mainly introduces km itm how to monitor the start and stop command records, the article is very detailed, has a certain reference value, interested friends must read it!

AIX CVM PatrolAgent start and stop method:

Start:

a. Log in to the managed host with the monitoring user (itm6) (after logging in, you will directly enter the Patrol home directory)

The form of monitoring directory is: * / bmc/Patrol3

B. ps-ef | grep Patrol checks whether the Patrol process exists. If it does not exist, execute step c

c. Run: PatrolAgent starts the monitoring agent

Stop:

a. To monitor whether the user logs in to the managed host (ps-ef | grep Patrol checks whether the Patrol process exists)

b. Run: pconfig + KILL command

c. Execute: ps-ef | grep Patrol

d. Drop the remaining snmpmagt process kill-9

E. Ps-ef | grep Patrol checks whether Agent is stopped.

Or

# su-itm6

$pwd

/ opt/bmc/Patrol3

$. / ctrl_scripts.sh-a stop stops monitoring

$ps-ef | grep java this monitor cannot be killed with KILL-9. It will soon force itself to start a JAVA process.

$id

Uid=205 (itm6) gid=1 (staff) groups=4 (adm)

$PatrolAgent starts monitoring

$ps-ef | grep Patrol

Windows CVM PatrolAgent start and stop method:

Start:

a. To monitor the user to log in to the managed host

b. Start the service (local) to check if the PatrolAgent process exists

c. Run: PatrolAgent starts the monitoring agent

Stop:

a. To monitor the user to log in to the managed host

b. Start the service (local) and stop the PatrolAgent process

The above is all the contents of the article "how km itm monitors start and stop command records". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!