[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#330403: marked as done (sysrq: no time for terseness)



Your message dated Sat, 03 Jan 2009 06:14:49 +0800
with message-id <87eizlwe1y.fsf@jidanni.org>
and subject line Re: [PATCH] sysrq: more explicit, less terse help messages
has caused the Debian Bug report #330403,
regarding sysrq: no time for terseness
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
330403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330403
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-doc-2.6.12
Version: 2.6.12-2
Severity: wishlist
File: /usr/share/doc/linux-doc-2.6.12/Documentation/sysrq.txt.gz
Tags: upstream

sysrq.txt.gz should say more about "oom_kill". One doesn't know where
to look to learn more.

P.S., and please pass this to who is in charge:

When we try the h command, we get
SysRq : HELP : loglevel0-8 reBoot tErm Full kIll saK showMem Nice
powerOff showPc unRaw Sync showTasks Unmount

How does "Full" correspond to killing hogs? And "kIll" might look like
"klll" on some terminals.

Anyway, picking from an emergency list is no time to be so cryptic.
The sysadmin is in trouble and he needs to know what each choice is
for clearly.  Therefore the help output should be something more like
what one sees with
$ zgrep ^\' $f sysrq.txt.gz


--- End Message ---
--- Begin Message ---
OK thanks. Closing bug.


--- End Message ---

Reply to: