mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benoit Boissinot <bboissin@gmail.com>
To: Damir Perisa <damir.perisa@solnet.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: documentation? (i learned something today ;-) )
Date: Sat, 15 Oct 2005 15:40:08 +0200	[thread overview]
Message-ID: <40f323d00510150640q1b1a996p85c9b4ff468de346@mail.gmail.com> (raw)
In-Reply-To: <200510151524.02123.damir.perisa@solnet.ch>

On 10/15/05, Damir Perisa <damir.perisa@solnet.ch> wrote:
> hi all,
>
> Le Saturday 15 October 2005 09:48, Anton Altaparmakov a écrit:
>  | If it has sysrq compiled in as root just do:
>  |
>  | echo s > /proc/sysrq-trigger
>  | echo u > /proc/sysre-trigger
>  | echo s > /proc/sysrq-trigger
>  | echo b > /proc/sysrq-trigger
>  |
>  | This will "sync", "umount/remount read-only", "sync", "immediate
>  | hardware reboot". Should always work...
>
> i'm impressed that i see that sysrq also works from procfs.... the
> "PrintScreen/SysRq" button on my keyboard from time to time does not work
> (old keyboard) and then it's pain hitting this key if you have to.
>
> great news that you can also pass sysrq requests using proc - i've learned
> something today... is this documented somewhere? maybe i'm bad in
> reading/finding docs but i think i'm not the only one here. can somebody
> point me to the links of docs where all this magic is specified? if not,
> i will try to start my own docs on how to use the linux kernel magic.
> mainly a collection of tricks like this and similar ones.
>
> thank you in advance + greetings,
> Damir

it is mentionned in Documentation/sysrq.txt

On all -  write a character to /proc/sysrq-trigger.  eg:

                echo t > /proc/sysrq-trigger

regards,

Benoit

  reply	other threads:[~2005-10-15 13:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15  1:46 Forcing an immediate reboot Marc Perkel
2005-10-15  1:50 ` Lee Revell
2005-10-15  6:47   ` Coywolf Qi Hunt
2005-10-15  6:51     ` Marc Perkel
2005-10-15  7:48   ` Anton Altaparmakov
2005-10-15  7:56     ` Coywolf Qi Hunt
2005-10-15  8:16       ` Anton Altaparmakov
2005-10-16  0:10         ` Petr Vandrovec
2005-10-15 13:23     ` documentation? (i learned something today ;-) ) Damir Perisa
2005-10-15 13:40       ` Benoit Boissinot [this message]
2005-10-15 14:52         ` Documentation/files somewhere online? Damir Perisa
2005-10-15 15:02           ` Denis Vlasenko
2005-10-15 15:13             ` Michael Krufky
2005-10-15 23:18               ` Documentation/files online: available at git in webinterface Damir Perisa
2005-10-15 14:29     ` Forcing an immediate reboot Marc Perkel
2005-10-15  1:55 ` Randy.Dunlap
2005-10-15  2:24 ` Danny ter Haar
2005-10-15  6:21 ` Willy Tarreau
2005-10-15  6:50   ` Coywolf Qi Hunt
2005-10-15 10:24 ` Denis Vlasenko

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=40f323d00510150640q1b1a996p85c9b4ff468de346@mail.gmail.com \
    --to=bboissin@gmail.com \
    --cc=damir.perisa@solnet.ch \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®