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: Laurent Bercot <ska-supervision@skarnet.org>
Cc: supervision@list.skarnet.org
Subject: Re: Reboot or Shutdown commands dont exit from tty auto
Date: Sun, 24 Nov 2024 15:46:35 +0100	[thread overview]
Message-ID: <f76b76dfed6e3f1f0f28a98aa4c3916e@disroot.org> (raw)
In-Reply-To: <em155d8896-9b4d-4319-8e8e-f04f5cb6902e@b1971efe.com>

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

El 2024-11-24 13:49, Laurent Bercot escribió:

>> Would it then be correct to remove agetty from the supervised?
> 
> No, you should be able to run a shutdown command from any terminal,
> the design of s6-linux-init is made for that use case.
> 
> What's happening is that your agetty is resistant to the signal it's
> being sent, so it's not dying when it should.
> 
> Some implementations of getty explicitly resist SIGTERM. So, try
> "echo SIGHUP > down-signal" in the service directory for your agetty.
> 
> --
> Laurent

Thank you Laurent, it works perfectly with that "echo", at least I'm not 
crazy xDD

Can I do anything to make my agetty behave compatible or accept this 
signal? The solution would be to implement ngetty?

Thanks again, Luis.

  reply	other threads:[~2024-11-24 14:46 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 [this message]
2024-11-24 16:39         ` [SOLVED] " lumaro via supervision
2024-11-24 22:47           ` Laurent Bercot
2024-11-25  5:00             ` lumaro via supervision

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=f76b76dfed6e3f1f0f28a98aa4c3916e@disroot.org \
    --to=supervision@list.skarnet.org \
    --cc=lumaro@disroot.org \
    --cc=ska-supervision@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).