From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Service socklog-unix locks users out of the system if /var/log/socklog does not exist
Date: Sun, 04 May 2025 19:04:49 +0200 [thread overview]
Message-ID: <20250504170449.3AF672F927@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54043@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/54043#issuecomment-2849171643
Comment:
This is an imaginary issue.
In general, any service can have an arbitrary list of seemingly trivial prerequisites. It is not the job of the service to ensure that all are met. Ultimately, the user is responsible for understanding and satisfying these prerequisites. This is especially true when the user breaks customary expectations like the availability of persistent storage for logs. If you're going to mount something ephemeral over directory structures created by the system, you should take steps to ensure that the hierarchy below is recreated at the time of mount, whether or not consumers of that directory deign to make a good-faith effort to repopulate the hierarchy on demand.
We will certainly consider PRs that increase user convenience by creating an expected directory on demand or even allowing the user to configure the location of expected directories. However, these proposals must stand on their own utility. The existence of footguns in Void is not a problem *ipso facto*.
prev parent reply other threads:[~2025-05-04 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 2:28 [ISSUE] " abhocetabhac
2025-01-22 16:50 ` dkwo
2025-05-01 15:53 ` vincele
2025-05-04 11:50 ` [ISSUE] [CLOSED] " ahesford
2025-05-04 11:50 ` ahesford
2025-05-04 13:08 ` abhocetabhac
2025-05-04 17:04 ` ahesford [this message]
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=20250504170449.3AF672F927@inbox.vuxu.org \
--to=ahesford@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).