public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Tomas Mudrunka <tomas.mudrunka@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH] /proc/sysrq-trigger can now pause processing for one second
Date: Mon, 18 Dec 2023 13:05:11 +0100	[thread overview]
Message-ID: <c22997c9-6d99-4e1f-9015-b7f80be2a720@kernel.org> (raw)
In-Reply-To: <20231218114222.283705-1-tomas.mudrunka@gmail.com>

On 18. 12. 23, 12:42, Tomas Mudrunka wrote:
> Writing ',' to /proc/sysrq-trigger now causes processing to
> pause for one second.
> 
> This is useful, because recently accepted patch allows
> to write multiple keys at once to /proc/sysrq-trigger.
> But it might be desirable to add slight delay between actions.
> 
> Eg. between (e)TERM and (i)KILL it makes sense to put slight delay,
> so processes have chance to run TERM handlers before being KILLed.
> 
> Now we can send TERM, wait for two seconds and KILL like this:
> 
> echo _e,,i > /proc/sysrq-trigger

Bah, what's wrong with:
  echo e > /proc/sysrq-trigger
  sleep 2
  echo i > /proc/sysrq-trigger
?

thanks,
-- 
js
suse labs


  reply	other threads:[~2023-12-18 12:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 11:42 [PATCH] /proc/sysrq-trigger can now pause processing for one second Tomas Mudrunka
2023-12-18 12:05 ` Jiri Slaby [this message]
2023-12-18 12:13   ` Tomáš Mudruňka
2023-12-18 12:18     ` Greg Kroah-Hartman
2023-12-18 12:37       ` Tomáš Mudruňka
2023-12-18 12:44         ` Greg Kroah-Hartman
2023-12-18 12:53           ` Tomáš Mudruňka

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=c22997c9-6d99-4e1f-9015-b7f80be2a720@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=tomas.mudrunka@gmail.com \
    /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