From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tigervnc: a working runit service for the tigervnc vncserver cannot be written
Date: Wed, 04 Oct 2023 15:55:40 +0200 [thread overview]
Message-ID: <20231004135540.JR7YFMZnoH_nAVre6wtX9P02auYKcpf7NwIdD0i5yGg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45522@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/45522#issuecomment-1746930927
Comment:
You seem incapable of distinguishing "policy" from "design requirements". The operation of `runsv` is described thoroughly in its manual page. The runit FAQ linked in the handbook also clearly states that processes must remain in the foreground. We expect users to read the documentation and, especially if they attempt to design custom components like system services, understand the mechanisms they are using.
Your service is broken because the `run` script you wrote fails to meet the requirements of `runsv`, plain and simple.
prev parent reply other threads:[~2023-10-04 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:44 [ISSUE] tigervnc: multiple patches needed to create a working runit service for the tigervnc vncserver zmudc
2023-08-17 21:32 ` tigervnc: a working runit service for the tigervnc vncserver cannot be written zmudc
2023-08-17 21:44 ` ahesford
2023-08-17 21:51 ` zmudc
2023-10-03 22:57 ` ahesford
2023-10-03 22:57 ` [ISSUE] [CLOSED] " ahesford
2023-10-04 0:08 ` ahesford
2023-10-04 13:36 ` zmudc
2023-10-04 13:55 ` 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=20231004135540.JR7YFMZnoH_nAVre6wtX9P02auYKcpf7NwIdD0i5yGg@z \
--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).