[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c22997c9-6d99-4e1f-9015-b7f80be2a720@kernel.org>
Date: Mon, 18 Dec 2023 13:05:11 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Tomas Mudrunka <tomas.mudrunka@...il.com>,
Jonathan Corbet <corbet@....net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH] /proc/sysrq-trigger can now pause processing for one
second
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
Powered by blists - more mailing lists