From: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
To: Matthias-Christian Ott <matthias.christian@tiscali.de>
Cc: Diego Calleja <diegocg@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: make OOM more "user friendly"
Date: Sat, 02 Apr 2005 20:36:37 +0300 [thread overview]
Message-ID: <424ED825.1030706@tuleriit.ee> (raw)
In-Reply-To: <424ECF4D.6070800@tiscali.de>
Matthias-Christian Ott wrote:
> Diego Calleja schrieb:
>
>> When people gets OOM messages, many of them don't know what is
>> happening or what
>> OOM means. This brief message explains it.
>>
>> --- stable/mm/oom_kill.c.orig 2005-04-02 17:44:14.000000000 +0200
>> +++ stable/mm/oom_kill.c 2005-04-02 18:01:02.000000000 +0200
>> @@ -189,7 +189,8 @@
>> return;
>> }
>> task_unlock(p);
>> - printk(KERN_ERR "Out of Memory: Killed process %d (%s).\n",
>> p->pid, p->comm);
>> + printk(KERN_ERR "The system has run Out Of Memory (RAM + swap),
>> a process will be killed to free some memory\n");
>> + printk(KERN_ERR "OOM: Killed process %d (%s).\n", p->pid, p->comm);
>>
>> /*
>> * We give our sacrificial lamb high priority and access to
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
> I disagree this is _not_ usefull. If the user don't knows what OOM
> means he can use google to get this information.
:) Somewhat like "Use your mobile phone to call helpdesk if your mobile
phone is broken". Maybe such messages should have some kind of link to
information in Documentation/ ?
regards,
Indrek
prev parent reply other threads:[~2005-04-02 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 16:05 make OOM more "user friendly" Diego Calleja
2005-04-02 16:58 ` Matthias-Christian Ott
2005-04-02 17:11 ` Diego Calleja
2005-04-02 17:36 ` Indrek Kruusa [this message]
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=424ED825.1030706@tuleriit.ee \
--to=indrek.kruusa@tuleriit.ee \
--cc=akpm@osdl.org \
--cc=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.christian@tiscali.de \
/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