File: omprog-binary.rst

package info (click to toggle)
rsyslog 8.2512.0-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 30,464 kB
  • sloc: ansic: 123,809; sh: 42,109; makefile: 5,962; javascript: 1,842; python: 1,222; lex: 607; yacc: 193; perl: 162; sql: 103; tcl: 9; ruby: 2
file content (57 lines) | stat: -rw-r--r-- 1,406 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
.. _param-omprog-binary:
.. _omprog.parameter.action.binary:

binary
======

.. index::
   single: omprog; binary
   single: binary

.. summary-start

Specifies the command line of the external program to execute.

.. summary-end

This parameter applies to :doc:`../../configuration/modules/omprog`.

:Name: binary
:Scope: action
:Type: string
:Default: none
:Required?: yes
:Introduced: at least 5.x, possibly earlier

Description
-----------
Full path and command line parameters of the external program to execute.
Arbitrary external programs should be placed under the /usr/libexec/rsyslog directory.
That is, the binaries put in this namespaced directory are meant for the consumption
of rsyslog, and are not intended to be executed by users.
In legacy config, it is **not possible** to specify command line parameters.

Action usage
------------
.. _param-omprog-action-binary:
.. _omprog.parameter.action.binary-usage:

.. code-block:: rsyslog

   action(type="omprog" binary="/usr/libexec/rsyslog/log.sh")

Legacy names (for reference)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Historic names/directives for compatibility. Do not use in new configs.

.. _omprog.parameter.legacy.actionomprogbinary:

- $ActionOMProgBinary — maps to binary (status: legacy)

.. index::
   single: omprog; $ActionOMProgBinary
   single: $ActionOMProgBinary

See also
--------
See also :doc:`../../configuration/modules/omprog`.