port: a reservation kept only while the configuration in force has it

Once reserved, a port is dropped when a configuration comes in force
that neither reserves it anew nor has a service on it: after chroot no
reservation can be made again, only the usage of the socket a service
takes over keeps it. The reservation of the configuration before no
longer waits for its last client to let it go: the reload releases it
at once, the socket living on where a service of the new one has
claimed it, closing where none has.
This commit is contained in:
Vladimir Dubrovin committed 2026-11-21 16:17:35 +03:00
1 parent 17306f63f9
commit eec09dc4e9
4 files changed
+74 -14

No files matched your search

+8 -5
View File
@@ -1516,11 +1516,14 @@ privileged port can be opened before \fBsetuid\fR and \fBchroot\fR take the
rights to open it away, the \fBport\fR line placed above them and the
service below. A service of the configuration on the same address, of
the same type, takes the socket over when it starts, instead of opening
one of its own; a port no service takes stays reserved until the
configuration is left. The address is an IPv4 one by default, an IPv6
one in brackets. The socket options are written as for \fB-o\fR, and are
what the socket has: those which act only before bind() cannot be
changed on a socket the service takes over.
one of its own; a port no service takes stays reserved. After chroot no
reservation can be made again, so a reload keeps a port only while the
configuration coming in force reserves it anew or has a service on it:
the port line can be left out of what is read there, the service on
the socket that is already open keeping it. The address is an IPv4 one
by default, an IPv6 one in brackets. The socket options are written as
for \fB-o\fR, and are what the socket has: those which act only before
bind() cannot be changed on a socket the service takes over.
.br
port tcp 443
.br