aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorJimmy Olgeni <olgeni@FreeBSD.org>2022-03-11 07:22:02 +0000
committerJimmy Olgeni <olgeni@FreeBSD.org>2022-03-11 07:22:43 +0000
commit0b0963234709b713a02afd660465649cb88a6da1 (patch)
tree488576481033873cdcacb81b0a703a565c47798d /UPDATING
parent9b7b7746fac501b001ff1ced3d27448331fcc72d (diff)
downloadports-0b0963234709b713a02afd660465649cb88a6da1.tar.gz
ports-0b0963234709b713a02afd660465649cb88a6da1.zip
net/nats-server: improve rc.d
- Add nats to UIDs and GIDs - Add extra commands for logrotate and 'lame duck mode'. From the docs: In production we recommend that a server is shut down with "lame duck mode" as a graceful way to slowly evict clients. With large deployments this mitigates the "thundering herd" situation that will place CPU pressure on servers as TLS enabled clients reconnect. After entering lame duck mode, the server will stop accepting new connections, wait for a 10 second grace period, then begin to evict clients over a period of time configurable by the configuration option. This period defaults to 2 minutes.
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING8
1 files changed, 8 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 8144db70b5ef..c8e7bc2e9d04 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,14 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20220311:
+ AFFECTS: users of net/nats-server
+ AUTHOR: olgeni@FreeBSD.org
+
+ A dedicated 'nats' user was added, replacing 'nobody' in the startup script.
+ You should check your configuration and assign updated ownership to your data
+ files.
+
20220227:
AFFECTS: users of graphics/bmeps
AUTHOR: takefu@airport.fm