supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jan Braun <janbraun@gmx.de>
To: peter@easthope.ca
Cc: supervision@list.skarnet.org
Subject: Re: Starting xinetd in Void Linux.
Date: Fri, 27 Dec 2024 18:53:03 +0100	[thread overview]
Message-ID: <Z27pf0UqRwUE1i8Y@abakus> (raw)
In-Reply-To: <6e010a4a2cd50805@abakus>

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

peter@easthope.ca schrob:
> lrwxrwxrwx 1 root root 27 Jan 14  2021 /etc/sv/xinetd/supervise -> /run/runit/supervise.xinetd
> 
> The last line above flashes reverse video on a red background; a hint
> that /run/runit/supervise.xinetd doesn't exist.

...yet. Correct tho.

> So xinetd failed to start.

No, not because of that. See below.

> I've read https://docs.voidlinux.org/config/services/.  No mention of
> /run/<anything>.

/run/<anything> is an implementation detail not worthy of being
mentioned. :)

The interesting part is
https://docs.voidlinux.org/config/services/#enabling-services
ln -s /etc/sv/<service> /var/service/

> How does runit start a service?

runsvdir will (within 5s) notice that /var/service/xinetd/ has appeared,
and then start "runsv xinetd".

> Where in the process is /run/runit/supervise.<service> created?

runsv will notice that ./xinetd/supervise is a dangling symlink, and
create the directory (assuming /run/runit/ exists).

> A fix for this failure?

The only failure appears to be that you didn't enable the service before
expecting it to work.
Otherwise, what's the output of "sudo sv start xinetd"?

cheers,
    Jan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2024-12-27 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6e010a4a2cd50805@abakus>
2024-12-27 17:53 ` Jan Braun [this message]
2024-12-27 18:56 Roger Pate via supervision
  -- 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=Z27pf0UqRwUE1i8Y@abakus \
    --to=janbraun@gmx.de \
    --cc=peter@easthope.ca \
    --cc=supervision@list.skarnet.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).