From 7e79f319a8ef7c79c588259621e0a64eecef4cfd Mon Sep 17 00:00:00 2001 From: Ben Nemec Date: Thu, 25 Oct 2018 15:05:46 +0000 Subject: [PATCH] Add release note for file descriptor limit change This could have an operator impact, so we should mention it in the release notes. See c0a86998203315858721a7b2c8ab75fbf5cd51d9 for the actual implementation of the feature. Change-Id: Ib29e96307caa39c21936f216d9aed7907e7a7331 --- .../file-descriptor-limit-e2b2a3033b9ef21e.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 releasenotes/notes/file-descriptor-limit-e2b2a3033b9ef21e.yaml diff --git a/releasenotes/notes/file-descriptor-limit-e2b2a3033b9ef21e.yaml b/releasenotes/notes/file-descriptor-limit-e2b2a3033b9ef21e.yaml new file mode 100644 index 0000000..873574f --- /dev/null +++ b/releasenotes/notes/file-descriptor-limit-e2b2a3033b9ef21e.yaml @@ -0,0 +1,14 @@ +--- +features: + - | + A configurable limit on the number of file descriptors that can be opened + by a rootwrap-started process has been added. It defaults to 1024, but + can be adjusted by setting the ``rlimit_nofile`` option in rootwrap.conf + to a larger or smaller value. +upgrade: + - | + Because a file descriptor limit was added in this release (see the features + section for details), rootwrap processes that were previously relying on + inheriting their parent process's descriptor limits may exhaust their + available file descriptors. Use the ``rlimit_nofile`` option to restore + the previous limits if this is the case.