| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit d3986a312f5fbcfd0e78e6b147eef419fb4e5f54.
|
|
The current reload implementation (sending a SIGHUP signal to the
process) fails, and the difference between reload and restart is not
clear. Systemd does not require an implementation for reload.
|
|
Two scenarios are tested, server setup using: a static key and a CA.
|
|
|
|
Thanks: Fabio Pedretti
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes: #958315
|
|
system configuration
Closes: #958296
|
|
|
|
|
|
|
|
Refresh d/copyright
|
|
|
|
|
|
|
|
|
|
|
|
This generally seems to be the wrong knob to protect against runaway
forks (as it does not limit per instance, but per user systemwide), but
a general mediation is still under discussion. Meanwhile bump the limit
for the Debian unit to 100.
Upstream openvpn-client@.service and openvpn-server@.service still use
10
See Bug#861923 for discussion.
|
|
"safe fork mode" (Closes: #772812, #900805, #907452)
|
|
Same change has been done upstream in 2.4.7
Closes: #868806
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
