On Tue, 3 Apr 2001, mike ledoux wrote:
> I'd take a guess that your system either doesn't support per-process
> limits as configured ...
I wasn't aware it was even an option not to. Do you happen to know what I
should check? Kernel config file? /proc/sys?
> ... or that your mozilla shell script is disabling them for you.
If I add the "-H" switch, it still happens, so that rules that out, no?
Um, now wait a minute. I do this:
ulimit -Hd 1000
ulimit -Hd 100
... and I get a "cannot raise limit" error from the second command. I know
it's late, but 100 < 1000, isn't it?
> What do you get if you try somtehing like:
>
> ulimit -d 1 -m 1
> vi
"Out of memory!Segmentation fault (core dumped)"
> FWIW, you don't really expect to run mozilla in less than 1M, do you?
'Course not. That was just an extreme case to demonstrate that something
was obviously wacked.
Originally, I had both set to 64M, but then a runaway Mozilla crashed my X
session. I started narrowing them down to see if something was funky, and lo
and behold, something was.
I need sleep. <thunk> Zzzzzzzzz....
--
Ben Scott <[EMAIL PROTECTED]>
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy of any other person, entity or |
| organization. All information is provided without warranty of any kind. |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
