From: Martin Pool <mbp@sourcefrog.net>
To: hsdm <hsdm@hsdm.com>, linux-kernel@vger.kernel.org
Subject: Re: Is it possible to add this feature.
Date: Wed, 06 Aug 2003 17:47:16 +1000 [thread overview]
Message-ID: <pan.2003.08.06.07.47.15.831811@sourcefrog.net> (raw)
In-Reply-To: 20030806005348.GB15764@matchmail.com
On Tue, 05 Aug 2003 17:53:48 -0700, Mike Fedyk wrote:
> On Tue, Aug 05, 2003 at 08:30:54PM -0400, Kurt Wall wrote:
>> Quoth hsdm:
>> > Is it posible to limit the amount of memory or CPU time per user?
> Basically, no.
>
>> ulimit -m
>> ulimit -t
>
> This is per session, and the user can have many sessions. Unless you
> limit the number of sessions a user can have...
Mike is correct that you cannot have system-wide per-user limits at the
moment, at least in the standard kernel. However, it would be possible to
add it, if you find somebody to develop it for you.
--
Martin
next prev parent reply other threads:[~2003-08-06 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 0:20 Is it possible to add this feature hsdm
2003-08-06 0:30 ` Kurt Wall
2003-08-06 0:53 ` Mike Fedyk
2003-08-06 7:47 ` Martin Pool [this message]
2003-08-06 9:03 ` Peter Chubb
2003-08-07 6:44 ` Patrick McLean
2003-08-07 12:32 ` Alan Cox
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=pan.2003.08.06.07.47.15.831811@sourcefrog.net \
--to=mbp@sourcefrog.net \
--cc=hsdm@hsdm.com \
--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