supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Roger Pate via supervision" <supervision@list.skarnet.org>
To: peter@easthope.ca, supervision@list.skarnet.org
Subject: Re: Starting xinetd in Void Linux.
Date: Fri, 27 Dec 2024 18:56:26 +0000	[thread overview]
Message-ID: <07e3bc60bcdc6c8272abb834f9e236fcf1951b3c@pate.house> (raw)

December 27, 2024 at 11:51 AM, peter@easthope.ca wrote:
> I've read https://docs.voidlinux.org/config/services/. No mention of 
> /run/<anything>.

The Void Linux documentation could be better.

Did you follow the instructions in section "Enabling Services", and if something unexpected happened, what was that?

Once the service has been enabled, did you follow the instructions starting with "To start, stop, restart or get the status of a service", and if something unexpected happened, what was that?

It would be nice if their documentation provided a through-line example of installing a package, enabling a corresponding service, testing the service, and configuring the service to start on boot.  If you want them to do that, you might ask them at https://github.com/void-linux/void-docs.  Their documentation also says this about contributing: "If you have any questions, feel free to ask them via IRC in #voidlinux on irc.libera.chat, or in the voidlinux subreddit."

             reply	other threads:[~2024-12-27 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 18:56 Roger Pate via supervision [this message]
     [not found] <6e010a4a2cd50805@abakus>
2024-12-27 17:53 ` Jan Braun
  -- strict thread matches above, loose matches on Subject: below --
2024-12-27 15:44 peter

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=07e3bc60bcdc6c8272abb834f9e236fcf1951b3c@pate.house \
    --to=supervision@list.skarnet.org \
    --cc=peter@easthope.ca \
    --cc=roger@pate.house \
    /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).