Re: openvpn: should it include a runit service?

[slymattz <slymattz@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

New comment by slymattz on void-packages repository

https://github.com/void-linux/void-packages/issues/48834#issuecomment-1953082771

Comment:
Enabling OpenVPN through `ln -sv /etc/sv/openvpn /var/service` would do nothing by default as /etc/openvpn does not even exist in Void's OpenVPN package. 

You would have to either 
```
mkdir -p /etc/openvpn
chmod 755 /etc/openvpn
cp /usr/share/examples/openvpn/client.conf /etc/openvpn/openvpn.conf
chmod 600 /etc/openvpn/openvpn.conf
vim /etc/openvpn/openvpn.conf # modify the default script
# or
cp /path/to/your/config.conf /etc/openvpn/openvpn.conf # if you have a tailor-made config for yourself
```
With no user intervention, OpenVPN won't run. If you have another path pointing to a client/server configuration, you can point to it by:
`echo "CONF_FILE=/path/to/vpn.conf > /etc/sv/openvpn/conf`

As for the pipewire and pulseaudio analogy - I think these are completely different cases as the preferred method for them is, like you say, to be run by a user.

In an OpenVPN config file, you can specify both the user and the group that the process should be run by. As a matter of fact, you can run the process as an unprivileged user (on Debian, for instance, you just insert these lines in your openvpn config):

_/etc/openvpn/openvpn.conf_
```
user nobody
group nogroup
```