Tru64 V4.0G unpatched
Is this a "feature", a bug or the way it is supposed to work?
My system parameter per-proc-data-size is 268435456 (256MB).
I have not set max-per-proc-data-size so it takes the
default of 1GB.
When a user logs in and examines his environment he sees:
$ ulimit -d
data(kbytes) 262144
as expected defaulting to 256MB.
If he then requests a bump to 500MB all is well:
$ ulimit -d 500000
$ ulimit -d
data(kbytes) 500000
BUT!!! If he now wants to increase again, he cannot:
$ ulimit -d 600000
ksh: ulimit: exceeds allowable limit
$ ulimit -d
data(kbytes) 500000
REMEMBER: the system paramter max-per-process-data-size
is set for 1073741824 or 1GB.
(For those gurus who recognize that ulimit is a shell
function in ksh, the same failure occurs if /usr/bin/ulimit
is invoked.)
AND!!! If he logins in again and tries, it succeeds:
$ ulimit -d 600000
$ ulimit -d
data(kbytes) 600000
It appears that once the data limit has been changed via
ulimit, that value becomes the "max-per-proc-data-size" for that
process regardless of the setting of the system parameter.
Am I missing something here???
--CHRis
Chris H. Ruhnke
Mid-Range Technical Services
IBM Global Services
St. Louis, MO
Office: (314) 233-7314
Pager: (800) 759-8888 PIN 8714690
O'Toole's Law: Murphy is an optimist.
Received on Thu Nov 30 2000 - 20:25:39 NZDT