ksh erroneously sets RLIMIT_CPU instead of RLIMIT_AS with 'ulimit -v'
Issue
- ksh erroneously sets RLIMIT_CPU instead of RLIMIT_AS with 'ulimit -v'
- Steps to Reproduce:
$ ulimit -v 100000
$ ulimit -a
address space limit (kbytes) (-M) unlimited
core file size (blocks) (-c) 0
cpu time (seconds) (-t) 102400000 <= this is wrong
data size (kbytes) (-d) unlimited
file size (blocks) (-f) unlimited
locks (-L) unlimited
locked address space (kbytes) (-l) 32
nice (-e) 0
nofile (-n) 1024
nproc (-u) 71168
pipe buffer size (bytes) (-p) 4096
resident set size (kbytes) (-m) unlimited
rtprio (-r) 0
socket buffer size (bytes) (-b) 4096
stack size (kbytes) (-s) 10240
threads (-T) not supported
process size (kbytes) (-v) 100000
- Expected results:
address space limit (kbytes) (-M) 100000
core file size (blocks) (-c) 0
cpu time (seconds) (-t) unlimited
data size (kbytes) (-d) unlimited
file size (blocks) (-f) unlimited
locks (-L) unlimited
locked address space (kbytes) (-l) 32
nice (-e) 0
nofile (-n) 1024
nproc (-u) 71168
pipe buffer size (bytes) (-p) 4096
resident set size (kbytes) (-m) unlimited
rtprio (-r) 0
socket buffer size (bytes) (-b) 4096
stack size (kbytes) (-s) 10240
threads (-T) not supported
process size (kbytes) (-v) 100000
Environment
- Red Hat Enterprise Linux 5
- ksh-20100202-6.el5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.