From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sourceware.cygnus.com
Subject: [PATCH] setrlimit/getrlimit
Date: Wed, 15 Dec 1999 07:46:00 -0000 [thread overview]
Message-ID: <19991215164633.A30703@Wotan.suse.de> (raw)
Hi,
Here are 2 patches for the setrlimit/getrlimit problem with both current
glibc snapshots: 2.2 and 2.1.3
I have moved the u_long RLIM_INFINITY stuff into the i386 directory, so
it is Intel specific. The default is now singed long for RLIM_INFINITY.
This is correct for ALPHA. Don't know about PPC or ARM, so I let it
the old value until there is a solution how to handle this. In the
moment there is no second syscall for binary compatibility on this
platforms.
Jakub, I changed the sparc/bits/resouces.h file as you suggested,
sparc32 uses signed long, sparc64 unsigned long. Could you please
look at the patch ?
I have one problem with this: What happens if somebody compiles
his sparc64 binaries with the new header files and runs for example
linux 2.2.5 ? This kernel doesn't reject negative rlimit values.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.
next reply other threads:[~1999-12-15 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 7:46 Thorsten Kukuk [this message]
1999-12-15 8:04 ` Jakub Jelinek
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=19991215164633.A30703@Wotan.suse.de \
--to=kukuk@suse.de \
--cc=libc-hacker@sourceware.cygnus.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).