"Why isn't the new ulimit setting being picked up? "
The new ulimit has been picked up. The coredump has changed from 0 to 4194304 which I suppose is the number that ulimit uses to mean unlimited. On the version of ulimit that I use it prints "unlimited" instead of the number.
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 3968
virtual memory (kbytes, -v) unlimited
"Isn't /etc/profile read when ksh is used?"
The ulimit command is actually part of the shell. That is why your ksh formats the output from the ulimit command differently than my bash does.
Last edited by jailbait; 02-10-2005 at 12:15 PM.