What is a rationale for --no-bind in auto-services by Systemd?
Posted: Sun Apr 30, 2023 12:19 pm
Hi!
I'm looking at option "--no-bind" for an auto generated Systemd units to be started: (Debian 11 Bullseye):
Is there any rationale of no port binding at client side, if it's known beforehand the port number will NOT be occupied by a process?
To bind or not to bind is declared in configuration file on admin choice. But for auto-generated Systemd's units with clients it's enforced at start by direct option specification.
What a reason? Except a risk to catch a port collision issue.
I'm looking at option "--no-bind" for an auto generated Systemd units to be started: (Debian 11 Bullseye):
Code: Select all
# cat /usr/lib/systemd/system/openvpn-client@.service | grep ExecStart
ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config %i.conf
To bind or not to bind is declared in configuration file on admin choice. But for auto-generated Systemd's units with clients it's enforced at start by direct option specification.
What a reason? Except a risk to catch a port collision issue.