[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[50 character or so descriptive subject here (for reference)]
From: |
Mark Mitchell |
Subject: |
[50 character or so descriptive subject here (for reference)] |
Date: |
Wed, 25 Oct 2000 15:20:18 -0700 |
There is no way to use `ulimit' to set RLIMIT_AS under GNU/Linux.
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: Linux
Compiler: gcc
Compilation CFLAGS: -DHAVE_VFPRINTF -DHAVE_UNISTD_H -DHAVE_STDLIB_H
-DHAVE_LIMITS_H -DHAVE_GETGROUPS -DHAVE_RESOURCE -DHAVE_SYS_PARAM
-DVOID_SIGHANDLER -DHAVE_GETDTABLESIZE -DHAVE_BCOPY -DHAVE_GETPW_DECLS
-DHAVE_GETHOSTNAME -DHAVE_WAIT_H -DHAVE_DUP2 -DHAVE_STRERROR
-DHAVE_DIRENT_H -DHAVE_STRING_H -DHAVE_VARARGS_H -DHAVE_STRCHR
-DHAVE_DEV_FD -Di386 -DLinux -DSHELL -DHAVE_ALLOCA -DHAVE_ALLOCA_H
-O2 -m486 -fno-strength-reduce
uname output: Linux dumbledore.codesourcery.com 2.2.16-3smp #1 SMP Mon Jun 19
19:00:35 EDT 2000 i686 unknown
Bash Version: 1.14
Patch Level: 7
Description:
The RLIMIT_AS resource limit (which is the limit Linux uses to prevent
too much meomry from being allocated to a single process) can't be
set with the ulimit builtin.
Repeat-By:
Fix:
I'd be willing to take a whack at a patch, but I'm not sure where to send
it. Who is maintaining bash these days?
- [50 character or so descriptive subject here (for reference)], aprakash, 2000/10/10
- [50 character or so descriptive subject here (for reference)], Hirokazu Tsuda, 2000/10/11
- [50 character or so descriptive subject here (for reference)], Jonathan Amery, 2000/10/13
- Re: [50 character or so descriptive subject here (for reference)], Chet Ramey, 2000/10/17
- [50 character or so descriptive subject here (for reference)],
Mark Mitchell <=
- Re: [50 character or so descriptive subject here (for reference)], Chet Ramey, 2000/10/26
- [50 character or so descriptive subject here (for reference)], Eric G. Bergeron, 2000/10/26