supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: silent boot with runit
Date: Mon, 13 Jul 2020 10:40:56 +0000	[thread overview]
Message-ID: <em432423b0-05b3-408f-97d5-1afe0bbffc76@elzian> (raw)
In-Reply-To: <20200713052307.jii33536txmlif7e@polarbear>

>I was wondering if it is possible to get a silent boot without having to
>modify runit itself. With systemd, the `quiet` kernel parameter acheives
>this. Is there anything similar for runit to prevent messages being
>displayed to the tty?

  No, runit hardcodes stdout and stderr to /dev/console. In order to
silence things, you'd have to:
  - either redirect the console to something nonexistent or quiet on
the kernel command line (would "console=null" work?)
  - or redirect stdout and stderr for the service you want to keep
quiet. For instance, if you want the supervision tree to be quiet,
you could add >/dev/null 2>&1 to the runsvdir invocation in
/etc/runit/2.

(With s6-linux-init, all of init's output is redirected to the default
logger, and you have a switch for whether or not to also display it
on the console.)


>Also I tried looking in the mailing list archives, but neither site was
>up.

  skarnet.org has been up for about 300 days. It is possible, however,
that specific messages that you wanted to access in the archive did not
display correctly.

--
  Laurent


      reply	other threads:[~2020-07-13 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  5:23 Kian Kasad
2020-07-13 10:40 ` Laurent Bercot [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=em432423b0-05b3-408f-97d5-1afe0bbffc76@elzian \
    --to=ska-supervision@skarnet.org \
    --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).