From: slymattz <slymattz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn: update to 2.6.9.
Date: Sun, 18 Feb 2024 22:56:15 +0100 [thread overview]
Message-ID: <20240218215615.DA0D224B47@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48693@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
New comment by slymattz on void-packages repository
https://github.com/void-linux/void-packages/pull/48693#issuecomment-1951457118
Comment:
https://github.com/void-linux/void-packages/pull/17906#issuecomment-569937899 is really intriguing and I wonder what the rationale for such a decision was.
Anyhow, I see things two-fold here:
1) running OpenVPN as a server - you must have a runit service here to start it on boot
2) running OpenVPN as a client - you don't have to have a runit server here unless you want to run it on boot
So three scenarios pop-up: two where having a runit service is highly essential and one where it is redundant (like when you run openvpn /etc/openvpn/client/1.conf &
As a personal note, I've run the runit service in a server instance successfully today, so it works.
These are the technicalities but I'm wondering on what your opinions are. I propose a discussion.
next prev parent reply other threads:[~2024-02-18 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:33 [PR PATCH] " Bnyro
2024-02-18 19:47 ` slymattz
2024-02-18 21:33 ` Bnyro
2024-02-18 21:56 ` slymattz [this message]
2024-02-18 21:56 ` slymattz
2024-02-18 22:36 ` Bnyro
2024-02-19 17:44 ` slymattz
2024-02-22 15:12 ` slymattz
2024-03-04 19:27 ` slymattz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240218215615.DA0D224B47@inbox.vuxu.org \
--to=slymattz@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).