From: Bodo Eggert <harvested.in.lkml@7eggert.dyndns.org>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>,
schilling@fokus.fraunhofer.de, matthias.andree@gmx.de,
linux-kernel@vger.kernel.org, tytso@mit.edu, arjan@infradead.org
Subject: Re: Rationale for RLIMIT_MEMLOCK?
Date: Thu, 26 Jan 2006 01:12:15 +0100 [thread overview]
Message-ID: <E1F1ukJ-0002DA-LK@be1.lrz> (raw)
In-Reply-To: 5yUUI-6JR-15@gated-at.bofh.it
Joerg Schilling <schilling@fokus.fraunhofer.de> wrote:
> I could add this piece of code to the euid == 0 part of cdrecord:
>
> LOCAL void
> raise_memlock()
> {
> #ifdef RLIMIT_MEMLOCK
> struct rlimit rlim;
>
> rlim.rlim_cur = rlim.rlim_max = RLIM_INFINITY;
I think you should rather use the size you're going to mlock, or at least
the upper bound.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
next prev parent reply other threads:[~2006-01-26 0:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5y7B5-1dw-15@gated-at.bofh.it>
[not found] ` <5y7KL-1DZ-31@gated-at.bofh.it>
[not found] ` <5yddh-1pA-47@gated-at.bofh.it>
[not found] ` <5ydni-1Qq-3@gated-at.bofh.it>
[not found] ` <5yek1-3iP-53@gated-at.bofh.it>
[not found] ` <5yeth-3us-33@gated-at.bofh.it>
[not found] ` <5yf5O-4iF-19@gated-at.bofh.it>
[not found] ` <5yfI4-5kU-11@gated-at.bofh.it>
[not found] ` <5ygE4-6LK-35@gated-at.bofh.it>
[not found] ` <5yhqg-7ZR-5@gated-at.bofh.it>
[not found] ` <5yi2X-zm-7@gated-at.bofh.it>
2006-01-24 9:14 ` CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?) Bodo Eggert
2006-01-24 14:38 ` Joerg Schilling
2006-01-24 17:44 ` CD writing in future Linux (stirring up a hornets' nest) Bodo Eggert
[not found] ` <5ygDT-6LK-3@gated-at.bofh.it>
[not found] ` <5yscc-68j-5@gated-at.bofh.it>
[not found] ` <5ysvk-6JI-5@gated-at.bofh.it>
[not found] ` <5ysvk-6JI-3@gated-at.bofh.it>
[not found] ` <5yEn7-7Or-21@gated-at.bofh.it>
[not found] ` <5yUUI-6JR-15@gated-at.bofh.it>
2006-01-26 0:12 ` Bodo Eggert [this message]
2006-02-03 20:49 Rationale for RLIMIT_MEMLOCK? Michael Kerrisk
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 10:56 Matthias Andree
2006-01-23 11:05 ` Arjan van de Ven
2006-01-23 16:54 ` Matthias Andree
2006-01-23 17:00 ` Arjan van de Ven
2006-01-23 18:01 ` Matthias Andree
2006-01-23 18:13 ` Arjan van de Ven
2006-01-23 18:55 ` Matthias Andree
2006-01-23 19:04 ` Arjan van de Ven
2006-01-23 19:38 ` Joerg Schilling
2006-01-23 20:30 ` Matthias Andree
2006-01-23 21:23 ` Joerg Schilling
2006-01-23 22:05 ` Matthias Andree
2006-01-24 8:52 ` Arjan van de Ven
2006-01-24 9:08 ` Joerg Schilling
2006-01-24 9:15 ` Arjan van de Ven
2006-01-24 9:18 ` Joerg Schilling
2006-01-24 21:28 ` Theodore Ts'o
2006-01-24 23:19 ` Edgar Toernig
2006-01-25 15:38 ` Joerg Schilling
2006-01-24 23:26 ` Matthias Andree
2006-01-24 23:27 ` Matthias Andree
2006-01-25 15:33 ` Joerg Schilling
2006-01-25 16:01 ` Matthias Andree
2006-01-24 10:51 ` Matthias Andree
2006-01-23 20:30 ` Lee Revell
2006-01-23 21:33 ` Joerg Schilling
2006-01-23 19:57 ` Lee Revell
2006-01-23 21:34 ` Theodore Ts'o
2006-01-24 11:06 ` Matthias Andree
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=E1F1ukJ-0002DA-LK@be1.lrz \
--to=harvested.in.lkml@7eggert.dyndns.org \
--cc=7eggert@gmx.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=schilling@fokus.fraunhofer.de \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).