Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-4253: dash.allinvoked parameter

Auditing and Monitoring Service ,  

12 April,16 at 11:14 AM

Applies to:
All versions of Centrify DirectAudit
What does the dash.allinvoked parameter do?
Are there any side effects when enabling or disabling that parameter in /etc/centrifyda/centrifyda.conf?
This configuration parameter was previously required to support auditing of shells invoked in scripts and is mainly for command-level auditing. 
This parameter is deprecated in DA 3.x and is not seen in /etc/centrifyda/centrifyda.conf but code honors it.

The side effect is it can cause heavy traffic for remote sessions if enabled (Note default is dash.allinvoked: true).
The parameter is no longer required and can be removed if you upgrade the agent to the latest version 3.x and enable auditing through NSS. 
If you do not update the agent, you can use this parameter to specify whether to audit all shell invocations. 
If set to true, all login and non-login shells are audited. 
If set to false, only login shells and login sub-shells are audited. If set to false, invoked shells are not audited. 
Note: dash.allinvoked work only for per-command auditing starting DA 3. 
The command dareload needs to be executed for changes to go into effect.