[Openvpn-users] Can -enable-small help on a low resource VPS

[debbie10t]

Hi,

From: https://forums.openvpn.net/viewtopic.php?f=6&t=23762#p69056

<q>
Looks like I can't run openvpn. The service is failing to start up due
to "Job for ***@server.service failed **because a configured
resource limit was exceeded** ".

Yes. I've searched through the documentation as well as searched through
google. No applicable results.

I was kinda afraid of that happening since my VPS is small. 128mb RAM.
</q>

The VPS is Linux as systemd is in use.
The user will probably have to build else where and upload the binary.

But would --enable-small be of any use in this case ?

Thanks

[David Sommerseth]

Post by debbie10t
Hi,
From: https://forums.openvpn.net/viewtopic.php?f=6&t=23762#p69056
<q>
Looks like I can't run openvpn. The service is failing to start up due
resource limit was exceeded** ".
Yes. I've searched through the documentation as well as searched through
google. No applicable results.
I was kinda afraid of that happening since my VPS is small. 128mb RAM.
</q>
The VPS is Linux as systemd is in use.
The user will probably have to build else where and upload the binary.
But would --enable-small be of any use in this case ?
Thanks

The --enable-small configure switch will basically make the OpenVPN
binary smaller, by removing a lot of static texts (like --help) and SSL
library error strings (so instead of OpenSSL providing a fairly
unredable error message, you get something completely incomprehensible
instead).

So --enable-small will not change the memory footprint used when
running. Log files will more or less be the same too (with the
exception of some reduced error strings). This feature is more commonly
wanted on users deploying OpenVPN on embedded devices where the flash
memory for application storage is heavily restricted.