Increasing "MEMORY" size in ulimit...

[Steven Schweda]

> [...[ if you applied the 'ulimit -m'
> command for 'unlimited' then you can see 16
> digit value by applying following command:
>
> #ulimit -H

No, not really.

urt# /usr/bin/ulimit -H
unlimited

urt# ulimit -H
unlimited

urt# ulimit -m unlimited

urt# ulimit -H
unlimited

urt# /usr/bin/ulimit -H
unlimited

urt# /usr/bin/ulimit -m unlimited

urt# ulimit -H
unlimited

urt# /usr/bin/ulimit -H
unlimited

I show how I get what I get. You never seem
to show how you get what you claim to get,
and I never seem to get what you claim to
get when I do what you say you do.

Actual commands and actual results are often
much more useful than vague descriptions of
commands and results. (They tend to reduce
wasted time and effort, too.)

[aique]

Well Steven what i think arguments never ends. But i only want to say that i was not kidding at all and on my machine These commands showed the same results as i showed to you people out there. And i have no intentions to waste any of yours time.

Anyhow my problem is solved so i am now going to close this thread.

Thanks for your compliments towards me :(

[Steven Schweda]

It might be nice if you posted a summary of
the solution you found, in case someone with
a similar problem seaches this forum and
finds this thread.

And if you ever figure out which "ulimit"
acts the way you say yours does...

[aique]

Well actually we only had to change 'datasize' and 'per_proc_address_space'. It worked and there was no need to change 'memory' size. According to HP experts, those 'Oracle Alerts' should be ignored which we did and installed Oracle successfully :)
But i still can't understand that why "#ulimit -m unlimited" command sets memory field to 16-digit figure for that terminal session.
Bye.

[Steven Schweda]

> But i still can't understand that why
> "#ulimit -m unlimited" command sets memory
> field to 16-digit figure for that terminal
> session.

And I can't understand why you won't say
which "ulimit" you are using, which makes it
hard to guess why you see what you see.

My latest guess is that it's the built-in in
/bin/sh, which does appear to act that way.
You should try a better shell. I seem to be
using GNU bash 2.05, and its built-in
"ulimit" has no such problems. The real
program, "/usr/bin/ulimit", as I've shown,
also has no such problems.

http://www.gnu.org/software/bash/bash.html

Apparently bash 3.1 is current. The command
line editing feature alone is worth the
effort.