When changes to the configuration take effect


Every operation that changes the configuration of a PATROL Agent also changes the data and index configuration files and the variables in the agent's memory. The new variables take effect immediately. Such changes, however, do not affect variables that must be acted upon at startup.

The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.

List of variables that require the PATROL Agent to be restarted
  • /AgentSetup/preloadedKMsArch
  • /AgentSetup/defaultAccount
  • /AgentSetup/disabledKMs
  • /AgentSetup/accessControlList
  • /AgentSetup/accessDenyList
  • /AgentSetup/sessionsInitMayFail
  • /AgentSetup/defaultDisplay
  • /AgentSetup/pemEvMemRetention
  • /AgentSetup/pemLogName
  • /AgentSetup/PslDebug
  • /AgentSetup/SnmpConfigAccess
  • /AgentSetup/MatchShortHostName
  • /AgentSetup/msvcrtMinVer
  • /AgentSetup/VmsPtdBufferSize
  • /AgentSetup/VmsPtdInitAlloc
  • /AgentSetup/VmsPtdIncrAlloc
  • /AgentSetup/hostLookupCacheSize
  • /AgentSetup/EnableSysOutputAclCheck
  • /AgentSetup/maxOutboundRemoteSessions
Warning

Do not use the PATROL console to edit the /AgentSetup/defaultAccount and OSdefaultAccount variables. For more information about default account variables, see Modifying the default account variable.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*