Add new functionality for omuxsock in rsyslog - #18262
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
1267509 to
7f3d60b
Compare
|
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
- Changes looks good.
- All three upstream patches apply cleanly.
- The upstream unit tests pass successfully when run in a privileged container with Valgrind installed and rsyslog built using the --enable-valgrind option.
- The new functionality introduced by the upstream PR works as expected.
- Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1174345&view=results
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
net: Add NetworkNamespace APIs Moves network namespace management logic out of individual plugins and into rsyslog's shared net module as reusable APIs, so any plugin can switch into a Linux network namespace to open a socket without duplicating the code.
add-network-namespace-APIs.patch:New functionality for omuxsock Upgrades the omuxsock output plugin to support abstract Unix socket names, connection-oriented sockets (STREAM/SEQPACKET), and sending log messages into a different Linux network namespace, while also fixing a bug that caused the socket to be unnecessarily closed and reopened for every message.
adding-new-functionality-for-omuxsock.patch:[Fix message loss for connected Unix domain sockets] Fixes a regression where an omuxsock STREAM or SEQPACKET connection remained unusable after a send error, causing all subsequent messages to be silently dropped until rsyslog restarted.
[fix-message-loss-bug-for-connected-Unix-domain-sockets.patch]:Change Log
Does this affect the toolchain?
NO
Test Methodology
rsyslog-8.2308.0-6.azl3.src.rpm.log
rsyslog-8.2308.0-6.azl3.src.rpm.test.log
Patch application:

Installation and Uninstallation:

