From: <stone_wang@sohu.com>
To: "Andrew Morton" <akpm@osdl.org>, <riel@redhat.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re:Re: [PATCH] Linux-2.6.11-rc5: kernel/sys.c setrlimit() RLIMIT_RSS cleanup
Date: Sun, 27 Feb 2005 19:05:51 +0800 (CST) [thread overview]
Message-ID: <4365289.1109502351571.JavaMail.postfix@mx20.mail.sohu.com> (raw)
I have a buddy who encountered the "ulimit" confusion,
when he and his team deployed Linux as the platform for a multi-user online programming test competition system.
And generally, i think the kernel/system shall work as it said(return of syscalls/output of commands) :)
But rss limit might be a historical issue, with already many applications depending on it :(
Stone Wang
----- Original Message -----
From: Andrew Morton
To: stone_wang@sohu.com
Cc: riel@redhat.com ;linux-mm@kvack.org ;linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux-2.6.11-rc5: kernel/sys.c setrlimit() RLIMIT_RSS
cleanup
Sent: Sun Feb 27 18:31:36 CST 2005
>
> <stone_wang@sohu.com> wrote:
> >
> > $ ulimit -m 100000
> > bash: ulimit: max memory size: cannot modify limit: Function not implemented
>
> I don't know about this. The change could cause existing applications and
> scripts to fail. Sure, we'll do that sometimes but this doesn't seem
> important enough.
WARNING: multiple messages have this Message-ID (diff)
From: <stone_wang@sohu.com>
To: Andrew Morton <akpm@osdl.org>,
riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] Linux-2.6.11-rc5: kernel/sys.c setrlimit() RLIMIT_RSS cleanup
Date: Sun, 27 Feb 2005 19:05:51 +0800 (CST) [thread overview]
Message-ID: <4365289.1109502351571.JavaMail.postfix@mx20.mail.sohu.com> (raw)
I have a buddy who encountered the "ulimit" confusion,
when he and his team deployed Linux as the platform for a multi-user online programming test competition system.
And generally, i think the kernel/system shall work as it said(return of syscalls/output of commands) :)
But rss limit might be a historical issue, with already many applications depending on it :(
Stone Wang
----- Original Message -----
From: Andrew Morton
To: stone_wang@sohu.com
Cc: riel@redhat.com ;linux-mm@kvack.org ;linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Linux-2.6.11-rc5: kernel/sys.c setrlimit() RLIMIT_RSS
cleanup
Sent: Sun Feb 27 18:31:36 CST 2005
>
> <stone_wang@sohu.com> wrote:
> >
> > $ ulimit -m 100000
> > bash: ulimit: max memory size: cannot modify limit: Function not implemented
>
> I don't know about this. The change could cause existing applications and
> scripts to fail. Sure, we'll do that sometimes but this doesn't seem
> important enough.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2005-02-27 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 11:05 stone_wang [this message]
2005-02-27 11:05 ` Re:Re: [PATCH] Linux-2.6.11-rc5: kernel/sys.c setrlimit() RLIMIT_RSS cleanup stone_wang
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=4365289.1109502351571.JavaMail.postfix@mx20.mail.sohu.com \
--to=stone_wang@sohu.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.