supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "lumaro via supervision" <supervision@list.skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: [SOLVED] Re: Reboot or Shutdown commands dont exit from tty auto
Date: Mon, 25 Nov 2024 06:00:58 +0100	[thread overview]
Message-ID: <bb3a24782f93f64951f607f9787e7ffb@disroot.org> (raw)
In-Reply-To: <em1cc7ee0d-6e7f-4b0d-bd41-1955571824c9@6e7aba6e.com>

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

El 2024-11-24 23:47, Laurent Bercot escribió:

>> Can I do anything to make my agetty behave compatible or accept this 
>> signal? The solution would be to implement ngetty?
> 
> No, it's just historical behaviour for terminal managers to die on
> SIGHUP instead of SIGTERM, and it kind of makes sense too. There's
> nothing to fix here, because the fix would cause more chaos than it
> solves problems. It is, unfortunately, just something you need to
> remember: when supervising a getty, always set the down-signal to
> SIGHUP.
> 
> --
> Laurent

A very important detail that has had me stuck for months not to ask, 
very clarifying your answer Laurent, thank you for creating an 
alternative to systemd, I will continue to move forward until I fully 
adopt s6 system. A hug.
--
Luis.

      reply	other threads:[~2024-11-25  5:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24  8:47 lumaro via supervision
2024-11-24 10:57 ` Hoël Bézier
2024-11-24 12:26   ` lumaro via supervision
2024-11-24 12:49     ` Re[2]: " Laurent Bercot
2024-11-24 14:46       ` lumaro via supervision
2024-11-24 16:39         ` [SOLVED] " lumaro via supervision
2024-11-24 22:47           ` Laurent Bercot
2024-11-25  5:00             ` lumaro via supervision [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=bb3a24782f93f64951f607f9787e7ffb@disroot.org \
    --to=supervision@list.skarnet.org \
    --cc=lumaro@disroot.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).