Find resolvconf automatically does not always work about openvpn-update-resolv-conf

[maleadt]

Bumped in this as well, and I assume this is because OpenVPN scrubs the environment before invoking the up or down scripts (you can verify this by adding an env command to the script). One of the missing environment variables is PATH, breaking which.

Workaround: add setenv PATH /usr/bin (or wherever your resolvconf binary is located) to your OpenVPN config.

[usommerl]

Configuration issue. There is no reasonable way to fix this in openvpn-update-resolv-conf. You can circumvent this issue by adding the following option to your OpenVPN-Client configuration:

setenv PATH <DIRECTORY_WITH_RESOLVCONF_BINARY>

[usommerl]

I've added a debug statement and ran the script with commit 994574f:

Apr 20 06:53:32 nyx update-resolv-conf[5271]: RESOLVCONF=

I'm using a systemd unit to activate the openvpn configuration that triggers the execution of the script

[usommerl]

@maleadt You are right. I initially thought it was systemd that scrubs the environment but that is not the case. Your solution works for me as well and I think it is better than to modify update-resolv-conf.sh itself.