Bug 1053641

Summary:	RFE: The imuxsock module doesn't support binding individual sockets to rulesets
Product:	Red Hat Enterprise Linux 7	Reporter:	Tomas Heinrich <theinric>
Component:	rsyslog	Assignee:	Jiří Vymazal <jvymazal>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	medium	Docs Contact:	Vladimír Slávik <vslavik>
Priority:	medium
Version:	7.0	CC:	dapospis, dkopecek, jvymazal, ksrot, lmiksik, pasik, pvrabec, rsroka
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rsyslog-8.24.0-6.el7	Doc Type:	Enhancement
Doc Text:	Feature: The imuxsock module is able to bind individual sockets to rulesets. Reason: Customer is unable to set ruleset per socket input. Result: Customer doesn't have to use the same ruleset for each socket input he needs. He is free to choose one for exact socket or use global one. Global ruleset can be override by that per socket ruleset --> per socket has higher priority.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 09:53:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1313490
Bug Blocks:

Description Tomas Heinrich 2014-01-15 14:52:39 UTC

Description of problem:
The mechanism of assigning a separate ruleset[1] for each input is not implemented for the imuxsock[2] module.

Version-Release number of selected component (if applicable):
rsyslog-7.4.7-1.el7

Expected results:
Each unix socket listener can be assigned a different ruleset.

Additional info:
imtcp and imudp already have this functionality.

[1] http://www.rsyslog.com/doc/multi_ruleset.html
[2] http://www.rsyslog.com/doc/imuxsock.html

Comment 7 Jiří Vymazal 2017-02-01 14:39:33 UTC

Starting with rsyslog 8.17.0 imuxsock supports binding rulesets so this will be fixed by the rebase

Comment 13 errata-xmlrpc 2017-08-01 09:53:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2306