×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Important

   

This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 21.02. Open link

BMC PATROL Agent for BMC Helix Operations Management 21.02 ... Using Managing UNIX Environment variables

Operation of stored environment variables

The PATROL Agent inherits the environment of the shell in which it is started. The PATROL startup scripts, ./patrolrc.sh (Korn and Bourne shell) and ./.patrolrc (C shell), treat your user-defined shell script file as optional. If the user-defined shell script file exists, the startup script sources it after all other PATROL script processing. If it does not exist, the script continues. The startup script (patrolrc.sh and .patrolrc, respectively) is read by the ./Patrol and ./PatrolAgent scripts, which are usually used to start the console and agent, respectively.

Warning

To guarantee that the PATROL Agent and PATROL Console source the user-defined scripts (userrc.sh and .userrc) during startup, source the appropriate startup scripts (./patrol.sh and ./.patrolrc) before starting the agent and console.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Rashmi Gokhale on Oct 09, 2019
environment_variables

Comments

Log in or register to comment.

Purpose of storing environment variables
Supported file name and format for PATROL
© Copyright 2014 - 2021 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.