Use this documentation with care! It describes
the heavily outdated version 5, which was actively
developed around 2010 and is considered dead by the
rsyslog team for many years now.
This documentation reflects the latest update of the previously existing (now removed) v5-stable branch. It describes the 5.10.2 version, which was never released. As such, it contains some content that does not apply to any released version.
To obtain the doc that properly matches your installed v5 version, obtain the doc set from your distro. Each version of rsyslog contained the version that exactly matches it.
As general advise, it is strongly suggested to upgrade to the current version supported by the rsyslog project. The current version can always be found on the right-hand side info box on the rsyslog web site.
Note that there is no rsyslog community support available for this heavily outdated version. If you need to stick with it, please ask your distribution for support.
omuxsock: Unix sockets Output Module¶
Module Name: omuxsock
**Available since: ** 4.7.3, 5.5.7
Author:Rainer Gerhards <email@example.com>
This module supports sending syslog messages to local Unix sockets. Thus it provided a fast message-passing interface between different rsyslog instances. The counterpart to omuxsock is imuxsock. Note that the template used together with omuxsock must be suitable to be processed by the receiver.
- $OMUxSockSocket Name of the socket to send data to. This has no default and must be set.
- $OMUxSockDefaultTemplate This can be used to override the default template to be used together with omuxsock. This is primarily useful if there are many forwarding actions and each of them should use the same template.
Currently, only datagram sockets are supported.
The following sample writes all messages to the “/tmp/socksample” socket.
$ModLoad omucsock $OMUxSockSocket /tmp/socksample *.* :omuxsock:
This documentation is part of the rsyslog project.