Robie Basak schreef op 18-09-2017 0:40:
On Mon, Sep 18, 2017 at 12:32:26AM +0200, Göran Hasse wrote:
They must have "forgot it".
In that case, in the first instance upstream should be contacted
directly with this report. Then the problem can be fixed for everyone
without risking confusion to
Göran Hasse schreef op 18-09-2017 0:32:
They must have "forgot it".
An openvpn client service have the same importance as the login
program.
So it should be restarted (with some backoff strategy maybe).
A system service of this importance should *always* be restarted after
a krash! We had
Den 2017-09-18 kl. 00:15, skrev Robie Basak:
> Hi Göran,
>
> On Wed, Sep 13, 2017 at 06:50:27AM +0200, Göran Hasse wrote:
>> PLEASE se to that the default configuration of openvpn is so that it will
>> restart after an exit.
>
> Do you know why the upstream OpenVPN project don't set this as
On Mon, Sep 18, 2017 at 12:32:26AM +0200, Göran Hasse wrote:
> They must have "forgot it".
In that case, in the first instance upstream should be contacted
directly with this report. Then the problem can be fixed for everyone
without risking confusion to Ubuntu users by having OpenVPN behave
Hi Göran,
On Wed, Sep 13, 2017 at 06:50:27AM +0200, Göran Hasse wrote:
> PLEASE se to that the default configuration of openvpn is so that it will
> restart after an exit.
Do you know why the upstream OpenVPN project don't set this as default
already? That'd be the first question to answer I
Göran Hasse schreef op 13-09-2017 6:50:
Hello,
Last week I had a major incident in our company.
The root of this was that openvpn was controled by systemd and
the configuration was set so that if the server died (a client
configuration)
was not restarted.
All 20 client I had got some
Hello,
Last week I had a major incident in our company.
The root of this was that openvpn was controled by systemd and
the configuration was set so that if the server died (a client configuration)
was not restarted.
All 20 client I had got some problem with my main server and
made an exit. We
