From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: headscale-0.16.4
Date: Wed, 12 Oct 2022 08:56:40 +0200 [thread overview]
Message-ID: <20221012065640.xzmRjMnWZE9wXR4RhvGnOHsJwKWJ7Yn6kMDg5KPIgwU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39864@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
New review comment by teldra on void-packages repository
https://github.com/void-linux/void-packages/pull/39864#discussion_r993064530
Comment:
`headscale` creates a sock file in this dir. (Please refer to the vsed statement in `post_extract` and maybe the config.yaml.)
I think, headscale is originally not intended to run as unprivileged user. I circumvent this with the creation of a headscale owned folder.
next prev parent reply other threads:[~2022-10-12 6:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 14:27 [PR PATCH] New Package: headscale-0.16.4 teldra
2022-10-10 14:39 ` teldra
2022-10-10 14:42 ` paper42
2022-10-10 15:01 ` teldra
2022-10-10 15:06 ` paper42
2022-10-10 22:12 ` [PR PATCH] [Updated] " teldra
2022-10-10 22:13 ` teldra
2022-10-10 22:23 ` teldra
2022-10-10 22:38 ` [PR PATCH] [Updated] " teldra
2022-10-12 5:05 ` [PR REVIEW] New package: headscale-0.16.4 0x5c
2022-10-12 5:05 ` 0x5c
2022-10-12 5:05 ` 0x5c
2022-10-12 5:05 ` 0x5c
2022-10-12 6:38 ` teldra
2022-10-12 6:38 ` teldra
2022-10-12 6:56 ` teldra [this message]
2022-10-12 6:58 ` teldra
2022-10-12 6:58 ` teldra
2022-10-12 6:59 ` [PR PATCH] [Updated] " teldra
2022-10-12 6:59 ` teldra
2022-10-12 7:00 ` teldra
2022-10-12 7:09 ` teldra
2022-10-12 7:28 ` [PR REVIEW] " teldra
2022-10-12 7:35 ` teldra
2022-10-12 7:40 ` teldra
2022-10-13 3:53 ` 0x5c
2022-10-13 4:00 ` 0x5c
2022-10-13 4:23 ` 0x5c
2022-10-13 6:29 ` [PR PATCH] [Updated] " teldra
2022-10-13 6:31 ` teldra
2023-01-12 2:29 ` github-actions
2023-01-27 1:59 ` [PR PATCH] [Closed]: " 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=20221012065640.xzmRjMnWZE9wXR4RhvGnOHsJwKWJ7Yn6kMDg5KPIgwU@z \
--to=teldra@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).