From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openvpn: should it include a runit service?
Date: Mon, 19 Feb 2024 20:36:49 +0100 [thread overview]
Message-ID: <20240219193649.57E5A2BD59@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48834@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/48834#issuecomment-1953063448
Comment:
Might make sense to include example services for client and server, resembling `usr/lib/systemd/system/openvpn-client@.service` and `usr/lib/systemd/system/openvpn-server@.service` so users don't blindly enable the service just because they want to use openvpn as a client.
We've had bad experiences with shipping ready to use system services for things that should most likely not run as the system services, as example the pipewire and pulseaudio system services, where unexpected users started to enable those services without knowing that the preferred method of starting them is through some other means.
pipewire ships the example service as `/usr/share/examples/sv/pipewire`: https://github.com/void-linux/void-packages/blob/f574870935ed5c4f122c5ba84417f449dd4ca863/srcpkgs/pipewire/template#L61
next prev parent reply other threads:[~2024-02-19 19:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:40 [ISSUE] " slymattz
2024-02-19 19:34 ` Duncaen
2024-02-19 19:34 ` Duncaen
2024-02-19 19:34 ` Duncaen
2024-02-19 19:36 ` Duncaen
2024-02-19 19:36 ` Duncaen [this message]
2024-02-19 19:53 ` slymattz
2024-02-19 19:55 ` slymattz
2024-02-19 19:57 ` Duncaen
2024-02-19 19:58 ` Duncaen
2024-02-19 19:58 ` slymattz
2024-02-19 19:59 ` Duncaen
2024-02-19 20:00 ` slymattz
2024-02-19 20:01 ` slymattz
2024-02-19 20:02 ` slymattz
2024-02-19 20:02 ` slymattz
2024-02-19 20:08 ` slymattz
2024-02-19 20:11 ` slymattz
2024-02-19 20:11 ` slymattz
2024-02-19 20:18 ` slymattz
2024-02-19 20:21 ` slymattz
2024-05-20 1:46 ` github-actions
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=20240219193649.57E5A2BD59@inbox.vuxu.org \
--to=duncaen@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).