Legacy Configuration Directives

All legacy configuration directives need to be specified on a line by their own and must start with a dollar-sign.

Note that legacy configuration directives that set object options (e.g. for inputs or actions) only affect those objects that are defined via legacy constructs. Objects defined via new-style RainerScript objects (e.g. action(), input()) are not affected by legacy directives. The reason is that otherwise we would again have the ability to mess up a configuration file with hard to understand constructs. This is avoided by not permitting to mix and match the way object values are set.

• Configuration Parameter Types
• Legacy Global Configuration Statements
  • True Global Directives
  • main queue specific Directives
• Legacy Directives affecting Input Modules
  • Legacy Directives affecting multiple Input Modules
  • immark-specific Directives
• Legacy Action-Specific Configuration Statements
  • Generic action configuration Statements
  • omfile-specific Configuration Statements
  • omfwd-specific Configuration Statements
  • omgssapi-specific Configuration Statements
  • action-queue specific Configuration Statements
• Ruleset-Specific Legacy Configuration Statements
  • $RulesetCreateMainQueue
  • $RulesetParser

See also

Help with configuring/using Rsyslog:

• Mailing list - best route for general questions
• GitHub: rsyslog source project - detailed questions, reporting issues that are believed to be bugs with Rsyslog
• Stack Exchange (View, Ask) - experimental support from rsyslog community

See also

Contributing to Rsyslog:

• Source project: rsyslog project README.
• Documentation: rsyslog-doc project README