Is it just me, or did something change?
It seems that now you can't raise resource limits after they've been
lowered. I've had a 'ulimit -c 0' in my login profile for a while;
previously when I needed to do debugging, I'd raise the limit to
something reasonable at the shell prompt, and then debug away.
Now it seems to be the case that once the (e.g,) core limit has been
lowered, you can't raise it again. Am I just remembering this wrong?
Here's a transcript from a "normal" user on a 4.0-current box, using
/bin/sh:
$ ulimit -a
cpu time (seconds, -t) unlimited
file size (512-blocks, -f) unlimited
data seg size (kbytes, -d) 524288
stack size (kbytes, -s) 65536
core file size (512-blocks, -c) unlimited
max memory size (kbytes, -m) unlimited
locked memory (kbytes, -l) unlimited
max user processes (-u) 531
open files (-n) 1064
sbsize (bytes, -b) unlimited
$ ulimit -c 5000
$ ulimit -a
cpu time (seconds, -t) unlimited
file size (512-blocks, -f) unlimited
data seg size (kbytes, -d) 524288
stack size (kbytes, -s) 65536
core file size (512-blocks, -c) 5000
max memory size (kbytes, -m) unlimited
locked memory (kbytes, -l) unlimited
max user processes (-u) 531
open files (-n) 1064
sbsize (bytes, -b) unlimited
$ ulimit -c 60000
ulimit: ulimit: bad limit: Operation not permitted
$ ulimit -c 6000
ulimit: ulimit: bad limit: Operation not permitted
$
Has something changed, or has it been like this all along?
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
